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

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 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 240[59]:0:0:0::/16 or a large number of subnets within this range

Status:    In progress

This is a follow-up to [[Steward_requests/Global/2018-10#Global_block_for_IPv6_range_240[59]:*]]. I strongly believe that all subnets mentioned in the previous request should be blocked as well rather than just the three picked out, especially since the above two in this request, not falling under the list from the previous request, are sources of this spam as well. @Horcrux and Trijnstel: Mahir256 (talk) 06:46, 16 November 2018 (UTC)

I should check for collateral, but as a general comment I'm usual not in favor of blocking such huge IPv6 ranges. Trijnsteltalk 10:08, 16 November 2018 (UTC)
@Trijnstel: The newest incarnation of this spam is on the Romani Wikipedia. You may wish to check whether "User:Wikiromanadm" is the same individual. Mahir256 (talk) 15:36, 16 November 2018 (UTC)
@Sjoerddebruin, Stryn, Ajraddatz, -revi, علاء, HakanIST, and Hoo man: as Wikidata admins and stewards who can tackle the threatening behavior from this individual. Mahir256 (talk) 17:19, 16 November 2018 (UTC)

Global block for 125.212.177.0/20

Status:    In progress

So many IPs of this range are doing vandalism in various wikis, mainly in lists of flags. --Mr. Fulano! Talk 17:09, 24 November 2018 (UTC)

I just came here to report 176 for the same reason. Just blocked 125.212.176.220 on mlwiki -- Razimantv 07:57, 8 December 2018 (UTC)

Global blocks for 107.175.0.0/17 and 107.175.128.0/17

Status:    In progress

(or 107.175.0.0/16 cross-wiki-contribs ST IP info WHOIS robtexgblockglist)

At meta I am seeing constant spambot infringements from within the /16, and I see that we have previously blocked the /16 before, though when I do some IP checks they seem to be separate /17s though both still seem to be server colo sets. GUC doesn't show that a block would be problematic, so I am asking for both /17s to have an extended block time, maybe a couple of years if that isn't problematic for logged in users (unknown and may be worth checking for account spambots anyway). Thanks or the consideration.  — billinghurst sDrewth 00:56, 26 November 2018 (UTC)

@Billinghurst: GUC works on subnets again? I get 0 results.   — Jeff G. ツ please ping or talk to me 18:21, 30 November 2018 (UTC)
GUC won't show either abusefilter and spamblocklist hits or deleted contributions, and who knows what accounts may be are created within those two ranges. I do know what I see, hence the report, and we do know that there is a history with these ranges.  — billinghurst sDrewth 06:46, 1 December 2018 (UTC)

Global block for 185.158.132.0/22

Status:    In progress

This range is spambot problematic at Meta and has been identified as such previously and now locally blocked until the end of 2020. I will hazard a guess that it is the same xwiki, if it is clear of user accounts, you may wish to consider blacklisting.  — billinghurst sDrewth 01:47, 26 November 2018 (UTC)

Global block for 125.212.128.0/18

Status:    In progress

Cross-wiki vandalism. --jdx Re: 12:28, 26 November 2018 (UTC)

Global unblock for 198.52.128.0/17

Status:    In progress

This IP address was blocked back in 2014 for "webhost Avante Hosting Services + 198.52.217.44". It appears that the IP address in question has been rotated to different users. Charwinger21 (talk) 07:01, 30 November 2018 (UTC)

Specifically, the range was assigned to Carrytel (an ISP) on 2018-05-23. Charwinger21 (talk) 09:19, 1 December 2018 (UTC)

Global block for 2001:4898::/32

Status:    In progress

Abused ip range from a cloud provider XXBlackburnXx (talk) 21:14, 2 December 2018 (UTC)

Global block for several ranges in Jakarta, Indonesia

Status:    In progress

Anon-only for ∼1 month, please. Page blanking. Tries to harass cross-wiki those sysops who block them. Subsumes two requests by Jeff_G. above. Incnis Mrsi (talk) 12:07, 3 December 2018 (UTC)

Global block for 94.130.0.0/16

Status:    In progress

Cross-wiki vandalism. Vermont (talk) 03:12, 6 December 2018 (UTC)

Global block for 2001:b400::/32

Status:    In progress

Cross-wiki LTA 影武者(KAGE) usually used[1].--MCC214Talk with me#Contributions with me 10:05, 6 December 2018 (UTC)

Global block for 2600:8800:3980:2550:0:0:0:0/64

Status:    In progress

Block evasion by MisterAnthony (talk · contribs), same as this recent request but is now using a slightly different IP range. The same Wikidata item that was linked in that request shows the same behaviour from this IP range and there are already a number of local blocks for this range or IPs from this range. - Nikki (talk) 17:45, 6 December 2018 (UTC)

Global block for 2600:8800:3980:2550:F109:50C8:54AD:4584

Status:    In progress

The same guy as the globally blocked 2600:8800:3981:78A0:B537:446F:EB0A:FBC2 cross-wiki-contribs ST IP info WHOIS robtexgblockglist and 2600:8800:3981:7A80:194E:E87A:2510:F53C cross-wiki-contribs ST IP info WHOIS robtexgblockglist. Still vandalizing and creating crappy non-articles on several projects. Thx, XenonX3 (talk) 21:26, 7 December 2018 (UTC)

Global block for DRV IP

Status:    In progress

Dog and rapper vandal. Xwiki activity over the last few weeks. Vermont (talk) 22:43, 9 December 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 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 Satoshi Kondo/WorldCreaterFighter

Status:    In progress

After being blocked indefinitely in the English-language Wikipedia because of his massive abuse of sockpuppets and persistent POV edits, he switches to the German Wikipedia and got blocked indefinitely there for massive spamming. Hee keeps creating accounts and edits both with IPs and new sockpuppets for years since 2015, as the List in the English-language Wikipedia of Vanjagenije, Sro23 and GeneralizationsAreBad shows it. --Sonra Mint (talk) 17:11, 6 November 2018 (UTC)

Sonra Mint is itself a sock puppet of user de:Benutzer:Dribbler and blocked in german wikipedia(Special:CentralAuth/Sonra Mint). And i do not know how often i have to say this: I am not WorlCreaterFighter. Look at my english talkpage. I have made a list of my former socks.(talkpage) I have also said that I will not work on these topics anymore. Sonra Mint is possibly related to some of them, as he/she is a confirmed sock aswell. Btw. User Tomurtogo is blocked as sock of Tigril(Tirgil34). Satoshi Kondo (talk) 11:17, 7 November 2018 (UTC)
He(or she) is possibly an albanian user, 310 edits on albanian wiki, also blocked on netherland wiki for sockpuppetry... Satoshi Kondo (talk) 11:08, 7 November 2018 (UTC)

Why am I listed here? I just saw the message in Wiki. Please take me from that list. I have nothing to do with this, or am related with this sock in any way. Regards, Akocsg (talk) 17:09, 10 November 2018 (UTC)

Note: Satoshi Kondo is a contributor to Wikimedia Commons user. Why wasn’t our community notified about this de facto ban proposal? Incnis Mrsi (talk) 12:55, 1 December 2018 (UTC)

Global lock/unlock for Xayahrainie43

Status:    In progress

Crosswiki abuse, indef enwiki due to CIR issue as well as block evade using IP, indef zhwiki due to DE --Cohaf (talk) 18:05, 12 November 2018 (UTC)

Note, there was a change in behavior which implies that he is not a bot. However, the actions carried out have implied that he is intentionally pushing anti-policy article changes and those changes are detrimental to the quality of articles (including unnecessary changes to navbox and other related issues). There is a high possibility for this kind of vandalism to occur at other projects (en.wikiversity / zh.wikiversity) due to his actions. Note to others: this is a Taiwan IP and his behavior looks like a long term abuser at the zhwiki though not confirmed.--1233 | Questions?| This message is left by him at 18:37, 12 November 2018 (UTC)
Update: after comparing the IP addresses Xayahrainie43 used to evade blocking at enwiki with the IP ranges that LTA using at zhwiki and behavior comparison at zhwiki, we now consider that the link between Xayahrainie43 and that LTA to be around Likely Likely, thanks.--無聊龍 (talk) 04:45, 13 November 2018 (UTC)

Global lock for cross-wiki LTA Jessechi sock

Status:    In progress

--MCC214Talk with me#Contributions with me 10:43, 19 November 2018 (UTC)

Global lock for Dicklands Light Railway

Status:    In progress

LTA: Fuerdai vandal/BMX on WheeIs. Could be an impersonator, but most likely the original.--SkyGazer 512 (talk) 01:09, 23 November 2018 (UTC)

Global lock for socks of Avoided (or an impostor)

Status:    In progress

14th to 15th:

Please lock his socks, check the underlying IPs and block IPs and (if found) as well additional accounts. A block for found IP ranges should be considered. If blocked locally, but not locked globally, it could end like this. Avoided (and his impostors) are located in Germany and Austria, IP adresses found from other than these countries are probably open proxies and should be blocked for 1 year. Regards --Schniggendiller (talk) 21:19, 23 November 2018 (UTC)

Global lock for Jeandu33

Status:    In progress

Cross-wiki abuse. Sock of Raymond51. -★- PlyrStar93 Message me. 01:39, 26 November 2018 (UTC)

Global lock for Markdabeast1 and their socks

Status:    In progress

All the accounts are xwiki spamming. (1) ‐‐1997kB (talk) 07:48, 26 November 2018 (UTC)

Global lock for LTA

Status:    In progress

Long-term abuse. Vermont (talk) 10:49, 29 November 2018 (UTC)

Also:

Lock all:

-★- PlyrStar93 Message me. 18:50, 1 December 2018 (UTC)

Global lock for LTA

Status:    In progress

Lock all:

Esteban16 (talk) 00:25, 30 November 2018 (UTC)

Global lock/unlock for Shameel Done socks

Status:    In progress

All the same obvious self-promo socks of globally locked master listed above, xwiki spamming still. Praxidicae (talk) 14:30, 1 December 2018 (UTC)

Global lock for Shiwam Kumar Sriwastaw socks

Status:    In progress

Long-term abuse. Vermont (talk) 11:10, 5 December 2018 (UTC)

Global lock/unlock for myself

Status:    In progress

This is because I am no longer active from all of these Wikimedia media and also block me too. Khris249 (talk) 05:53, 7 December 2018 (UTC)

Global lock for Samyuktha.ka

Status:    In progress

Lock evasion of globally locked user N_R_Pavan_Kumar (talk • contribs • block • x-wiki • CA • lwcheckuser) --Count Count (talk) 13:39, 7 December 2018 (UTC)

This lock also relates to [[Steward_requests/Global#Global_block_for_240[59]:0:0:0::/16_or_a_large_number_of_subnets_within_this_range]] above. Mahir256 (talk) 16:04, 7 December 2018 (UTC)

Global lock for NatigKrolik

Status:    In progress

Today I noticed that this User did add the same wrong information in a lot of language versions. [2] [3] [4] (He did this in about 12 language versions) At first I thought it could be a mistake. But then I noticed such edits and that the user is already blocked in bg. hy. nl. sv. and uk. Wikipedia --Yoda1893 (talk) 17:58, 7 December 2018 (UTC)

No. I want no global block. Annegret Kramp-Karrenbauer was elected Leader of the CDU [5]. —The preceding unsigned comment was added by NatigKrolik (talk) 19:26, 7 December 2018
Then why did you add today Friedrich Merz as CDU party leader instead on about 10 CDU pages? and why did you make such edits which already caused indefinite blocks in 5 language versions? --Yoda1893 (talk) 19:34, 7 December 2018 (UTC)
No. Annegret Kramp-Karrenbauer as CDU party leader was edited on about 5 CDU pages. --NatigKrolik (talk) 19:46, 7 December 2018 (UTC)
Merz 1, Merz 2, Merz 3, Merz 4, Merz 5, Merz 6 - These are all your edits. Now after you were reported, you did add the right information to some other pages. I could believe that it was a mistake, if I wouldn't have seen your other edits and your block statistics. I don't like Mr. Putin but you definitely weren't blocked for no reason. --Yoda1893 (talk) 20:00, 7 December 2018 (UTC)

Global lock for socks of Avoided (or an impostor)

Status:    In progress

20th to 21st:

Please lock his socks, check the underlying IPs and block IPs and (if found) as well additional accounts. A block for found IP ranges should be considered. If blocked locally, but not locked globally, it could end like this. Avoided (and his impostors) are located in Germany and Austria, IP adresses found from other than these countries are probably open proxies and should be blocked for 1 year. Regards --Schniggendiller (talk) 19:55, 8 December 2018 (UTC)

George Reeves Person, again

Status:    Done

Please check the underlying IP and block it/them as long as is reasonable - Pretty sure I know what it is but won't speculate here - please check for other socks because he usually makes a bunch when he finds an unblocked IP. Thanks, Antandrus (talk) 22:38, 8 December 2018 (UTC)

Yes check.svg Done Ruslik (talk) 20:59, 9 December 2018 (UTC)

Global lock for Ed.Vallejo

Status:    Done

Cross-wiki abuse (spamming). -★- PlyrStar93 Message me. 01:30, 9 December 2018 (UTC)

From interaction here at meta, I believe that the request is premature if we apply a modicum of GF. It may happen, though, I don't think that we are there yet.  — billinghurst sDrewth 02:55, 9 December 2018 (UTC)
I rescind my comment. Not worth saving. Lock away.  — billinghurst sDrewth 04:46, 9 December 2018 (UTC)
Yes check.svg Done --Alaa :)..! 08:13, 9 December 2018 (UTC)

Global lock for Albert20009's sockpuppet

Status:    Done

--Lanwi1(talk) 16:03, 9 December 2018 (UTC)

Yes check.svg Done --Alaa :)..! 17:51, 9 December 2018 (UTC)

Global lock for Spiridon Monica Cristina

Status:    In progress

Cross-wiki abuse. Only spamming pointless edits in multiple wikis. -★- PlyrStar93 Message me. 16:41, 9 December 2018 (UTC)

Global lock for Jskeezy19

Status:    Done

Cross-wiki vandalism and addition of spam. --Operator873 (talk) 19:09, 9 December 2018 (UTC)

Yes check.svg Done Ruslik (talk) 20:57, 9 December 2018 (UTC)

Global lock for ElisaZuy82

Status:    Done
Yes check.svg Done Ruslik (talk) 20:56, 9 December 2018 (UTC)

Global lock for Happyminecrafter12

Status:    In progress

LTA; possibly Glapz, but many of the more recent LTAs like to impersonate each other (assuming they're not related). SURJECTION ·talk·contr·log· 20:52, 9 December 2018 (UTC)

Global lock for accounts

Status:    In progress

Lock all:

Long-term abuse, socks of WhenDatHotlineBling. -★- PlyrStar93 Message me. 21:45, 9 December 2018 (UTC)

Global lock for Surjection ón round objects

Status:    In progress

LTA. SURJECTION ·talk·contr·log· 22:15, 9 December 2018 (UTC)

Global lock for socks of Avoided (or an impostor)

Status:    In progress

22nd to 23rd:

Please lock his socks, check the underlying IPs and block IPs and (if found) as well additional accounts. A block for found IP ranges should be considered. If blocked locally, but not locked globally, it could end like this. Avoided (and his impostors) are located in Germany and Austria, IP adresses found from other than these countries are probably open proxies and should be blocked for 1 year. Regards --Schniggendiller (talk) 22:17, 9 December 2018 (UTC)

Global lock for fuerdai

Status:    In progress

Long-term abuse. -★- PlyrStar93 Message me. 22:18, 9 December 2018 (UTC)

Global lock WhenDatHotlineBling sock

Status:    In progress

 Confirmed WDHB sock. TonyBallioni (talk) 00:04, 10 December 2018 (UTC)

See also