Jump to content

Commons:Administrators' noticeboard/Blocks and protections

This page is semi-protected against editing.
From Wikimedia Commons, the free media repository
Latest comment: 1 day ago by The Squirrel Conspiracy in topic Dnerm

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

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.


Unicode data semi-protection

This discussion was archived without a proper resolution. tl;dr all of the data files under Category:Unicode Module Datasets should definitely be at the very least indefinitely semi-protected, either directly or through some indirect means, because of their (very) high visibility. — SURJECTION / T / C / L / 21:11, 16 August 2025 (UTC)Reply

Looking at that discussion, it looks like we want to protect at the template editor level, but the user who requested protection has not gotten around to requesting that level of rights. - Jmabel ! talk 00:35, 17 August 2025 (UTC)Reply
Protecting at the template editor level is fine too, at least for some of the data, but we shouldn't leave them unprotected until we get that sorted out. Don't let the perfect be the enemy of the good. — SURJECTION / T / C / L / 17:47, 17 August 2025 (UTC)Reply
✓ Done all protected at template editor level. That was tedious, we really ought to have a tool for mass protection. - Jmabel ! talk 21:24, 17 August 2025 (UTC)Reply
@Jmabel Why? 😭 ToncianTaien (talk) 03:31, 19 August 2025 (UTC)Reply
Change it back to semi-protection right now! 😡 BashBuilder (talk) 05:01, 19 August 2025 (UTC)Reply
Sorry, I thought the conclusion at the linked discussion was that this should be protected at template editor level, and that certainly was my read of Surjection's request here. BashBuilder I will accept your interpretation and lower this to autopatrollers. Certainly no one below that level should be messing with these. This is going to take me another half-hour or so. If someone wants this changed yet again after that, ask someone other than me. - Jmabel ! talk 05:12, 19 August 2025 (UTC)Reply
✓ Done - Jmabel ! talk 05:45, 19 August 2025 (UTC)Reply
Thank you! I will upload files with Creative Commons and become an autopatroller soon. ToncianTaien (talk) 06:06, 19 August 2025 (UTC)Reply
Me too! I will upload over 1000 images with Creative Commons. BashBuilder (talk) 06:13, 19 August 2025 (UTC)Reply
These two accounts are almost certainly operated by the same person who has socked extensively on en.wikt, but that's a whole another subject... — SURJECTION / T / C / L / 08:59, 19 August 2025 (UTC)Reply
@Surjection Those 2 accounts are not a sockpuppet in en.wiktionary.org. BiggCooker (talk) 13:56, 19 August 2025 (UTC)Reply
Nevermind, one of their accounts was blocked here too. Maybe a Commons CU could look at it. (I suspect the account that responded to me above is them, too. I've had to block dozens of their socks on en.wikt alone.) — SURJECTION / T / C / L / 23:03, 19 August 2025 (UTC)Reply
I have started a checkuser case, see Commons:Requests for checkuser#BiggCooker. Tvpuppy (talk) 13:08, 21 August 2025 (UTC)Reply

So if BashBuilder and BiggCooker weren't legit, should this indeed be raised back to template editor? (Not that I'm volunteering to do the work yet again.) - Jmabel ! talk 18:25, 21 August 2025 (UTC)Reply

I agree, I'll do it. —‍Mdaniels5757 (talk • contribs) 17:22, 24 August 2025 (UTC)Reply
✓ Done, here's the script I used:
from pywikibot import config, Site, Category
from pywikibot.pagegenerators import CategorizedPageGenerator, PrefixingPageGenerator
from itertools import chain

config.put_throttle = 5
commonswiki = Site("commons", "commons")
pages = set(chain( # Get uncategorized pages under Data:Unicode data too, in case it was forgotten
   CategorizedPageGenerator(
      Category(commonswiki, "Category:Unicode_Module_Datasets")
   ),
   PrefixingPageGenerator("Data:Unicode_data"),
))

