Steward requests/Global

This page hosts requests for global (un)blocks, (un)locks and hidings.

For global IP block requests, read the guideline and make a request below under Requests for global (un)block. Indicate why a global block is necessary and for how long.
For account lock requests, read the guideline and post under Requests for global (un)lock and (un)hiding.
For local requests here on Meta, see Meta:Requests for help from a sysop or bureaucrat.

If you are here because you have been affected by a global block, please see Global blocks/FAQ for more information about global block and routes to appeal.

Note: (un)blocks apply to IP addresses; and (un)locks apply to global accounts.

Cross-wiki requests
CheckUser information Global blocks/locks Permissions (global) Permissions (bot) Permissions (other) Username changes/ usurpation requests Miscellaneous requests URL blacklisting Title/username blacklisting Email blacklisting
Meta-Wiki requests
CheckUser information Deletion Permissions Requests for help

Requests for global (un)block

Latest comment: 4 minutes ago18 comments6 people in discussion

Please be sure to follow the instructions below:

Your request might be rejected if you don't follow the instructions.

Please also review Global blocking. Only IP addresses can be globally blocked at this moment. Please see #Requests for global (un)lock and (un)hiding if your request involves an account.

Global blocks don't affect Meta-Wiki, so if your IP address is blocked, you can still appeal here. IP addresses that cause disruption on Meta should be reported at Meta:Requests for help from a sysop or bureaucrat instead of here so that they can be blocked locally.

Please describe the kind of cross wiki abusive activity you see from the IP. Saying an IP is a long term abuser is not helpful, but saying "IP vandalizes at ban.wikipedia, no.wikipedia and vi.wikipedia" is. This is especially important for range blocks. If you do not provide enough details, your request might be declined.

Instructions for making a request

Before requesting, make sure that:

You know the IP address(es) you wish to have globally blocked or unblocked.
For blocks, the global blocking criteria are met.
For unblocks, your request addresses the original reason for blocking the IP, if any.

To make a request for the address(es) to be blocked or unblocked

Copy the template below to the bottom of this section and explain why the address(es) should be blocked/unblocked.

=== Global block/unblock for [[Special:Contributions/Some IP address|Some IP address]] ===
{{Status}} <!-- Do not remove this template -->
* {{Luxotool|IP address}}
Description, evidence, diffs, etc. --~~~~

When requesting that your IP be unblocked, note that stewards need to know your IP address to even consider a request.: To find your IP, please visit https://www.whatismyip.com/; You are not required to disclose your IP in public - you may make requests privately to any steward on IRC or by email at: stewardswikimediaorg

Global block for 41.97.172.190

Status: In progress

