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→
Shortcut:
SRG
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 unblock for 165.227.0.0/16

Status:    In progress

I think I have been blocked for no reason The message is below. You are currently unable to edit Wikipedia. Editing from your IP address range (165.227.0.0/16) has been blocked (disabled) on all Wikimedia wikis until 21:55, 1 October 2022 by Vituzzu (meta.wikimedia.org) for the following reason:

hosting service with open proxies such as 165.227.146.182 This block began on 21:55, 1 October 2017

You can contact Vituzzu to discuss the block and you may make unblock requests or file appeals at meta:Steward requests/Global. Your current IP address is 165.227.189.36. Please include all above details in any queries you make.

Global block for Spambot IP 2405:204:140F:3424:0:0:0:0/64

Status:    Not done

Persistent cross-wiki link spamming. Please Globally Block this IP for at least 3-6 months. LightandDark2000 (talk) 18:45, 17 August 2018 (UTC)

I found another IP that was behaviorally identical to the first set. The spamming activity on en.wiki can be seen here. LightandDark2000 (talk) 18:52, 17 August 2018 (UTC)
Too much collateral on the IPV4 range. Can you give an example of spam from the IPV6 range? I can't find any. – Ajraddatz (talk) 20:06, 30 August 2018 (UTC)
@Ajraddatz: Here are some of the recent examples of cross-wiki spamming: [1][2]. LightandDark2000 (talk) 09:31, 1 September 2018 (UTC)
X mark.svg Not done stale now, from what I can tell. – Ajraddatz (talk) 17:04, 14 October 2018 (UTC)

Global block for 78.14.138.0/22

Status:    Not done

Persistent link-spamming and vandalism within the last several months. (See here for example.) Most of the recent abuse is on the /24 range, but the abuse also extends to the wider /22 range as well. 🌀 LightandDark2000 (talk) 19:25, 8 September 2018 (UTC)

Then, why there is no local blocks? --Alaa :)..! 07:25, 11 September 2018 (UTC)
There was a local block on the most recently-abused IPs, but the local block(s) expired a few days after I had made this request. 🌀 LightandDark2000 (talk) 08:16, 15 September 2018 (UTC)
X mark.svg Not done stale now. – Ajraddatz (talk) 17:04, 14 October 2018 (UTC)

Global block for 99.203.28.117 and 2600:1:950F:CCA2:0:0:0:0/64

Status:    Not done

See Meta:Requests_for_help_from_a_sysop_or_bureaucrat/Archives/2018-09#Block_needed_for_range. The same troll is starting up again (this time as en:Special:Contributions/99.203.28.117) with registering accounts on different language Wikipedias and leaving threats and other such harassment (see de:Spezial:Beiträge/Loewehugs). I don't know if it's possible to include exceptions in globally locking talk pages or something, but if so, maybe it'd be easier to just semi-protect any talk page addressed to me on any project that isn't in English or Simple English (the only two languages I can really communicate in)? --Ian.thomson (talk) 01:04, 14 September 2018 (UTC)

X mark.svg Not done stale now. – Ajraddatz (talk) 17:06, 14 October 2018 (UTC)

Global block 77.179.111.244

Status:    Not done

The globally blocked user likely blocked as IP Special:Contributions/77.180.8.47 has now started to use dewiki to ask users to edit wikidata on their behalf when their edits at Wikidata directly get reverted. Despite having been asked to seek deblock prior to new edits, the user hasn't done so and keeps reverting edits. --Jura1 (talk) 17:35, 15 September 2018 (UTC)

X mark.svg Not done stale now. – Ajraddatz (talk) 17:09, 14 October 2018 (UTC)

Global block for the boy band vandal

Status:    In progress

They're still at it ... see this discussion at the French village pump. Please block for as long as practical, given this editor's proven relentlessness. --Graham87 (talk) 06:16, 16 September 2018 (UTC)

Global unblock for 128.210.106.73

Status:    In progress

This is an IP address that belongs to Purdue University. IP lookups return "Purdue University" or "West Lafayette, IN, USA" which is where Purdue University is located. It should have nothing to do with open proxies. Please unblock the IP. --Rwalle (talk) 22:52, 17 September 2018 (UTC)

@Vituzzu: --Alaa :)..! 21:11, 12 October 2018 (UTC)

Global block for 202.137.32.74

Status:    Not done

Cross-wiki vandalism. --Xiplus (talk) 12:01, 18 September 2018 (UTC)

X mark.svg Not done sorry for late. The lase edit on 22 Sep --Alaa :)..! 13:53, 10 October 2018 (UTC)

