Steward requests/Global

From Meta, a Wikimedia project coordination wiki
< Steward requests
This is an archived version of this page, as edited by 1234qwer1234qwer4 (talk | contribs) at 14:11, 16 October 2021 (Reporting JaniBrubaker08 (TwinkleGlobal)). It may differ significantly from the current version.
Shortcut:
SRG
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; and (un)locks apply to global accounts.


Cross-wiki requests
Meta-Wiki requests

Requests for global (un)block

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.
Please describe the kind of cross wiki abusive activity you see from the IP. Saying an IP 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) 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 the address(es) to be blocked or unblocked

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@wikimedia.org

Global block for 104.218.66.37

Status:    Done

Long-term abuse. --कन्हाई प्रसाद चौरसिया (talk) 09:59, 16 October 2021 (UTC)[reply]

Done ----Alaa :)..! 12:26, 16 October 2021 (UTC)[reply]

Global block for 2600:1006:B000:0:0:0:0:0/40

Status:    In progress

Long-term abuse. Cross-wiki abuse. Global lock evasion by Birmal123. ---- Jeff G. ツ (please ping or talk to me) 10:14, 16 October 2021 (UTC)[reply]

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

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 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-stewardsconnect 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-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 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 Halemo

Status:    In progress

An Internet troll. A sockmaster. Long-term abuse. Operator of Lock all:

and a lot of older socks. It also operated today 213.137.65.237 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye and 185.3.145.28 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye.

It has already been blocked under משה הלוי (talk • contribs • block • xwiki-contribs • xwiki-date (alt) • CA • ST • lwcheckuser) in 2007, due to endless harassment of Gilgamesh.
Here it is written about this person, as well as here. Dgw (talk) 00:48, 11 September 2021 (UTC)[reply]

