Wikimedia Commons

Commons:Administrators' noticeboard/Blocks and protections

< Commons:Administrators' noticeboard

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-reports@wikimedia.org instead. If reporting threatened harm to self or others also email emergency@wikimedia.org.

Vandalism
[new section]		 User problems
[new section]		 Blocks and protections
[new section]		 Other
[new section]

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
21, 20, 19, 18, 17, 16, 15, 14, 13, 12, 11, 10, 9, 8, 7, 6, 5, 4, 3, 2, 1
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
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
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
COMMONS DISCUSSION PAGES (index)

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.


Unprotect Template:YouTube CC-BY/i18n

This template now uses the Translate extension, which means that any changes to the /i18n page only go live once a translation administrator accepts them. I think we can trust translation administrators that they won’t accept vandalism or legally incorrect edits. Could someone please remove the page protection so that anyone can propose changes by directly editing the page? Thanks in advance! (Note that Template:YouTube CC-BY is not protected by the Translate extension, so that should remain protected.) —Tacsipacsi (talk) 10:35, 1 November 2023 (UTC)Reply[reply]

Still. —Tacsipacsi (talk) 20:17, 8 November 2023 (UTC)Reply[reply]
Is there really no admin who could fulfill or decline this request in two weeks? I put here a timestamp from the far future; feel free to remove it once it has been handled, but not before. —Tacsipacsi (talk) 22:29, 14 November 2023 (UTC)Reply[reply]
  Not done: This could result in page history getting polluted by vandals. And the template will hardly need any editing, see history, talk page, only translation edit requests. This system would be okay in case minor changes but if someone makes a trival change, how will translation admins handle it? They will have to move to talk page to discuss it with others, puts unnecessary work and confusion on tadmins. Therefore the change should be discussed on talk first, will be implemented by template editor or admin only after consensus. -- CptViraj (talk) 04:57, 15 November 2023 (UTC)Reply[reply]

This could result in page history getting polluted by vandals.

And so what? The point of the wiki method is that it’s okay for the page history to get polluted by vandals if it also allows constructive edits to go through more quickly and easily.

And the template will hardly need any editing, see history, talk page, only translation edit requests.

The page history doesn’t mean much: it not being edited can also be because no one bothers with doing or fulfilling edit requests. For the talk page, the real one is at Template talk:YouTube CC-BY, which contains at least one topic that waits for someone to draft a change. Also, “hardly any” editing is more than what’s currently possible for regular users.

This system would be okay in case minor changes but if someone makes a trival change, how will translation admins handle it? They will have to move to talk page to discuss it with others, puts unnecessary work and confusion on tadmins. Therefore the change should be discussed on talk first, will be implemented by template editor or admin only after consensus.

Worst case, the edit needs to be reverted and brought up on the talk page. Even in this worst case, there is a concrete diff to be discussed rather than just some description of what one would like to see. Protection is appropriate in two cases:
  • If vandalism would become immediately very highly visible (main page, parts of templates used all over the place that directly affect the English-language output). Thanks to the Translate extension, this isn’t the case here.
  • To stop actual, demonstrable vandalism, using the lowest protection level that is enough to stop the vandalism. Since this template has been fully/template-protected since 2016, no vandalism can be demonstrated and thus we should assume good faith, i.e. that people won’t vandalize it.