Global block for 92.91.246.51 and 109.8.69.21

Status:    In progress

Several other dynamic IP's are also punctually used, but on very busy ranges.

This vandal has restarted to vandalize (massive insertion of false information) after 1 month of global blocking of its two regulars IP's.

LTA since June 2018 on: frwiki (principal), enwiki, eswiki, itwiki and dewiki.

More infos :

Thank you.

(sorry for my bad english)

--Tractopelle-jaune (talk) 20:19, 18 September 2018 (UTC)

Global block for 184.147.48.152: Bell Canada toroon4664w vandal

Status:    In progress

Cross-wiki vandalism . --Tuanminh01 (talk) 10:11, 19 September 2018 (UTC)

Comment Comment Seems to be the same vandal with Steward requests/Global/2018-07#Global block for IP of the Bell Canada vandal. Using the same ISP and editing the same articles, e.g. en:Hiroshi Tsuburaya, es:Yukari Ōshima, and ja:カタリナ・ヘッカー.--侵入者ウィリアム (talk) 14:09, 19 September 2018 (UTC)
Comment Comment The vandal now uses IP:184.147.49.4 cross-wiki-contribs • ST • IP info • robtex • gblock • glist.--侵入者ウィリアム (talk) 19:08, 23 September 2018 (UTC)
Note: Given the changing IPs, it appears that a block on 184.147.48.0/23 cross-wiki-contribs • ST • IP info • robtex • gblock • glist would be the best option here. LightandDark2000 🌀 (talk) 07:55, 24 September 2018 (UTC)

Global block for 159.253.170.131

Status:    Done

being pretty feral for over a day, see abuselog.  — billinghurst sDrewth 22:55, 19 September 2018 (UTC)

Yes check.svg Done --Alaa :)..! 13:56, 10 October 2018 (UTC)

Global block for 38.122.71.170

Status:    In progress

Global block for 111.94.214.153

Status:    In progress

Long-term cross-wiki abuse: Mey Chan vandal. -ArdiPras95 (talk) 22:27, 23 September 2018 (UTC)

Global block for 49.7.4.0/24

Status:    In progress

Cross-wiki vandalism. --Xiplus (talk) 02:59, 25 September 2018 (UTC)

Global block for 185.46.76.35

Status:    In progress

Cross-wiki vandalism. --Guycn2 · ☎‏ 17:01, 26 September 2018 (UTC)

Global block for 185.46.76.12

Status:    In progress

Cross-wiki vandalism. --Guycn2 · ☎‏ 10:00, 27 September 2018 (UTC)

Global block for 69.89.16.0/20

Status:    In progress

Cross-wiki vandalism from a webhost netblock containing open proxies.   — Jeff G. ツ please ping or talk to me 16:49, 28 September 2018 (UTC)

This would be an expansion of the existing global blocks on 69.89.31.68 and 69.89.31.136.   — Jeff G. ツ please ping or talk to me 16:31, 29 September 2018 (UTC)

Global block for 120.37.186.10

Status:    Not done

Cross-wiki vandalism: user:Szm020730. --Buggia 08:34, 30 September 2018 (UTC)

X mark.svg Not done sorry for late. The lase edit since 29 Sep 2018 --Alaa :)..! 14:01, 10 October 2018 (UTC)

Global block for 185.244.217.240/28

Status:    In progress

From an analysis at enWS I am seeing several spamming IP addresses in the range 185.244.217.240/28 for over a month. Can I please get an extended block on this range. Thanks.  — billinghurst sDrewth 12:13, 1 October 2018 (UTC)

Global block for 85.10.48.0/20

Status:    Not done

Open proxy. --OJJ (talk) 13:45, 3 October 2018 (UTC)

X mark.svg Not done /20 range not an open proxy (only specific IPs in this range) --Alaa :)..! 13:59, 10 October 2018 (UTC)

Global block for 2001:E68:4439:7CAE:9D23:57CF:A004:40A5

Status:    In progress

Cross-wiki vandalism. SURJECTION ·talk·contr·log· 11:55, 4 October 2018 (UTC)

Global block for 2001:4898:80E8::/48

Status:    In progress

Cross-wiki spamming from a hosting netblock. Expansion of global block on 2001:4898:80E8:0:2F2C:1F28:6A34:8C70 cross-wiki-contribs • ST • IP info • robtex • gblock • glist by @Tegel.   — Jeff G. ツ please ping or talk to me 10:08, 8 October 2018 (UTC)