Yesterday it made an edit warring in the Hebrew Wikipedia in the article about Harry Borochow. Its war was against בורה בורה here and here, and against זור987 here. In the edit summary of its war versus זור987, it wrote: "I support the return of the photo, but once it has been opposed, the discussion should be exhausted and it should not be returned in an edit war by the army of Arnon's lawyers". As a troll, it supported the return of the photo, but made edit warring against the return of the photo just for the war. Furthermore, Arnon Borochov was not exist in the Hebrew Wikipedia. Only ארנון בורוכוב and ארנון ב edited in the Hebrew Wikipedia. Both of them were Halemo itself, and both of them were globally locked.
It also advertised as an anonymous 213.137.65.237 in the talk page of Harry Borochow that Arnon Borochov was the grandson of Ber Borochov although it was not written anywhere. The single person who claimed it was Halemo itself, but it did not use any source of its claim, violating the rule of BLP in any Wikipedia page, including talk pages. As an anonymous 213.137.65.232, it put the template {{"גוגל|"ארנון בורוכוב}} and wrote in the edit summary: "Google knows e v e r y t h i n g", but did not provide any proof that Arnon was the grandson of Ber Borochov. Google showed mainly articles which Halemo wrote itself, there he claimed that Arnon was the grandson, but did not provide any source.
As an anonymous 213.137.65.232, it wrote to the administrator Yoavd who was also a chess expert: "Arnon's sock account has been blocked globally by Matanya, and you are probably aware that the user who ran to protect him has been permanently blocked and returned in disguise and continues to violate the rules. Starling, crow, etc." but again it did not deal with any issue of Harry Borochow. Furthermore, user:Arnon Borochov did not write anything in the Hebrew Wikipedia. Only ארנון בורוכוב and ארנון ב wrote there, and they were both Halemo.
It also tagged again experts of Chess and experts of Zionism in the notability discussion of Harry Borochow as well as tagging another wikipedian who was not involved in the current discussion, just for increasing the flame.
In the blocking reason of משה הלוי (talk • contribs • block • xwiki-contribs • xwiki-date (alt) • CA • ST • lwcheckuser), who is Halemo, it has already been written by Odedee: "טרול" (Troll). Dgw (talk) 02:25, 11 September 2021 (UTC)[reply]
Here it canvassed by 213.137.65.227 the HeWP CU to explain at Meta why they checked user:Arnon Borochov after user:ארנון בורוכוב had stolen its identity. Dgw (talk) 19:58, 15 September 2021 (UTC)[reply]
After it had failed to bring here the HeWP CU, it tried to dig by user:213.137.65.217 Matanya who confirmed on Sept. 17 2021 that user:ארנון בורוכוב stole the identity of user:Arnon Borochov. User:213.137.65.217 investigated Matanya if he truly wrote it, although Matanya wrote it on his own talk page in the HeWP. Dgw (talk) 00:15, 22 September 2021 (UTC)[reply]
User:חיים 7 is deeply involved with it. It advertised three times copyvio links to a scanned article of Yedioth Ahronoth and to a screenshot of a living person from Channel 10, which were both advertised on the website of the sockmaster Halemo. It made an endless outing in spite of nobody had proven it, keeping warning HeWP users who deleted the outing, and voided adminship edits. It also claimed that a sock of user:ארנון בורוכוב was not locked, in spite of it was locked. Dgw (talk) 02:04, 22 September 2021 (UTC)[reply]
User:חיים 7, who is involved with Halemo, hounded me more than a time and more than twice, although ערן clearly prohibited at least three times hounding in the HeWP. חיים 7 canvassed twice in the HeWP RFC the application of ערן in the RFH, here and here. The application in the RFH was declined, as well as the appeal of קיפודנחש. User חיים 7 is an interface administrator in the HeWP and should not carry on this role, after it had been warned several times by דגש, who was an administrator as well as an interface administrator. Here is an example of a warning. In the end, IKhitron, another interface administrator, moved from the mainspace the text which חיים 7 made. Dgw (talk) 15:22, 28 September 2021 (UTC)[reply]
Canvassing and outing by 213.137.65.222 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye, which is operated by the sockmaster Halemo (talk • contribs • block • xwiki-contribs • xwiki-date (alt) • CA • ST • lwcheckuser), and an additional canvassing today by חיים 7 in the HeWP RFC. I requested to lock Halemo, but 213.137.65.222 misled חיים 7, and חיים 7 misled the HeWP RFC.
A similar hounding was made by Tony Nescafe (talk • contribs • block • xwiki-contribs • xwiki-date (alt) • CA • ST • lwcheckuser), who was also operated by the sockmaster Halemo.
On September 22, 2021, 213.137.65.197 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye misled and canvassed the HeWP administrator HaShumai by writing: "Dorian builds theories on dilapidated foundations and misleads administrators and stewards". Matanya wrote: "A third user had an access to the Wiki accounts". 213.137.65.197 wrote: "The identity of the user with access to Dorian's account was not specified, although in this case it does not matter if it was a blocked x or a troll y". Matanya and 213.137.65.197 wrote the same. No misleading has been done by me. Halemo and its long list of socks hound me.
Furthermore, חיים 7 requested ערן and ביקורת to make a block in the HeWP, due to an SRG application to lock Halemo. Halemo was involved and suspected of computer issues. I was not suspected of anything. Dgw (talk) 16:10, 1 October 2021 (UTC)[reply]
Yesterday חיים 7 again canvassed my application to the HeWP RFC. It also misled the HeWP users by translating to the wrong Hebrew. It claimed (in Hebrew) that I claimed of violating my copyrights. I edited by the cc by-sa licence in the WM projects, and my copyrights were not violated. "Yedioth Ahronoth" copyrights were violated: The links to Halemo's website, which חיים 7 published in the HeWP page, led to a whole scanned article of Yedioth Aharonot. Copyvio links are forbidden in the WM projects. Therefore Halemo.net website has to be blacklisted in the WM projects.
Until now it canvassed at least four times from Meta to the HeWP RFC: 1, 2, 3, 4.
It seems that it is not the right person for being an interface administrator. Dgw (talk) 01:12, 5 October 2021 (UTC)[reply]
The HeWP administrator דגש forked the discussion from the HeWP RFC into my talk page in the HeWP, after the HeWP bureaucrat ערן had already told me his decision two days ago, with a similar link. It was the second time that דגש forked a discussion today, after he had already been told by another HeWP administrator Ldorfman not to do it: "הדיון פוצל באופן מיותר לחלוטין" (The discussion was forked completely unnecessarily). Dgw (talk) 11:42, 10 October 2021 (UTC)[reply]
Today חיים 7 changed my talk page. It did not have any permission to do it, and leave only what it wants. It also removed the turquoise margins which I did in my talk page:
{| cellpadding="10" cellspacing="8" style="width: 100%; margin-bottom: 20px; background-color: #0ABAB6; border: 2px solid navy;
חיים 7 also removed the template __לא_לחיפוש__ (__NOINDEX__) from my talk page, for showing it in the search engines.
I have a full access to my talk page in the HeWP, and the actions of חיים 7 are not accepted. It is a clear evident that חיים 7 is not suitable to be an interface administrator. It is not a bureaucrat nor administrator, and its actions are made by Non-Wikipedia's reasonning. Its actions are not the goal of WM, and are too near to the actions of Halemo.
I ask a steward to revert my talk page to this version, and to delete this page. Thank you, Dgw (talk) 15:24, 10 October 2021 (UTC)[reply]

Global lock for spambots/vandals

Status:    In progress

Sometimes via IP (-> /64 Range)

Crosswiki Linkspam (apkfun.com) and vandalism, socketpuppets of Apkcare (talk · contribs) (globally blocked by @Teles:).

Most likely (according to the name and account creation time, but no edits so far) also these accounts. Perhaps CU needed to identify further socketpuppets:

Lock all:

.

@Schniggendiller: fyi. --Johannnes89 (talk) 17:06, 14 September 2021 (UTC)[reply]

Global locks and blocks for socks of LTA Hoa112008

Status:    In progress

Long-term abuse lock evasion, see the block log. HurricaneEdgar 00:27, 16 September 2021 (UTC)[reply]

I'm inclined to decline this request due to lack of information.
  • There's no indication of which LTA this account is a sock of.
  • Absent further information, it looks to be a commons-only issue manageable by local blocks.
Please elaborate, thanks. —MarcoAurelio (talk) 13:35, 18 September 2021 (UTC)[reply]
The LTA appears to be mentioned in the request header. ~~~~
User:1234qwer1234qwer4 (talk) 00:03, 19 September 2021 (UTC)[reply]

This sock master also interested like tropical cyclone & modular etc this should Global lock also this sock confirm that this is Hoa112008 need global lock like previous global lock sock hoa112008 HurricaneEdgar 15:22, 19 September 2021 (UTC)[reply]

See also c:COM:ANB#User:Hoa112008 LTA sock and c:Commons:Requests for checkuser/Case/Hoa112008. -- Jeff G. ツ (please ping or talk to me) 12:46, 3 October 2021 (UTC)[reply]

I added 1.52.127.201. See also honeypot c:User:Hoahocphantu/Gallery of molecular electrical potential maps. -- Jeff G. ツ (please ping or talk to me) 12:45, 9 October 2021 (UTC)[reply]

I second this report. This person is still engaging in cross-wiki socking. Please Lock the accounts and Globally Block the IPs. LightandDark2000 🌀 (talk) 21:24, 13 October 2021 (UTC)[reply]

Global lock for Seyit12

Status:    In progress

Terms of use violation. Cross-wiki paid editing without disclosure, indeffed on two projects. --~StyyxTalk? ^-^ 20:07, 18 September 2021 (UTC)[reply]

I believe ToU violations should be dealt by WMF themselves. --Minorax«¦talk¦» 03:44, 13 October 2021 (UTC)[reply]

Global lock for Npcjeffrey and 大撚

Status:    In progress

Abandoned alt SPA accounts of WMF banned 蟲蟲飛. Sanmosa Outdia 10:18, 19 September 2021 (UTC)[reply]

Adjusted at 12:34, 19 September 2021 (UTC). Sanmosa Outdia 12:34, 19 September 2021 (UTC)[reply]
@Sanmosa So CCF = 大撚? And if so should we also lock 大撚 (talk • contribs • block • xwiki-contribs • xwiki-date (alt) • CA • ST • lwcheckuser) ? Thanks. Camouflaged Mirage (talk) 12:25, 19 September 2021 (UTC)[reply]
Adjusted. Sanmosa Outdia 12:34, 19 September 2021 (UTC)[reply]
Noted with thanks, I am just puzzled why Npcjeffrey is in the request where 大撚 isn't. It will be a much easier lock if some local sysop can confirm both are CCF though IMHO. Camouflaged Mirage (talk) 13:31, 20 September 2021 (UTC)[reply]
@Camouflaged Mirage: CCF is likely a sock or meat of 大撚 (who was blocked in 2016 along with dozens of socks) according to their contributions, though it is impossible to confirm. Itcfangye (talk) 17:21, 19 September 2021 (UTC)[reply]
Locally indefinitely blocked, but as CCF is globally banned, there is still a need to have the 2 accounts globally locked. Sanmosa Outdia 05:52, 20 September 2021 (UTC)[reply]
In my opinion, it's hard to say Npcjeffrey is 蟲蟲飛 or 魏鵬展. 魏鵬展(male) 's wechat is Npcjefferey (see blog.sina.com.cn/u/1622654207); while 蟲蟲飛 uploaded her selfie at commons (later Oversighted), which indicated she is female. It's unfair to globally lock Npcjeffrey for this. I'm OK with 大撚, though. Crowley666 (talk) 08:10, 20 September 2021 (UTC)[reply]
@Crowley666 Why then 大撚 is okay to be locked when Npcjeffrey is not? Isn't both the same user? See the local block log. Camouflaged Mirage (talk) 13:33, 20 September 2021 (UTC)[reply]
Local block is based on  It looks like a duck to me. While 大撚's personality and their use of '﹗' makes me believe 大撚 is CCF, Npcjeffrey didn't show enough information. Npcjeffrey registered in 2009, long before 大撚 and CCF. Crowley666 (talk) 13:46, 20 September 2021 (UTC)[reply]
See also [1], NPC used "," while 大撚 used "，". Crowley666 (talk) 13:51, 20 September 2021 (UTC)[reply]
@Crowley666: The sex information public given is somehow useless here, as it may be fake. Npcjeffrey, 魏鵬展 and 蟲蟲飛 should have sockpuppetry relation, or if not, meatpuppetry relation. Both conditions require locking. Sanmosa Outdia 15:29, 20 September 2021 (UTC)[reply]
I wonder if meatpuppetry needs block. In this case, Npcjeffrey only have 2 edits. If Npcjeffrey is blocked, then this block is counted as a part of OA2021, and can't be reverted. Crowley666 (talk) 16:14, 20 September 2021 (UTC)[reply]
@Crowley666: Meatpuppetry is even more serious than sockpuppetry, so more obviously needs a lock. He (or she) may appeal to the Interim Trust & Safety Case Review Committee if that Office action can be appealed. Sanmosa Outdia 00:13, 21 September 2021 (UTC)[reply]
Regarding the local block of Npcjeffrey, my point is that Npcjeffrey showed a similar pattern of recognition of policies and articles, according to his/her comment. The pattern is not about "﹗" and other easily visible things. Yes, judging all of these based on two edits (Npcjeffrey) could be weak and not well justified. A probable compromise is considering Npcjeffrey as meat puppet of 大撚, that is to say, the individual in real world controlling Npcjeffrey is different from that of 大撚. Since Office Actions target individuals behind the accounts, Npcjeffrey will not be one of the targets of the recent OA, until we finally figure this problem out. Tiger- (talk) 04:25, 21 September 2021 (UTC)[reply]
I don't feel both (Npcjeffre,大撚) are 蟲蟲飛,魏鵬展 is male but 蟲蟲飛 is female (When before 蟲蟲飛 has been global ban,she show in zh.wiki user page).--MCC214#ex umbra in solem 13:20, 24 September 2021 (UTC)[reply]
Coincidentally, I have submitted a user check request on zh wiki regarding these two users half a month ago (https://zh.wikipedia.org/w/index.php?title=Wikipedia:%E5%85%83%E7%B6%AD%E5%9F%BA%E7%94%A8%E6%88%B6%E6%9F%A5%E6%A0%B8%E8%AB%8B%E6%B1%82&oldid=67789305). In vain though due to lack of IP evidence after half a decade. The missing link between these two users is a page they were both keen to maintain (https://zh.wikipedia.org/wiki/%E9%AD%8F%E9%B5%AC%E5%B1%95). In my request I have a very rigorous proof of CCF = 大撚 (which in turn = NPCJeffrey, both wiki user AND the person in real life). I have also pointed out in my request that, some users and even admin in zh wiki have chosen to turn a blind eye to the overwhelming evidences. Logic they uphold includes "CCF claimed that she is a she, so CCF can't be NPCJeffrey, a he.". This is a threat, as CCF by then could always return with new accounts and bypass the global lock by just SAYING "I keep a dog, CCF doesn't. so I ain't CCF". Ihatesmoker (talk) 03:54, 7 October 2021 (UTC)[reply]
Why you feel CCF=大撚？You see AFD discussion in 梁世聰?If you see this,you will feel 梁世聰=魏鵬展?Imho,your very rigorous proof is not any evidence to support when all CCF edit very sure is 大撚,also,CCF Not only need to keep 魏鵬展's page.--MCC214#ex umbra in solem 11:15, 7 October 2021 (UTC)[reply]
Unlike yours, mine is a rigorous proof. Above link refers. Grateful if you could kindly stop arguing by saying silly things like "CCF is a girl, so she can't be 大撚/魏鵬展".--Ihatesmoker (talk) 16:38, 8 October 2021 (UTC)[reply]
And by the way, the DEDUCTION I had wasn't not what you described: the missing link is the IP address 124.244.113.46, which updated non-researchable information (then and now) of the NPCJeffrey in real life, AND, eventually, CCF admitted 124.244.113.46 to be his/her/its IP address. The former proved that 124.244.113.46 to be NPCJeffrey as no other individual could have updated that piece of information onto wikipedia. -- Ihatesmoker (talk) 16:46, 8 October 2021 (UTC)[reply]
For non-Chinese speaking meta admin: if you care to read my deduction in English, feel free to drop me a message and I can do the translation for you. I just don't want someone else to keep spinning and putting words into my mouth, like what we have here. -- Ihatesmoker (talk) 16:51, 8 October 2021 (UTC)[reply]
As I said locally,when 大撚 said it is younger generation in DRV,it isn't young,also,if CCF not female and not herself,why she put female photo in her old user page?--MCC214#ex umbra in solem 10:13, 9 October 2021 (UTC)[reply]
Since there is no local admin confirmation, I suggest to Steward close this request as not done. IMO the relationship between CCF and 大撚 should be discussed in local first. If there are clear evidence, submiting global lock request to T&S may be a better choice. SCP-2000 10:34, 9 October 2021 (UTC)[reply]

Global lock for Md Solaiman and Solaiman006

Status:    In progress

Socks of locked Md Solaiman-420. ---- Jeff G. ツ (please ping or talk to me) 13:14, 20 September 2021 (UTC)[reply]

Global lock for Girlsmeindo

Status:    In progress

Long-term abuse. Cross-wiki abuse. LTA Ratna Sarita. --– Symphonium264 (talk) 14:00, 27 September 2021 (UTC)[reply]

Global lock for Why thy tho

Status:    In progress

Long-term abuse. Lock evasion of İsmail Kendir. --DarkMatterMan4500 (talk) (contribs) 16:37, 27 September 2021 (UTC)[reply]

Global lock for RTGRHGTH

Status:    In progress

Long-term abuse. Incredibly likely the same person as FBGFGHGHY. --DarkMatterMan4500 (talk) (contribs) 11:24, 1 October 2021 (UTC)[reply]

@DarkMatterMan4500 and Luk3. I don't think RTGRHGTH meets the criteria for a g lock though. FBGFGHGHY was locked by RadiX upon request by Luk3, but who is FBGFGHGHY an LTA of? If the sock master of FBGFGHGHY wasn't locked, then FBGFGHGHY shouldn't be locked. It's seems like an English Wikipedia issue to me, and not a global issue. SHB2000 (talk | contibs) 12:07, 1 October 2021 (UTC)[reply]
SHB2000 I was wondering the same thing, but then again, I think it might've belonged to another LTA. DarkMatterMan4500 (talk) (contribs) 12:09, 1 October 2021 (UTC)[reply]
But which LTA though? Usually single wiki LTAs don't get locked. SHB2000 (talk | contibs) 12:11, 1 October 2021 (UTC)[reply]
Unless if they were revived sleepers that recently made edits, that's my guess here. DarkMatterMan4500 (talk) (contribs) 12:15, 1 October 2021 (UTC)[reply]
The only case of a VOA I've seen get locked is Special:CentralAuth/Datdude1 but that's an LTA who I suspect had previous socks locked (based on previous incidents on mswiki). SHB2000 (talk | contibs) 13:03, 1 October 2021 (UTC)[reply]
@SHB2000: You probably meant to ping User:LuK3, so I'm doing it here. Cheers! --Luk3 (talk) 13:56, 1 October 2021 (UTC)[reply]
Luk3/LuK3 Who do you think RTGRHGTH might be a sockpuppet of anyway? DarkMatterMan4500 (talk) (contribs) 14:00, 1 October 2021 (UTC)[reply]
SHB2000 and DarkMatterMan4500 the LTA in question is w:en:WP:LTA/NS. I'm not going to go into specifics regarding the revision deleted edits but in my experience I locally block and then request a glock. -- LuK3 (Talk) 14:02, 1 October 2021 (UTC)[reply]
I looked in one of the categories, and I have discovered some recent socks that I will be throwing here shortly. DarkMatterMan4500 (talk) (contribs) 14:05, 1 October 2021 (UTC)[reply]
oh dang. Thanks for doing that. (this isn't the first time I've pinged the wrong person based on a similar username) SHB2000 (talk | contibs) 14:03, 1 October 2021 (UTC)[reply]

Global lock for Stalo4546

Status:    In progress

Long-term abuse. Sockpuppets of Nate Speed, and please check en:Wikipedia:LTA/NS for more information. Not sure if the master needs locking or anything, but these accounts are the most recent socks I could find here. --DarkMatterMan4500 (talk) (contribs) 14:13, 1 October 2021 (UTC)[reply]

@DarkMatterMan4500: Has Nate ever edited any project other than enwiki? None of these accounts have, and even as someone who has dealt with him a fair bit, I don't remember a single instance of crosswiki abuse. Blablubbs (talk) 15:51, 1 October 2021 (UTC)[reply]
Ah, just saw the conversation above – apologies. Unless I'm missing something, I don't think there is any benefit to locking Nate. It's long-term abuse, yes, but there is nothing that can be done on meta that can't be done locally. Blablubbs (talk) 16:03, 1 October 2021 (UTC)[reply]
Yeah, I think just the socks for the time being can be locked. DarkMatterMan4500 (talk) (contribs) 17:33, 1 October 2021 (UTC)[reply]

Global lock for Wild965

Status:    In progress

Long-term abuse. Lock evasion of ConsumersDistributingonline. Please refer to en:Wikipedia:Sockpuppet investigations/ConsumersDistributingonline for more. --DarkMatterMan4500 (talk) (contribs) 10:22, 2 October 2021 (UTC)[reply]

Searching through the archives from this August, I have found 9 more socks that appears to have been found recently. DarkMatterMan4500 (talk) (contribs) 10:36, 2 October 2021 (UTC)[reply]

Global lock for Moo moo I like cows =)

Status:    In progress

Long-term abuse. See locked accounts 1, 2, 3. --~~~~
User:1234qwer1234qwer4 (talk) 13:03, 2 October 2021 (UTC)[reply]

Something went wrong with the LockHide template when you reported Moo moo I like cows =). DarkMatterMan4500 (talk) (contribs) 13:36, 2 October 2021 (UTC)[reply]
It seems like this would be better reported to Simple WP CUs to handle the confirmation/define who this is. -- Amanda (aka DQ) 03:20, 4 October 2021 (UTC)[reply]
Ping @Masti, who recently locked Special:CentralAuth/Quack Quack Donald Duck is here I. ~~~~
User:1234qwer1234qwer4 (talk) 15:02, 7 October 2021 (UTC)[reply]