Tacsipacsi (talk) 00:31, 16 November 2023 (UTC)Reply[reply]
With respect, I disagree. We have template sandboxes for experiments, one can propose changes by linking to it, main template pages shouldn't be edited directly. Here, the page will have to be marked for translation everytime, even after reverting vandal edits. And it's not a job of translation administrators to decide what should be on a template, they work on making a template translatable, like putting translation tags, tweaking, etc... -- CptViraj (talk) 07:29, 16 November 2023 (UTC)Reply[reply]
Unprotecting the page doesn’t mean that any changes should be done directly there – they can, for example minor and uncontroversial ones. And if a translation admin is uncomfortable accepting the change, they don’t have to (or can decide to revert it, asking the user to discuss on the talk page). —Tacsipacsi (talk) 10:46, 18 November 2023 (UTC)Reply[reply]
Again, that's not a job of tadmins, their job is to prepare/maintain translation side, decide on translation tags, system, etc... If we start implementing this system on every translatable template, we'll see them popping up on Special:PageTranslation for every edit, even rollbacks, and tadmins will simply be overburden. -- CptViraj (talk) 18:34, 19 November 2023 (UTC)Reply[reply]
If we start implementing this system on every translatable template – it is implemented on most translatable templates. As the default is (and should be) that pages are not protected, most translatable templates are not protected either. To be exact, out of the 628 translatable templates, only 51 (or 8%) are indefinitely protected at any level. 21 of these protections are semi-protections, and only the other 30 (or 5%) are template editor protections (there are no fully protected translatable templates). While I don’t think any protection is necessary – as the wiki principle is that it should be easy to fix mistakes, not hard to commit them –, changing the protection to semi would be an acceptable compromise for me. —Tacsipacsi (talk) 10:39, 21 November 2023 (UTC)Reply[reply]
Thank you for the list, as you can see, the unprotected ones are lower-transclusion templates, while those with medium number of transclusions are semi-protected, and those with higher transclusions like this one are template-protected. The wiki principal has exceptions, otherwise we wouldn't have protections in the first place. Here, the main thing is we have template sandboxes, talkpages, etc for proposing changes, you just don't edit a highly transcluded page directly for proposing changes, and as I said above, if we allow that, the authority will shift towards tadmins in these translatable templates, which is fundamentally wrong. I understand your position, and I know I might be sounding bureaucratic here, but trust me, I'm not bolstering up any bureaucracy, I'm just standing with the already running practices and what I believe is beneficial. You are free to ask any other admin(s) to decide if you want, but count me in oppose for unprotection and neutral (compromised) on downgrading. -- CptViraj (talk) 17:34, 21 November 2023 (UTC)Reply[reply]

Kukurydziarz

A1Cafel (talk) 16:34, 18 November 2023 (UTC)Reply[reply]

I feel like I'd want a bit more confidence before blocking someone on the basis that they're blocked for "possible block evasion". @A1Cafel: I'd suggest you open up a request for checkuser that explains your case for why the two accounts are socks for one another, and gives evidence that the use of multiple accounts in the way that they did actually violates Commons' relevant policy. — Red-tailed hawk (nest) 05:07, 19 November 2023 (UTC)Reply[reply]
  Done by Elcobbola per results of the related checkuser investigation. — Red-tailed hawk (nest) 02:00, 21 November 2023 (UTC)Reply[reply]

User:Jeepyear

I've been observing this user all morning. They're clearly another sock of Jurisdrew as per the duck test. They've uploaded a few historical revisions of SVG flag images. The harrassment on my talk page also shows that they have a previous grudge against myself despite having no previous interactions with this account, due to my involvement in initiating a checkuser request on 4 other sock accounts of Jurisdrew and nominating their files for deletion. I don't think another checkuser is required here. Fry1989 eh? 17:26, 18 November 2023 (UTC)Reply[reply]

@Fry1989   Done. Please remember to notify subjects of posts here; you can use {{subst:Discussion-notice|noticeboard=COM:AN/B|thread=|reason=}} for this. —‍Mdaniels5757 (talk • contribs) 17:39, 18 November 2023 (UTC)Reply[reply]
My presumption was that with this being such a very obvious sock, it would not be neccessary as there is no real defence the user can provide. I'll be sure to do so in the future though. Fry1989 eh? 18:12, 18 November 2023 (UTC)Reply[reply]
@Fry1989:   Globally locked as an LTA.   — 🇺🇦Jeff G. ツ please ping or talk to me🇺🇦 09:08, 22 November 2023 (UTC)Reply[reply]

2600:387::/44

  — 🇺🇦Jeff G. ツ please ping or talk to me🇺🇦 10:17, 20 November 2023 (UTC)Reply[reply]

  Done Blocked for 3 years. The block history is a novel here... Yann (talk) 10:43, 20 November 2023 (UTC)Reply[reply]

User:Angel Keleyan

Angel Keleyan (talk · contributions · Move log · block log · uploads · Abuse filter log) 

Continue to upload copyvio images after warnings. 0x0a (talk) 13:08, 20 November 2023 (UTC)Reply[reply]

  Done Blocked for a week, and Commons:Deletion requests/Files uploaded by Angel Keleyan. Yann (talk) 13:50, 20 November 2023 (UTC)Reply[reply]

