Steward requests/Global

From Meta, a Wikimedia project coordination wiki
< Steward requests(Redirected from SRG)
Jump to navigation Jump to search
← Requests and proposals Steward requests (Global) latest archive→
Shortcut:
SRG
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. 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.

If you are here because you have been blocked by a global block, and believe that the block is in error or you have not done anything wrong, there are a few methods through which you can appeal:

  • If the IP is not currently blocked on Meta, you can post a request to this page following the instructions below to have the IP unblocked.
  • If the IP is currently blocked on Meta, you can post an appeal on your talk page. For maximum effectiveness, ping the steward who globally blocked the IP address using the code {{ping|USERNAME}} so that they are notified about it.
  • If you are editing from an account and have been caught by a global IP block that is unlikely to be removed (i.e. because it is an open proxy or because of long-term abuse), you can request an individual exemption from the block at the requests for global permissions page. Please see the section on global IP block exemptions on that page for specific instructions for making a request.
  • If none of those options work, you are free to contact the stewards using this form or sending a direct email to stewards(at)wikimedia.org.

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


Cross-wiki requests
Meta-Wiki requests


Requests for global (un)block

Symbol comment vote.svg 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.
Instructions for making a request

Before requesting, make sure that:

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

To make a request for an account to be locked or unlocked

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: stewards(at)wikimedia.org

Global block for proxies

Status:    In progress

All proxies with edits in multiple projects. Rafael (stanglavine) msg 16:56, 2 August 2019 (UTC)

Global block Proxies/Spambots

Status:    In progress

[1] [2] [3] --WikiBayer 👤💬 19:08, 7 August 2019 (UTC)

[4]--WikiBayer 👤💬 19:40, 7 August 2019 (UTC)

Proxys (Spambots) --WikiBayer 👤💬 08:22, 10 August 2019 (UTC)

Global block for Globally Banned GRP

Status:    In progress

Ban evasion of GRP - see history of s:wt:Administrators' noticeboard --DannyS712 (talk) 00:51, 8 August 2019 (UTC)

See contributions on simple english wikipedia. Thanks, --DannyS712 (talk) 23:55, 12 August 2019 (UTC)

Ban evasion by George Reeves Person. Already blocked on two wikis.   — Jeff G. ツ please ping or talk to me 15:10, 18 August 2019 (UTC)

Global block for 143.255.56.0/22

Status:    In progress

Abused webhost/proxy. (HostDime) --Zaxxon0 (talk) 02:49, 15 August 2019 (UTC)

Global block for 2600:387:6:902:0:0:0:0/64

Status:    In progress

Crosswiki vandalism. 2600:387:6:902:0:0:0:0/64 is already rangeblocked on three wikis.   — Jeff G. ツ please ping or talk to me 16:37, 22 August 2019 (UTC)

Global block for extremely disruptive LTA

Status:    In progress

The moment this last global block expired, they immediately started vandalizing again. Praxidicae (talk) 21:07, 26 August 2019 (UTC)