Global block for 184.96.229.38

Status:    Done

Block evasion/cross-wiki personal attacks, see also [[5]]. May want to block the host or range. --IanDBeacon (talk) 17:55, 11 October 2018 (UTC)

Yes check.svg Done by Vituzzu --Alaa :)..! 12:20, 12 October 2018 (UTC)

Global block for 126.100.198.29

Status:    Done

Cross-wiki vandalism. --SM7--talk-- 12:53, 12 October 2018 (UTC)

Yes check.svg Done --Alaa :)..! 13:18, 12 October 2018 (UTC)

Urgent Global Unblock request for 103.217.104.18

Status:    Not done

@Alaa@Linedwell @TNT @Ruslik0, Green Giant, and Rxy: @Jyothis:When I am trying to edit any page its showing following message...... 

   You do not have permission to edit this page, for the following reasons:
   
   Your IP address has been blocked on all wikis. The block was made by Vituzzu (meta.wikimedia.org). The reason given is per m:NOP .
   Start of block: 22:35, 5 November 2017
   Expiry of block: 22:35, 5 May 2019
   Your current IP address is 103.217.104.18

But untill yesterday, I could edit pages without any problem. Please check my edit history.

Please unblock the IP.

Thank You --Ra1han (talk) 19:10, 13 October 2018 (UTC)

Hi there. Since the IP is an Open Proxy, your best course of action would be to pursue a Global IP Block exemption, because Wikimedia has a policy against allowing Open Proxies and some VPN networks. LightandDark2000 🌀 (talk) 23:16, 13 October 2018 (UTC)
@LightandDark2000 Hi, thanks for the reply. I was testing the ip, it's not a open proxy. All device in my wifi network getting the same public ip. I think the guide line for checking proxy was not followed correctly. Please solve the issue.

Thank you.--Ra1han (talk) 10:10, 14 October 2018 (UTC)

So frustrating, no one seems to care. I wish someone would come to help.--Ra1han (talk) 12:55, 14 October 2018 (UTC)

X mark.svg Not done This IP address appears to be a proxy connection <Cyber Communication Bangladesh>, also blocked in ruwiki as OP. So, you can ask for global IP block exemption --Alaa :)..! 21:12, 14 October 2018 (UTC)

@Alaa Thanks for the reply. That Cyber Communication Bangladesh is my isp. I am requesting for a IP block exemption. Please check that.

Thank You--Ra1han (talk) 04:16, 15 October 2018 (UTC)

Can any one confirm me how [open proxies] Policy is applicable for blocking 103.217.104.18 as in [info] you can see this ip is static ip from my isp as you can see that 

   Services:	None detected
   Assignment:	Static IP

As per the policy , 

   Publicly available proxies (including paid proxies) may be blocked for any period at any time.

As you can see this ip was assigned static and not a open proxy. How the blocking rules apply in this case?

Thank You--Ra1han (talk) 09:28, 15 October 2018 (UTC)

Global block for 113.7.74.213

Status:    Done

Cross-wiki vandalism. --Xiplus (talk) 06:03, 14 October 2018 (UTC)

Yes check.svg Done --Alaa :)..! 12:04, 14 October 2018 (UTC)

Global block for 103.51.153.82

Status:    Done

Disruptive editing giving threat's sockip of User:Ivan Disouza . --Tiven2240 (talk) 16:47, 14 October 2018 (UTC)

Yes check.svg Done --Alaa :)..! 21:00, 14 October 2018 (UTC)

Global block for 184.96.229.38

Status:    Done

Globally blocked a few days ago. LTA, see enwikiquote. Vermont (talk) 17:28, 14 October 2018 (UTC)

Also please see [[6]]. --IanDBeacon (talk) 17:30, 14 October 2018 (UTC)
Yes check.svg Done by Bsadowski1 --Alaa :)..! 21:03, 14 October 2018 (UTC)

Global block for 195.143.129.132

Status:    Done

Globally blocked on the 11th for xwiki vandalism. They add xwiki links to other language versions of the article in the lead, randomly removes images and content, and machine translates content from the English Wikipedia to put on smaller wikis. Most active on so.wiki. Vermont (talk) 09:49, 15 October 2018 (UTC)

Yes check.svg Done for 1 week - TNT 💖 10:33, 16 October 2018 (UTC)

Global block for 69.174.249.0/25

Status:    In progress