Global lock for Seemitfe socks

Status:    In progress

Sockpuppets found in enwiki sockpuppet investigation, see w:en:Wikipedia:Sockpuppet investigations/Osourdounmou. CU-confirmed to each other. --Blablubbs (talk) 15:42, 2 October 2021 (UTC)[reply]

Global lock for Bot clean up 1.02

Status:    In progress

Long-term abuse. CU-confirmed to Xavier 500.30.10 via en:Wikipedia:Sockpuppet investigations/Xavier 500.30.10 and this archive. --DarkMatterMan4500 (talk) (contribs) 13:19, 3 October 2021 (UTC)[reply]

Global lock for LTA Mazum24 sock

Status:    In progress

Lock all:

Obvious Global Lock evasion by the LTA Mazum24, given the behavior. This LTA is known for cross-wiki edit-warring, and low-quality/improperly-licensed image uploads on Commons, mostly involving tropical cyclone images. The socks have also been confirmed by a CU on en.wiki. Please run a sleeper check and Globally Block his IPs. LightandDark2000 🌀 (talk) 00:41, 4 October 2021 (UTC)[reply]

Global lock for Brigbuds

Status:    In progress

Long-term abuse. Lock evasion: Vishaal Elias Manesh via this category. --DarkMatterMan4500 (talk) (contribs) 10:49, 4 October 2021 (UTC)[reply]

