Steward requests/Global

From Meta, a Wikimedia project coordination wiki
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, link to the username of the steward who globally blocked the IP address using the code [[User:USERNAME|USERNAME]] so that they are pinged by 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 email using this form or writing at stewards-at-wikimedia.org.

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

Cross-wiki requests
Meta-Wiki requests

Contents


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 http://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 46.101.128.0/17

Status:    In progress

46.101.128.0/17

This range belongs to Deutsche Telekom, probably the largest provider in Germany --Eingangskontrolle (talk) 18:47, 14 January 2018 (UTC)

Then BGP info says otherwise. According to that, 46.101.128.0/17 belongs to Digital Ocean which is a web hosting service. -★- PlyrStar93. Message me. 18:52, 14 January 2018 (UTC)
I would agree with PlyrStar. As the WHOIS tool on Labs and RIPE itsself would confirm this. --Wiki13 talk 18:58, 14 January 2018 (UTC)

139.59.0.0/16. the same thing - I am a customer of Deutsche Telekom and I am again blocked after two edits 139.59.147.242 --Eingangskontrolle (talk) 19:06, 14 January 2018 (UTC)

That one's still Digital Ocean. I also did a traceroute from my network to the IP's you mentioned, and the packet never goes through Deutsche Telekom's nodes, while I did another traceroute for a Deutsche Telekom (AS3320) IP and I can see hops belonging to that network. Maybe you should check if your computer has certain VPN services enabled, and see if there are potentially unwanted programs hijacking your traffic, and use different devices under the same network (e.g. cell phone etc. connected to your wifi) and see if they still give you the same IP as the current device you are using. -★- PlyrStar93. Message me. 19:19, 14 January 2018 (UTC)
I would say the use has some kind of VPN service running, cause otherwise you wouldn't end at Digital Ocean. If this is indeed the case maybe a global IP exempt could be granted to the account. --Wiki13 talk 19:28, 14 January 2018 (UTC)

Global block for 47.74.0.0/18, 198.13.32.0/19, 2a0b:4342:4000::/36, 2400:8900::/30, and 47.91.0.0/19

Status:    In progress
  1. Those IP addresses belong to companies who provide VPS services which can be used for open proxies.
  2. Those IP ranges were related to disruptive editing on Chinese Wikipedia involved posting rumors and attacking informations of Wikimedia User Group China (WUGC) and discrimination article content against Shanghai immigrants (e.g. [1], [2], [3], [4], [5]).
  3. A subset of 2400:8900::/30 has already been globally blocked by Vituzzu.
  4. This edit reveals that 守望者爱孟 (who's been banned globally by WMF) was related to this proxy. (He deleted the response from 守望者爱孟 and wrote this in the summary: "有啥好回应的,谁爱撕谁撕,谁爱封谁封,封一个号这么爽,我滋磁"; translation: There's nothing needed to be responded. Enjoy your quarrel and block. [If ]blocking one account gives you such pleasure, I support [you in doing it].).
  5. The first two IP ranges was unblocked in Chinese Wikipedia by User:Techyan who is one of the liaisons of Wikimedians of Mainland China (WMC).
  6. There is a competition between the WMC and WUGC, and members of WMC have posted a lot of rumors and attacking informations against WUGC on Chinese Wikipedia (see the history of WP:中国维基媒体用户组). I didn't believe that the Chinese Wikipedia can prevent those edits happening again in the future. --PhiLiP (talk) 10:26, 28 December 2017 (UTC)

I totally have no idea why you mentioned me. That's a nonsense to global block IP ranges without being abused globally. Tons of excuses, none of them are related to cross-wiki vandalism. --TechyanTalk) 21:43, 29 December 2017 (UTC)

The policy states that "[g]lobal blocks should only be placed where ... local blocks... would be ineffective, or inefficient." Given that there are admins actively sabotaging the local effort to contain vandals, escalating to global blocks is not only suitable, but necessary. -Mys_721tx (talk) 20:45, 31 December 2017 (UTC)
When banning PhiLiP and Mys 721tx globally, Wikipedia will be peaceful.Gszq (talk) 07:10, 3 January 2018 (UTC)

Global block for Special:Contributions/2804:431:d718::/47

Status:    In progress

Cross-wiki vandalism. Repetitively adds and removes whitespace characters. This IP range was globally blocked in September 2017 and has become active again on several wikis. NinjaRobotPirate (talk) 01:01, 7 January 2018 (UTC)

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 unblock 85.174.236.106