Colocation webhost provider (ServerBeach/Cogeco-1) being used for crosswiki abuse by w:en:Wikipedia:Sockpuppet investigations/ConsumersDistributingonline / w:fr:Wikipédia:Faux-nez/Distribution aux Consommateurs. Ivanvector (talk) 13:55, 15 October 2018 (UTC)

Global block for Some IP Addresses

Status:    In progress

Cross-wiki vandal about USB related subjects. This person already used different IPs some months ago. A protection was set in august but the man restart vandalizing (and I started a new protect request on WD). Also, with an older IP adress, the man attacked an administrator by answering "LOL" to his answer (it was some months ago so I don't remember the page, but if you need it I will be able to find).

Cordially and thank you in advance. --Niridya (talk) 20:55, 15 October 2018 (UTC)

Global block for xwiki abuse

Status:    Done

This is the IP that changes maps about the China/Tibet border disputes and the India/Pakistan border disputes with the intent of disruption. It was globally blocked on the 8th by Tegel for 3 days, and has resumed it's xwiki vandalism after its block expired. Thanks, Vermont (talk) 00:15, 16 October 2018 (UTC)

Done for one week. Matiia (talk) 01:10, 16 October 2018 (UTC)

Global block for 2600:8800:3981:78A0:0:0:0:0/64

Status:    In progress

Block evasion by globally locked account MisterAnthony (talk · contribs). See, for example, this history at Wikidata. It's safe to do long-term (~6 months) blocks on these /64s. They usually stay allocated to him for close to a year. I range blocked for 6 months on English Wikipedia. NinjaRobotPirate (talk) 03:57, 16 October 2018 (UTC)

Global block for 121.140.88.142

Status:    In progress

Cross-wiki vandalism --XXBlackburnXx (talk) 14:05, 16 October 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 unlock for Ezekiel53746

Status:    On hold

Please see my current account's talk page here and WP:AN request here. In short, I want to appeal the block on the account at en~wiki and clear the mess I've made with it and other accounts. I feel bad that I still kept evading Ezekiel53746's block, let alone wasn't caught for it for years. I want to actually solve it. I was told that appeals will only be heard by the main account, but there's nothing I can do about that unless Ezekiel53746 is unlocked. Zeke Essiestudy (talk) 04:59, 2 September 2018 (UTC)

I have moved this discussion on "Requests_for_comment/Global_unlock_for_Ezekiel53746". Web SourceContent Management System 11:21, 7 September 2018 (UTC)

Global lock for Fauzty

Status:    In progress

Cross-wiki abuse,indefinite in zh.wiki and en.wiki[7],the unblock request was declined[8] in en.wiki(before in zh.wiki the similar unblock request same was declined[9][10]),and cross-wiki vandalism,personal attacks and disruptive editing only,also see en:Wikipedia:Miscellany_for_deletion/User:Fauzty/sandbox(Delete reason is:The user has been blocked. The material appears to be disruptive),en:User_talk:Fauzty#August_2018_2,en:User_talk:Fauzty#a_pityand,en:User_talk:Fauzty#there_is_no_disruptive_editing,en:User_talk:Fauzty#August_2018_3,Steward_requests/Global/2018-08#Global_lock_for_Fauzty and Steward_requests/Global/2018-08#Global_lock_for_Fauzty_2,some conduct similar to zh.wiki and User:Jasonnn~zhwiki[11],and using the en.wiki as a space to circumvent his/her blocks on the zh.wiki[12] and to continue disputes that originate in en.wiki,and zh.wiki is qualitative this user conduct is disrupt Wikipedia to illustrate a point and make too many unconvincing or disruptive unblock requests[13][14],zh.wiki and en.wiki community is not deal with the problem to this user,and this user is cross-wiki vandalism,personal attacks and disruptive editing only long time,and personal attacks in zh:User_talk:Fauzty([15][16](Wordpress是部落格平台，而不是新聞網站。為什麼Zenk0113要謊稱這個新聞網站。這大家不得而知。這種一見即知的謊言也要講的用意是?)[17](請你不要胡說八道)[18](關於血口噴人的 Zenk0113)[19][20](Bluedeck 血口噴人、屈打成招)[21](討論頁指引上寫明了，要根據事實而討論，而既然你有包庇謊報的Zenk0113的事實，AT你就是違反WP_討論頁指引，而且對本人做出極度不禮貌行為)[22](你多次破壞他人用戶討論頁，加入明顯不實指控。第一次不實指控、第二次不實指控、第三次不實指控)[23](Zenk0113竄改誤導機械人的證據在此鏈結)[24](事情是從我在互助客棧揭發User:Zenk0113鬼祟編輯)[25][26][27][28][29][30][31][32][33][34][35][36][37]),en:User_talk:Fauzty(難以置信的瘋狂封鎖行為，在此聲明：User:Alex Shih作出不符事實的指控，在本人指出基本事實，即本人沙盒創建於2018年元月，User:Alex Shih竟拒絕承認此一「簡單查證即可獲得理解」的基本事實，而對本人施加所謂的「封禁」。此一施加封禁的惡劣行徑，已經證明User:Alex Shih阻止我自己本人為自己申明基本事實。本人所寫的文章，本人可以作出解答。而User:Alex Shih此一封禁之目的，在於阻止本人對自己所寫的文章作出本人的權威性解釋，意圖阻止「來自作者的說明」，意圖製造「缺席審判」),en:User:Fauzty/sandbox,en:User:Fauzty/sandbox/02,en:User:Fauzty/sandbox/03(「沒發生編輯戰Zenk0113卻謊稱發生編輯戰」，「Bluedeck哄騙聲稱應該對Zenk0113另案處理，實際上是設陷阱」，「胡蘿蔔偽報胡亂舉報誣報，至今未曾向受害者道歉」) and en:User:MCC214/Fauzty & MCC214 Talk page(因此自2018年11月25日起，中文維基百科必然必須永久關閉/長久如此，中文維基百科已經長期連續不斷違背維基百科基本理念，永久關閉是必然的結果/那麼中文維基百科當然理應永久關閉/所以2018年11月25日起中文維基百科即將永久關閉/中文維基百科因為違反編輯方針必須於2018年11月25日永久關閉/很明顯在2018年11月25日中文維基百科必須永久關閉/反正2018年11月25日中文維基百科的永久關閉，已經成為定局)(zh.wiki would close indef in 25 November),I believe this user would continue to cross-wiki abuse,I think global lock this user is the best opportunity,also,if something can be done about that too,that would be great.--MCC214Talk with me#Contributions with me 10:53, 18 September 2018 (UTC)

I only edit once (at main namespace) and it's an orinary edit. The so-called block is itself a violation to en:WP:EXPLAINBLOCK. 本人已經指出 Alex Shih 所寫的完全與所發生的事實相反，對本人實施難以置信的瘋狂封鎖行為。本人不曾違反任何規定，倒是 Alex 拒絕說明封禁，長達一個月，至今仍然拒絕說明。已經構成長期連續違背 en:WP:EXPLAINBLOCK，本人只編輯一次，本人對 Alex 提問之後，Alex 竟然以封禁代替回答，一個月來提不出任何本人曾經違反任何規定的證據。因為本人在該討論期間，只在主條目編輯過一次，亦屬於極為普通的編輯，任何封禁皆不可能施加在本人身上。任何對於本人的封禁皆已經違反英文維基百科的 en:WP:EXPLAINBLOCK。--Fauzty (talk) 15:37, 18 September 2018 (UTC)
Alex Shih did not provide any reviewable evidence, which is required by the policy, in fact did not proveide any evidence at all. When I asked him, he refuse to answer. Clear violation to en:WP:EXPLAINBLOCK. Alex used block to answer. Alex still deny the fact that I only edit once (at the main namespace), and my editing is an ondinary one. Why editing once constitutes a block? Alex still refuses to provide evidence when asked, and still refuses to answer.--Fauzty (talk) 15:45, 18 September 2018 (UTC)
Alex still refused to answer the question I asked in [38]. I asked it in August. He still refuses to answer to this day. Alex's description of the status of the sandbox seems very far from what it was. For the most part, what Alex said is contrary to the fact. Alex still deny the fact that THERE ARE academic papers. Denial is the first sign.--Fauzty (talk) 15:59, 18 September 2018 (UTC)
Blocking someone asking you questions is itself a violation to the en:WP:blocking policy. Blocking the very someone who is asking you equals to "DID NOT ANSWER", equals to "REFUSE TO EXPLAIN". An admin who refusing to explain is an admin violating the policy of en:WP:blocking policy. --Fauzty (talk) 16:07, 18 September 2018 (UTC)
This is very serious to cross-wiki abuse(vandalism,personal attacks and disruptive editing),and violate en:wikipedia:User_pages#What_may_I_not_have_in_my_user_pages? long time after this user have been indefinite in zh.wiki and en.wiki,Support Support global lock,and I hope meta stewards can check this user edit,because this is very serious to cross-wiki abuse(vandalism,personal attacks and disruptive editing),also,this user most edit is only personal attacks and disruptive editing.--MCC214Talk with me#Contributions with me 08:23, 19 September 2018 (UTC)
And Alex Shih blocked Fauzty before,Alex Shih already said:Fauzty, do not be disingenuous. Only one short section of the main sandbox is about what you are referring to, and sandbox 2 and 3 are all collections of evidences. If you intentionally deny the obvious again, you will be swiftly blocked for disruptive editing as there is no tolerance for this behaviour on the English Wikipedia[39],but this user completed[40][41][42][43][44],and Alex Shih will block Fauzty,so this user said is not completed face,and another admin same said:Since you say this is not a language issue, I have to conclude you're being deliberately disingenuous by ignoring others arguments and the content of your own sandboxes. There may be some academic papers there, but there's also lots of content that isn't relevant to any academic papers, government systems, or the English Wikipedia. Alex Shih warned you about denying the obvious; you continued[45],but this user only in order to disrupt Wikipedia to illustrate a point,and cross-wiki abuse(vandalism,personal attacks and disruptive editing) in there after this user have been indefinite in zh.wiki[46][47] and en.wiki[48][49],and some conduct similar to zh.wiki[50][51][52],also,this user only filled up with a series of vidence of misconduct against various editors/administrators in the sandbox on this user.--MCC214Talk with me#Contributions with me 08:38, 19 September 2018 (UTC)
  • Support making the lock on Fauzty global and a steward lock. The editor appears to be using the English Wikipedia to argue about an issue on the Chinese Wikipedia, and that is a cross-encyclopedic issue, and the editor might go to another Wikipedia if not blocked. The oppose request by the editor, like all of the posts to his talk page, is a wall of text. Robert McClenon (talk) 00:03, 22 September 2018 (UTC)
Well, it seems I declined the last lock request, so I won't handle this. That said, I can't find anything outside of enwiki and zhwiki and the user is already blocked on both wikis, so a lock isn't needed, unless some evidence is shown about some on going cross-wiki abuse. Matiia (talk) 17:53, 22 Sember 2018 (UTC)
Matiia,but the problem to this user what matters is that this user are using there as a space to circumvent your blocks on the Chinese Wikipedia and English Wikipedia and to continue disputes that originate there.--MCC214Talk with me#Contributions with me 11:22, 26 September 2018 (UTC)
@MCC214: The user is blocked on both wikis, is there any abuse on other wikis? Matiia (talk) 21:32, 26 September 2018 (8 (UTC)

Global lock for GabriellePalafox & RileyLair1 from it.wv + 2 IPs

Status:    In progress

spambot on it.WV (RileyLair1 is stopped by filter 1 on WV, 185.226.72.169 and 109.230.203.163 stopped by Global filters 104 & 102 )--Wim b / [ t ] 17:33, 19 September 2018 (UTC)

add 2 another spambots from it.wq:
Lock all:

Global unlock for Sohosanna and etc

Status:    In progress

They were not blocked as a sock of Unypoly.

They were locked by Steward due to notorious misleading of Wikitori.

kowp unblocked Sohosanna today.

Wikimedia should unlock them. —The preceding unsigned comment was added by 호로조 (talk) 01:11, 25 September 2018 (UTC)

Global lock for George Reeves Person sockpuppets and IPs

Status:    Done

The most recent sockpuppets of GRP, posting spam and links to hate pages about those who oppose his spam and misinformation campaign. Blocking the underlying IPs -- Chicago Public Library (probably 66.99.0.0/22 and 64.107.0.0/22) would be helpful as well. Antandrus (talk) 00:13, 27 September 2018 (UTC)

The entire ranges for AS19480 CHICAGO PUBLIC LIBRARY are: 64.107.0.0/22, 64.107.131.0/24, 66.99.0.0/22 and 66.99.4.0/23. -★- PlyrStar93 →Message me. ← 00:18, 27 September 2018 (UTC)
In more than 12 years I've never seen him on 64.107.131.0/24 or 66.99.4.0/23 (may be the branches he edits from) - but any shutdown of these ranges would be helpful. They seem to be his primary locations these days. Antandrus (talk) 01:04, 27 September 2018 (UTC)
Followup - please CU 64.107.219.0/24 (Triton College) -- while he was there yesterday evening he probably made some sleepers. I just removed a bunch of his spamlinks on fi, sv, tr, sr. Antandrus (talk) 17:24, 2 October 2018 (UTC)
It appears that Alaa accidentally introduced the error in this edit ([53]) only a few hours ago, so that was probably not the reason why this request is being overlooked. Alex Shih (talk) 03:23, 15 October 2018 (UTC)
Locked the ones I could find. Thanks for the report. --Bsadowski1 (talk) 03:39, 15 October 2018 (UTC)

Global lock for Love244506

Status:    In progress

This is a troll from Hebrew Wikipedia that registered and began vandalizing other projects. Dolev (talk) 17:45, 27 September 2018 (UTC)

@דולב: which wikis? Matiia (talk) 22:00, 27 September 2018 (UTC)
English Wikinews for example. Dolev (talk) 10:07, 28 September 2018 (UTC)
@דולב: what wikis besides that? Matiia (talk) 17:17, 29 September 2018 (UTC)
Currently, none, but meanwhile the troll has registered under another user name:
You should revert all his edits, lock all of his users and prevent him from registering again. Dolev (talk) 19:29, 27 September 2018 (UTC)

Global lock for socks of Avoided (or an impostor)

Status:    In progress

19th 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) 09:53, 29 September 2018 (UTC)

Global lock for socks of Avoided (or an impostor)

Status:    In progress

22nd to 24th:

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:56, 29 September 2018 (UTC)

Global lock for socks of Avoided (or an impostor)

Status:    In progress

25th to 27th:

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:01, 30 September 2018 8 (UTC)

Global lock for socks of Avoided (or an impostor)

Status:    In progress

28th to 30th:

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) 01:38, 3 Octobeer 2018 (UTC)

