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[edit]

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 block for 166.84.1.2[edit]

Status:    In progress

Dedicated proxy IP, registered to this webhosting service. Likely a banned/blocked user socking. They've engaged in constant harassment of an en.wiki admin. 2601:1C0:4401:F360:7DF8:AF46:7C8B:7470 02:36, 21 March 2017 (UTC)

Global block for 213.136.64.0/20[edit]

Status:    In progress

Webhosting/VPN service. Connected through "MobiProxy" VPN service.—The preceding unsigned comment was added by 213.136.77.188 (talk)

Global block for 210.209.72.0/24[edit]

Status:    In progress

Webhosting/VPN service. Connected through "MobiProxy" VPN service.—The preceding unsigned comment was added by 210.209.72.186 (talk)

Global block for 113.20.28.0/22[edit]

Status:    In progress

Webhosting/VPN service. Connected through "MobiProxy" VPN service.—The preceding unsigned comment was added by 198.236.201.79 (talk)

Global block for Brazilian IP Addresses[edit]

Status:    In progress

Brazilian IPs performing persistent editing war and vandalism and 3RR violation at zh-yue:華地馬 and zh-yue:華德馬艾坎塔拉, and also have got the same edit features in zh-yue:卡米洛 山塔納 this topic. According to the experiences for wikipedia's sock puppets. I think they are USER:JoseNivalJunior2531. Because I have checked for their IPs (see their IPs in iplocation.net), they come from either Fortaleza or Poco da Pedra, Brazil.--PQ77wd (talk) 23:23, 2 April 2017 (UTC)

Newest information: Latest IP have made the same violation in zh-yue:奧巴諾‎. It's so similiar for these IP edit features from above. --PQ77wd (talk) 00:04, 3 April 2017 (UTC)

Comment CommentIf they only make disruptive edits in zh-yue, then why not just block them there? -- ? —The preceding unsigned comment was added by PokestarFan (talk)

Because we have no IP checkers in zh-yue. And also the administrators ignore these IPs' bad behaviors. --PQ77wd (talk) 02:21, 5 April 2017 (UTC)
Newest information: I have seen 177.98.222.173 that IP was the same edit feature like of above in zh-yue:孔愛德 on today.--PQ77wd (talk) 00:24, 6 April 2017 (UTC)

Global block for Long-term Wikinews spambots[edit]

Status:    In progress

Long-term spam in English Wikinews. —Alvaro Molina ( - ) 11:22, 17 April 2017 (UTC)

Abuse filter blocked the IP which is to expire after 31 hours. -- acagastya 12:03, 17 April 2017 (UTC)

Global block for 2607:FB90:0:0:0:0:0:0/32[edit]

Status:    In progress

Cross-wiki abuse and Long-term abuse on English Wikipedia. --209.242.141.28 18:16, 17 April 2017 (UTC)

That's a rather large global block request, considering how T-Mobile only hands /128s to its wireless customers. Dargasea (talk)

Global block for 209.242.141.28[edit]

Status:    In progress

Crosswiki abuse blocked by Widr for one year and it currently blocked by Az1568 for one week can you please global block for one week for now? --2602:306:36D5:5690:ADD7:9362:B1DD:5708 17:24, 29 April 2017 (UTC)

Global block for Bertrand101 IPS[edit]

Status:    In progress

Long-term abuse; Bertrand101 --99.109.85.105 05:01, 30 April 2017 (UTC)

Feasibility of global block for 2A03:2880:____:____:FACE:B00C:0:____[edit]

Status:    In progress

Hello,
While patrolling on Wikidata, I frequently see problems from users using the address ranges 2A03:2880:____:____:FACE:B00C:0:____, such as synchronized attacks on items (example1, example2). I have also noticed that:

I am not an expert about open proxy. I don't know whether all these addresses are open proxies and should be blocked. But if I look at the first global block, 2A03:2880:11:1FEC:0:0:0:0/64, I am wondering: perhaps 2A03:2880:11:0:0:0:0:0 corresponds to open proxies too? perhaps 2A03:2880:0:0:0:0:0:0 corresponds to open proxies too (my example of Stalk toy request shows that several Wikipedia administrators think so)? perhaps these address ranges should be blocked?
Regards --NicoScribe (talk) 22:59, 2 May 2017 (UTC) +NicoScribe (talk) 18:11, 4 May 2017 (UTC) +NicoScribe (talk) 17:36, 5 May 2017 (UTC)

The Ipv6 address saboteur sometimes use 66.220.158.103、66.220.158.107、66.220.158.108、66.220.158.109 as well, i used to track the addresses since sep 2016, they have a same pattern of behavior and targets.Cherjau (talk) 23:25, 10 May 2017 (UTC)

