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 ^{[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}

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.

Add Flickr accounts to bad authors list

Hope this is the right spot... I found some more Flickr accounts which engage in license laundering. These Flickr accounts mass re-upload photos from The Canadian Press, Reuters, Government of Canada, and other sources. These are copyrighted photos that are falsely released under a Public Domain license. The file EXIF data is hidden on Flickr, but once downloaded you can clearly see all EXIF that shows the correct photographers / rights holders. Here is an example of one: Image laundered on Flickr Same image on Canadian Press site. I see that other similar accounts have already been blocked, such as madison.beer
Users to block: Do Not Speak As Loud As My Heart & Taylor Atkinson. PascalHD (talk) 21:41, 10 November 2023 (UTC)Reply[reply]

I'll add them to the list on Commons:Questionable Flickr images. Thank you for reporting these accounts. — Red-tailed hawk _(nest) 14:52, 11 November 2023 (UTC)Reply[reply]

Duongdanh110106

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

Upload images on the Internet regardless of copyright status and mark them own work, may be Shinichiheiji1234 sock I am I ^Talk 15:52, 11 November 2023 (UTC)Reply[reply]

Done Warned, files deleted. @Shinichiheiji1234: You have to inform the uploader when you nominate a file for deletion. Yann (talk) 17:26, 11 November 2023 (UTC)Reply[reply]

The reporting user was blocked indefinitely for sockpuppetry thanks to Taivo. — 🇺🇦Jeff G. ツ_{please ping or talk to me}🇺🇦 04:51, 12 November 2023 (UTC)Reply[reply]

@Jeff G. This user hasn't been blocked. I am I ^Talk 13:08, 14 November 2023 (UTC)Reply[reply]

@Đơn giản là tôi: Please read this log. I wrote "reporting", not "reported". Also, please ensure that your signature includes your username visibly. — 🇺🇦Jeff G. ツ_{please ping or talk to me}🇺🇦 09:16, 15 November 2023 (UTC)Reply[reply]

WaftCinematic

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

User continues to upload image on the Internet and labels as "Own work". 0x0a (talk) 08:33, 13 November 2023 (UTC)Reply[reply]

Done 2nd block of 3 months - lets hope they get the message Gbawden (talk) 10:21, 13 November 2023 (UTC)Reply[reply]

2607:fb91:bc6:f33e:ac39:bd12:83e6:b04

2607:fb91:bc6:f33e:ac39:bd12:83e6:b04 (talk · contribs · deleted contribs · logs · edit filter log · block user · block log)

Crosswiki vandalism. -- Jan Kameníček (talk) 16:43, 13 November 2023 (UTC)Reply[reply]

Already done (log) by CptViraj. — Red-tailed hawk _(nest) 01:41, 14 November 2023 (UTC)Reply[reply]

User:重吉笑里

重吉笑里 (talk · contributions · Move log · block log · uploads · Abuse filter log) block user

While receving copyvio warnings, this user repeatedly uploaded the same copyvio portraits. Netora (talk) 14:40, 14 November 2023 (UTC)Reply[reply]

Final warning given, will be blocked on next copyvio, please report. Thanks! -- CptViraj (talk) 06:22, 15 November 2023 (UTC)Reply[reply]

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]

Template:Image

{{Image}} has been vandalized multiple times today, most recently with what appears to be a suggestion to protect the template. I agree: this template is used all over the place, including in {{Editnotice}} when |image= is set, as it is in {{Editnotices/Namespace/Data}}. – Minh Nguyễn ^💬 05:56, 15 November 2023 (UTC)Reply[reply]

Semi-protected and blocked IPv6 range for a week. -- CptViraj (talk) 06:20, 15 November 2023 (UTC)Reply[reply]

Aswin027