Global lock for socks of Avoided (or an impostor)

Status:    In progress

1st to 3rd:

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:45, 3 Octobe 2018 (UTC)

Global lock for Raymondskie99 socks

Status:    In progress

Lock all:

Long-term abuse. theinstantmatrix (talk) 23:32, 11 October 2018 (UTC)

Global lock for LTA Daniel "Danny" Wilson socks

Status:    In progress

Lock all:

Socks of an LTA. Appears to be related to the Daniel "Danny" Wilson sockfarm. LightandDark2000 🌀 (talk) 00:14, 13 October 20tober 2018 (UTC)

Global lock for LTA Catcreekcitycouncil

Status:    Done

Socks of the LTA User:Catcreekcitycouncil. This user is responsible for extremely persistent abuse, serial socking, personal attacks, trolling, and possibly some cross-wiki abuse over the course of the last 6 years. Given the persistent abuse and attacks, this LTA's master account should be locked. LightandDark2000 🌀 (talk) 05:22, 13 O October 2018 (UTC)

Vast majority of them has no recent edits to cross check against. I have checked and locked what I could. --Jyothis (talk) 12:45, 15 October 2018 (UTC)

Global lock for Willy ffhd is innocent

Status:    In progress

Lock all:

Long-term abuse.--SkyGazer 512 (talk) 19:57, 13 October 2018 (UTC)