for page in pages:
    print(f"protecting {page}")
    page.protect(
        reason="High cross-wiki use, see [[Special:Permalink/1077265368#Unicode_data_semi-protection]] and linked discussions",
        protections={"edit": "templateeditor", "move": "templateeditor"},
    )

for page in pages:
    print(f"{page} has protections {page.protection()}")

print(f"total pages protected: {len(pages)}")
—‍Mdaniels5757 (talk • contribs) 18:18, 24 August 2025 (UTC)Reply
Only 21 accounts are banned after CU-investigation, User:BashBuilder is one of them. Still  Support done protection to level "template editor" of all in Category:Unicode Module Datasets. Ping me if you need an edit and lack the right. Dusan has the right now too. Taylor 49 (talk) 18:02, 25 August 2025 (UTC)Reply

Sockpuppets

These accounts are re-uploading the deleted files of globally locked user دامر العمري (talk · contribs). Marbletan (talk) 12:31, 19 August 2025 (UTC)Reply

✓ Done blocked and nuked these four plus two more I spotted with CheckUser. The Squirrel Conspiracy (talk) 14:05, 19 August 2025 (UTC)Reply

@The Squirrel Conspiracy: (or another admin). The user listed below appeared today and is re-uploading the same deleted files. Can you have a look? Marbletan (talk) 13:21, 22 August 2025 (UTC)Reply

✓ Done The Squirrel Conspiracy (talk) 16:32, 22 August 2025 (UTC)Reply

RPP

Template:NOIRLab request page protection.

Reason: 23,000 transclusions. Waddie96 (talk) 20:06, 21 August 2025 (UTC)Reply

✓ Done Semi-protected. Yann (talk) 16:17, 22 August 2025 (UTC)Reply
👍 Waddie96 (talk) 20:29, 22 August 2025 (UTC)Reply

Block request for Hopeful2day

 Comment Final warning sent, one file deleted. Yann (talk) 16:16, 22 August 2025 (UTC)Reply
Thanks @Yann. @Pushingforward appears to be a related account; it has repeatedly uploaded the same copyrighted image that Hopeful2day has; flagging in case you want to take a look. Dclemens1971 (talk) 17:27, 22 August 2025 (UTC)Reply
✓ Done I blocked Pushingforward indef. for socking. Yann (talk) 08:46, 24 August 2025 (UTC)Reply

User:TS01800 and false claim of ownership at File:Thomas Sewell August 2025.jpg

TS01800, uploaded a file at File:Thomas Sewell August 2025.jpg and they claimed that the image is their own work (refer to Special:Diff/1076013160). They have gone on to reassert that it is their own work two more times at Special:Diff/1077081556 and Special:Diff/1077088119. This is contradicted by statements they have made on my user talk where they admit it is not their own work (refer to Special:Diff/1077086530). Can the file be protected so that they can't continually revert to make claims that it is their own work when it is not. TarnishedPathtalk 04:55, 24 August 2025 (UTC)Reply