IP 85.174.236.106 is owned by Hotel and it is not Open Proxy, a lot of times before I could easily use Wiki in hotels but now I watch a message that I signed in via open proxy and it was blocked. Voltmetro (talk) 17:11, 12 January 2018 (UTC)

Global block for 188.32.0.0/16

Status:    In progress

Cross-wiki adding vandalism/spam. Виталий Мирный (talk) 20:38, 16 January 2018 (UTC)

Global block for Special:Contributions/95.186.228.102

Status:    In progress

IP sock of cross-wiki date vandal User:Aliabbashiraqi79. See, for example, [6] and [7]; [8] and [9]. NinjaRobotPirate (talk) 01:38, 20 January 2018 (UTC)

Global block for 188.32.0.0/17

Status:    In progress

IP sock of cross-wiki date vandal User:Никита-Родин-2002. Locked in ruwiki Виталий Мирный (talk) 17:38, 20 January 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.
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 Diegusjaimes

Status:    On hold

Hi, I'm not a normal IP. I am the same user. I can't edit with my original account, because this actually locked, and i can't access its. I request unlock and ask for forgiveness for the damages caused at this time. Thanks in advance --181.61.83.227 03:25, 27 July 2017 (UTC) PD: Sorry for my english

To the Stewards, Bernard is a CU and can confirm a new block evasion [10] --Ks-M9 [disc.] 16:24, 28 July 2017 (UTC).
I created it simply to continue editing. There is no vandalism or anything bad. I am worried that Wikipedia in Spanish will be so drastic with users who want to edit for the first time, or who want to resume editing, and I am also puzzled by the fact that they consider everyone as a "toxic element" to Anyone who gets blocked. 181.61.83.227 18:23, 28 July 2017 (UTC) PD: The last text is traduced by Google"
See w:WP:BE and w:WP:SOCK - Using other account to continue editing while blocked is not permitted in most Wikimedia projects, even if the editor only makes good edits.
  • For Diegusjaimes: I suggest you do no edit in Spanish Wikipedia, using any account or anonymously, in no less than six months (i.e. until at least 2018-1-29) and request an unblock there. You're free to contribute other Wikimedia projects once you are unlocked.
  • For stewards: I think the account can be unlocked as long as there're no longer crosswiki issue. This allows user to make significant and useful contributions to other WMF projects (which is beneficial for unblocking in eswiki).

--GZWDer (talk) 19:18, 28 July 2017 (UTC)

Comment. I believe that the initial lock is wrong on a number of grounds. 1) Socking has no impact upon the use of the primary account. 2) Socks are not against WMF terms and use, and the use of global lock is not for this purpose of locking primary accounts. If the user is to be excluded we should be using a consensus of the community discussed in a global ban rather than summary exclusion by judge and jury stewardry.  — billinghurst sDrewth 22:07, 5 September 2017 (UTC)

Global unlock for Celestianpower

Status:    On hold

I am not sure why my account was blocked in the first place. It says my account was compromised and so globally blocked, but I see no evidence of this in my contributions. I used to be an administrator on en-wikipedia and en-wiktionary but I have been inactive for a while. Looking to make some sporadic edits, but unable to log in. The message on my en-wikipedia talk page says that I should contact a steward to have it reversed. Is this the correct channel for that? Thanks! —The preceding unsigned comment was added by 109.181.34.182 (talk) 22:30, 29 October 2017‎ (UTC)

Your account was locked by WMF staff due to account compromised in the past. @Tim Starling (WMF): There is a unlock requests issue at here. SA 13 Bro (talk) 23:25, 29 October 2017 (UTC)
I was watching filtered authentication logs and saw the attacker successfully log in to your account in real time. So I locked it immediately, before they were able to do any damage. This attacker typically defaced the English Wikipedia main page within minutes of each account compromise, so it was important to act quickly. The attacker was using publicly available password databases from other websites, such as Yahoo and LinkedIn, correlating email addresses with user names, and trying the passwords against Wikipedia. So it's important that you change your password on any website where you've been using it. See https://haveibeenpwned.com/ -- Tim Starling (WMF) (talk) 23:47, 29 October 2017 (UTC)
@Tim Starling (WMF): Thank you for alerting me. That's quite worrying. So if I change my password, am I able to continue using this account? Thanks 109.181.34.182 00:04, 30 October 2017 (UTC)
Yes, you can continue to use that account. I assume you still have access to your email? A steward should contact you, confirm your identity, unlock your account, and give you advice on setting up 2FA. -- Tim Starling (WMF) (talk) 02:00, 30 October 2017 (UTC)
@Tim Starling (WMF): That's great news. Happy to set up 2FA. When might a steward contact me and through what channel? Email? Thanks, 109.181.34.182 12:41, 30 October 2017 (UTC)
You should e-mail stewards@wikimedia.org if you want your account unlocked. Ruslik (talk) 19:47, 30 October 2017 (UTC)
The related ticket on OTRS is ticket:2017103110006322. Trijnsteltalk 22:37, 27 November 2017 (UTC)

