Steward requests/Global

From Meta, a Wikimedia project coordination wiki
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 Spambot IP 2405:204:140F:3424:0:0:0:0/64

Status:    In progress

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)

Global block for 78.14.138.0/22

Status:    In progress

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)

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

Status:    In progress

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)

Global block 77.179.111.244

Status:    In progress

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)

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)

Global block for 202.137.32.74

Status:    In progress

Cross-wiki vandalism. --Xiplus (talk) 12:01, 18 September 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 robtexgblockglist.--侵入者ウィリアム (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 robtexgblockglist would be the best option here. LightandDark2000 🌀 (talk) 07:55, 24 September 2018 (UTC)

Global block for 159.253.170.131

Status:    In progress

being pretty feral for over a day, see abuselog.  — billinghurst sDrewth 22:55, 19 September 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)

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 AbraKadavrovkakaetgromko

Status:    In progress
  • AbraKadavrovkakaetgromko (talk • contribs • block • x-wiki • CA • lwcheckuser)
  • On 6 September 2018, this user was permanently blocked in the Russian Wikipedia. Since 3 September, he began to vandalize "Адыгэй" page in the Adyghe Wikipedia. He continues to revoke the edits of users who undo his vandalisms. Obviously, this user does not intend to make a positive contribution. Also, with transliteration, user's name violates the ethical norms in Russian language (~ "Abra Kadavrov doing poo-poo loudly").--Soul Train (talk) 21:45, 25 September 2018 (UTC)

Global unlock for Ezekiel53746

Status:    In progress

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 socks of Avoided (or an impostor)

Status:    In progress

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:04, 7 September 2018 (UTC) C)

Global lock for socks of Avoided (or an impostor)

Status:    In progress

3rd to 4th:

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) 12:16, 8 September 2018 (UT2018 (UTC)C)

Global lock for LTA sock

Status:    In progress

Sock of an LTA user. The Wikimediæ account is an obvious sock of the person behind the Locked Wikipediæ account. The IP network listed underneath is also an Open Proxy network. 🌀 LightandDark2000 (talk) 20:29, 8 Septembember 2018 (UTC)

@There'sNoTime: Can you please take a look at this report? Thanks. LightandDark2000 🌀 (talk) 00:19, 24 September 2018 ( 2018 (UTC)

Global lock for Cross-wiki vandal

Status:    In progress

Cross-wiki vandalism. Given the rapid page-move vandalism on en.wikipedia and this account's activity, it is very likely that this account is a sock of a recent LTA vandal, or a Willy on Wheels imitator troll. Please check for sleepers and also Globally Block the underlying IP(s). 🌀 LightandDark2000 (talk) 07:04, 15 Septembeeptember 2018 (UTC)

Global lock for Fauzty

Status:    In progress

Cross-wiki abuse,indefinite in zh.wiki and en.wiki[5],the unblock request was declined[6] in en.wiki(before in zh.wiki the similar unblock request same was declined[7][8]),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[9],and using the en.wiki as a space to circumvent his/her blocks on the zh.wiki[10] 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[11][12],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([13][14](Wordpress是部落格平台,而不是新聞網站。為什麼Zenk0113要謊稱這個新聞網站。這大家不得而知。這種一見即知的謊言也要講的用意是?)[15](請你不要胡說八道)[16](關於血口噴人的 Zenk0113)[17][18](Bluedeck 血口噴人、屈打成招)[19](討論頁指引上寫明了,要根據事實而討論,而既然你有包庇謊報的Zenk0113的事實,AT你就是違反WP_討論頁指引,而且對本人做出極度不禮貌行為)[20](你多次破壞他人用戶討論頁,加入明顯不實指控。第一次不實指控、第二次不實指控、第三次不實指控)[21](Zenk0113竄改誤導機械人的證據在此鏈結)[22](事情是從我在互助客棧揭發User:Zenk0113鬼祟編輯)[23][24][25][26][27][28][29][30][31][32][33][34][35]),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 [36]. 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[37],but this user completed[38][39][40][41][42],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[43],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[44][45] and en.wiki[46][47],and some conduct similar to zh.wiki[48][49][50],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)

Global lock for LTA My Royal Young socks

Status:    In progress

Socks of the LTA My Royal Young. Please also check for sleepers and Globally Block the underlying IPs for at least 6 months, given the persistent abuse. 🌀 LightandDark2000 (talk) 02:25, 19 September 2018 (UTC)

Please also Globally Block the IPs (especially the first range) because it looks like there is also a significant amount of socking activity coming from them. LightandDark2000 🌀 (talk) 18:04, 25 September 2018 (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 lock for Alec Smithson socks

Status:    In progress

Wikipedia:Long-term abuse/Alec Smithson. Is it worth trying check-user here? Thank you, Justlettersandnumbers (talik0|talk) 20:31, 23 September 2018 (UTC)

Global lock for LTA FrancoLeymas sock

Status:    In progress

Sock of the LTA User:FrancoLeymas, who is known for cross-wiki abuse. Please also check for sleepers. LightandDark2000 🌀 (talk) 04:36, 24 September 2018 (UTC)

Global lock for sock of LTA User:118 alex or someone else

Status:    In progress

Possible sock of the cross-wiki LTA User:118 alex, according to the SPI page of that LTA. This account is a confirmed sock of TimothyHouse1 and possibly related to Patch101. Whoever this account belongs to, it's obvious that cross-wiki abuse is involved. LightandDark2000 🌀 (talk) 05:04, 24 September 2018 (UTC)

Global lock for socks of Avoided (or an impostor)

Status:    Done

17th to 18th:

+

+

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) 10:40, 24 September 2018 (UTC)

Yes check.svg Done masti <talk> 10:33, 25 September 2018 (UTC)