User:Alwataralwatar30

Alwataralwatar30 (talk · contributions · Move log · block log · uploads · Abuse filter log) 

Continue to upload copyrighted Internet images and claim them as own works. 0x0a (talk) 18:24, 20 November 2023 (UTC)Reply[reply]

  Done Blocked for a week, all obvious copyvios deleted. Remaining files need to be checked. Yann (talk) 19:14, 20 November 2023 (UTC)Reply[reply]

User:Conkoskip

Despite being warned several times, the user attempts to bypass rules through license laundering, adding bogus license reviews (see abuse filter log), and adding false information (diff). The user repeatedly also only uploads the same images. nicolas talkpage★★★ 19:21, 20 November 2023 (UTC)Reply[reply]

  Done Blocked for a week. All files deleted. License laundering is a NO-NO. Yann (talk) 19:29, 20 November 2023 (UTC)Reply[reply]

Ashvin29

Ashvin29 (talk · contribs) has continued to upload non-free images, mainly movie posters, despite warnings. They asked about this on my user talk page and I pointed them to uploading them on EN as non-free files, but they've continued to upload basically the same file multiple times since. Ravensfire (talk) 14:44, 21 November 2023 (UTC)Reply[reply]

  Done Blocked for a week, and Commons:Deletion requests/Files uploaded by Ashvin29. Other files uploaded by this user are also suspicious: he claims to have 3 high-end cameras within 4 different pictures. However I couldn't find copy elsewhere. Yann (talk) 16:39, 21 November 2023 (UTC)Reply[reply]

File:Острог Љиљана Петровић 20 07 2021.jpg

Please undo, protect and redact: [1]. --Matěj Suchánek (talk) 14:54, 21 November 2023 (UTC)Reply[reply]

  Done by Achim. Taivo (talk) 10:48, 22 November 2023 (UTC)Reply[reply]

User:Baildan

Another apparent sockpuppet of Jurisdrew, per the duck test. Newly created account uploading historical revisions of various flags. Fry1989 eh? 15:54, 21 November 2023 (UTC)Reply[reply]

  Done Blocked. All files already nominated. Yann (talk) 16:19, 21 November 2023 (UTC)Reply[reply]
@Fry1989:   Globally reported as an LTA.   — 🇺🇦Jeff G. ツ please ping or talk to me🇺🇦 09:09, 22 November 2023 (UTC)Reply[reply]

File:Licensing tutorial hi.svg

Please unprotect it for a while; I'd like to reupload it with some translation fixes. ~ Saur (talk • contribs) 03:37, 22 November 2023 (UTC)Reply[reply]

@Saurmandal You should have reupload permissions now; please ping me when you are done so I can reprotect the file. —‍Mdaniels5757 (talk • contribs) 19:44, 22 November 2023 (UTC)Reply[reply]
@Mdaniels5757: Done, thank you! ~ Saur (talk • contribs) 10:38, 23 November 2023 (UTC)Reply[reply]
  Done reprotected. You're welcome! —‍Mdaniels5757 (talk • contribs) 19:41, 23 November 2023 (UTC)Reply[reply]

One 7 Graphics

  — 🇺🇦Jeff G. ツ please ping or talk to me🇺🇦 08:49, 22 November 2023 (UTC)Reply[reply]

  Blocked. -- CptViraj (talk) 08:59, 22 November 2023 (UTC)Reply[reply]
@CptViraj: Thanks!   — 🇺🇦Jeff G. ツ please ping or talk to me🇺🇦 09:00, 22 November 2023 (UTC)Reply[reply]

User:Top Rent A Car

Top Rent A Car (talk · contribs · deleted contribs · logs · edit filter log · block user · block log)

The account was likely created for advertisement or promotion, and the username indicates that the account represents a group or company. -- Doclys👨‍⚕️👩‍⚕️ 🩺 • 💉 15:31, 22 November 2023 (UTC)Reply[reply]

  Done —‍Mdaniels5757 (talk • contribs) 19:46, 22 November 2023 (UTC)Reply[reply]

Shoot for the Stars

  — 🇺🇦Jeff G. ツ please ping or talk to me🇺🇦 22:31, 22 November 2023 (UTC)Reply[reply]

  Comment No edits since 23 October Gbawden (talk) 07:00, 23 November 2023 (UTC)Reply[reply]