Added another obvious sock. Please also check for sleepers. LightandDark2000 🌀 (talk) 23:07, 13 October 2018 (UTC)
Who is this LTA? Matiia (talk) 00:11, 14 October 2018 (UTC)
I don't know who this LTA is, but it is the same LTA as the one that created this Locked account: Willy ffhd sd fndfn rgn fgfngj fgfjjfj fnffiiicccccc fgdnrreowowpwpw4 44 4 4 4 4ffff. @Oshwah: Oshwah or one of the other Stewards might know; my guess is that that is a "Willy on Wheels" imitator troll. LightandDark2000 🌀 (talk) 00:27, 14 October 2018 (UTC)

Global lock for LTA Glapz socks

Status:    In progress

Obvious sock of the serial LTA vandal Glapz, given that this account made an edit that was completely identical to another known IP sock of Glapz. Please also check the account and the IPs for sleepers. LightandDark2000 🌀 (talk) 23:16, 13 October 2018 (UTC)

Note to Stewards: This LTA claims to be a different person from Catcreekcitycouncil, even though both LTAs share some behavioral similarities (you can see more on Catcreekcitycouncil's behavior at WP:LTA/CCCC). It would be worth checking to see if this is the case, or if Glapz is a new sockfarm of CCCC. LightandDark2000 🌀 (talk) 23:33, 13 October 2018 (UTC)
I've requested a review of the account's block, as it's not at all convincing. zzuuzz (talk) 23:47, 13 October 2018 (UTC)
Withdrew the Lock request for the named account - the account appears to be unrelated. Please still Check the IPs for sleepers. LightandDark2000 🌀 (talk) 00:16, 14 October 2018 (UTC)

I re-opened this report, after replacing Cchen49 with an actual Glapz sock, ֍֍. Please Lock this account. LightandDark2000 🌀 (talk) 00:01, 14 October 2018 (UTC)}}