The /16 block proposed by Praxidicae does not pertain to any single entity – can she point to any single vandalistic edit originating from 159.146.128.0/17? The /16 even doesn’t map to one country, which can easily be seen in whois(1) and is confirmed with traceroute(1) as well. Incnis Mrsi (talk) 11:34, 29 August 2019 (UTC)
well half of the edits are deleted but did you bother to even look? take a look at the last 30 reverts there. There are hundreds of edits crosswiki like this. Praxidicae (talk) 11:42, 29 August 2019 (UTC)
Hey, we discuss how large range to block in 159.146. – right? Not a single 159.146.x.y found where x ≥ 128. Respectfully (for a fellow LTA hunter), open a book on IP addressing, find a chapter on CIDR notation, and try to realize what am I speaking about. Incnis Mrsi (talk) 12:29, 29 August 2019 (UTC)
@Incnis Mrsi: Your behavior is extremely hostile and anything but respectful. If you have an issue with this request, make it clear without insulting the requesting contributor. Vermont (talk) 12:36, 29 August 2019 (UTC)
Please take a look at the range of contribs, you'll notice that every single edit since July 30th from this range has been this exact vandal. That's also not including all the deleted contribs and that's just a small handful of one IPs edits in this range. See this also. So what range would you suggest in this case? If you wish to continue this lecture, you're welcome to take it to my talk page provided you can remain civil. Praxidicae (talk) 12:55, 29 August 2019 (UTC)
Possibly Special:GlobalBlock/159.146.0.0/17—after the steward Tegel and Iliev of bg.Wikipedia—would be a reasonable solution. As for those who block a whole /16 in cases where only a small part of the range is evidently active, they manage local wikis (some rather small) where little (if any) collateral damage can be expected from the carpet bombing, especially if with an IP-only block. Moreover, /16 is bluntly easier to memorize due to “159.146.*” wildcard. Global actions should require higher accuracy and a decent qualification. Incnis Mrsi (talk) 15:46, 29 August 2019 (UTC)
You're seriously calling the difference between a /16 and a /17 a "carpet bombing"? Vermont (talk) 22:29, 29 August 2019 (UTC)

2019-09-04T21:44:04: Tegel (meta.wikimedia.org) globally blocked 159.146.0.0/17 (expires on 2019-09-06 at 04:44:04, anonymous only) (Cross-wiki abuse). The simplewiki block has been adjusted to match that range as well. ToBeFree (talk) 04:17, 5 September 2019 (UTC)

Global unblock for 151.48.0.0/17

Status:    In progress


Facts:13th june a steward (masti) blocked this italian ip range globally for six months with the motivation 'Cross-wiki spam: spambot'.There was not a spambot which is a computer making automatical spam edits but just a troll who abused account creation.The steward also blocked about twenty fake accounts created from that ip range whose only edits were message spamming in various wikipedias.I have seen that the messages were invitations to many users to join a votation in it.wikipedia.org which was closed short after so probably the abuser would have stopped anyway.But yet the block is still active for about 33000 ips until december.
Considerations:a globalization block is useful to protect wikipedia but this kind of block exceeds this need.It is excessive both because the abuser has apparently no more reasons to continue his abuse and because to stop his abuse it was sufficient preventing users from that ip range from creating new accounts instead of blocking completely the possibility to edit anything.I know that every block causes unavoidably some collateral damage but in this case the collateral damage is too high but most important it is not necessary.I would not be asking to unblock the ip range if the problem was a spambot or an anonymous user who spammed his messages from various ip addresses from this range.I am asking to unblock the ip range because the abuser used the new accounts he continued creating to spam messages.
Request:imho the most proper solution which both protects wikipedia from the abuser's possible return and makes the least possible collateral damage for the remaining 33000 innocent users is globally blocking new account creations but allowing editing from ips.In this way users can continue contributing anonymously and it would be even easier checking possible disruptive edits by keeping an eye on the ip range.Also consider that this italian ip range is maybe the most common provided by the telecommunication company 'Wind' and that a large part of italian contributors are currently prevented from editing for no justified reason.It is still possible that some users from this ip range will commit some abuse but no ip range contains zero percent of abuse and from this ip range no more abuse than from any other ip range is committed.You can check the contributions from the blocked ip range in it.wikipedia.org to verify my affirmation.So please review this six months global block and change its settings to allow normal users to make their usual constructive edits while preventing the abuser from creating new accounts.
Controversies:if there is no techical possibility to allow anonymous editing and prevent account creations perhaps the full block itself could be reconsidered.I have explained above that the abuser who caused the block had created so many accounts to spam messages about a votation which ended short after that.There is a very very little risk that the abuser restarts ceating accounts to spam messages so a block lasting till december is very likely no longer necessary.Users from this range who do not have accounts are prevented fro contributing for no reasons.The only reason that range was full of abuse was because of that damn abuser who created fake accounts in several different wikipedias.Or perhaps there is something else than that abuser that stewards know and in that case please explain what.I had a look at that range contrbutions in a few wikipedias and did not notice more abuse there than in any other normal ip range.Please read this final part abut possible controversies.
LuluGigi (talk) 14:31, 9 September 2019 (UTC)

