Commons:Administrators' noticeboard/Blocks and protections
Shortcuts: COM:AN/B • COM:AN/P • COM:RFPP
This is a place where users can communicate with administrators, or administrators with one another. You can report vandalism, problematic users, or anything else that needs an administrator's intervention. Do not report child pornography or other potentially illegal content here; e-mail legal-reportswikimedia.org instead. If reporting threatened harm to self or others also email emergencywikimedia.org. | |||
---|---|---|---|
Vandalism [ ] |
User problems [ ] |
Blocks and protections [ ] |
Other [ ] |
Report users for clear cases of vandalism. Block requests for any other reason should be reported to the blocks and protections noticeboard.
|
Report disputes with users that require administrator assistance. Further steps are listed at resolve disputes.
|
Reports that do not suit the vandalism noticeboard may be reported here. Requests for page protection/unprotection could also be requested here.
|
Other reports that require administrator assistance which do not fit in any of the previous three noticeboards may be reported here. Requests for history merging or splitting should be filed at COM:HMS. |
Archives | |||
115, 114, 113, 112, 111, 110, 109, 108, 107, 106, 105, 104, 103, 102, 101, 100, 99, 98, 97, 96, 95, 94, 93, 92, 91, 90, 89, 88, 87, 86, 85, 84, 83, 82, 81, 80, 79, 78, 77, 76, 75, 74, 73, 72, 71, 70, 69, 68, 67, 66, 65, 64, 63, 62, 61, 60, 59, 58, 57, 56, 55, 54, 53, 52, 51, 50, 49, 48, 47, 46, 45, 44, 43, 42, 41, 40, 39, 38, 37, 36, 35, 34, 33, 32, 31, 30, 29, 28, 27, 26, 25, 24, 23, 22, 21, 20, 19, 18, 17, 16, 15, 14, 13, 12, 11, 10, 9, 8, 7, 6, 5, 4, 3, 2, 1 |
96, 95, 94, 93, 92, 91, 90, 89, 88, 87, 86, 85, 84, 83, 82, 81, 80, 79, 78, 77, 76, 75, 74, 73, 72, 71, 70, 69, 68, 67, 66, 65, 64, 63, 62, 61, 60, 59, 58, 57, 56, 55, 54, 53, 52, 51, 50, 49, 48, 47, 46, 45, 44, 43, 42, 41, 40, 39, 38, 37, 36, 35, 34, 33, 32, 31, 30, 29, 28, 27, 26, 25, 24, 23, 22, 21, 20, 19, 18, 17, 16, 15, 14, 13, 12, 11, 10, 9, 8, 7, 6, 5, 4, 3, 2, 1
| ||
Note
- For page protection requests, please state protection type, file name, and proposed protection time span. See also: Protection Policy.
- Before proposing a user be blocked, please familiarize yourself with the Commons' Blocking Policy.
- Remember to sign and date all comments using four tildes (
~~~~
), which translates into a signature and a time stamp. - Notify the user(s) concerned via their user talk page(s).
{{subst:Discussion-notice|noticeboard=COM:AN/B|thread=|reason=}}
is available for this. - Administrators: Please make a note if a report is dealt with, to avoid unnecessary responses by other admins.
Request to protect Historical flags
The Historical flags has been vandalized by a IP user named "173.215.96.214" repeatedly, and I'm sick of having to revert this nonsense. I believe the pages need semi-protection and for all of 173.215.96.214's edits to be reverted. Wheatley2 (talk) 17:23, 12 August 2024 (UTC)
- Done Semi-protected. Honey pot for vandals. Yann (talk) 18:55, 13 August 2024 (UTC)
Cyber.Eyes.2005
- User: Cyber.Eyes.2005 (talk · contributions · Move log · block log · uploads · Abuse filter log)
- Reasons for reporting: Sockmaster banned on enwiki, made this edit. See also en:Wikipedia:Sockpuppet investigations/Cyber.Eyes.2005 and archive. Once a sockmaster... — 🇺🇦Jeff G. ツ please ping or talk to me🇺🇦 15:39, 13 August 2024 (UTC)
They posted the below comment on Simple English Wikipedia and asked me to move it over:
No comment on any of this myself. Just passing it on. The Squirrel Conspiracy (talk) 16:54, 13 August 2024 (UTC)
- I once blocked @Cyber.Eyes.2005 on Urdu-Wikipedia exactly for the same reason but it seems they have learned their lesson and are contributing constructively. I'd suggest no action, unless they engage in anything problematic. They ain't socking anymore, unless you'd want to waste a CU's time again. Regards, Aafi (talk) 17:52, 13 August 2024 (UTC)
Assalam 0202
- Assalam 0202 (talk · contributions · Statistics · Recent activity · block log · User rights log · uploads · Global account information)
Account created to vandalize. Four edits, all disruptive and reverted -- Basile Morin (talk) 02:17, 14 August 2024 (UTC)
- Not done All edits on 26 May 2021. Stale. The Squirrel Conspiracy (talk) 02:38, 14 August 2024 (UTC)
- Question @The Squirrel Conspiracy: So these vandals noticed too late should not be reported here?
- No warning, nothing to prevent a recurrence? -- Basile Morin (talk) 03:04, 14 August 2024 (UTC)
- What do you want us to do? Counter-vandalism archaeology? The account last edited over three years ago. There's nothing to be done now. Bedivere (talk) 04:00, 14 August 2024 (UTC)
Warned with {{Test2}}.
- The edits have just been reverted today. I find useful to warn the user, so that when he / she reiterates, the block will be easier. In 2024, 2025, or later. Read that on Commons:Blocking policy#Before blocking.
- For information, if you suggest to the lambda users like me not to report, we will just stop using this section next time the vandal operates.
- The "archaeology" analogy was not so educative, in my opinion an appropriate and rational explanation would have been useful.
- Bye -- Basile Morin (talk) 04:45, 14 August 2024 (UTC)
- Per Commons:Blocking policy, blocks are preventative and not punitive. The account that hasn't edited in three years isn't likely to edit again. Why should we block? —Matrix(!) {user - talk? -
uselesscontributions} 05:55, 14 August 2024 (UTC)- @Matrix: , thanks for your (polite) response. Interesting point of view. Two questions :
- After 100% disruption / vandalism in 4 edits, do you think this user is likely to edit constructively later? Is it a good start here? Why don't you block him / her immediately, so we are safe for the future? And if the behavior changes, then a new start will be possible (AND better).
- Why has this vandal not been caught earlier? It appears (from today only, just by chance) that the authorship of the images has been diverted during 3 years. Nobody noticed, no user, no admin. Why not reported here or elsewhere? Is counter-vandalism working or are we discouraged to report them in anyway? -- Basile Morin (talk) 06:30, 14 August 2024 (UTC)
- There have been cases where vandals have a few years later made constructive edits. Blocking them a few years after they vandalised is simply unnecessary, since blocks are preventative and not punitive. There's also the additional complication the user wasn't warned the first time.
- Sometimes subtle vandalism goes unnoticed. It just happens sometimes. I remember reverting some vandalism at File:Edgar Allan Poe Signature.svg from 2015 in 2022! In this case, just revert, warn and move on. Of course, if it is happening recently, then report here.
- —Matrix(!) {user - talk? -
uselesscontributions} 09:05, 14 August 2024 (UTC)
- Per Commons:Blocking policy, blocks are preventative and not punitive. The account that hasn't edited in three years isn't likely to edit again. Why should we block? —Matrix(!) {user - talk? -
Not sure if any uploads of the account survive reviews. Enhancing999 (talk) 14:36, 14 August 2024 (UTC)
- Some are clearly PD (though falsely claimed as "own work"). - Jmabel ! talk 19:35, 14 August 2024 (UTC)
- Looks to me like uploads include a fair amount of valid PD content, misdescribed and mis-licensed. - Jmabel ! talk 19:50, 14 August 2024 (UTC)
- @Krd: seems to have nuked much of it. Haven't seen any PD stuff. Enhancing999 (talk) 20:14, 14 August 2024 (UTC)
Bruno pnm ars
- User: Bruno pnm ars (talk · contributions · Move log · block log · uploads · Abuse filter log)
- Reasons for reporting: For years, I have been railing against incomplete deletion requests, which are caused by malformed use of {{Delete}} templates and lack of follow-through, and which are populating subcats of Category:Incomplete deletion requests. This problem spurred the creation of that category 17:57, 1 February 2007 (UTC), over 17 years ago, and my tracking of it 18:16, 14 November 2020 (UTC), over three years ago. As a precedent, ColorfulSmoke was blocked 17:07, 29 December 2020 (UTC) by Mdaniels5757 with an expiration time of 3 days (account creation blocked) for "Continuing to make malformed deletion requests despite repeated instructions; not responding to concerns on talk page", pursuant to the discussion archived at Commons:Administrators' noticeboard/Blocks and protections/Archive 29#ColorfulSmoke, and Alex Neman was blocked 16:30, 27 January 2023 (UTC) by Yann with an expiration time of 1 month (account creation blocked) for "Continuing to make malformed deletion requests despite repeated instructions; not responding to concerns on talk page" pursuant to the discussion archived at Commons:Administrators' noticeboard/Blocks and protections/Archive 34#Alex Neman. Bruno pnm ars made this edit 9 August 2024 (UTC): including a {{Delete}} tag as the reason. I reminded them of their mistake and warned them in this edit 12:36, 9 August 2024 (UTC). They neglected to respond per User talk:Bruno pnm ars#File:Cover of Massafghanistan by Kid Yugi.jpg, and made such an edit again in these edits 07:53, 14 August 2024 (UTC): again including a live {{Delete}} tag in the reason and compounding their error by including a live {{Dw no source since}} tag in the reason. Please block them. — 🇺🇦Jeff G. ツ please ping or talk to me🇺🇦 14:48, 14 August 2024 (UTC)
- At least from filespace. — 🇺🇦Jeff G. ツ please ping or talk to me🇺🇦 11:07, 18 August 2024 (UTC)
User:اضاف
This user has been warned several times for copyright violations and has been blocked in the recent past for it too. Now that their block has expired, they appear to be re-uploading the deleted copyright violations and sourcing them to newly uploaded Flickr files (Commons:License laundering). I've marked a couple files for speedy deletion, but maybe an admin can have a look at the others. Thank you. Marbletan (talk) 19:32, 14 August 2024 (UTC)
- Done Blocked indef. License washing is a no-no. All copyvios deleted. Yann (talk) 20:19, 14 August 2024 (UTC)
User:Oslo73729
- Oslo73729 (talk · contributions · Statistics · Recent activity · block log · User rights log · uploads · Global account information)
LTA of Malttew9983, again uploading political symbols or flag of Panamanian political parties. Taichi (talk) 06:17, 15 August 2024 (UTC)
- Done Blocked, all files deleted. Yann (talk) 07:17, 15 August 2024 (UTC)
User:Aomseen
Please consider blocking Aomseen (talk · contributions · Statistics · Recent activity · block log · User rights log · uploads · Global account information) for being Category:Sockpuppets of Aommyabrina. Thank you so much. 🙏 -- Librovore (talk) 15:49, 15 August 2024 (UTC)
- Done Blocked, file deleted. Yann (talk) 17:56, 15 August 2024 (UTC)
User:Redlines777
- Redlines777 (talk · contributions · Statistics · Recent activity · block log · User rights log · uploads · Global account information)
Obvious sock of User:Anonymous91111111, reuploading the same copyvio images. - MrOllie (talk) 23:10, 15 August 2024 (UTC)
- Done Blocked by DMacks. Yann (talk) 09:06, 16 August 2024 (UTC)
User talk:Prismatech
User talk:Prismatech advertisement despite warnings modern_primat ඞඞඞ ----TALK 13:59, 17 August 2024 (UTC)
- Done Blocked, files already deleted. Yann (talk) 16:03, 17 August 2024 (UTC)
Dennis Takalao
- Dennis Takalao (talk · contributions · Statistics · Recent activity · block log · User rights log · uploads · Global account information)
Please consider blocking this user. They obviously don't understand copyright. Cryptic-waveform (talk) 16:01, 17 August 2024 (UTC)
- Done Blocked for a week, all copyvios deleted. Yann (talk) 16:06, 17 August 2024 (UTC)
"Erect penis.jpg" "Erect penis 3.jpg"
File:Erect penis.jpg File:Erect penis 3.jpg Please lock forever to level "recreate: sysop only". Reuploaded too many times. Taylor 49 (talk) 22:19, 18 August 2024 (UTC)
Can any admin delete and protect this filename from reupload since it's repeatdly been reuploaded by different users, presumably sockpuppets or meatpuppets. Jonteemil (talk) 02:43, 19 August 2024 (UTC)
- Done Deleted the file. Watchlisted the file name. The sockmaster is going to keep trying no matter what we do, so we might as well leave the name open so the new uploads are easier to find.