Jump to content

Commons:Administrators' noticeboard/Blocks and protections

Add topic
From Wikimedia Commons, the free media repository

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

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.


User:PickUp-10026444-413

[edit]

User: PickUp-10026444-413 (talk · contributions · Move log · block log · uploads · Abuse filter log

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 PickUp1994 (talk · contribs), PickUp412 (talk · contribs), Pickup9386 (talk · contribs), PickUp-Max2024 (talk · contribs), etc, which indicates their relationship.

-- Miwako Sato (talk) 10:42, 29 March 2026 (UTC)Reply

✓ Done. Indefinite block. Taivo (talk) 10:59, 29 March 2026 (UTC)Reply
[edit]

Dharshan Karthikeyan (talk · contribs) has been uploading images of Indian television show title screens which have all been deleted. I've left them warnings here and a message on their en wiki talk page as well. They've continued today, uploading the same title screen image that's been deleted three times already. See Special:Log/Dharshan_Karthikeyan. Ravensfire (talk) 12:34, 31 March 2026 (UTC)Reply

✓ Done Blocked for a week, last file deleted. Yann (talk) 12:41, 31 March 2026 (UTC)Reply

Request autoconfirmed protection for File:Primäres System.png

[edit]

Although the volume isn't high, most of the edits on this image are either from vandalism or reverting vandalism. Likely a target due to its use in Category:Systems. Please let me know if this is below the threshold of protection so I can keep future requests in mind. Thanks, --Stux (talk) 22:35, 31 March 2026 (UTC)Reply

✓ Done. 3 years autopatroller-level protection. Semi-protection was not enough, because some vandals were old users with a lot of edits (now indefinitely blocked anyway). Taivo (talk) 09:18, 1 April 2026 (UTC)Reply

User:GOATlegroscaca

[edit]

User: GOATlegroscaca (talk · contributions · Move log · block log · uploads · Abuse filter log

Reason for reporting: Used for vandalism on fr-wiki, offensive name Nicolas22g (talk) 18:18, 1 April 2026 (UTC)Reply

✓ Done. I blocked the user indefinitely, the only upload is deleted. Taivo (talk) 09:10, 2 April 2026 (UTC)Reply

Statistics about Italian places (semi-protection)

[edit]

Dušan Kreheľ (talk) 22:01, 1 April 2026 (UTC)Reply

✓ Done. Full protection is not needed. Auropatroller-protection is enough. Taivo (talk) 09:23, 2 April 2026 (UTC)Reply

Rikutyanman

[edit]

A1Cafel (talk) 03:20, 3 April 2026 (UTC)Reply

✓ Done. 2 weeks block for uploading out-of-scope files after warnings and re-uploading content deleted per community consensus. All contributions are already deleted. Taivo (talk) 10:51, 3 April 2026 (UTC)Reply

Block User:Leirbag reib

[edit]

In 2012, the account Gabriel bier was blocked from Commons “with an expiration time of indefinite” for “uploading unfree files after warnings”. Over nearly 13 years, and assuming the basics of copyright were learned, no effort was made to request an unblock. In February 2025, Gabriel bier expressed, on the Portuguese-language Wikipedia, the intention to request courtesy vanishing for privacy-related reasons. Since vanishing requires the user not to be blocked on any project, I requested their unblock on Commons, which was granted by Bedivere “as the user is vanishing” [1].

However, in June of that same year, the person behind the account returned under the name “Leirbag reib” (“Gabriel bier” reversed; confirmed by CheckUser [2]), even violating existing editing restrictions on ptwiki, as noted by administrator Kascyo. There is an ongoing (un)block discussion for this account, in which no consensus seems to have been reached regarding the user’s return to the Portuguese-language Wikipedia (some administrators against the return argue that, for example, there was abuse of the vanishing process, and that it should be permanent). Since the account was unblocked here at my request solely for the purpose of vanishing, and considering abuse has been alleged in their case, I argue the original block should be reinstated on this new account until the user, acknowledging their prior misconduct, requests an unblock on their own and an administrator grants it (considering vanishing on Commons, unlike on the ptwiki, is not expected to be permanent). Yacàwotçã (talk) 08:21, 3 April 2026 (UTC)Reply

Bedivere (forgot to ping; will notify on talk page regardless as it’s mandatory) Yacàwotçã (talk) 08:22, 3 April 2026 (UTC)Reply
 Not done. Leirbag reib has 0 edits in Commons, so he has not abused multiple accounts here. As he is unblocked by Bedivere, he is allowed to edit Commons. In my opinion vanished users are allowed to come back, if they want. But as his username "Renamed user ####" is difficult to remember, it's allowable to create a new user account, as long as he does not use the old account. Taivo (talk) 11:03, 3 April 2026 (UTC)Reply
They were unblocked by @Bedivere to request vanishing, not to edit on Commons acknowledgeding the reasons for their block. Look, I’m not opposed to the unblock, but it should only happen once that requirement is met, which as of now at least isn’t the case here, since the user never cared about being unblocked normally Yacàwotçã (talk) 11:55, 3 April 2026 (UTC)Reply
Each Wiki has its own rules. For example, a user could be blocked on enwiki indefinitely for say disruptive editing or banned from say a certain topic area i.e. planes, automobiles. However, the ban/block behaviour in most cases does not apply here. We welcome constructive contributions. In fact, some users opt for clean starts/avoid harassments. So far as there is no active restriction in place then its all good. LuvsMG481 (talk) 13:33, 3 April 2026 (UTC)Reply
I agree in principle with Yacawotca. The only reason that led to their unblock was to allow them to vanish. But their troublesome history was not acknowledged and, even though I'm not opposed that they remain unblocked, at the very least they should acknowledge their past mistakes and move on. Bedivere (talk) 13:48, 3 April 2026 (UTC)Reply
I believe courtesy vanishing only applies to users in good standing not if they are blocked if i'm not mistaken. This new user could be a COM:SOCK - indef block I think was appopriate. Courtesy vanishing is not intended as a temporary measure, nor as a way to avoid scrutiny or avoid sanctions. and in this regard, the user was simply avoiding scrutiny for copyvio. This is unacceptable. LuvsMG481 (talk) 13:53, 3 April 2026 (UTC)Reply

Commons:Twinkle/Preferences

[edit]

Commons:Twinkle/Preferences (edit | talk | history | links | watch | logs)

This should be template-editor-protected to prevent vandalism

It was already move-vandalised once (albeit years ago); the English Wikipedia page of the same title, which the Commons page was forked from, has the first kind of protection Whyiseverythingalreadyused (t · c · he/him) 12:31, 3 April 2026 (UTC)Reply

Won't Autopatrol protection be enough for edit? We can apply full protection for move though. Shaan SenguptaTalk 13:49, 3 April 2026 (UTC)Reply
Well that's good too Whyiseverythingalreadyused (t · c · he/him) 13:51, 3 April 2026 (UTC)Reply

Block request for User:Future Freq MGMT

[edit]

Future Freq MGMT (talk · contributions · Move log · block log · uploads · Abuse filter log Username containing a commercial trademark LuvsMG481 (talk) 13:30, 3 April 2026 (UTC)Reply

The account has been dormant ever since its first and only edit (which was to upload File:Super Flu Press by Falko Gerlinghoff 017.jpg, the image you nominated for F1 speedy deletion)
It doesn't need to be blocked right now since it's not a demonstrable long-term abuser, but it's worth a check Whyiseverythingalreadyused (t · c · he/him) 14:21, 3 April 2026 (UTC)Reply
Its the actual username, there's no where i mentioned it was a sock or long-term abuser. Read the facts carefully. My friend is an actress, usually these MGMT stuff would be commercial usernames. LuvsMG481 (talk) 14:45, 3 April 2026 (UTC)Reply
There is possibly an implication of being the management of the musical act Future Frequency. If they stay active, and they make edits that are related to that, that could be a problem. But I don't see it as an automatic block, and I think if there is an issue here it would be better to take it up through COM:AN/U, inform them on their user talk page, and at least give them a proper chance to participate in the discussion. - Jmabel ! talk 18:00, 3 April 2026 (UTC)Reply
For some reason, I was using an automated script. It directed me to this one. I'm so sorry, but as said I'm not some tech junkie to know all this. I actually should have put it there LuvsMG481 (talk) 18:28, 3 April 2026 (UTC)Reply
Hey, so I should change my username cause MGMT feels wrong ... is that right? Future Freq MGMT (talk) 20:07, 3 April 2026 (UTC)Reply
Its actually because you are presumed to represent a talent agency. My friend is an actress and she gets involved with MGMT talent teams. I highly suggest you should. It isn't too difficult, just use this tool and go from there. Once its all done, an admin will close the discussion and you are all in the clear. Let's talk about it on my talkpage. LuvsMG481 (talk) 20:10, 3 April 2026 (UTC)Reply
Okay ... never intended ... than it would be great if wiki would block this from the beginning ... anyways .. thanks for the info and the tool ... I requested a change. Future Freq MGMT (talk) 20:13, 3 April 2026 (UTC)Reply
I think we can close this discussion. No action is needed. User resolved concerns. LuvsMG481 (talk) 20:14, 3 April 2026 (UTC)Reply