Pinging Ruslik to lock the other 2 sockpuppets from this report, which includes Brigbuds and Bergwalt. DarkMatterMan4500 (talk) (contribs) 23:40, 6 October 2021 (UTC)[reply]

Global lock for Cheapalbums

Status:    In progress

Long-term abuse. CU-confirmed to ZestyLemonz via en:Wikipedia:Sockpuppet investigations/ZestyLemonz. --DarkMatterMan4500 (talk) (contribs) 12:16, 4 October 2021 (UTC)[reply]

Global lock for Md.labibsikder

Status:    In progress

Lock all:

Cross-wiki spamming, advertising, and sockpuppeting. -- Afeef (talk) 04:32, 5 October 2021 (UTC)[reply]

Global lock for socks of locked Zeemodeofficial1

Status:    In progress

Crosswiki spam. Socks of locked Zeemodeofficial1. Please see c:Commons:Requests for checkuser/Case/Zeemodeofficial1. ---- Jeff G. ツ (please ping or talk to me) 15:47, 5 October 2021 (UTC)[reply]

Global lock for Allflipzone

Status:    In progress

Spam / spambot. --Daniuu (talk) 20:50, 5 October 2021 (UTC)[reply]

Half of these I seem to be missing the point on, and one I locked for a non-spam reason. Would like some clarity on this request please. Especially the last account. Spam has to be the users clear and only intention for it to be lockable. -- Amanda (aka DQ) 01:58, 6 October 2021 (UTC)[reply]
All of these accounts were found in various abuse filters, specifically written to keep certain spammers out. Apparently, I accidentally included a false positive with the last one (removed that one for now). The frustrated edits include edits like this for the first one. The second one appeared to have been spamming his own Facebook page (although I doubt this should be categorized fully as spam and will remove that one too). Solaiman was also caught by certain abuse filters (and has a local block on Commons), which is partly the reason for the request. When reconsidering, a local block could cover this. Mizzymilez23 was requested for this edit. I hope I was able to provide some additional clarifications and will further clarify this request when needed, AmandaNP. --Daniuu (talk) 21:39, 9 October 2021 (UTC)[reply]

