Steward requests/Global

From Meta, a Wikimedia project coordination wiki
< Steward requests(Redirected from SRG)
Jump to: navigation, 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 block 2600:8800:3000:0:0:0:0:0/36

Status:    In progress

Block evasion by globally locked user MisterAnthony. He has been occasionally active on Interlingua wikipedia as various IPs since the locking of his named account:

with a sudden recent flurry of activity:

His signature on iawiki is the creation of micro-stub articles for U.S. actors, each containing one sentence in Interlingua and another in Spanish, partly redundant with the first (ia:Special:Diff/592001). The wikidata item histories indicate he creates similar fill-in-the-blanks micro-stubs for the same actor in dozens of other small languages, together with messing around with wikidata itself.

I havve blocked the /36 on iawiki for 6 months and don't expect collateral problems, based on the size of iawiki and observation of the contributions in the range. There have been previous global blocks within the range:

The 3081 range above is probably stale. The 3080 and 3982 have received blocks as just mentioned. The 3981 is new. If /36 is excessive for a global block, may I suggest:

(Incidentally, a new named account has just appeared: AnthonyAW. Even with only 4 edits, it looks like a sock of this user. Will bear watching.)

--Tortoise0308 (talk) 19:25, 11 January 2018 (UTC)

Global block for the boy band vvandal

Status:    In progress

Cross-wiki vandal (see also en:Wikipedia:Long-term_abuse/Boy_band_vandal) active for more than 10 days. --Horcrux92 (talk) 08:36, 31 January 2018 (UTC)

Could somebody please action this? Also 2001:56a:f580::/41 would need to be blocked, per the last requests linked from the abuse report. Graham87 (talk) 07:16, 27 February 2018 (UTC)
Also, account creation should be allowed, due to collateral damage. I've just found out that the strongest block will apply for IP addresses which have been both locally and globally blocked, so if account creation were disabled in the global block, that would undo the account-creation-enabling effect of the local one. Graham87 (talk) 16:15, 1 March 2018 (UTC)
Graham87, that is not possible: "Global blocks should, wherever practicable and sensible, be placed with the anonymous only flag on. Remember that even in this case account creation from the blocked address(es) is prevented." @ Global blocks. Emphasis mine. — regards, Revi 10:39, 24 March 2018 (UTC)
@Revi: Ah OK; thanks for letting me know. I'd only heard one report of collateral damage in a year, so ... meh. Graham87 (talk) 13:31, 24 March 2018 (UTC)
Also add 2001:56a:f104:b300::/64 and 75.159.116.143 cross-wiki-contribsSTIP inforobtexgblockglist to the list. Graham87 (talk) 19:00, 1 April 2018 (UTC)
Ditto with 199.126.52.20 cross-wiki-contribsSTIP inforobtexgblockglist. Graham87 (talk) 11:39, 5 April 2018 (UTC)

Global block for 2605:380:32:495:43F2:A1::/96

Status:    In progress

Please, hard-block for a year. It seems to me that the entire /96 IPv6 range, or at very least 2605:380:32:495:43F2:A1::/112 cross-wiki-contribsSTIP inforobtexgblockglist—216 addresses—is allocated to a globally banned long-term abuser or somebody impersonating him. See c:Special:Contributions/2605:380:32:495:43F2:A1::/112 for details, note two distinct IPv6s. Incnis Mrsi (talk) 19:29, 26 March 2018 (UTC)

From a theoretical point of view minimum prefix length to block should be 64 bits. --Vituzzu (talk) 19:32, 26 March 2018 (UTC)
Blocked IPv6 prefixes both broader and narrower than /64 exist in Wikimedia. The former are up to /32 which is rather common in en.Wikipedia. The latter are usually point blocks (/128), but sometimes /96. From my layman’s understanding, IPv6 prefix specification may “theoretically” be any integer from /0 to /128 inclusively, although MediaWiki refuses to handle anything broader than /32 for security reasons. If one can mount a valid objection against blocking this /96—an insignificant portion of all IPv6 Internet—then formulate it clearer, please. I have difficulty comprehending an oracle’s remark above. Incnis Mrsi (talk) 21:02, 26 March 2018 (UTC)

Global block for 106.187.0.0/16

Status:    In progress

Colocated webhosts with open proxies and active blocks on 10 wikis.   — Jeff G. ツ 12:56, 29 March 2018 (UTC)

@Jeff G.: I see 106.187.0.0/18 cross-wiki-contribsSTIP inforobtexgblockglist and 106.187.96.0/21 cross-wiki-contribsSTIP inforobtexgblockglist blocked in en. in ru.wikipedias, but these ranges combined are more than three times smaller than /16. In which namely wikis such large range as /16 is blocked? In any case, a more solid substantiation should be presented for request to block 216 IPv4 addresses. Incnis Mrsi (talk) 06:22, 30 March 2018 (UTC)
@Incnis Mrsi: Please see this block log (in Japanese) at Japanese Wiktionary.   — Jeff G. ツ 10:29, 30 March 2018 (UTC)