Note: denied yesterday by the steward علاء (Alaa). Argumentum ad nauseam? Incnis Mrsi (talk) 20:19, 9 September 2019 (UTC)

I did not requested it again just to insist.I requsted it again because the reason given was false or a least not clear.This block does not affect anonymous users only.The correct sentence would be that already registered users only are not affected by it.The abuse this range is said to be full of is just that particular abuser's.Maybe there is something more than him that we do not know and in this case the stewards were asked by me to explain what but if there was only a single vandal casuing a lot of abuse in a lot of wikipedias spamming accounts and messages this is not a valid reason to block such a wide ip range for so long a time and the reasons are explained in the last point of my previous message.I am not going to insist until the ip rnge is unblocked.I just want stewards to give a valid reason to keep it blocked because it is almost sure that is will not run further risks of abuse from now to december.LuluGigi (talk) 14:14, 10 September 2019 (UTC)

Global block for webhost/proxies

Status:    In progress

Abused webhost/proxy (Psychz Networks, FranTech Solutions). See Stalktoy. --Zaxxon0 (talk) 07:09, 10 September 2019 (UTC)

Global block for GRP

Status:    In progress

See incubator:Special:Contributions/89.64.50.68 - GRP global ban evasion. Thanks, --DannyS712 (talk) 22:00, 10 September 2019 (UTC)

This one too... Nigos (talk) 23:42, 10 September 2019 (UTC)

Another IP used by GRP used to intimidate someone on eswiki. Nigos (talk) 23:55, 10 September 2019 (UTC)

Global block for 2402:1980::/32

Status:    In progress

Crosswiki vandalism. Blocked on 3 wikis.   — Jeff G. ツ please ping or talk to me 05:12, 11 September 2019 (UTC)

Global block for GRP

Status:    In progress

GRP is threatening to hack my account. Nigos (talk) 01:13, 13 September 2019 (UTC)

Another one. Nigos (talk) 01:40, 13 September 2019 (UTC)

+2 --DannyS712 (talk) 03:00, 13 September 2019 (UTC)

+1 --DannyS712 (talk) 03:26, 13 September 2019 (UTC)

Another one Nigos (talk) 01:35, 14 September 2019 (UTC)

Global block for 49.199.148.21

Status:    In progress
Cross-wiki abuse. see enwiki & metawiki contribs. --WhitePhosphorus (talk) 14:38, 16 September 2019 (UTC)

Global block for 203.64.161.183

Status:    In progress
Cross-wiki abuse (zhwiki, wikidata). --Xiplus (talk) 01:17, 17 September 2019 (UTC)

Global block for 186.138.241.200

Status:    In progress
Cross-wiki abuse. --Xiplus (talk) 08:50, 17 September 2019 (UTC)

Global block for 83.31.7.128

Status:    In progress

Crosswiki vandalism.   — Jeff G. ツ please ping or talk to me 10:54, 18 September 2019 (UTC)

Global block for HaionNet IP addresses

Status:    In progress

Abused webhost/proxy same as those blocked on September 15th. (HaionNet) --보네르 (talk) 11:50, 18 September 2019 (UTC)

Global Block for Denver LTA IPs

Status:    In progress

w:WP:LTA/DENVER. Rangeblocked on en Wikipedia. --IanDBeacon (talk) 15:00, 18 September 2019 (UTC)

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