Global lock for Ponytailgirl

Status:    In progress

Long-term abuse. Lock evasion: MariaJaydHicky. --DarkMatterMan4500 (talk) (contribs) 21:03, 5 October 2021 (UTC)[reply]

Added 2 more here. If possible, a sleeper check could be useful, as I'll leave the other 2 from the Wikipedia:Sockpuppet investigations/MariaJaydHicky page until a further check can be found. DarkMatterMan4500 (talk) (contribs) 21:08, 5 October 2021 (UTC)[reply]
DarkMatterMan4500, that is not lock evasion, the first two accounts were created before the lock on the sockpuppeteer was put in place on 30 August, with one last being used 6 years ago. --Ferien (talk) 21:11, 5 October 2021 (UTC)[reply]
@Ferien: Well, either way I'd say it still counts, given that other recent accounts before MariaJaydHicky's original account was locked, there was a lot of his/her socks that were getting locked. And, if I can recall, it was on cross-wiki abuse. DarkMatterMan4500 (talk) (contribs) 21:14, 5 October 2021 (UTC)[reply]
I realized that the second one I added was too stale, and I apologize for adding it here. I meant to add a recent sock that hasn't been stale yet, but accidentally added the 6 year old account. DarkMatterMan4500 (talk) (contribs) 22:31, 5 October 2021 (UTC)[reply]