Global blocks for spambot webhosts

Status:    In progress

Webhosts used by spambots. MER-C (talk) 12:18, 30 March 2018 (UTC)

IPVanish VPN used for spamming. MER-C (talk) 13:59, 30 March 2018 (UTC)

PureVPN plus webhost range used for spamming. MER-C (talk) 16:29, 16 April 2018 (UTC)

  • [1] GZ systems = PureVPN. Doing some... — regards, Revi 18:08, 20 April 2018 (UTC)

Same spam, different day. MER-C (talk) 17:08, 21 April 2018 (UTC)

Global block for 95.26.0.0/16

Status:    In progress

Hello. This user is:

  1. repeatedly adding false information
  2. been blocked several times for vandalism on en.wp, and globally blocked (95.26.18.111) for long-term abuse
  3. abusing many projects since (at least) mid-June 2017, cf. the list above
  4. ignoring the comments from other contributors, cf. my last attempt of discussion, one of my other attempts of discussion, en:User talk:95.26.222.66, en:User talk:95.26.140.56, etc.
  5. the unique user of 95.26.0.0/16 since mid-June 2017 (except for a few edits that might be from someone else: 6 edits on commons, 109 (out of 245) on en.wp, 2 on fr.wp, 1 on fr.wiktionary, 6 on it.wp, etc.)
  6. sometimes (but more often in the past) using 95.25.0.0/16 and 176.59.0.0/16.

Regards --NicoScribe (talk) 17:15, 20 April 2018 (UTC)

@NicoScribe: did anybody try to complain to the ISP? There are many legitimate users in this /16 range. It is not a hosting making its business exactly for housing trolls and other scum. Incnis Mrsi (talk) 19:31, 20 April 2018 (UTC)
@Incnis Mrsi: thank you for your comments. I am sorry, I have made a mistake in my item 5: the Russian Wikipedia is the unique project with many legitimate contributions in this /16 range. So a local unblocking should be applied on the Russian Wikipedia.
I have not made a complaint to the ISP. But this user is just a cross-wiki long-term abuser, and there are many cross-wiki long-term abusers, and most of the time their cases are managed with blocks or filters. If this case is managed by a complaint to the ISP, I would be surprised (but I rarely report cases of cross-wiki long-term abusers, and of course I don't have the experience of a steward). --NicoScribe (talk) 06:18, 21 April 2018 (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 global locked, you may appeal here without logging in. If you don't want to leak your IP address, you can also 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 the template 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, --~~~~

Global unlock for Virajmishra

Status:    In progress

yes i have readed so I came after 3 month. And i don't have any other account neither i have created any editing. Please remove global blocking of my account. In future i will never ever try to make any account. Please unlock my this account virajmishra account as soon as possible. Thanks.2405:204:A582:4B02:D7C8:CAC0:877B:BA1D 07:25, 9 April 2018 (UTC)

@Ruslik0: User appealing this at my talk page. SA 13 Bro (talk) 11:36, 9 April 2018 (UTC)
What projects are you going to edit? Even if I unlock your account, you will remain blocked in English Wikipedia and Commons. Ruslik (talk) 20:05, 12 April 2018 (UTC)
This page is semi-protection, please answer your statement to Ruslik0 at your own talk page only. @Ruslik0: He also appealing the unblock request on English Wikipedia in not very long ago, have a look on this reviewed comment by admin Boing! said Zebedee. SA 13 Bro (talk) 21:26, 12 April 2018 (UTC)

Global lock for 8 socks of Ven0m2014

Status:    In progress

A cross-wiki copyvioman and sock puppeteer—ru.Wikipedia, Commons—also of bad conduct (harassment). Indefblocked on Commons. Incnis Mrsi (talk) 22:08, 21 April 2018 (UTC)

Five socks more. At this point, locking the master Ven0m2014 (talk • contribs • block • x-wiki • CA • lwcheckuser) can be considered as well. Incnis Mrsi (talk) 09:27, 22 April 2018 (UTC)

4 more socks:

I would also ask for complete removal of the 2 accounts that were created to mock my username. --Túrelio (talk) 15:42, 22 April 2018 (UTC)

Global lock for Portunick

Status:    Done

Confirmed by me on this SPI, as a sock of Tertulius, already locked globally. EVinente (talk) 00:35, 22 April 2018 (UTC)

Yes check.svg Done --Alaa :)..! 14:59, 22 April 2018 (UTC)

Global lock for Nipponese Dog Calvero

Status:    In progress

LTA - socks of Nipponese Dog Calvero. -★- PlyrStar93. Message me. 00:40, 22 April 2018 (UTC)

Global lock for vandalism-only accounts

Status:    Done

Cross-wiki abuse, vandalism. -★- PlyrStar93. Message me. 00:40, 22 April 2018 (UTC)

Yes check.svg Done --Alaa :)..! 14:57, 22 April 2018 (UTC)