41.97.172.190 xwiki-contribs • xwiki-date ^(alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye

Proxy used by a certain Person. Thanks in advance! -- Jeff G. ツ (please ping or talk to me) 15:26, 31 May 2024 (UTC)Reply

I don't see any global contributions anywhere, could this be clarified? EPIC (talk) 15:27, 31 May 2024 (UTC)Reply

Global block for 85.153.226.156

Status: Done

85.153.226.156 xwiki-contribs • xwiki-date ^(alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye

Long-term abuse. Cross-wiki abuse. Wooze (talk) 21:36, 31 May 2024 (UTC)Reply

Done EPIC (talk) 21:48, 31 May 2024 (UTC)Reply

Global block for 2A01:E0A:3C4:9E20:6834:F07:26C3:6C3D

Status: Done

2A01:E0A:3C4:9E20:6834:F07:26C3:6C3D xwiki-contribs • xwiki-date ^(alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye

Cross-wiki abuse. Wooze (talk) 22:19, 31 May 2024 (UTC)Reply

Done EPIC (talk) 23:14, 31 May 2024 (UTC)Reply

Global block for 37.39.132.132

Status: Done

37.39.132.132 xwiki-contribs • xwiki-date ^(alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye

Cross-wiki abuse. Wooze (talk) 22:35, 31 May 2024 (UTC)Reply

Done EPIC (talk) 23:15, 31 May 2024 (UTC)Reply

Global block for 79.27.62.204

Status: Done

79.27.62.204 xwiki-contribs • xwiki-date ^(alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye

Long-term abuse. Estrellato (talk) 03:01, 1 June 2024 (UTC)Reply

Robot clerk note: Done by AntiCompositeNumber. MajavahBot (talk) 03:25, 1 June 2024 (UTC)Reply

Global block for 185.86.106.148

Status: Done

185.86.106.148 xwiki-contribs • xwiki-date ^(alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye

Long-term abuse. Caught by global anti-vandalism filter. Seems to be reoccuring copyvio abuse of some kind. Estrellato (talk) 03:26, 1 June 2024 (UTC)Reply

Robot clerk note: Done by AmandaNP. MajavahBot (talk) 03:45, 1 June 2024 (UTC)Reply

Global block for 24.46.160.70

Status: Done

24.46.160.70 xwiki-contribs • xwiki-date ^(alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye

Long-term abuse. Cross-wiki abuse. Blocked as LTA in enwiki (range: /22), /24 blocked in simplewiki. MathXplore (talk) 04:27, 1 June 2024 (UTC)Reply

Done EPIC (talk) 05:23, 1 June 2024 (UTC)Reply

Global block for 73.25.160.111

Status: Done

73.25.160.111 xwiki-contribs • xwiki-date ^(alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye

Cross-wiki abuse. Blocked at enwiki/simplewiki. MathXplore (talk) 04:28, 1 June 2024 (UTC)Reply

Done EPIC (talk) 05:25, 1 June 2024 (UTC)Reply

Global block for 2001:FD8:1804:95FC:F56A:AD81:5DC4:12AB

Status: Done

2001:FD8:1804:95FC:F56A:AD81:5DC4:12AB xwiki-contribs • xwiki-date ^(alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye

Long-term abuse. Same as Special:Contributions/122.2.104.0/21, Special:Contributions/122.2.96.0/19, etc. MathXplore (talk) 04:31, 1 June 2024 (UTC)Reply

Done EPIC (talk) 05:25, 1 June 2024 (UTC)Reply

Requests for global (un)lock and (un)hiding

Latest comment: 3 minutes ago26 comments12 people in discussion

Note that global blocking currently only applies to IPs, due to a technical limitation. If you wish to request a named account for global [un]locking, please request a global [un]lock here instead. Be sure to follow the instructions below:

Your request might be rejected if it doesn't include the necessary information.
Warning! This page is publicly viewable. If the account name is grossly insulting or contains personal information please contact a steward privately in #wikimedia-stewards^connect or email your request to the stewards VRT queue at stewards-oversightwikimediaorg (direct wiki interface) but do not post it here. Thanks.
Warning! This is not the place to ask for locks based on your opinion that someone is disruptive. Global locks are used exclusively against vandalism and spam, not because of content disputes, not because you think that someone deserves to be globally blocked. In such cases, you should ask for local blocks at appropriate places.
If you are globally locked, you should appeal your lock to stewards-appealswikimediaorg.

Please describe abusive activity of an account before reporting them here. Since stewards are often not active at projects the reported accounts are, things that seem obvious to you may not be equally obvious to the reviewing steward.

Instructions for making a request

Before requesting that a global account be (un)locked, please be sure that:

You have evidence of cross-wiki disruption from the account(s).
You can show that it is not feasible to use local-only blocks or other measures like page protection to combat the disruption.
You have considered making the request in #wikimedia-stewards^connect, especially for account names which will be hidden, or for urgent requests.

To make a request for an account to be locked or unlocked: Copy one of the codes below to the bottom of this section and explain why the account(s) should be locked/unlocked.

=== Global lock/unlock for Foo ===
{{status}} <!-- do not remove this template -->
* {{LockHide|username}}
* {{LockHide|username|hidename=1}} <!-- if you do not want the name to be visible on this page -->
*...
Reasons, etc. --~~~~

For many accounts:

=== Global lock for spambots/vandals ===
{{status}} <!-- do not remove this template -->
{{MultiLock|username|username2|username3}}
{{MultiLock|username|username2|username3|hidename=1}} <!-- if you do not want the names to be visible on this page -->
*...
Reasons, etc, --~~~~

Global lock for Won1017

Status: On hold

Won1017 (talk • contribs • block • xwiki-contribs • xwiki-date ^(alt) • CA • ST • lwcheckuser)

Cross-wiki abuse. Already blocked from 5 wikis by vandalism and abusing, and continuing block evasion at kowiki. No more mercy, enough for global lock. LR0725 ( Talk / Contribs ) 16:26, 28 May 2024 (UTC)Reply

On hold, checking with a kowiki steward. EPIC (talk) 16:30, 28 May 2024 (UTC)Reply

Reference: q:ko:사용자토론:Whitetiger#사과의_말씀과_함께_모든_진실을_밝힙니다: This user already said that they have made sock recently. LR0725 ( Talk / Contribs ) 18:20, 28 May 2024 (UTC)Reply

Yes, the main reason why I wanted to check was because the kowiki steward in question declined a request for global lock of this user the first time to give them an ultimatum, and also because this seems to be a young user who doesn't seem to be too aware of what they are doing. EPIC (talk) 18:29, 28 May 2024 (UTC)Reply

In kowiki, I and other admins have given many opportunities. Although he is young, it is no use to show him mercy anymore. He already made about 100(or more) accounts while saying, "I will not make sock puppets anymore" for several times, not only q:ko:사용자토론:Whitetiger#사과의_말씀과_함께_모든_진실을_밝힙니다 case. Whitetiger (talk) 04:44, 29 May 2024 (UTC)Reply

@LR0725: has there been abuse outside of kowiki after they got an ultimatum? EPIC (talk) 06:57, 29 May 2024 (UTC)Reply

After an ultimantum from Sotiale, they made so many sock accounts at kowiki (as confessed themselves).

But, ok, no firm evidence for abuse outside the kowiki. However, why should we just always allow this kind of malicious behaviors? Because they are kid? They make sock accounts every day, personal attacking, and vandalism. And next day, they come and say, "I am sorry I won't do it ever plz don't global lock me". And then, same pattern every day.

All Korean wiki community is just being tired by that system-challenging user. Why should we hesitate? LR0725 ( Talk / Contribs ) 07:21, 29 May 2024 (UTC)Reply

After the original account email was blocked, he routinely conducted terrorism through e-mails using socks accounts and tested the limit of patience through multiple accounts every time. He is the one who gave up the opportunity even though most of the sysops of kowiki executed and controlled his blocking, even though they gave him several opportunities. It is no longer evidence clear that he is "young." How many users should be harmed and personally blasphemed for it? How many users have to go beyond their patience? ㅡ Joayong (Suggest) 08:29, 29 May 2024 (UTC)Reply

@EPIC Not outside the Korean wikimedia project, but he also made other sock puppets in Korean Wiktionary and Korean Wikiquote, which are not blocked as they are not linked to Korean Wikipedia and other. --Whitetiger (talk) 08:50, 29 May 2024 (UTC)Reply

Comment I don't have a strong opinion against locking them. This is because they may come to different conclusions depending on their perspective, and I do not expect their behavior to improve in the short term. However, there are a few things that need to be clarified; most of the above opinions focus on local affairs, so it is important to understand exactly what the questions asked by stewards about global lock mean. It is quite clear that for global locks to apply, the damage they cause must be cross-wiki. As I understand it, EPIC is asking you to provide a clear rationale. You tend to argue that global locks can be guaranteed because of kowiki local abusing. There are continuous local LTA cases that occur every day in many local areas, even more serious than those, even personal attacks, but this is not handled as a global lock. This is because it is a local difficulty and not a global difficulty, and that is a serious misunderstanding of global lock. Therefore, there is no point in claiming local affairs difficulties so that you can lock their account. So, as to why they should be locked, you have to prove that they caused cross-wiki problem, and any other circumstances are meaningless. Tl;dr: multiple kowiki admins asserting local affairs will not have a positive impact on this request(as this increases the likelihood that this will look like a local problem to other users), so it is recommended that you focus your justification on their cross-wiki abusing. Eg. concretizing what Whitetiger presented, it is necessary to explain in detail how this is cross-wiki abuse and how it is related. --Sotiale (talk) 09:13, 29 May 2024 (UTC)Reply

He avoided kowiki's user talk block by using wikiquote - see what I linked above - and pretending as a normal user in Korean wiktionary and wikiquote while creating numerous sock puppets in wikipedia. He also requested to meta admins to be unblocked in kowiki during that period. If it is not a cross-wiki abuse just because the projects are using the same language, then all projects using Korean(+meta) should block his account(and lots of other sock puppets, if necessary) manualy. I don't think that's a good idea. --Whitetiger (talk) 11:41, 29 May 2024 (UTC)Reply