Commons:Administrators' noticeboard/Blocks and protections

From Wikimedia Commons, the free media repository
Jump to navigation Jump to search

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
19, 18, 17, 16, 15, 14, 13, 12, 11, 10, 9, 8, 7, 6, 5, 4, 3, 2, 1
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
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
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
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.


From COM:ANU#Time for a ban on DRs and speedy deletions?, there seems to be a general consensus for a 3-month ban on EugueneZelenko from making DRs or SDs. I'm keeping this as short as possible to prevent myself from adding my personal opinions to this message, but could an admin have a look at this and implement this ban? --SHB2000 (talk) 11:09, 17 February 2023 (UTC)Reply[reply]

After 72 hours, seriously no response? I should say, though, that I'm a bit disappointed how admins on Commons are essentially shielded from blocks and bans, albeit indirectly. SHB2000 (talk) 09:56, 20 February 2023 (UTC)Reply[reply]
and people here want an "arbcom" run by admins...yeah never gonna works and this might just be Exhibit A.. Stemoc 10:11, 20 February 2023 (UTC)Reply[reply]
Well, that's a perfect recipe for losing long-term editors... SHB2000 (talk) 10:57, 21 February 2023 (UTC)Reply[reply]
@Gestumblindi, Yann, Ellywa, and King of Hearts: Can one of the admins in the original discussion weigh in or take action? Gbawden (talk) 11:53, 21 February 2023 (UTC)Reply[reply]
@Gbawden: If I see this correctly, no technical blocking would be involved for now - as participation in DRs or editing of file description pages except for SDs would still be allowed. So this would basically mean we ask EugeneZelenko "don't make any DRs or SDs for three months from now on", with a block if he doesn't comply? Gestumblindi (talk) 12:30, 21 February 2023 (UTC)Reply[reply]
Don't ask him not to do it, tell him not to. And it has to be done by an administrator in their official capacity with a message/warning on his talk page. Otherwise, it's just toothless. --Adamant1 (talk) 16:37, 21 February 2023 (UTC)Reply[reply]
Yes. This has to be a warning, not just a request. It would make sense for the wording of the warning to include the words you put in quotes, Gestumblindi: Do not do a and b for the next three months, and if following that, you continue to engage in the behavior that users have complained about in the other thread (x, y and z), a block will be imposed. I think that's the consensus. -- Ikan Kekek (talk) 03:21, 22 February 2023 (UTC)Reply[reply]
  • So you want someone to close the other discussion? What does coming here to say "I want someone to close that discussion with a ban on him right now do? You want to start another discussion with support votes for closing that discussion with a ban on him? -- Ricky81682 (talk) 23:59, 22 February 2023 (UTC)Reply[reply]
  • The other discussion hasn't been closed so starting a separate discussion and wanting people to comment here is precisely the wrong way to handle things. There isn't a "general consensus" and coming somewhere new to state that you have one and want another person to close that discussion for you is why you aren't going to get results. A ban on making DRs or SDs does not require a block or protection so why are you here? You aren't proposing blocking him, you aren't proposing protecting any page and since it hasn't been settled, you can't demand someone block him from doing something he hadn't been banned from doing. Feel free to run to another board and be shocked no one is going to comment in a third or fourth place about the same thing as you just jumping with what you want and make more demands on other people. -- Ricky81682 (talk) 23:56, 22 February 2023 (UTC)Reply[reply]
Do you have any sense of how long it's likely to take for any action to happen? I understand your reaction, but when nothing happens, it's understandable for someone to do something to see if there's a way to get attention to move things along. If you think of things using a customer service model, you'll understand. -- Ikan Kekek (talk) 01:20, 23 February 2023 (UTC)Reply[reply]

Spam-only account. Tryvix1509 (talk) 12:52, 17 February 2023 (UTC)Reply[reply]

✓ Done. The user is warned, all contributions deleted. Taivo (talk) 17:36, 18 February 2023 (UTC)Reply[reply]

