Commons:Administrators' noticeboard

Shortcut: COM:AN

• Community portal
  • introduction
• Help desk
• Village pump
  • copyright
  • proposals
  • technical
• Administrators' noticeboard
  • vandalism
  • user problems
  • blocks and protections

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
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	129, 128, 127, 126, 125, 124, 123, 122, 121, 120, 119, 118, 117, 116, 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	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	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

^{Translate this page}

Administrators: Please make a note if a report is dealt with, to avoid unnecessary responses by other admins.

purge Admin backlog

---

Copyright:

• Copyright violations: ~62
• Unfree Flickr files: ~0
• Recent unfree Flickr images: ~0
• No permission since 8 April 2026: ~23
• No source since 8 April 2026: ~3
• Media uploaded without a license as of 2026-04: ~216

Other:

• Duplicates: ~2
• Advertisements/spam: ~0
• Personal photos/selfies: ~29
• Other speedy deletions: ~23
• Categories for discussion: 134 months
• Media requiring a split up: ~1
• Requests for unblock: ~2
• Undeletion requests: ~11

Protected edit requests:

• Full protection: ~16
• Interface admin: ~11
• Technical: ~0
• Template protection: ~6
• Protection level: ~0

See also: DR, HMS, …

COMMONS DISCUSSION PAGES

• Commons Help desk
• Village pump (general discussion)
  • Copyright
  • Proposals
  • Technical
• Graphics and photography discussion
  • Photography critiques
  • Image improvement
    • Illustration workshop
    • Map workshop
    • Photography workshop
    • Video and sound workshop
• Categories for discussion
• Undeletion requests
• Deletion requests
• Volunteer Response Team/Noticeboard
• Translators' noticeboard
• Work requests for bots

---

• Contact administrators
  • Vandalism
  • User problems (Dispute resolution)
  • Blocks and protections
• Bureaucrats' noticeboard
• CheckUser requests
• Oversight requests

---

• Telegram
• IRC ^webchat
• Commons mailing list (archive)
• Commons' bugs on Phabricator

Note

• 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|thread=|reason=}} ~~~~ is available for this.
• Administrators: Please make a note if a report is dealt with, to avoid unnecessary responses by other admins.

Rename requests - target already exists

Hello everyone, per this discussion on COM:VPP Phabricator task T421373 is resolved by @Nemoralis and delete-redirect right has been granted to filemovers. Therefore I propose a minor change in {{Rename}}.
Currently if someone makes a rename request for a filename to move to one of its single revision redirects or any other exisiting name, the message reads

The specified target file exists. File movers will be unable to rename this file. An admin is required or choose another name. Use {{duplicate|(File name)}} if the file is exactly the same.

Now I don't think it can be automatically determined if the proposed name is indeed a single revision redirect. So we can just add a few words and it might be enough. Maybe something like

The specified target already exists. File movers will be unable to rename this file if the proposed name is not a single revision redirect. An admin is required in such a case or choose another name. Use {{duplicate|(File name)}} if the file is exactly the same.

This is my suggestion. Someone may choose better words. Its just that I feel the message needs to reflect the change that has happened. I think a lot of filemovers have no idea about this change bcoz they were never notified (atleast not me). I know bcoz I participated in that discussion. Maybe a mass message to every filemover notifying this change will also help. And also adding info about delete-redirect at COM:FM just like it has about suppressredirect. Shaan Sengupta^Talk 09:05, 9 April 2026 (UTC)

Alternate possible wording: "The specified target already exists. File movers will still be able to rename this file if the proposed name is a single-revision redirect, but otherwise this move will require an admin, or you can choose another name. Please use {{duplicate|(File name)}} if the target name already contains exactly the same file." Not sure if that's better, just laying out options. - Jmabel ! talk 20:28, 9 April 2026 (UTC)

@Jmabel, I tried not to add too many words as it would become lengthy. What about "The specified target already exists. File movers can rename this file only if the proposed name is a single-revision redirect; otherwise, this move will require an admin, or you can choose another name. Use {{duplicate|(File name)}} if both files are exactly the same." This has about 46 fewer characters than your suggested version and 6 more than my initial version. Shaan Sengupta^Talk 09:28, 10 April 2026 (UTC)

Fine with me. - Jmabel ! talk 23:09, 10 April 2026 (UTC)

Good. Then I would request you or anyone else interested to kindly do the needful. Thank you. Shaan Sengupta^Talk 01:11, 11 April 2026 (UTC)

Template:Rename/i18n brought in line. Obviously, translations will be needed. - Jmabel ! talk 05:01, 11 April 2026 (UTC)

@Jmabel, plz see this revision. This was done after you applied those changes. It still shows the same old wording to me. I even purged to force latest version. No change, maybe the same thing needs to be done somewhere else too. Shaan Sengupta^Talk 06:11, 11 April 2026 (UTC)

@Shaan Sengupta: If someone can tell me where to edit, I'll edit. Being an admin means I can edit, not that I understand every complex, semi-documented template on Commons. FWIW, Template:Rename/en, which I would have expected to edit, is just a redirect to Template:Rename/i18n. - Jmabel ! talk 16:34, 11 April 2026 (UTC)

@Jmabel, I tried but didn't succeed that time. Upon some more digging now, it looks like Template:Rename/layout is the one. Shaan Sengupta^Talk 17:21, 11 April 2026 (UTC)

Special:Diff/1195627456. Looks like that did it. - Jmabel ! talk 17:28, 11 April 2026 (UTC)