Symbol comment vote.svg 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 your request 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-stewardsconnect or email your request to the stewards OTRS queue at stewards(at)wikimedia.org (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@wikimedia.org.
Instructions for making a request

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

  1. You have evidence of cross-wiki disruption from the account(s).
  2. You can show that it is not feasible to use local-only blocks or other measures like page protection to combat the disruption.
  3. You have considered making the request in #wikimedia-stewardsconnect, 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 [[User:Foo|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 Unlock for non LTAs

Status:    In progress

Lock all:

Reasons: This case is similar to Steward_requests/Global/2019-08#Global_unlock_for_innocent_users. First, they did not do any vandalism in Chinese Wikipedia and the editorial habits were not same as LTAs. Second, they are Mainland China user that they have used Simplified Chinese when they are editing, and they need to use the proxy to edit Wikipedia. So their IP address may same as some LTA. Third, some of zhwiki people think that may not be LTAs. Here is our discussion on VP. Please unlock these account. Thank you!--SCP-2000 (talk) 16:11, 8 September 2019 (UTC)

{{notdone}} They are LTAs beyond reasonable doubt. Ruslik (talk) 20:21, 11 September 2019 (UTC)
@Ruslik0: Could you please don't process this case because of the potential conflict of interest? Also please another steward process this case. Thank you! --SCP-2000 (talk) 08:52, 12 September 2019 (UTC)
This case should be processed by another steward. Ruslik0 has an obvious conflict of interest in this case, per common sense. A simple {{tl}} is made for instance. ΣανμοσαThe Trve Lawe of free Monarchies 04:29, 15 September 2019 (UTC)
I must state that, it is common and normal for Chinese users to browse wiki projects (inc. Wikipedia) with the aid of Proxy due to the affection of GFW. So, it is easy for stewards to get a false conclusion that some accounts are LTAs. I kindly ask any steward(s) applicable to unlock the accounts, thank you. ΣανμοσαThe Trve Lawe of free Monarchies 04:34, 15 September 2019 (UTC)

Global unlock for Ezekiel53746

Status:    In progress

Hi there. Copy and pasting from the e-mail I sent to stewards@wikimedia.org:

I made a Request for Comment to get this account unlocked back in September 2018 but it didn't work out. I am making another one because it's been a full year since I filed an appeal and I still want to get the account unlocked and overturn my ban on Wikipedia. I have no intention of continuing the disruptive behavior that got me banned in the first place: Sock puppetry, vandalism, general incompetence, I want to at least earn some degree of trust from the Wikipedia community back.

Any which way, I have been told that in order to overturn the block on my Wikipedia account I have to at least get it unlocked first.

Thank you for your consideration. --Zeke Essiestudy (talk) 02:21, 9 September 2019 (UTC)

Look, the account has positive contributions to Commons. Moreover, the SUL was locked more than six years ago. I know nothing about conduct of this user in these 6 years, but IMHO unlock should be granted if there was no serious disruption during the last year. Incnis Mrsi (talk) 20:07, 9 September 2019 (UTC)
{{done}} by Mathonius. Willy1018 (talk) 17:47, 13 September 2019 (UTC)
@Willy1018:This request is global unlock, not global lock. --SCP-2000 (talk) 18:42, 13 September 2019 (UTC)

Global lock for Kiko4564

Status:    In progress

Cross wiki vandalism on various wikis including enwiki, commons and simplewiki. Kiko4564 has also used a huge amount of sockpuppets in an unsuccessful attempt to avoid scrutiny. 51.7.158.45 00:11, 16 September 2019 (UTC)

Global lock for LTA WhenDatHotlineBling socks

Status:    In progress

Lock all:

Obvious socks of the LTA WhenDatHotlineBling, who is known for cross-wiki vandalism and trolling. Please run a sleeper check and Globally Block his IPs (usually Proxies or VPNs), because he is known for using sleeper accounts for vandalism. LightandDark2000 🌀 (talk) 02:33, 17 September 2019 (UTC)

@Ruslik0, Bsadowski1, and Stryn: Can you please lock this LTA's accounts? He's still active right now. Thanks. LightandDark2000 🌀 (talk) 09:04, 17 September 2019 (UTC)

Lock all:

Adding a bunch more socks and IPs - not sure if I should be adding them here or in a new section, but these all fit the same pattern. Bradv🍁 13:24, 18 September 2019 (UTC)

Global lock for cross-wiki abuse and LTA

Status:    In progress

Lock all:

Lock all:

Same user of Special:CentralAuth/史上最囂張破壞者韓導,also,I hope to check whether there have sleepers and block their IP(s)/IP range(s) if they have create account,thanks.--MCC214#ex umbra in solem 10:12, 17 September 2019 (UTC)

Global lock for cross-wiki abuse and LTA

Status:    In progress

Lock all:

Sock of Special:CentralAuth/Xayahrainie43,also,I hope to check whether there have sleepers and block their IP(s)/IP range(s) if they have create account,thanks.--MCC214#ex umbra in solem 10:14, 17 September 2019 (UTC)

Global lock for cross-wiki abuse and LTA

Status:    In progress

Lock all:

Sock of Special:CentralAuth/3GFRIENDSNSD,also,I hope to check whether there have sleepers and block their IP(s)/IP range(s) if they have create account,thanks.--MCC214#ex umbra in solem 11:27, 17 September 2019 (UTC)

Global lock for Thebestsholaraglossologistever

Status:    In progress

Cross-wiki vandalism. — surjection 〈?〉 20:25, 17 September 2019 (UTC)

Global lock

Status:    In progress
Long-term abuse. Cross-wiki abuse. --Xiplus (talk) 00:22, 18 September 2019 (UTC)
Same user of Special:CentralAuth/史上最囂張破壞者韓導,also,I hope to check whether there have sleepers and block their IP(s)/IP range(s) if they have create account,thanks.--MCC214#ex umbra in solem 06:18, 18 September 2019 (UTC)

Global lock for cross-wiki abuse and LTA

Status:    In progress

Lock all:

It looks like a duck to me LTA,Impersonator of my user name and me,also,I hope to check whether there have sleepers and block their IP(s)/IP range(s) if they have create account,thanks.--MCC214#ex umbra in solem 06:23, 18 September 2019 (UTC)

Global lock for cross-wiki abuse and LTA

Status:    In progress

Lock all:

Same user of Special:CentralAuth/坦帕灣光芒460,also,I hope to check whether there have sleepers and block their IP(s)/IP range(s) if they have create account,thanks.--MCC214#ex umbra in solem 08:27, 18 September 2019 (UTC)

Global lock

Status:    In progress
Long-term abuse. --Xiplus (talk) 09:19, 18 September 2019 (UTC)
Same user of Special:CentralAuth/史上最囂張破壞者韓導,also,I hope to check whether there have sleepers and block their IP(s)/IP range(s) if they have create account,thanks.--MCC214#ex umbra in solem 09:25, 18 September 2019 (UTC)

Global lock for 黒瀬さん

Status:    In progress

Cross-wiki vandalism. He is opened his password for JAWN. He calls himself JAWP blocked account User:ウルトラひかり.--アルトクール (talk) 14:29, 18 September 2019 (UTC)

Global lock for It's gonna be awesome

Status:    In progress

Cross-wiki vandalism. indef-ed on 4 wikis. --痛心疾首 (talk) 14:31, 18 September 2019 (UTC)

Global lock for Sockpuppet

Status:    In progress

Username violation/sock of User:John574. --IanDBeacon (talk) 15:12, 18 September 2019 (UTC)

Global lock for 2 spambot accounts

Status:    In progress

Lock all:

Spambot accounts, blocked on nl.wiktionary after attempts to add blacklisted links. --MarcoSwart (talk) 19:24, 18 September 2019 (UTC)

Global lock for PavelMuhin99

Status:    In progress

Sockpuppet of global locked User:Панн. --A.Savin (talk) 19:28, 18 September 2019 (UTC)

Global lock for Yahadzija

Status:    In progress

Ban evasion, sock of User:Yahadzija. --Zaxxon0 (talk) 21:50, 18 September 2019 (UTC)

Global lock for LTA Arturo Gustavo socks

Status:    In progress

Lock all:

Socks of the LTA Arturo Gustavo. Please run a sleeper check and Globally Block the IP(s) as well, because he often uses his IPs for cross-wiki trolling. LightandDark2000 🌀 (talk) 02:23, 19 September 2019 (UTC)

See also

Cooperation requests for: comments (local) (global) · translation

Retrieved from "https://meta.wikimedia.org/w/index.php?title=Steward_requests/Global&oldid=19393030"