Commons:Administrators' noticeboard/Blocks and protections

Shortcuts: COM:AN/B • COM:AN/P • COM:RFPP

• 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
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	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	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	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: ~9
• Unfree Flickr files: ~0
• Recent unfree Flickr images: ~37
• Media uploaded without a license as of 2025-11: ~138

Other:

• Duplicates: ~119
• Advertisements/spam: ~0
• Personal photos/selfies: ~10
• Other speedy deletions: ~11
• Categories for discussion: 84 months
• Media requiring a split up: ~0
• Requests for unblock: ~4
• Undeletion requests: ~14

Protected edit requests:

• Full protection: ~37
• Interface admin: ~12
• 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

• 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.

File:Standing sexual intercourse.webm

Needs indefinite protection against IP/new account editing due to constant addition of needlessly pornographic text in the description Dronebogus (talk) 08:53, 23 November 2025 (UTC)

 Done --Yann (talk) 08:58, 23 November 2025 (UTC)

Isn't the timed text equally a problem? That also reads as rather pornographic to me. - Jmabel ! talk 18:28, 23 November 2025 (UTC)

@Jmabel: I reverted to a better description —Matrix(!) _{ping one}^{when replying} {user - talk? - _uselesscontributions} 21:30, 25 November 2025 (UTC)

Socks of Jagdeep singh bittu

• Diljit46 (talk · contributions · Move log · block log · uploads · Abuse filter log) block user
• Ranjity (talk · contributions · Move log · block log · uploads · Abuse filter log) block user
• Yamanjit2 (talk · contributions · Move log · block log · uploads · Abuse filter log) block user

Sockpuppets of Jagdeep singh bittu, as per investigation at en:Wikipedia:Sockpuppet investigations/Deepcruze. 0x0a (talk) 07:30, 24 November 2025 (UTC)

Accounts blocked. Not saying "done" because further action may be needed, I'm not familiar enough with what the issues are likely to be on this particular user. - Jmabel ! talk 19:10, 24 November 2025 (UTC)

Often the issues here are they upload images from Youtube videos that are not tagged with a compatible license, or images that they find online about celebrities that they claim are their own work and pretty obviously are not. They do upload images that appear to be valid (meta data from a mobile device). The unabashed nature of the bad faith uploads tends to make me suspicious of almost everything they upload though. Ravensfire (talk) 22:48, 24 November 2025 (UTC)

Inappropriate username

• Scoobyjew911 (talk · contributions · Move log · block log · uploads · Abuse filter log) block user

Presumably intended as a reference to en:9/11 conspiracy theories#Israel. Belbury (talk) 12:46, 25 November 2025 (UTC)

User:Oil-Neuro280737

User: Oil-Neuro280737 (talk · contributions · Move log · block log · uploads · Abuse filter log) block user

Reason for reporting: Apparently a sockpuppet (Category:Sockpuppets of Saranphat chaiphet) created for block evasion, because (1) the user uploaded copyvio files related to Nan province, which are exactly the same files as those uploaded by the socks in the mentioned category, and (2) the username is similar to those in the mentioned category, such as Oil-Neuro1994 (talk · contribs), Max-Oil2024 (talk · contribs), PickOil281994 (talk · contribs), etc, which indicates their relationship.

-- Miwako Sato (talk) 02:40, 27 November 2025 (UTC)

 Done indef-blocked. - Jmabel ! talk 05:29, 27 November 2025 (UTC)

File:Forms of government.svg

Set the file to allow autoconfirmed users to overwrite for 24 hours. This is for me to upload a new version of the file to indicate a change in the form of government of Guinea-Bissau due to a coup d'état. KPOfficial26 (talk) 11:46, 28 November 2025 (UTC)

@KPOfficial26: that is exactly the setting it has had for some time: autoconfirmed users. (There is higher protection for moving the file, but presumably you don't need to do that.) Are you having trouble uploading? - Jmabel ! talk 18:44, 28 November 2025 (UTC)

It says I have autoconfirmed protections but that I cannot be able to overwrite the file. KPOfficial26 (talk) 18:54, 28 November 2025 (UTC)

@KPOfficial26: Do you have a "Upload a new version of this file" link above "File usage on Commons"?   — 🇺🇦Jeff G. ツ please ping or talk to me🇺🇦 20:09, 28 November 2025 (UTC)

The text does not say that, it instead says "You cannot overwrite this file." KPOfficial26 (talk) 20:20, 28 November 2025 (UTC)

@Jmabel: the file has Upload Protection of autopatroller. The Allow Overwriting template is there, but autoconfirmed users cannot upload a new file because of the upload protection. Abzeronow (talk) 23:36, 28 November 2025 (UTC)

Oops, I didn't notice that. I'll lower that upload protection.

@KPOfficial26: when you are done, can you please notify back here, so someone can revert that protection as soon as possible? Thanks. - Jmabel ! talk 23:59, 28 November 2025 (UTC)

I attempted to upload the new version, but when I clicked submit, it said that the filename is currently protected from re-uploading and can be used solely by administrators. I don't know how to get through this, especially since the protection settings are temporarily lowered for now. KPOfficial26 (talk) 00:10, 29 November 2025 (UTC)

@KPOfficial26: It looks to me like at 03:35, 29 November 2025 (UTC) you uploaded successfully, and the result also looks correct to me, so I will restore the higher level of protection. - Jmabel ! talk 06:42, 29 November 2025 (UTC)

User:Fabe56

service links, GD Fabe56 (talk · contributions · Move log · block log · uploads · Abuse filter log) block user Hundreds of uploads are identified as copyright violation. See User talk:Fabe56/Archive/2025 ~2025-36998-15 (talk) 07:15, 29 November 2025 (UTC)

Yes, Fabe56 did indeed load hundreds of copyvios into Commons (and also a lot of files of dubious educational usability and surely even more with unsuitable filenames which make them hard to find. This is the most recent example from yesterday: File:Fish？ (1720158053).jpg - no meaningful name, sub-par quality and thus out of scope. But to put this criticism into relation with the total work: the XTools tell me the following numbers for Commons: live edits number 330,485 (96% of total) and deleted edits 13,733 (4% of total). Four percent deleted edits is not a large part.

That said, I would like them to curate their Flickr imports much more thoroughly, even if that would definitively entail to not reach such high scores of uploads anymore. In fact, I asked them previously exactly that: User talk:Fabe56/Archive/2025#Apparent laziness while importing from Flickr. I would support and perhaps even wish for administrative actions to enforce such a behavioural change. That could take the guise of a prohibition to use the Flickr importer or a selective upload blocking until 250 or 500 or 1000 or whatever number is deemed suitable images from the past upload batches are fully curated (including: copyright checks, Commons scope checks, quality checks, file names, descriptions, categories). Afterwards, only X new files (50? 100?) are permissible to get imported, then another curating batch could be mandatory. Regards, Grand-Duc (talk) 08:33, 29 November 2025 (UTC)

Yes, good suggestion. Fabe56 was not informed of this discussion. I did it now. Yann (talk) 08:39, 29 November 2025 (UTC)