This LTA is still socking and vandalizing. Please Lock his accounts and run a sleeper check. LightandDark2000 🌀 (talk) 21:56, 15 October 2018 (UTC)

Global lock for Nipponese Dog Calvero

Status:    In progress

Lock all:

Long-term abuse. -★- PlyrStar93 →Message me. ← 06:40, 14 October 2018 (UTC)

Lock all:

Add--Lanwi1(talk) 15:17, 16 October 2018 (UTC)

Global lock for Jessechi sock accounts

Status:    Done

Lock all:

Long-term abuse, sock of Jessechi. -★- PlyrStar93 →Message me. ← 06:54, 14 October 2018 (UTC)

--Jyothis (talk) 12:13, 15 October 2018 (UTC)

Global lock for Spambot LTA Black magic specialist sock

Status:    Done

Another sock of the "Black magic specialist" spambot sockfarm. Please also check for sleepers and Globally Block the underlying IP(s). LightandDark2000 🌀 (talk) 20:45, 14 October 2018 (UTC)

--Jyothis (talk) 12:27, 15 October 2018 (UTC)

Global lock for AlviZamanTheHoaxSchoolEditor

Status:    In progress

Long-term abuse, sock of Alvi Z. -★- PlyrStar93 →Message me. ← 08:03, 14 October 2018 (UTC)

