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
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 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 global 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.
LuluGigi (talk) 09:39, 2 August 2019 (UTC)

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 for 2600:1700:8b60:ca00::/64

Status:    In progress

Cross wiki abuse; BLP violations. --Zaxxon0 (talk) 10:23, 3 August 2019 (UTC)

Global block for Year LTA

Status:    In progress

Persistent cross-wiki vandalism for the past several months (going back more than a year on en.wiki). This person has vandalized en.wiki, es.wiki, pt.wiki, fr.wiki, de.wiki, and Simple Wikipedia recently (other sites are probably affected as well). Most of the abuse involves date-changing vandalism and BLP vandalism (including attacks). The LTA appears to be the only person using this range, and there are almost no positive contributions on any wiki in the past year. After being rangeblocked on en.wiki in June, they took their vandalism cross-wiki again, most notably on simple.wiki. Please block the range (set to "anon-only") for at least 6 months. LightandDark2000 🌀 (talk) 17:45, 5 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 125.27.0.0/16

Status:    In progress

Proxys abuse only [5] --WikiBayer 👤💬 19:56, 7 August 2019 (UTC)

Global block GRP evasion

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.   — Jeff G. ツ please ping or talk to me 15:10, 18 August 2019 (UTC)

Global block for 185.174.156.0/22

Status:    In progress

Abused webhost/proxy (HostRoyale). --Zaxxon0 (talk) 09:26, 9 August 2019 (UTC)

Global block for 45.70.0.0/17

Status:    In progress

Proxies Spambots and abuse only. https://tools.wmflabs.org/meta/stalktoy/45.70.0.0%2F17 --WikiBayer 👤💬 08:30, 10 August 2019 (UTC)

Global block for Proxies Spambots

Status:    In progress

See here [6] --WikiBayer 👤💬 11:41, 11 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)

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 lock for offensive username

Status:    In progress

Makes fun of abortion. Also, only edit was spam creation at sv:Fysik_2. Thanks, --DannyS712 (talk) 00:38, 13 August 2019 (UTC)

Global lock for xwiki spammer (Bhartiya rashtriya)

Status:    In progress
Praxidicae (talk) 13:32, 14 August 2019 (UTC)

Global lock for xwiki vanity spammer

Status:    In progress
I'm pretty sure there's an actual master already locked but I can't recall the name but it's fairly obvious. Praxidicae (talk) 18:48, 15 August 2019 (UTC)

Global lock for more Yash Shah vanity spammers

Status:    In progress
see Mike walt for an example of past locked socks. Praxidicae (talk) 19:38, 15 August 2019 (UTC)

Global lock for LTA WhenDatHotlineBling socks

Status:    In progress

Lock all:

Obvious socks of the LTA WhenDatHotlineBling, given the behavior. Please check for sleepers and Globally Block their IPs, since they are known for generating sleeper accounts and trolling while logged out. Additionally, all of the listed IPs are either Open Proxies or VPN networks, so please block those as well. LightandDark2000 🌀 (talk) 01:21, 16 August 2019 (UTC)

@Ruslik0, Bsadowski1, and Tegel: Can you please take care of this one? Thanks. LightandDark2000 🌀 (talk) 21:49, 17 August 2019 (UTC)

Global lock for some accounts

Status:    In progress

Lock all:

User name personal attacking,request for this zh.wiki request,we hope to check whether there have sleepers and check their relationship,also,block their IP(s)/IP range(s) if they have create account,thanks.--MCC214#ex umbra in solem 10:32, 16 August 2019 (UTC)

Global lock for vanity spammer

Status:    In progress
See Analpa12, N.K.MONDAL etc... Praxidicae (talk) 12:46, 16 August 2019 (UTC)

Global unlock for innocent users

Status:    In progress

Both users were locked as the result of a recent check on an LTA on Chinese Wikipedia. However, we are confident that both users are NOT the LTA himself for clear behavioral evidence. Please unlock these accounts immediately or it would be definitely bad for newbies. --TechyanTalk) 14:06, 16 August 2019 (UTC)

I don't know are they innocent or not, however, there is a huge local discussion where many users expresses their faith that the user is innocent. I have no comments on this case but I wish that the stewards can make a through investigation and hope that this can be resolved as soon as possible. I hope that more information can be given (like the ISPs / UA used) and how the stewards make determination that the users are socks of NDC. Thanks much. --Cohaf (talk) 11:02, 17 August 2019 (UTC)
The first user is (from CU point of view) indistinguishable from 哀悼中國共產黨竊國70週年: the same IP, the same UA string and created just a few hours apart. Ruslik (talk) 08:02, 18 August 2019 (UTC)

Global lock for 4 spambot accounts

Status:    In progress

Lock all:

Spambot accounts, blocked on nl.wiktionary after attempts to add blacklisted links or triggering global filter 69 or 72. --MarcoSwart (talk) 12:28, 17 August 2019 (UTC)

Global lock for socks of locked Garwel

Status:    In progress

Lock evasion. Please also monitor c:Category:Sockpuppets of Garwel.   — Jeff G. ツ please ping or talk to me 03:11, 18 August 2019 (UTC)

Global lock for Albert_Giban86 and socks

Status:    In progress

Main account was only blocked on one project, but sockpuppets involved in cross-wiki abuse. See commons:Category:Sockpuppets_of_Albert_Giban86 (Gimbalpapuaalbert Papuaalbertgiban has already been locked). --94rain Talk 06:21, 18 August 2019 (UTC)

Global lock for Wonderfool socks

Status:    In progress

Lock all:

These appear to be socks of Wonderfool and the others recently discovered (Cyckleletya, ChubbEdtres, Brusher21a, Mookar21a, and Lifer616) have already been locked by Ruslik0. Please see the enwiki Sockpuppet Investigation. --TheSandDoctor Talk 16:18, 18 August 2019 (UTC)

Global lock for long-term abuser and dewiki global ban-evading sockpuppet of Avoided

Status:    In progress

Der, der nix über Enissa weiß, aber mehr als du (talk • contribs • block • xwiki-contribs • xwiki-date • CA • ST • lwcheckuser)

Sock puppet of globally locked user Avoided. Indonesia Kita Wiki yang adil, makmur dan sejahtera yang membangun bangsa dan negeri! (talk) 20:22, 18 August 2019 (UTC)

Global lock for Ritiksharmanew

Status:    In progress

New sock puppet of Yash gawli. Эlcobbola talk 20:29, 18 August 2019 (UTC)

+1 Эlcobbola talk 20:40, 18 August 2019 (UTC)
+1 Эlcobbola talk 20:46, 18 August 2019 (UTC)

Global lock for various accounts

Status:    In progress

Lock all:

Cross-wiki abuse. -★- PlyrStar93 Message me. 00:05, 19 August 2019 (UTC)

Global lock for MCC216

Status:    In progress

Lock all:

Cross-wiki abuse; impersonation of MCC214 94rain Talk 03:58, 19 August 2019 (UTC)

See also