@Gbawden: I'm sorry I didn't notice sooner.   — 🇺🇦Jeff G. ツ please ping or talk to me🇺🇦 15:12, 23 November 2023 (UTC)Reply[reply]
  Not done currently block is not needed. Taivo (talk) 10:39, 24 November 2023 (UTC)Reply[reply]

File:Twórca Koluchstyl.jpg

Please revert, protect and revdel: [2]. --Matěj Suchánek (talk) 11:25, 23 November 2023 (UTC)Reply[reply]

@Matěj Suchánek: I tagged File:Twórca Koluchstyl.jpg as a copyvio. Please use internal links. Admins: This file is being vandalized by IP socks of a globally banned LTA.   — 🇺🇦Jeff G. ツ please ping or talk to me🇺🇦 14:33, 23 November 2023 (UTC)Reply[reply]
@Achim55: Which globally banned LTA was using 93.140.192.121 (talk · contributions · Move log · block log · uploads · Abuse filter log) ?   — 🇺🇦Jeff G. ツ please ping or talk to me🇺🇦 22:08, 23 November 2023 (UTC)Reply[reply]
GRP/Projects/LS. He always uses VPN. --Achim55 (talk) 08:51, 24 November 2023 (UTC)Reply[reply]

Penile subincision

Penile subincision (talk · contributions · Move log · block log · uploads · Abuse filter log)  seems to be the new account for Mennessano (talk · contributions · Move log · block log · uploads · Abuse filter log) . Commons:Deletion requests/Files uploaded by Penile subincision QTHCCAN (talk) 14:22, 23 November 2023 (UTC)Reply[reply]

@QTHCCAN: I notified the users of this discussion on their user talk pages, as you should have done per the above.   — 🇺🇦Jeff G. ツ please ping or talk to me🇺🇦 15:17, 23 November 2023 (UTC)Reply[reply]
  Done Blocked, all files deleted. Yann (talk) 16:16, 23 November 2023 (UTC)Reply[reply]
@Yann: ... and Mennessano (talk · contributions · Move log · block log · uploads · Abuse filter log) ?   — 🇺🇦Jeff G. ツ please ping or talk to me🇺🇦 20:08, 23 November 2023 (UTC)Reply[reply]
  Done Blocked, all files deleted. Yann (talk) 21:48, 23 November 2023 (UTC)Reply[reply]

User:遠藤進之助

This user uploaded copyvio images repeatedly. From his talk page and DRs, this user didn't understand COM:L fundamentally and abandoned COM:EVID. Netora (talk) 01:47, 24 November 2023 (UTC)Reply[reply]

  Done. One week block. Taivo (talk) 10:44, 24 November 2023 (UTC)Reply[reply]

User:Ikeya hikaru

As soon as releasing from 2nd block, this user restarted uploading a copyvio portrait by cropping from non CC Youtube video. Netora (talk) 15:30, 24 November 2023 (UTC)Reply[reply]

  Done Blocked for 3 months. Yann (talk) 07:59, 25 November 2023 (UTC)Reply[reply]

User:Donkmoda

Another apparent sockpuppet of Jurisdrew, per the duck test. Newly created account uploading historical revisions of various flags. Fry1989 eh? 15:39, 24 November 2023 (UTC)Reply[reply]

  Blocked by Elcobbola. -- CptViraj (talk) 02:59, 25 November 2023 (UTC)Reply[reply]

User:William1230

Despite warnings, the user continued uploading images that is clearly not his/her own, violating the copyright of authors. 0x0a (talk) 06:57, 25 November 2023 (UTC)Reply[reply]

  Done Blocked for uploading any new files. This user should be unblocked when they have fixed the source, date, author, and license of the files they uploaded, and when they commit not to upload copyright violations. Yann (talk) 07:53, 25 November 2023 (UTC)Reply[reply]

User:Chonalu

Continued uploading a number of copyvio images after a final warning. 0x0a (talk) 07:48, 25 November 2023 (UTC)Reply[reply]

  Done Blocked for a week. All files deleted. Yann (talk) 07:58, 25 November 2023 (UTC)Reply[reply]
Add topic
Retrieved from "https://commons.wikimedia.org/w/index.php?title=Commons:Administrators%27_noticeboard/Blocks_and_protections&oldid=824969041"