Global lock for Peter M. C. Onions

Status:    In progress

Long-term abuse. Lock evasion: ConsumersDistributingonline. Their only edit was on their user page with a link, which is a dead giveaway right there. --DarkMatterMan4500 (talk) (contribs) 23:43, 6 October 2021 (UTC)[reply]

Adding 2 more to the report. DarkMatterMan4500 (talk) (contribs) 23:54, 6 October 2021 (UTC)[reply]

Global locks

Status:    In progress
Extended content

Spam/Promotion-only accounts. See also: c:COM:AN (perl). Unnamed UserName me 01:24, 8 October 2021 (UTC)[reply]

Global lock for cross-wiki spammers

Status:    In progress

See Talk:Wikiproject:Antispam#Trane007. MER-C 17:09, 9 October 2021 (UTC)[reply]

Global lock

Status:    In progress

Abusive username. --Ts12rAc (talk) 03:22, 10 October 2021 (UTC)[reply]

Global lock for Lunatic Longhair

Status:    In progress

Abusive username. --SHB2000 (talk | contibs) 09:38, 11 October 2021 (UTC)[reply]

@SHB2000 There is also Dictator Longhair (talk • contribs • block • xwiki-contribs • xwiki-date (alt) • CA • ST • lwcheckuser); however, it seem this LTA is limited to one wiki. ~~~~
User:1234qwer1234qwer4 (talk) 12:38, 11 October 2021 (UTC)[reply]
Thanks for the notice. While the LTA is limited to one wiki, the username is abusive. SHB2000 (talk | contibs) 12:47, 11 October 2021 (UTC)[reply]