Complex situation[edit]

Butting my head in here as a former steward who can probably help explain the complexity of the request being made. Noting that mw:Help:Range blocks/IPv6 is pertinent to understanding. The request while sounding (somewhat) simple, has larger implications and should reflect a policy decision and approach rather than a series of blocks.

Questions first:

  • Is there evidence of a system-wide problem for the overarching ranges, excluding the vanity IPs within the sets? Noting that there may be useful edits occurring crosswiki and for stewards to check such usage is not a trivial task, and one would expect a good reason for a global/broader block.
  • Is there evidence from your checkusers of whether this should be a hard or a soft block, as there may or may not be legitimate editing from logged-in accounts.

Commentary:
That said it is an interesting that the IPs is all facebook management IP range, so unless it is facebook staff, it is some type of proxy service. There seems to be clarity about the source, and almost a vanity approach to their range descriptions and use.

  • Do we (collectively) wish to stop/block facebook proxy addresses from editing wikis?
  • Do we have a clear understanding of the process being used to edit, and how widely it can be abused? How/why is facebook offering proxies for editing?
  • Blocking those subranges based solely on the :FACE: component of the IP address is going to be difficult/problematic as you need to start much further up the IP range if collective, and is going to involve significant range blocks. Or we have a plethora of small blocks on the lower ranges, which is time consuming, and difficult to manage.

Notes: 66.220.158.103 and like IPs show up as in the range 66.220.144.0/20 (facebook). It is a pretty tight range, and could be managed by blocking something like 66.220.158.96/28]

So if we need to stop those "...:face:booc:..." IP addresses doing it as global blocks for stewards is a problem, and it may be better to seek a better technical solution from the WMF developers. They may be able to do something outside of the wiki tools, or by other means. We should be resolving what is the issue, and does it constitute a global problem prior to acting.  — billinghurst sDrewth 04:37, 11 May 2017 (UTC)

Thank you, Cherjau. On the French Wikipedia, I have noticed that 66.220.158.108 is interested by the town covè in Benin [1] and that 66.220.158.103 is interested by the same town along with some 2A03:2880:____:____:FACE:B00C:0:____ users, in this history in 2015 and 2016.
Thank you, Billinghurst:
  • I admit that my understanding of the technical aspects is limited.
  • About your first question: I have not searched for evidence of a system-wide problem. I have just noticed that almost all the edits from 2A03:2880:____:____:FACE:B00C:0:____ users were incorrect, while loking at the "recent changes" lists on 2 projects: Wikidata and French Wikipedia. The edits are numerous: the list above has been created during a few days (and since the 5 May I have a local list with many other addresses from this range).
  • About your second question: I have not talked about this problem with administrators or checkusers from Wikidata and French Wikipedia.
  • You mentioned "proxy service", but did you read the last part of this edit on the English Wikipedia? It mentions interesting elements: "Facebook IPs used for vandalism/sockpuppetry", "open proxy for Facebook users", "massive vandalism", "Definitely registered to Facebook", "There's no non-facebook IP addresses being used in the /32 range", "longterm block on 2A03:2880::/32 for this sockdrawer", "abuse from anon-IPs", "face:b00c block collateral", "ip addresses with FACE:B00C in their range are used by internet.org app service", "that block is much too broad...no, it's not", "the persistent disruption and vandalism by that sockmaster is extensive", "someone from that range is trying to change my WP password", etc.
  • Since the beginning, I have talked about the block of 2A03:2880:0:0:0:0:0:0, not the block of all the addresses containing the :FACE: or :FACE:B00C: component.
  • I have one question: I suppose that the policy No open proxies is applicable to all Wikimedia projects, so why the block of an open proxy on one project (for instance 2A03:2880:0:0:0:0:0:0/__ on the English Wikipedia) is not systematically escalated to a global block here?
Thank you, Masti, for the global block that you applied on 9 May to User:2A03:2880:0:0:0:0:0:0/32 with the comment "open proxy". Is it linked to my request here?
Perhaps Tegel or Vituzzu (who have made some global blocks in the list above) or DMacks or JamesBWatson (who have blocked 2A03:2880:0:0:0:0:0:0/__ on English Wikipedia) have more information?
Regards --NicoScribe (talk) 15:36, 12 May 2017 (UTC)

Global block for 103.47.132.x/103.47.134.x[edit]

Status:    In progress