Maybe not. I'll leave three pings (with a sorry to bother) now. @Jeff G., @GPSLeo and @Krd, or anyone who can help. Shaan Sengupta^Talk 17:44, 11 April 2026 (UTC)

Rigging a deletion discussion

Fita-cola dos dois lados (talk · contributions · Statistics · Recent activity · block log · User rights log · uploads · Global account information) (assign permissions)
Deletion Delayer (talk · contributions · Statistics · Recent activity · block log · User rights log · uploads · Global account information) (assign permissions)
Commons:Deletion requests/File:Micro and nano view of gecko's toe.jpg is being compromised by a user who openly Revision #1195055007 brags about being a sockpuppet of Revision #1195055256 to manipulate discussions such as this. Borgenland (talk) 10:52, 11 April 2026 (UTC)

Borgenland, I have replaced the urls with {{Diff}} and mentioned the user names at the top to save the reviewing admin's time. I think both the accounts should be indeffed bcoz the person behind clearly thinks that it is completely ok to break the rules and openly brag about it. When I first saw Deletion Delayer openly naming Fita-cola dos dois lados on their userpage, I thought they might be doing it with an intent of framing Fcddl, but the DR comment (Revision #1195241727) made it easy as I hadn't check Global account info for other project status. ENWIKI has already confirmed these socks and indeffed DD. If it matters, I've blanked DD's userpage. Shaan Sengupta^Talk 11:09, 11 April 2026 (UTC)

 Done both accounts indeffed per report at COM:AN/B by Jmabel. Shaan Sengupta^Talk 17:28, 11 April 2026 (UTC)

IPBE for my bot account

Hi. Can my bot account be granted IPBE? It seems Flickr is blocking API calls from Toolforge cluster in the form of rate limiting and thus I'll have to run it on my server. Thanks!

• FlickrResourcesBot (talk · contributions · Statistics · Recent activity · block log · User rights log · uploads · Global account information) (assign permissions)

-- DaxServer (talk) 12:37, 11 April 2026 (UTC)

 Done It now has one. — regards, Revi 15:46, 11 April 2026 (UTC)

Hiding spam

I request these editions and the summary must be hidden because is a crosswiki spam for a YouTube video. Taichi (talk) 22:54, 12 April 2026 (UTC)

+1   — 🇺🇦Jeff G. ツ please ping or talk to me🇺🇦 23:14, 12 April 2026 (UTC)

 Done. I hided a lot of edits and semi-protected a lot of files. Taivo (talk) 17:27, 13 April 2026 (UTC)

Deletion request

I nominated several of my own uploads for deletion, as I uploaded them believing I had taken them ( I have been to these locations myself), and have since realized this was not the case. I would like them deleted whenever someone has the time. Kingsmasher678 (talk) 17:23, 15 April 2026 (UTC)

Could you explain further what happened here (how someone else's photos came into your possession and appeared to you to be your own)? - Jmabel ! talk 20:42, 15 April 2026 (UTC)

I am a caver and have been to the places the pictures were taken, and taken pictures in some of them. I just forgot which ones I took and which others took till I went back through and realized I was in one of them. I have already removed them from the pages they were present on and replaced them. Kingsmasher678 (talk) 21:15, 15 April 2026 (UTC)

@Kingsmasher678: I still don't get it. Did other people's pictures end up stored on your camera? On your computer? Or what? - Jmabel ! talk 05:07, 16 April 2026 (UTC)

Revision deletion request

Hello. I am requesting the revision deletion of the following versions of File:Department of Education.svg:

• 15:10, February 15, 2026 (UTC)
• 07:25, February 15, 2026 (UTC)
• 05:09, February 15, 2026 (UTC)

Reason: I misunderstood the SVG license of https://simplemaps.com/resources/svg-license, which is the source where I got an SVG map of the Philippines. I uploaded 3 revisions of the file before realizing that https://simplemaps.com doesn't allow redistribution of the SVG code without permission.

Thanks. Ethan8192 (talk) 20:38, 15 April 2026 (UTC)

 Done - Jmabel ! talk 20:46, 15 April 2026 (UTC)

Tricky rollback situation

When a user spams talk pages without signing, SignBot comes by in their wake and adds a pseudo-signature. This makes it very hard to do a rollback by any method I know. Is there a way to deal with that? (This is with reference to the recently blocked SaltyAFcsar1, but the modus operandi is one I've seen quite a bit lately.) - Jmabel ! talk 05:38, 16 April 2026 (UTC)

This user you mentioned has posted a youtube link in my talkpage, I don't understand. Tisha Mukherjee (talk) 08:01, 16 April 2026 (UTC)

@Tisha Mukherjee: Hi, and welcome. That was spam. The mentioned user spammed 70 times before being blocked. This section is about dealing with the spam efficiently and effectively.   — 🇺🇦Jeff G. ツ please ping or talk to me🇺🇦 09:05, 16 April 2026 (UTC)

@Jmabel: After reading the offending edit and the SignBot edit, my go-to link has been the "restore" link near the end of the lineitem for the last good revision on that page on that page's history. If that link doesn't appear, I edit that last good revision, ignore the warning, and save anyway. Complicating matters is the fact that the offending video's ID shows up in (apparently cached) regular search results on page Template:Nationaal Archief/ru, where that ID was removed back on 11 March. For Special:Diff/1198324088, when restore would have produced poor results, I used "undo" on the two edits together.   — 🇺🇦Jeff G. ツ please ping or talk to me🇺🇦 08:59, 16 April 2026 (UTC)