Jump to content
Wikimedia Meta-Wiki

Steward requests/Global

From Meta, a Wikimedia project coordination wiki
This is an archived version of this page, as edited by 190.46.233.97 (talk) at 05:27, 15 July 2017 (→‎Global lock for TheUltimateMinimalist: why do I always do this...). It may differ significantly from the current version .

Latest comment: 7 years ago by 190.46.233.97 in topic Requests for global (un)lock and (un)hiding
Due to persistent vandalism and disruption on this page, this page is currently semi-protected indefinitely. Globally blocked or locked users should appeal to stewards@wikimedia.org or UTRS.
If your account was locked with a reason "Compromised account", please contact ca@wikimedia.org.
This page hosts requests for global (un)blocks, (un)locks and hidings.

If you are here because you have been affected by a global block, please see Global blocks/FAQ for more information about global block and routes to appeal.

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


Cross-wiki requests
Meta-Wiki requests


Requests for global (un)block

Latest comment: 7 years ago 33 comments13 people in discussion
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 .
Global blocks don't affect Meta-Wiki, so if your IP address or account is blocked, you can still appeal here. IP addresses or accounts 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.
Please describe the kind of cross wiki abusive activity you see from the IP or account. Saying an IP or account is a long term abuser is not helpful, but saying "IP vandalizes at ban.wikipedia, no.wikipedia and vi.wikipedia" is. This is especially important for range blocks. If you do not provide enough details, your request might be declined.
Instructions for making a request

Before requesting, make sure that:

  1. You know the IP address(es) or accounts 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 or account, if any.

To make a request for the address(es) or account(s) to be blocked or unblocked

Copy the template below to the bottom of this section and explain why the address(es) or account(s) should be blocked/unblocked.
=== Global block/unblock for [[Special:Contributions/Some IP address or account|Some IP address or account]] ===
{{Status}} <!-- Do not remove this template -->
* {{Luxotool|IP address/username}}
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@wikimedia.org

Global unblock for 2A03:.&checktime(2880,0,0,':'):0:0:0:0/32

Status: In progress

By mistakely admin blocked this ip range 2A03:.&checktime(2880,0,0,':'):0:0:0:0/32 abusing this is open proxy actually this proxy is not open this is proxy of facebook's internet.org private organization please review and unblock it. --Gamma+ (talk) 03:26, 17 June 2017 (UTC) Reply