Global lock for Narmothis

Status:    In progress

Sockpuppet of Luis camilo álvarez vega, an LTA that vandalizes eswiki, enwiki and Commons since 2011. This sock is now attacking Commons. --Bankster (talk) 22:31, 11 October 2021 (UTC)[reply]

Global lock for BD Vinsa malica ashviya

Status:    Done

Long-term abuse. Cross-wiki abuse. LTA Hitzeed, confirmed by CU in idwiki. --– Symphonium264 (talk) 06:57, 12 October 2021 (UTC)[reply]

Done ----Alaa :)..! 07:16, 16 October 2021 (UTC)[reply]

Global lock for 548asiaslavia and Hrvatskiukrajinski

Status:    In progress

Sockpuppets of Adamdaniel864, who is globally locked for cross-wiki disruption. 548asiaslavia is currently cross-wiki spamming requests to be unblocked at uk.wiki: en.wiki, simple, uk.wiki; here the user confirms that they are the same user as Adamdaniel864. Hrvatskiukrajinski is blocked as an Adamdaniel864 sock on four projects: bg.wiki, en.wiki, uk.wiki, and wuu.wiki. --Bonadea (talk) 15:29, 13 October 2021 (UTC)[reply]

@Bonadea The master is earlier. This is lock evasion by User:Adam Asrul. --Camouflaged Mirage (talk) 12:36, 14 October 2021 (UTC)[reply]
@Camouflaged Mirage: Wow – thanks for the heads-up on this. This user has been around for rather longer than I thought. --Bonadea (talk) 07:39, 15 October 2021 (UTC)[reply]

Global lock for CharmenderDeol sock(s)

Status:    In progress

Sockpuppet(s) found in enwiki sockpuppet investigation, see w:en:Wikipedia:Sockpuppet investigations/CharmenderDeol. GeneralNotability (talk) 01:52, 15 October 2021 (UTC)[reply]

I'm not too sure about the acceptability of locking these accounts. I was involved in the original CU on this, but I don't think there is a global equivalent to the w:WP:MEAT Arbitration clause. That and UPE locks are usually not made. I won't decline this, but I don't think these accounts should be locked. -- Amanda (aka DQ) 14:37, 15 October 2021 (UTC)[reply]