Global lock for PavelStaykov's socks

Status:    In progress

Cross-wiki issues, socks are CU confirmed on enwiki. SPI: en:Wikipedia:Sockpuppet investigations/PavelStaykov - master is PavelStaykov. -★- PlyrStar93. Message me. 20:54, 8 January 2018 (UTC)

Global lock for Tamara787 socks

Status:    In progress

Cross-wiki issues with Tamara787. CU confirmed at enwiki. -★- PlyrStar93. Message me. 14:59, 13 January 2018 (UTC)

Global lock for Дима В

Status:    In progress

Long-term abuse. Locked in ruwiki. Виталий Мирный (talk) 17:25, 18 January 2018 (UTC)

Global lock for Hamza Ameer Raikoti

Status:    In progress

Cross-wiki abuse, socks of Ameer Hamza Raikoti. -★- PlyrStar93. Message me. 17:30, 18 January 2018 (UTC)

Global lock for NikitaSadkov

Status:    In progress

Long-term abuse. Locked in ruwiki. Виталий Мирный (talk) 17:40, 18 January 2018 (UTC)

Is (s)he a cross-wiki LTA? if yes, who? Matiia (talk) 17:43, 18 January 2018 (UTC)
Russians, affiliated with Kremlin, just started a global campaign against me, after banning me on RU-WP for a single edit, removing unsupported and false assessment of "terrorist" from Russian version of article on Amir Khattab. That is purely political persecution. NikitaSadkov (talk) 05:03, 19 January 2018 (UTC)
You are lying. I have never edited ru-wp, before that single edit on Amir Khattab. You have just noticed my Ukrainian IP, then instantly perma-banned me, leaving out even the "request unblock" option. Then again, I'm a citizen of Russia, even if forced to hide in Ukraine, due to being persecuted by Russian government for my poetry, so I have the right to edit Russian language wiki. NikitaSadkov (talk) 05:13, 19 January 2018 (UTC)

Global lock for Samsung Galaxy S

Status:    In progress

Long-term abuse. Locked in ruwiki and itwiki. Виталий Мирный (talk) 17:43, 18 January 2018 (UTC)

Global lock for Группа Кефир

Status:    In progress

Long-term abuse. Locked in ruwiki. Виталий Мирный (talk) 17:48, 18 January 2018 (UTC)

Global lock for Samsung Galaxy Note

Status:    In progress

Long-term abuse. Locked in ruwiki. Виталий Мирный (talk) 17:50, 18 January 2018 (UTC)

Global lock for Строгино

Status:    In progress

Long-term abuse. Locked in ruwiki. Виталий Мирный (talk) 17:53, 18 January 2018 (UTC)

Global lock for spambots

Status:    Done

Spambots. Wiki13 talk 23:08, 18 January 2018 (UTC)

Done. RadiX 03:48, 19 January 2018 (UTC)

Global lock for Rosy-Goggles

Status:    Done

Cross-wiki abuse (sock of Dopenguins). -★- PlyrStar93. Message me. 06:08, 19 January 2018 (UTC)

Yes check.svg Done Ruslik (talk) 13:32, 20 January 2018 (UTC)

Global lock for LatanyaLovett

Status:    Done

Probably spambot, blocked on nl.wiktionary after triggering global filter 72 --MarcoSwart (talk) 08:29, 19 January 2018 (UTC)

Yes check.svg Done Ruslik (talk) 13:29, 20 January 2018 (UTC)

Global lock for Jpy Inocente

Status:    Done

WP0 abusers. --jdx Re: 08:58, 19 January 2018 (UTC)

Yes check.svg Done Ruslik (talk) 13:38, 20 January 2018 (UTC)

Global block for BJSasso

Status:    Done