User: Aswin027 (talk · contributions · Move log · block log · uploads · Abuse filter log) block user
Reasons for reporting: Slews of abuse filter hits, some of them private, some of them indicating copyvios, some of them indicating spam. Actual copyvios. Failure to provide COM:EVID. The alleged source of many of the uploads is a private Instagram account with a similar username but only 11 posts. — 🇺🇦Jeff G. ツ_{please ping or talk to me}🇺🇦 09:14, 15 November 2023 (UTC)Reply[reply]

Done Last warning sent, and Commons:Deletion requests/Files uploaded by Aswin027. Yann (talk) 09:48, 16 November 2023 (UTC)Reply[reply]

@Yann: Thanks! — 🇺🇦Jeff G. ツ_{please ping or talk to me}🇺🇦 10:07, 16 November 2023 (UTC)Reply[reply]

N19Lu et al

Users: N19Lu (talk · contributions · Move log · block log · uploads · Abuse filter log) block user et al
Reasons for reporting: Please handle Commons:Requests for checkuser/Case/N19Lu based on behavior.

— 🇺🇦Jeff G. ツ_{please ping or talk to me}🇺🇦 11:38, 15 November 2023 (UTC)Reply[reply]

Done All blocked. Yann (talk) 10:02, 16 November 2023 (UTC)Reply[reply]

@Yann: Thanks! — 🇺🇦Jeff G. ツ_{please ping or talk to me}🇺🇦 10:06, 16 November 2023 (UTC)Reply[reply]

Semi-protection is not effective enough on {{Image}}

{{Image}} is used in system messages such as Mediawiki:Protectedpagetext. To prevent vandalism on system messages, I feel like it should be fully protected. 64.114 etc (talk) 19:04, 15 November 2023 (UTC)Reply[reply]

Your IP Special:Contributions/2604:3D08:9476:BE00:0:0:0:0/64 is blocked here and on wikidata. Your account is blocked on meta because of "making many bad translations" and I was planning to do the same here because of your poor translations as IP, see User talk:2604:3D08:9476:BE00:690A:57EB:30B8:D9. Your IP edits (5 edits within 2 days) of Template:Image just to make a point were vandalism. I'd be quiet if I were you... --Achim55 (talk) 19:31, 15 November 2023 (UTC)Reply[reply]

Do not disrupt Commons to illustrate a point. — 🇺🇦Jeff G. ツ_{please ping or talk to me}🇺🇦 19:50, 15 November 2023 (UTC)Reply[reply]

Kiava

User: Kiava (talk · contributions · Move log · block log · uploads · Abuse filter log) block user
Reasons for reporting: Continued copyvio uploading after warning for doing so. Callous disregard of final warning and personal attack in this edit.

— 🇺🇦Jeff G. ツ_{please ping or talk to me}🇺🇦 09:09, 16 November 2023 (UTC)Reply[reply]

Done Blocked for uploading files for a month. I asked Kiava to fix the 2 remaining files which are probably in the public domain, but with the wrong license. Yann (talk) 09:29, 16 November 2023 (UTC)Reply[reply]

@Yann: Thanks! — 🇺🇦Jeff G. ツ_{please ping or talk to me}🇺🇦 10:07, 16 November 2023 (UTC)Reply[reply]

Sockpuppets

Please see w:en:Wikipedia:Sockpuppet investigations/Krakhesh where enwiki has found sockpuppetry. At least two of the editors have uploaded here. 🇺🇦 Timtrent 🇺🇦 talk to me 🇺🇦 13:11, 16 November 2023 (UTC)Reply[reply]

Alotorus

User: Alotorus (talk · contributions · Move log · block log · uploads · Abuse filter log) block user
Reasons for reporting: Continued copyvio uploading after two blocks for doing so.

— 🇺🇦Jeff G. ツ_{please ping or talk to me}🇺🇦 14:49, 16 November 2023 (UTC)Reply[reply]

Done Blocked for 6 months, and Commons:Deletion requests/Files uploaded by Alotorus. Yann (talk) 15:21, 16 November 2023 (UTC)Reply[reply]

Add topic