Cross-wiki addition of hoaxes, same modus operandi as Steward requests/Global/2017-04#Global block for 103.47.132.x/103.47.134.x. Maybe this could be the case for a 103.47.132.0/24 range block, as has been done on nl.wiki. –Gpmat (talk) 12:17, 17 May 2017 (UTC)

Added one IP, vandalism still ongoing.–Gpmat (talk) 12:07, 22 May 2017 (UTC)

Global block for 71.208.177.245[edit]

Status:    In progress

Cross-wiki vandalism per this edit.   — Jeff G. ツ 11:41, 23 May 2017 (UTC)

Requests for global (un)lock and (un)hiding[edit]

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 lock/unlock for Gabrieldcecy again[edit]

Status:    In progress

Gabrieldcecy returned to Portuguese Wikipedia with your cross-wiki under the name of GabCecy. --148.0.126.111 14:08, 4 May 2017 (UTC)

Global lock for User:信任むりなの[edit]

Status:    In progress

This user is primarily aimed at harasses to Mirinano. This username means “Mirinano can't to gain his confidence”. This username included in ‟nano” of hiragana, so this username is inadequate. This user already blocked Jawiki. This user of act perhaps 2ch. --連綿 (talk) 19:27, 8 May 2017 (UTC)

  • Comment Comment I don't think this username is inappropriate. Also, this user does not, at least, vandalize here on META wiki. Please assume good faith.--73.163.243.31 00:32, 9 May 2017 (UTC)
  • Comment Comment Perhaps this user is jawiki sockmaster ja:LTA:AKANE. But there is no evidence :( --Marine-Bluetalkcontribs 17:09, 22 May 2017 (UTC)

Global unlock for Sher Aziz[edit]

Status:    In progress

Global lock for Unypoly[edit]

Status:    In progress

This is LTA/Unypoly. check this, and he is doing vandalism now. but Nobody blocks it.

How do you know if this user is Unypoly? Also you are grossly misunderstanding ko:백:인신 공격 금지. Jerrykim306 (talk) 06:27, 13 May 2017 (UTC)

Global lock for 이 높으신 보민 대왕님 앞에서 당장 절하라[edit]

Status:    In progress

이 높으신 보민 대왕님 앞에서 당장 절하라 (talk • contribs • block • x-wiki • CA • lwcheckuser)

Sock of sulutil:보민개 and more. see Steward requests/Global/2017-05#Global lock for 보민개. This user always claim that this user(보민개) is King. Also cross-wiki abuse in this wiki such as creating this user's page to claim this user is a king. Jerrykim306 (talk) 06:29, 13 May 2017 (UTC)

보민 대왕님의 금품 (talk • contribs • block • x-wiki • CA • lwcheckuser)

Impersonation or sock Jerrykim306 (talk) 07:44, 14 May 2017 (UTC)

Jerrykim306 (talk) 07:56, 20 May 2017 (UTC)

Jerrykim306 (talk) 06:11, 21 May 2017 (UTC)

Global lock for My Royal Young socks[edit]

Status:    In progress

Long-term abuse; My Royal Young --2602:306:36D5:5690:F180:393B:8086:D016 19:53, 13 May 2017 (UTC)

Comment Note This account had inactive since April 1, 2017 - Rama Ybrahim (Talk) 04:56, 20 May 2017 (UTC)

Global lock for Najaf ali bhayo[edit]

Status:    In progress

Long-term abuse. Blocked on enwiki. This user asks constantly a rename with several accounts, see here. A steward has been renamed by mistake, but user reincarnates with same name to reask a rename, Jmvkrecords (Intra talk) 05:05, 16 May 2017 (UTC).

Can we lock Sibghat Chaudhary too? Jmvkrecords (Intra talk) 05:08, 16 May 2017 (UTC).
I add a request to lock ELEPSIA. See here, Jmvkrecords (Intra talk) 14:36, 19 May 2017 (UTC).

Global unlock for Turkjakrapun[edit]

Status:    In progress

As my account was block : the following reason: Abusing multiple accounts: user:Turkjakrapun This block (ID #292189) is set to expire: indefinite. I am totally accept my mistake, and totally understand the reason for blocked me.
To be honest, At first I use account:Turkjakrapun to publish an article that in the end was blocked by the reason of "promotion/advertising". After that, I try to revised my article to make it in the correct way for Wikipedia but I can't because I was block. According to my stupidity, I was create another account (Jakrapun.s) and try to publish my revised article to Wikipedia again. And that was a big mistake for me and as I told you, I am totally understand that you will think I am try to evade the block on my old account.
At the end of the day, I beg you to please unblock me. So I can correct my mistake, and learn how to use Wikipedia with honestly., Turkjakrapun115.87.191.83 08:45, 16 May 2017 (UTC)

Feasibility of a global lock for many Bertrand101 sockpuppets[edit]

Status:    In progress

Batch 2[edit]

Batch 3[edit]

Long-term abuse; Bertrand101 --2602:306:36D5:5690:7CB0:4018:904C:D09E 22:29, 16 May 2017 (UTC)

@Ruslik0: In every batch theres many hoax stations to lock theres batch 1, batch 2, and batch 3 to mass global lock the users thanks Ruslik please lock the batches 1, 2, and 3 Thank you Ruslik 2602:306:36D5:5690:1955:4101:BF8E:E273 04:25, 17 May 2017 (UTC)

Global lock for Jr abad socks[edit]

Status:    In progress

Long-term abuse; Jr abad --2602:306:36D5:5690:1955:4101:BF8E:E273 04:53, 17 May 2017 (UTC)

Global lock/unlock for User:Vote (X) for Change[edit]

Status:    In progress

Long term abuse. Recently vandalized Commons. MechQuester (talk) 01:10, 19 May 2017 (UTC)

@MechQuester: seems like a cross-wiki abuse please contact a steward to lock it right now 209.242.141.28 20:55, 22 May 2017 (UTC)

Global lock for Masoom.bilal73[edit]

Status:    In progress

Cross-wiki abuse. Seems like a LTA --209.249.5.130 04:31, 19 May 2017 (UTC)

Global lock for 影武者(Nipponese Dog Calvero)[edit]

Status:    Done

--Lanwi1(Talk) 04:37, 22 May 2017 (UTC)

Yes check.svg Done.--HakanIST (talk) 05:20, 22 May 2017 (UTC)

Global lock for 影武者(Nipponese Dog Calvero)[edit]

Status:    Done

--Lanwi1(Talk) 15:13, 22 May 2017 (UTC)

Yes check.svg DoneDefender (talk) 15:51, 22 May 2017 (UTC)

Global lock for We will effing merc you[edit]

Status:    Done

Confirmed by CheckUser on enwiki --209.242.141.28 21:01, 22 May 2017 (UTC)

Yes check.svg Done by Shanmugamp7 38.96.9.224 01:45, 23 May 2017 (UTC)

Global lock for NASA'S GODFATHER HENRY MAC HENRY AND GODMOTHER EMMA WATSON[edit]

Status:    Done

Long-term abuse; HENRY APPLEGATE --38.96.9.224 22:10, 22 May 2017 (UTC)

Yes check.svg Done by Shanmugamp7 38.96.9.224 01:45, 23 May 2017 (UTC)

Global lock for Henry Applegate socks[edit]

Status:    In progress

Long-term abuse; HENRY APPLEGATE --209.249.5.140 01:38, 23 May 2017 (UTC)

Global lock for NASA LUNAR SERVICES[edit]

Status:    In progress

Long-term abuse; Henry Applegate, --209.249.5.130 01:41, 23 May 2017 (UTC)

Global lock for 影武者(Nipponese Dog Calvero)[edit]

Status:    Done

--Lanwi1(Talk) 17:13, 23 May 2017 (UTC)

Yes check.svg Done, Linedwell [talk] 18:23, 23 May 2017 (UTC)

Global lock for Albert20009's sockpuppets[edit]

Status:    Done

--Lanwi1(Talk) 17:24, 23 May 2017 (UTC)

Yes check.svg Done, Linedwell [talk] 18:23, 23 May 2017 (UTC)

Global lock for 6th batch of Bertrand101 socks[edit]

Status:    In progress

Long-term abuse; Bertrand101 , --209.249.5.130 22:03, 23 May 2017 (UTC)

Global lock for Jordan1043[edit]

Status:    Done

After being blocked at Commons, starts attacking people via Simple. --Jcb (talk) 15:30, 24 May 2017 (UTC)

Yes check.svg DoneDefender (talk) 15:45, 24 May 2017 (UTC)

Global abuse filters[edit]

Special:AbuseFilter/69: May 10[edit]

Status:    Done

Would a steward please add the domain skyrock.com to Special:AbuseFilter/69. Thanks.  — billinghurst sDrewth 12:20, 10 May 2017 (UTC)

Yes check.svg Done, Linedwell [talk] 14:37, 10 May 2017 (UTC)

: May 16[edit]

Status:    Done

Would a steward please add hatenablog.com to the Special:AbuseFilter/69. Thanks.  — billinghurst sDrewth 11:49, 16 May 2017 (UTC)

Yes check.svg Done.--HakanIST (talk) 12:21, 16 May 2017 (UTC)

See also[edit]