Sock of the highly prolific Dopenguins trying to impersonate me. Blocked on en.wiki and simple.wiki. --Djsasso (talk) 12:32, 19 January 2018 (UTC)

Yes check.svg Done Ruslik (talk) 13:41, 20 January 2018 (UTC)

Global lock for spam accounts

Status:    Done

Love specialist spambots. -★- PlyrStar93. Message me. 14:53, 19 January 2018 (UTC)

Yes check.svg Done Ruslik (talk) 13:50, 20 January 2018 (UTC)

Global lock for globally banned user

Status:    Done

Sock of INeverCry. -★- PlyrStar93. Message me. 15:25, 19 January 2018 (UTC)

Yes check.svg Done Ruslik (talk) 13:51, 20 January 2018 (UTC)

Global lock for Lucharhastaelfinal

Status:    In progress

Another sock of Paroespañol and Sardinaalabarbacoa. --Taichi - (あ!) 18:07, 19 January 2018 (UTC)

Global lock for Albert20009's sockpuppet

Status:    In progress

--Lanwi1(talk) 18:13, 19 January 2018 (UTC)

Global lock for spam accounts

Status:    In progress

Probably spambots, triggering spam abuse filters at en.wiktionary. -- Curious (talk) 19:01, 19 January 2018 (UTC)

Global lock for socks of Nipponese Dog Calvero

Status:    In progress

LTA cross-wiki. -★- PlyrStar93. Message me. 19:18, 19 January 2018 (UTC)

Global lock for Озабоченный Админ

Status:    In progress

Long-term abuse. Locked in ruwiki. Виталий Мирный (talk) 19:53, 19 January 2018 (UTC)

Global lock for Vony nees

Status:    Done

WP0 abuser. --Ilzhabimantara (talk) 22:48, 19 January 2018 (UTC)

Locked by Vituzzu. SA 13 Bro (talk) 16:31, 20 January 2018 (UTC)

Global lock for spambots

Status:    In progress

Spambots. Wiki13 talk 23:00, 19 January 2018 (UTC)

Global lock for Casaco noe

Status:    Done

WP0 abuser. --Ilzhabimantara (talk) 05:56, 20 January 2018 (UTC)

Have been locked by Vituzzu. SA 13 Bro (talk) 16:29, 20 January 2018 (UTC)

Global lock for Japan Football

Status:    In progress

Cross-wiki abuse. Multiples blocks across many projects and insists in the same behavior. EVinente (talk) 13:06, 20 January 2018 (UTC)

Proposal for the same reason. It has already been rejected many times.
  1. Steward requests/Global/2012-05#Global lock for Japan Football
  2. Steward requests/Global/2013-09#Global lock for Japan Football
  3. Steward requests/Global/2015-09#Global lock for Japan Football

--Japan Football (talk) 13:23, 20 January 2018 (UTC)

Global lock for sockpuppets of Nikita Rodin2002

Status:    Done

Long-term abuse and sockpuppets of Nikita Rodin2002. Locked in meta wikimedia Виталий Мирный (talk) 16:33, 20 January 2018 (UTC)

Global lock for sockpuppets of Nikita Rodin2002

Status:    In progress

Long-term abuse and sockpuppets of Nikita Rodin2002. Виталий Мирный (talk) 18:13, 20 January 2018 (UTC)

There is no global account are available while blocked on Russian Wikipedia as vandalism, it likely has been locked and hided. SA 13 Bro (talk) 21:01, 20 January 2018 (UTC)

Global lock for Martinho inocente

Status:    Done

WP0 abusers. --jdx Re: 17:53, 20 January 2018 (UTC)

Yes check.svg DoneDefender (talk) 21:17, 20 January 2018 (UTC)

Global lock for Super Hack

Status:    In progress

Cross-wiki spam. Locked in ruwiki and enwiki. Виталий Мирный (talk) 19:04, 20 January 2018 (UTC)

Global lock for FieryDomains

Status:    In progress

Cross-wiki spam. Locked in ruwiki and enwiki. Виталий Мирный (talk) 19:07, 20 January 2018 (UTC)

Global lock/unlock for AnnettHoney8331

Status:    In progress

Probably spambot, blocked on nl.wiktionary for adding page with spamlinks --MarcoSwart (talk) 20:00, 20 January 2018 (UTC)

Global lock for Simo11990

Status:    In progress

WP0 abusers. --jdx Re: 22:53, 20 January 2018 (UTC)

See also