Global lock for 쒸발새끼

Status:    Done

Vandalism, sock of 대우건설. -★- PlyrStar93. Message me. 00:44, 22 April 2018 (UTC)

Yes check.svg Done --Alaa :)..! 14:54, 22 April 2018 (UTC)

Global lock for Lendariomusiiiik

Status:    Done

WP0 abuser. --jdx Re: 08:00, 22 April 2018 (UTC)

Yes check.svg Done --Alaa :)..! 12:47, 22 April 2018 (UTC)

Global lock for Albert20009's sockpuppet

Status:    Done

Long-term abuse. --Ilzhabimantara (talk) 08:31, 22 April 2018 (UTC)

Yes check.svg Done --Alaa :)..! 12:47, 22 April 2018 (UTC)

Global lock for Antonius Ernestius

Status:    Done

WP0 abuser. --jdx Re: 10:28, 22 April 2018 (UTC)

Yes check.svg Done --Alaa :)..! 12:48, 22 April 2018 (UTC)

Global lock for LTA:ISECHIKA Sockpuppet User:プログラマリオ 春のパン祭り

Status:    Done

Japanese Wikipedia is Long-Term Abuse:LTA:ISECHIKA Sockpuppet.荒巻ストイチコフ (talk) 12:25, 22 April 2018 (UTC)

Yes check.svg Done --Alaa :)..! 14:53, 22 April 2018 (UTC)

Global lock for Fernandopinto421

Status:    Done

WP0 abusers. --jdx Re: 14:47, 22 April 2018 (UTC)

Yes check.svg Done --Alaa :)..! 14:49, 22 April 2018 (UTC)

Global lock for Alvi2006

Status:    Done

Sock of Alvi Z. -★- PlyrStar93. Message me. 15:47, 22 April 2018 (UTC)

Yes check.svg Done --Alaa :)..! 15:49, 22 April 2018 (UTC)

Global lock for Dj.sipho2016

Status:    Done

WP0 abuser. --jdx Re: 17:19, 22 April 2018 (UTC)

Yes check.svg Done Ruslik (talk) 19:31, 22 April 2018 (UTC)

Global lock for Дима Хван

Status:    In progress

Long-term abuse, Liza Veniza's sock. Marshmallych ?! 18:43, 22 April 2018 (UTC)

Global lock for Alvi Z. sock

Status:    Done

Long-term abuse. theinstantmatrix (talk) 22:07, 22 April 2018 (UTC)

Yes check.svg Done. Green Giant (talk) 23:29, 22 April 2018 (UTC)

Global lock for Neooxopus

Status:    In progress

New sock puppet of Yahadzija. Эlcobbola talk 22:31, 22 April 2018 (UTC)

Global lock for Essjaey/Cruizir sock

Status:    In progress

Sock of cross-wiki vandalism user Essjaey. -★- PlyrStar93. Message me. 00:19, 23 April 2018 (UTC)

Global lock for INeverCry sock

Status:    In progress

Sock of INeverCry. -★- PlyrStar93. Message me. 00:41, 23 April 2018 (UTC)

Global lock for spambots

Status:    In progress

Obvious spambot accounts. Given the recent user interactions, they appear to be operated by the same spammer (also see their edit filter logs). LightandDark2000 (talk) 04:14, 23 April 2018 (UTC)

The third spambot account is unrelated to the first 2, but this user is posting disturbing NSFW/explicit content on Wikipedia, so the account needs to be Globally Locked. LightandDark2000 (talk) 04:25, 23 April 2018 (UTC)

Global lock for Kavayahosten

Status:    In progress

WP0 abuser. --jdx Re: 05:26, 23 April 2018 (UTC)

Global lock for Albert20009's sockpuppets

Status:    In progress

Long-term abuse. --Ilzhabimantara (talk) 05:27, 23 April 2018 (UTC)

Global lock for cross-wiki LTA ROXELANA22 sock

Status:    In progress

Obvious sock/sleeper account of the cross-wiki LTA User:ROXELANA22. This user has been known for persistently vandalizing articles across multiple Wikimedia sites for 12 years, inserting extremely graphic/obscene content into articles (which required those edits to be deleted) attacking other users, issuing indirect death threats, and serial socking cross-wiki. Since this user is known for migrating locally-blocked socks to resume vandalism on other sites, and also re-using years-old sock accounts (at least going back 6 years), all of his socks need to be Globally Locked. LightandDark2000 (talk) 06:20, 23 April 2018 (UTC)

Global lock for "Fuerdai" socks

Status:    In progress

Cyp (talk) 06:24, 23 April 2018 (UTC)

Global lock for Blackmarch103

Status:    Done

Interwiki Spambot, please also delete contribs. --Pentachlorphenol (talk) 07:37, 23 April 2018 (UTC)

Done, but almost all of the wikis there have active admins so barring our deletion. — regards, Revi 07:43, 23 April 2018 (UTC)

See also