777alucard666

A1Cafel (talk) 04:50, 19 February 2023 (UTC)Reply[reply]

✓ Done Gbawden (talk) 06:48, 19 February 2023 (UTC)Reply[reply]

User:Jesus Cortez Matias All

Jesus Cortez Matias All (talk · contributions · Move log · block log · uploads · Abuse filter log Spam-only account. --Benutzer:WvB (talk) 10:44, 20 February 2023 (UTC)Reply[reply]

✓ Done: Indef. --Achim55 (talk) 12:33, 20 February 2023 (UTC)Reply[reply]

Pere prlpz0

Pere prlpz0 (talk · contributions · Move log · block log · uploads · Abuse filter log. Vandalizing File:Microsoft Edge logo (2019).svg. Marbletan (talk) 13:57, 20 February 2023 (UTC)Reply[reply]

  • Based on the recent history of that file page, it looks like the protection needs to be increased too. Marbletan (talk) 14:18, 20 February 2023 (UTC)Reply[reply]
✓ Done: Blocked indef, protection of file page raised from semi to full for 3 months. --Achim55 (talk) 15:36, 20 February 2023 (UTC)Reply[reply]

User:MatchJenny

MatchJenny (talk · contributions · Move log · block log · uploads · Abuse filter log

  • Copyvio after final warning. – Pbrks (t • c) 15:25, 20 February 2023 (UTC)Reply[reply]
Already done by Elcobbola. —‍Mdaniels5757 (talk • contribs) 19:03, 20 February 2023 (UTC)Reply[reply]

Please semi-protect it for an extended period of time because of IP vandalism. Thanks! A09 (talk) 21:43, 20 February 2023 (UTC)Reply[reply]

✓ Done. I semi-protected it indefinitely. Taivo (talk) 09:22, 21 February 2023 (UTC)Reply[reply]

User:César Augusto Ramos

César Augusto Ramos (talk · contributions · Move log · block log · uploads · Abuse filter log

  • Uploading copyvios after final warning. – Pbrks (t • c) 15:23, 21 February 2023 (UTC)Reply[reply]
✓ Done —‍Mdaniels5757 (talk • contribs) 15:35, 21 February 2023 (UTC)Reply[reply]

This IP address was just blocked at English Wikipedia following other blocks of IPs in this range over several months there. See en:Wikipedia:Sockpuppet investigations/KC626266 for the cases and patterns. THe person was blocked here for adding images of numerous phony flags and then embedding them in articles. This user made three edits here today, to Flags of cities of the United States, characteristic of their interest in flags and in manipulating them. Largoplazo (talk) 00:17, 22 February 2023 (UTC)Reply[reply]

✓ Done —‍Mdaniels5757 (talk • contribs) 00:23, 22 February 2023 (UTC)Reply[reply]

Please semi-protect both due to constant vandalism by a Lampung XL IP-hopper. Thanks. Flix11 (talk) 01:49, 22 February 2023 (UTC)Reply[reply]

Lampung XL IP-hopper

User: 140.213.0.0/17 (talk · contributions · Move log · block log · uploads · Abuse filter log
140.213.230.0/24 (talk · contributions · Move log · block log · uploads · Abuse filter log
203.78.0.0/17 (talk · contributions · Move log · block log · uploads · Abuse filter log
140.213.231.0/16 (talk · contributions · Move log · block log · uploads · Abuse filter log
Reason for reporting: Making nonsense deletion requests and vandalizing Indonesia national football team kits. A stretch, I know. But he is just annoying. Flix11 (talk) 02:36, 22 February 2023 (UTC)Reply[reply]

User:Tamiacoco

After copyvio warning, this user didn't stop uploading the same copyvio character's pictures. Netora (talk) 12:22, 22 February 2023 (UTC)Reply[reply]

✓ Done thanks Herby talk thyme 12:33, 22 February 2023 (UTC)Reply[reply]