Global lock for すらいむさん socks

Status:    Done
Long-term abuse. See also w:ja:LTA:SLIME (User:すらいむさん socks) or copycat. --しみはる君 (talk) 16:03, 15 October 2021 (UTC)[reply]
Done ----Alaa :)..! 07:14, 16 October 2021 (UTC)[reply]

Global lock for 想舞花

Status:    Done

Globally banned user: 冏 (Case #30145). Please block their using IP address/range if possible. --SCP-2000 16:19, 15 October 2021 (UTC)[reply]

Not done.-Jon Kolbert (talk) 05:39, 16 October 2021 (UTC)[reply]

@Jon Kolbert: Well, zhwiki has not blocked yet.... Anyway, FYI the edit pattern is same as Koniangpo, Lintenght etc. Thank you. SCP-2000 11:25, 16 October 2021 (UTC)[reply]
Done by Sotiale.--MCC214#ex umbra in solem 12:05, 16 October 2021 (UTC)[reply]

Global lock for socks

Status:    In progress
User list

Long-term abuse. See w:vi:Wikipedia:Yêu cầu kiểm định tài khoản/Trankimtuyensg. --Unnamed UserName me 21:01, 15 October 2021 (UTC)[reply]

Global lock for Singapore70089456

Status:    Done

Spam / spambot. --20041027 𝓽𝓪𝓽𝓼𝓾（talk） 06:27, 16 October 2021 (UTC)[reply]

Robot clerk note: Done by Sotiale. MajavahBot (talk) 07:05, 16 October 2021 (UTC)[reply]

Global lock for Adnoos45

Status:    In progress

Cross-wiki abuse. Crosswiki hoax with ip socks. --𝐖𝐢𝐤𝐢𝐁𝐚𝐲𝐞𝐫 👤💬 07:06, 16 October 2021 (UTC)[reply]

Global lock for Transportation & Warehousing

Status:    Done

Spam / spambot. --SHB2000 (talk | contibs) 07:30, 16 October 2021 (UTC)[reply]

Robot clerk note: Done by Sakretsu. MajavahBot (talk) 11:45, 16 October 2021 (UTC)[reply]

Global lock for latest socks of Igoryu1993

Status:    In progress

LTA, complete list here. --Achim (talk) 07:38, 16 October 2021 (UTC)[reply]

Global lock for Gërbert Marium

Status:    Done

Long-term abuse: A1cb3 (see 1, 2) --Mtarch11 (talk) 07:49, 16 October 2021 (UTC)[reply]

Robot clerk note: Done by Sakretsu. MajavahBot (talk) 11:25, 16 October 2021 (UTC)[reply]

Global lock for Nonebotnone

Status:    In progress

CU-confirmed sock of Md.labibsikder (who, along with three earlier socks, was locked in an earlier request here).--Jasper Deng (talk) 08:31, 16 October 2021 (UTC)[reply]

Global lock for cross-wiki abuse and LTA sock

Status:    Done

Lock all:

Same user of Special:CentralAuth/Kapol6360,also,please check sleepers and lock IP/IP range when account not stale.--MCC214#ex umbra in solem 10:09, 16 October 2021 (UTC)[reply]

Robot clerk note: Done by Sakretsu. MajavahBot (talk) 11:25, 16 October 2021 (UTC)[reply]

Global lock for LTA

Status:    In progress

Long-term abuse. Abusive username. -- JavaHurricane 11:34, 16 October 2021 (UTC)[reply]

Global lock for LTA

Status:    In progress

Long-term abuse. Abusive username. -- JavaHurricane 11:36, 16 October 2021 (UTC)[reply]

Global lock for NzemarshalCrypto

Status:    In progress

Cross-wiki abuse. ---- Jeff G. ツ (please ping or talk to me) 12:45, 16 October 2021 (UTC)[reply]

Global lock for 一只中国球

Status:    In progress

Spam / spambot. --SCP-2000 12:54, 16 October 2021 (UTC)[reply]

Global lock for French LTA creating insulting usernames

Status:    In progress

Abusive usernames insulting sysops. --Thibaut (talk) 12:58, 16 October 2021 (UTC)[reply]

Global lock for C64 is the best computer

Status:    In progress

Long-term abuse. Same Columbus edits as Special:CentralAuth/Your favorite emperor; both confirmed through a different editor. --~~~~
User:1234qwer1234qwer4 (talk) 14:03, 16 October 2021 (UTC)[reply]

Global lock for JaniBrubaker08

Status:    In progress

Spam / spambot. ntsamr. --~~~~
User:1234qwer1234qwer4 (talk) 14:11, 16 October 2021 (UTC)[reply]

See also

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

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