Comment: If it is a "private internet organization" (i.e., private web browsing through facebook's virtual servers), then it is considered to be a "webhost", not an open proxy, which is still blockable. 2601:1C0:10A:F73A:1056:9979:D4E9:73AE 11:18, 18 June 2017 (UTC) Reply
Pinging Masti. Poyekhali (talk) 00:22, 1 July 2017 (UTC) Reply

Global block for Cross-wiki meaningless pages vandal

Status: In progress

They are cross-wiki vandals, who create useless pages chiefly at wiktionaries in the same manner. Some of the pages are with the same title.

S/he tried to avoid deletion of the such pages at sh.wiktionary.org by removing notices. I assume that all four may be sockpuppets of 124.239.251.55 (currently globally blocked). --Eryk Kij (talk) 10:17, 5 July 2017 (UTC) Reply

They are the same person and a cross-wiki vandal on many projects. He's been active for serveal months and I've blocked 1.180.215.0/24, 1.180.237.0/24, 124.239.251.0/24 on zh-classical.wikipedia and 1.180.215.0/24 on zh.wikiquote. He also has a fixed IP 219.147.88.191. Maybe we should request for blocking:
1.180.215.0/24 xwiki-contribs • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye
1.180.237.0/24 xwiki-contribs • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye
124.239.251.0/24 xwiki-contribs • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye
219.147.88.191 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye (Already globally blocked)--Amanojaku (talk) 12:26, 5 July 2017 (UTC) Reply

Global block for 207.154.194.52

Status: In progress

Vandalism in BG Wikipedia and EN Wikipedia. Open proxy. 212.39.89.208 17:48, 13 July 2017 (UTC) Reply

Global block for 169.51.72.247

Status: Done

Open proxy. Recently used for abuse. 172.58.43.251 02:43, 14 July 2017 (UTC) Reply

Done. RadiX ∞ 02:45, 14 July 2017 (UTC) Reply

Global block for several open proxies

Status: Done

Open proxies. Recently used for abuse. @RadiX:. 73.96.115.29 03:33, 14 July 2017 (UTC) Reply

Done. RadiX ∞ 03:43, 14 July 2017 (UTC) Reply

Global block for 50.224.104.70

Status: Done

Long term abuse. Please also lock the accounts on the IP. --Ks0stm (T•C•G•E) 03:50, 14 July 2017 (UTC) Reply

Done. RadiX ∞ 17:11, 14 July 2017 (UTC) Reply

Global block for 188.32.0.0/16

Status: In progress

Stryn blocked me, 6 mouth changes 1 mouth. 49.212.177.73 04:15, 14 July 2017 (UTC) Reply

Global block for 77.87.48.179

Status: Done

Open proxy; recently used for abuse. 2601:1C0:4401:F360:6504:76AC:773C:626 04:55, 14 July 2017 (UTC) Reply

Done. RadiX ∞ 17:20, 14 July 2017 (UTC) Reply

Global block for 185.42.221.23

Status: Done

Open proxy; recently used for abuse. 2601:1C0:4401:F360:6504:76AC:773C:626 05:07, 14 July 2017 (UTC) Reply

Done. RadiX ∞ 17:09, 14 July 2017 (UTC) Reply

Global block for 118.193.5.16

Status: In progress

Open proxy; recently used for abuse. 2601:1C0:4401:F360:6504:76AC:773C:626 05:22, 14 July 2017 (UTC) Reply

Global block for 198.49.72.98

Status: Done

Obvious IP sock of LTA Wikinger with cross-wiki abuse, most likely an open proxy. -- Favonian (talk) 12:32, 14 July 2017 (UTC) Reply

Done. RadiX ∞ 17:00, 14 July 2017 (UTC) Reply

Global block for many open proxies

68.234.199.122

Status: Done

Open on ports 53, 80, 3333, and 5555.

Done. Rangeblocked. RadiX ∞ 00:48, 15 July 2017 (UTC) Reply

97.74.230.213

Status: Done

Open on ports 25, 80, 443, et al.

This one's done; I missed a global rangeblock that includes it. Ks0stm (T•C•G•E) 19:53, 14 July 2017 (UTC) Reply

107.181.169.230

Status: Done

Open on many ports, including 22, 80, 443, 8080.

Done. RadiX ∞ 00:50, 15 July 2017 (UTC) Reply

144.217.0.0/16

Status: Done

Web host range [1] hosting several open proxies.

Done. RadiX ∞ 01:10, 15 July 2017 (UTC) Reply

138.68.37.211

Status: Done

Open on many ports, including 80, 8080.

Globally range blocked. Ks0stm (T•C•G•E) 19:53, 14 July 2017 (UTC) Reply

138.197.194.31

Status: Done

Open on many ports, including 80, 8080.

Globally range blocked. Ks0stm (T•C•G•E) 19:53, 14 July 2017 (UTC) Reply

165.138.79.68

Status: Done

Open on many ports, including 22, 80, 443, 8080.

Done. RadiX ∞ 00:50, 15 July 2017 (UTC) Reply

47.208.209.111

Status: Done

Open on port 65000.

Done. RadiX ∞ 00:50, 15 July 2017 (UTC) Reply

52.35.243.30

Status: Done

Open on ports 22 and 80, et al.

Done. RadiX ∞ 00:50, 15 July 2017 (UTC) Reply

155.94.213.135

Status: Done

Open on port 22.

Globally rangeblocked. Ks0stm (T•C•G•E) 19:53, 14 July 2017 (UTC) Reply

70.97.223.199

Status: Done

Open on ports 1723 and 2000.

Done. RadiX ∞ 00:50, 15 July 2017 (UTC) Reply

68.180.57.63

Status: Done

Open on ports 53, 80, 5555, et al.
--Ks0stm (T•C•G•E) 19:30, 14 July 2017 (UTC) Reply

Done. Rangeblocked. RadiX ∞ 00:47, 15 July 2017 (UTC) Reply

Requests for global (un)lock and (un)hiding

Latest comment: 7 years ago 27 comments16 people in discussion
Be sure to follow the instructions below:
  • Your request might be rejected if it 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-stewards connect or email your request to the stewards VRT queue at stewards-oversight@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-appeals@wikimedia.org.

Please describe abusive activity of an account before reporting them here. Since stewards are often not active at projects the reported accounts are, things that seem obvious to you may not be equally obvious to the reviewing steward.

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-stewards connect , 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 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 unlock for GALAXYA8

Status: In progress

This user was asked to be unlocked globally per ko:user talk:175.117.14.235. And I can trust that the user didn't make 슊슊이 account maybe these accounts are logged in in a same IP, not a same person. The user has requested to be unlocked only original account(Not sock). This user has a real mind of apologizing. This user didn't mean to use sockpuppets. Stewards, this is just a local sockpuppetry, plus I'm the requester who request the lock for 슊슊이 because of abusive username(I believe that other person made/logged in same IPs.). Sorry for bad English. Hope this edit is not a disruptive editing. Thanks. Jerrykim306 (talk) 07:48, 7 June 2017 (UTC) Reply

Adding another comment that this user actually didn't want to use sock puppets. Stewards, I'm saying again that I'm the requester to lock this user's sockpuppets and I cancel it because they're not 슉슉이. Jerrykim306 (talk) 06:28, 19 June 2017 (UTC) Reply
There was very clear evidence, both checkuser and behavioural, connecting him to the other accounts. I am uncomfortable unlocking at this time. – Ajraddatz (talk) 07:35, 19 June 2017 (UTC) Reply
Excuse me, but if you said that checkuser was a clear evidence, maybe that user have logged in to same computer/mobile (like school computer) and the IPs got check usered(see en:WP:SHARE) by an accident. And this user doesn't know that user. How come that the users have been logged in a same IPs? Even other person. Hope stewards understand. :) Jerrykim306 (talk) 09:02, 20 June 2017 (UTC) Reply
Well behavioral is same as "1920x1080", "김 씨", "신태일김윤태짱", but is not same with 슊슊이 and maybe that user did login to a same computer but other person. Jerrykim306 (talk) 12:28, 21 June 2017 (UTC) Reply
Answering "How come that the users have been logged in a same IPs" might violate the Confidentiality Agreement (=Unanswerable), or they are lying. By the way, how can you ensure "And this user doesn't know that user?" — regards, Revi 14:17, 21 June 2017 (UTC) Reply
Answering "By the way, how can you ensure "And this user doesn't know that user?"" That user said multiple times that user abused accounts but not the 슊슊이s. Also Confidentiality Agreement (=Unanswerable) is right though and I'm not 100% sure too. No one is 100% sure too. Thanks. Jerrykim306 (talk) 06:24, 22 June 2017 (UTC) Reply
If I have a question, does it mean that is hard to unlock that user because of these problems? Jerrykim306 (talk) 09:15, 22 June 2017 (UTC) Reply

I want to talk at this request, I am GALAXYA8 and user:GALAXYA8's ip address and user:Jerrykim306 said to me at ko:user talk:175.117.14.235, "you should to write your opinion at unlock request". but i am using open proxy, i don't want to use open proxy. i was banned at korean wikipedia and other user said to me, "if you want to edit at wikipedia again, please do not create or use sockpuppets and your ip and use only your original account". my original account, GALAXYA8 was locked already, my account has an email address. if someone steward unlock my original account, i can edit and i will unblock at korean wikipedia. A few months ago, my ip address han been globally blocked at all wikimedia projects, blocked at this meta-wiki at the same time and reason was cross wiki-abuse. However, I am not LTA, not cross wiki abuse, not vandalism and i am tring stop to use open proxy. my sockpuppet are only these accounts user:1920x1080 user:김 씨 user:신태일김윤태짱 user:Kim9933 user:임시 계정, using my ip address, user:175.117.14.235 and i was not create other accounts. i am used my ip mostly and other ip used sometimes. i don't know when i was used other IP and what ip address is. my account locked after, i was requested to unlock my sockpuppet, but all request was refused and sockpuppet was blocked and locked. so, this chance is final chance, now please unlock and unblock my original account. if someone unlock my account, i will be unblocked and can edit to wikipedia again. but reject this request and keep lock my account, i will be global banned at all wikimedia projects forever! or someone steward do GLOBAL LOCK MY IP ADDRESS? i am wating for unlock my account. thanks --175.117.14.235 14:43, 9 July 2017 (UTC) Reply

You are not banned. Because "Banning Policy" is not a Korean Wikipedia's policy yet. There's no such thing as ban in korean wikipedia. By the way, if you use open-proxy you may be blocked long time until proxy closes.

I am not sure why there's non-related sockpuppets connecting to a same ip?(But not sure because of Confidentiality Agreement.) Very interesting.;; Jerrykim306 (talk) 05:27, 10 July 2017 (UTC) Reply

Global unlock for Sher Aziz

Status: In progress

This is my 3 global unlock request on meta @admins and @steward please give a response to me i used many times utrs they are waiting for when i will unlock global and they will unlock me on english wikipedia please accept my appeal.

-- 119.160.64.37 07:45, 8 July 2017 (UTC) Reply

Now i requested on meta please give me a response here.

-- 119.160.64.37 07:45, 8 July 2017 (UTC) Reply

I don't think this user can be unlocked because this user is blocked clearly good reason. I Oppose Oppose to be unlocked for this user. Jerrykim306 (talk) 07:03, 9 July 2017 (UTC) Reply

Global lock/unlock for Martimc123

Status: On hold

Well I wanted to be unlocked because I wanted to appeal in my account and I know I did many mistakes but I wanted to start from somewhere that's why I wanted to be unlocked well if could, Thanks for your time --109.49.183.212 11:40, 12 July 2017 (UTC) Reply

This request is being discussed. RadiX ∞ 12:53, 12 July 2017 (UTC) Reply
Please note the discussion on my talk as well. —DoRD talk 13:38, 12 July 2017 (UTC) Reply

Do you know what yes include that if want do you know what I don't have any secrets and I want to start from somewhere, so please note that I want one more chance. Thanks for your time 109.49.183.212 13:41, 12 July 2017 (UTC) Reply

Status: Done

Cross-wiki spam. --WhitePhosphorus (talk) 09:23, 13 July 2017 (UTC) Reply

Done masti <talk> 09:35, 13 July 2017 (UTC) Reply
Thanks, by the way it's Korean Wikipedia spammer.(This user is blocked in no-where.) Jerrykim306 (talk) 05:12, 14 July 2017 (UTC) Reply

Global lock for Bosanchero

Status: Done

New sock puppet of Yahadzija; confirmed and blocked on Commons; CUs can see info here. Эlcobbola talk 21:54, 13 July 2017 (UTC) Reply

Done. RadiX ∞ 01:21, 14 July 2017 (UTC) Reply

Global lock for LTA sockpuppet accounts

Status: In progress

Long-term abuse. @RadiX: 2601:1C0:4401:F360:6504:76AC:773C:626 04:38, 14 July 2017 (UTC) Reply

I'd additionally note that Pat, Mike and Jeff are all Incorrigible Troll socks, and were all blocked for socking and disruption on en-wiki yesterday. Purple backpack89 21:32, 14 July 2017 (UTC) Reply
Status: Done

Long-term abuse, sockpuppet of 118 alex. @RadiX: 174.70.182.199 20:43, 14 July 2017 (UTC) Reply

Done — Defender (talk) 01:01, 15 July 2017 (UTC) Reply

Global lock for TheUltimateMinimalist

Status: In progress

Long-term abuse, sockpuppet of 118 alex. 190.46.233.97 05:26, 15 July 2017 (UTC) Reply

See also

AltStyle によって変換されたページ (->オリジナル) /