Global lock for spambots

Status:    In progress
Added another one. Hiàn (talk) 13:33, 24 September 2018 (UTC)
Added yet another one. LightandDark2000 🌀 (talk) 02:26, 26 September 2018 (UTC)

Global lock for LTA

Status:    In progress

Long-term abuse, See Special:CentralAuth/MovieFan2018 for most obvious sock. Vermont (talk) 13:40, 24 September 2018 (UTC)

Global lock for LTA

Status:    Done

LTA, factual error also. L293D ( • ) 14:37, 24 September 2018 (UTC)

The account has been Globally Locked and Hidden, since it is no longer visible in the Global Account logs. LightandDark2000 🌀 (talk) 17:57, 25 September 2018 (UTC)

Global lock for RosemaryD37

Status:    In progress

Probably spambot, blocked on nl.wiktionary after triggering global filter 72 --MarcoSwart (talk) 22:44, 24 September 2018 (UTC)

Global lock for User:Newname

Status:    In progress

Someone created this account c. 2005 to test the then-new user renaming system at en:wp, and as it's a test/role account, it's been blocked consistently for years. Problem is, whenever someone makes a malformed request at en:wp:WP:CHU (example), a link to en:User:Newname appears, and the blocking admin gets a notification. Could this account be locked, so that we can unblock it at en:wp and spare the latest blocking admin from unhelpful notifications? Nyttend (talk) 23:48, 24 September 2018 (UTC)

Does the lock prevent notification? If it does, sure. — regards, Revi 09:02, 25 September 2018 (UTC)
-revi, I'm not sure if it directly prevents notification, but unblocking prevents notification, and locking enables unblocking, so at least indirectly it prevents it. Nyttend (talk) 22:55, 25 September 2018 (UTC)

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 House of Frazerdai

Status:    Done

Long-term abuse, obvious sock of BMX on WheeIs.--SkyGazer 512 (talk) 02:41, 25 September 2018 (UTC)

Done. — regards, Revi 08:57, 25 September 2018 (UTC)

Global lock for ModernERY2

Status:    Done

Cross-wiki vandalism and nonsense insertion. -★- PlyrStar93 Message me. 02:56, 25 September 2018 (UTC)

Done by Bsadowski1. — regards, Revi 08:59, 25 September 2018 (UTC)

Global lock for JustineMacCullag

Status:    Done

Spambot, blocked on nl.wiktionary after attempt to add blacklisted spamlinks. --MarcoSwart (talk) 07:17, 25 September 2018 (UTC)

Done. — regards, Revi 09:01, 25 September 2018 (UTC)

Global lock for spambot

Status:    Done

Spambot Vermont (talk) 11:35, 25 September 2018 (UTC)

Yes check.svg Done XenrøsE 00:14, 26 September 2018 (UTC)

Global lock for Caillou Pettis

Status:    In progress

Cross-wiki abuse. -★- PlyrStar93 Message me. 13:04, 25 September 2018 (UTC)

Global lock for Spambots

Status:    In progress

Accounts that triggered SPAM filters in pt.wikinews --Editor D.S (talk)Meta-Wiki Patroller.png 15:58, 25 September 2018 (UTC)

Global lock for Impersonator account

Status:    In progress

Obvious impersonation of another user (HickoryOughtShirt?4), and also a vandalism-only account. Please also check for sleepers. LightandDark2000 🌀 (talk) 17:56, 25 September 2018 (UTC)

Global lock for JonelleRothstein

Status:    In progress

Spambot, blocked on nl.wiktionary after attempt to add blacklisted spamlinks. --MarcoSwart (talk) 19:55, 25 September 2018 (UTC)

Global lock-hide for the username abuse

Status:    Done

Long-term abuse: also offensive account. Web SourceContent (Management System) 21:48, 25 September 2018 (UTC)

Yes check.svg DoneDefender (talk) 22:13, 25 September 2018 (UTC)

Global lock for KarineHarney442

Status:    In progress

Spambot. Esteban16 (talk) 22:41, 25 September 2018 (UTC)

Global lock for latest batch of STEFANY CHAR socks

Status:    In progress

Long-term abuse: STEFANY CHAR. XenrøsE 00:30, 26 September 2018 (UTC)

Global lock for JustinPD1

Status:    In progress

Global lock for Ipassedthefifthgrade

Status:    In progress

Cross-wiki vandalism. LightandDark2000 🌀 (talk) 02:37, 26 September 2018 (UTC)

Global lock for LTA Arturo Gustavo socks

Status:    In progress

Lock all:

Socks of the Arturo Gustavo LTA. The newest accounts are listed at the top. (The last account is possibly this LTA's original account, given the behavior and mention of an IP that Arturo Gustavo has used in the past.) The listed IP has also been vandalizing here on Meta. Please check for sleepers and Globally + Locally Block the underlying IPs (including the one listed above) for at least several months, to prevent further abuse. LightandDark2000 🌀 (talk) 03:42, 26 September 2018 (UTC)

Global lock for LTA Manda 1993

Status:    In progress

-ArdiPras95 (talk) 06:09, 26 September 2018 (UTC)

Global lock for OIADarlene

Status:    In progress

Spambot, blocked on nl.wiktionary after attempt to add blacklisted spamlinks. --MarcoSwart (talk) 09:10, 26 September 2018 (UTC)

Global lock for Medporn

Status:    In progress

Long-term abuse. All as same preson. Web SourceContent (Management System) 10:18, 26 September 2018 (UTC)

Global lock for Nipponese Dog Calvero sock

Status:    In progress

Long-term abuse. Sock of User:Nipponese Dog Calvero. Web SourceContent (Management System) 10:24, 26 September 2018 (UTC)

See also