@TarnishedPath is disruptively editing my image, claiming that the source is a video on youtube with 4 views.
I own the copyright for the original video footage in question and @TarnishedPathis falsely stating otherwise TS01800 (talk) 04:58, 24 August 2025 (UTC)Reply
You have clearly admitted that the image is not your own work and have reverted twice to reinsert claims that it is. TarnishedPathtalk 05:00, 24 August 2025 (UTC)Reply
Ok what would you be satisfied with then?
I get the person who originally took the video and then transferred the copyright to me, to submit a statement that they authorise the image (that they no longer own the copyright for) to be used?
Stop being disruptive TS01800 (talk) 05:03, 24 August 2025 (UTC)Reply
Also please consider that this user did the same thing with the only other image I have uploaded where he falsely copyright flagged (Special:Diff/1041864671) a selfie, claiming that the source was from some random twitter account.
@TarnishedPath is just being disruptive TS01800 (talk) 05:18, 24 August 2025 (UTC)Reply
That other image was correctly deleted and only allowed back up after you submitted a VRT ticket. You need to dial back your combative language. TarnishedPathtalk 05:22, 24 August 2025 (UTC)Reply
No, you got it taken down by citing an incorrect source. The same thing you are doing here TS01800 (talk) 05:23, 24 August 2025 (UTC)Reply
@TS01800: The original creator of the video must be credited. They authorize its use with the ticket. זיו「Ziv」For love letters and other notes 05:27, 24 August 2025 (UTC)Reply
Ok, I will get them to also do that, thanks TS01800 (talk) 05:34, 24 August 2025 (UTC)Reply
And you need to edit the file so that it states their name, not that it is your work. TarnishedPathtalk 05:58, 24 August 2025 (UTC)Reply
Ok, will do
Thanks for being so helpful TS01800 (talk) 06:13, 24 August 2025 (UTC)Reply
Pinging @Ziv as an involved admin. TarnishedPathtalk 05:02, 24 August 2025 (UTC)Reply
@TarnishedPath, The file has an open VRT ticket, and its review is the responsibility of the trusted members of the VRT team. I'm not a VRT member, so I can't verify the information. Please give them some time, as this is also voluntary work, and if anything is incorrect with the information provided, they will suggest the image for deletion. זיו「Ziv」For love letters and other notes 05:19, 24 August 2025 (UTC)Reply

Block request for Rastapopoulos25

Rastapopoulos25 (talk · contributions · Statistics · Recent activity · block log · User rights log · uploads · Global account information)

@Rastapopoulos25 has a long history of uploading copyrighted work and continues to do so despite a prior block in 2024. This user is not here to contribute positively to the project. Moumou82 (talk) 08:25, 24 August 2025 (UTC)Reply

✓ Done Blocked for a week, all files deleted. Yann (talk) 08:37, 24 August 2025 (UTC)Reply

Request file protection.

File:Breezeicons-actions-22-help-about.svg Request file protection.

576,655 transclusions. Waddie96 (talk) 09:38, 25 August 2025 (UTC)Reply

@Waddie96: ✓ DoneMatrix(!) ping onewhen replying {user - talk? - uselesscontributions} 10:04, 25 August 2025 (UTC)Reply

The omagol official

✓ Done Blocked, category deleted. Yann (talk) 17:28, 25 August 2025 (UTC)Reply

Dnerm

No meaningful contributions other than nudity, personally think most of their files could be speedied as vandalism per Com:Nudity. Takipoint123 (💬) 05:23, 26 August 2025 (UTC)Reply

I want to express some kind of  Support to this report. I concur in that a lot of his uploads were unsuitable per COM:Nudity, leading me to open Commons:Deletion requests/Files uploaded by Dnerm. Now, this uploader went and nominated himself the files I purposefully left out of the DR, as I thought that those not included were acceptable. Commons:Deletion requests/File:A photo of a person defecating.jpg is a DR about a photo that IMHO had some kind of educational value, for instance.
As it stand now, the only files not deleted are those in my mass DR. The others were put up for elimination by the uploader. I could see that behaviour either as wish to unbind himself from Commons or as an act of defiance, hence my initially stated "kind of support". Regards, Grand-Duc (talk) 06:01, 26 August 2025 (UTC)Reply
Personally I'm not too sure what they're up to either with the self-DRs. They've already blocked at Kowiki for vandalism [6] and also repeatedly uploaded after their warning at the talkpage too. If anything I would want them to make a good explanation if they could contribute to anything non-sexual in nature. Takipoint123 (💬) 06:33, 26 August 2025 (UTC)Reply
✓ Done Indef as NOTHERE. As for the self-DRs, it's exhibitionism. Happens all the time. The Squirrel Conspiracy (talk) 06:46, 26 August 2025 (UTC)Reply