Global lock for socks of Ivan Disouza

Status:    In progress

Sockpuppet of LTA sock master User:Ivan Disouza --Tiven2240 (talk) 17:07, 14 October 2018 (UTC)

Enwp SPI can be found here--Tiven2240 (talk) 06:24, 16 October 2018 (UTC)

JaySmith2018 sock

Status:    Done

LTA. Vermont (talk) 19:51, 14 October 2018 (UTC)

Yes check.svg Done by Alaa. Hiàn (talk) 03:58, 15 October 2018 (UTC)

Zaner25 sock

Status:    In progress

LTA and WP:DUCK. JC7V7DC5768 (talk) 03:52, 15 October 2018 (UTC)

Alec Smithson socks

Status:    Done

Check-user on Commons has identified these Smithson socks – please see c:Commons:Administrators' noticeboard/User problems#Indef block for 13 sockpuppets of globally locked User:Alec Smithson. Four others – CarmelaPolli (talk · contribs), SandraPol23 (talk · contribs), Arcate818 (talk · contribs) and Arch Bernocchi (talk · contribs) – are already locked. Thank you, Justlettersandnumbers (talk) 11:24, 15 October 2018 (UTC)

--Jyothis (talk) 12:14, 15 October 2018 (UTC)

Global lock for GabrielDyer

Status:    In progress

Global lock for spambots

Status:    In progress

Lock all:

I added a few more cross-wiki spambots. LightandDark2000 🌀 (talk) 19:03, 15 October 2018 (UTC)

Global lock for Fuerdai vandal

Status:    In progress

Long-term abuse. SA 13 Bro (talk) 16:50, 15 October 2018 (UTC)

Please also run a sleeper check. LightandDark2000 🌀 (talk) 19:02, 15 October 2018 (UTC)

Global lock for 2 spambots

Status:    In progress

Spambots, blocked on nl.wiktionary after triggering global filters 69 and 72 --MarcoSwart (talk) 04:10, 16 October 2018 (UTC)

Global lock for EmilMounts46958 & more spambot

Status:    In progress


Global lock for संदेश हिवाळे and dagduba lokhande

Status:    In progress

Lock all:

This seems as a revenge appeal to me. The both users are in conflict on w:mr and there is a bad history of this both users in conflicts (complainant and respondent). Requesting to keep request on hold untill local resolution of the matter. User:Sandesh Hiwale had no block history on w:mr and does not qualify policy. Rest all shall as per the wisdom of the steward --Tiven2240 (talk) 14:57, 16 October 2018 (UTC)

Global lock for Flasty Jam and socks

Status:    In progress

Lock all:

Cross-wiki abuse: harrassment on Boing! said Zebedee - [54] [55] [56] theinstantmatrix (talk) 05:12, 16 October 2018 (UTC)

Also: [57] [58] theinstantmatrix (talk) 12:22, 16 October 2018 (UTC)

See also

Cooperation requests for: comments (local) (global) · translation · logos

Retrieved from "https://meta.wikimedia.org/w/index.php?title=Steward_requests/Global&oldid=18475049"