Jump to content

User:Seudo/Test3

Add topic
From Meta, a Wikimedia project coordination wiki
Latest comment: 1 year ago by Drummingman in topic Requests for global (un)block
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 or accounts; and (un)locks apply to global accounts.

Cross-wiki requests
Meta-Wiki requests

Requests for global (un)block

[edit]

Please be sure to follow the instructions below:
Your request might be rejected if you don't follow the instructions.
Please also review Global blocking .
Global blocks don't affect Meta-Wiki, so if your IP address or account is blocked, you can still appeal here. IP addresses or accounts that cause disruption on Meta should be reported at Meta:Requests for help from a sysop or bureaucrat instead of here so that they can be blocked locally.
Please describe the kind of cross wiki abusive activity you see from the IP or account. Saying an IP or account is a long term abuser is not helpful, but saying "IP vandalizes at ban.wikipedia, no.wikipedia and vi.wikipedia" is. This is especially important for range blocks. If you do not provide enough details, your request might be declined.
Instructions for making a request

Before requesting, make sure that:

  1. You know the IP address(es) or accounts you wish to have globally blocked or unblocked.
  2. For blocks, the global blocking criteria are met.
  3. For unblocks, your request addresses the original reason for blocking the IP or account, if any.

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

Copy the template below to the bottom of this section and explain why the address(es) or account(s) should be blocked/unblocked.
=== Global block/unblock for [[Special:Contributions/Some IP address or account|Some IP address or account]] ===
{{Status}} <!-- Do not remove this template -->
* {{Luxotool|IP address}}
Description, evidence, diffs, etc. --~~~~
When requesting that your IP be unblocked, note that stewards need to know your IP address to even consider a request.
To find your IP, please visit https://www.whatismyip.com/
You are not required to disclose your IP in public - you may make requests privately to any steward on IRC or by email at: stewards@wikimedia.org

Global unblock for 185.89.36.0/22

[edit]
Status:    On hold

This was blocked in 2021 as an OP, but in the meantime the range is used by the German internet provider InternetNord ([1]). One of their customers complained to the German VRTS. I have already made an exempt for the range block on dewiki, but I would also request a total unlock globally. Thanks, XenonX3 (talk) 12:18, 23 February 2022 (UTC)Reply

@Martin Urbanec: --Alaa :)..! 14:03, 25 May 2022 (UTC)Reply

Global unblock for 2001:470::/32

[edit]
Status:    In progress

The block reason incorrectly identifies this range as an open proxy. It's neither proxy nor open. I learned that some admins believe the Hurricane Electric's service makes it “like” an open proxy, but note that none of the reasons usually given as the rationale for the no open proxies policy apply to it. There is no anonymity nor particularly high potential of abuse. There is no reason why blocking individual /64 or /48 networks wouldn't be effective in case of abuse.--MwGamera (talk) 22:35, 29 March 2022 (UTC)Reply

Oppose Oppose You say that there is no particularly high potential of abuse, but that doesn't match our logs. It's full of spambots. AntiCompositeNumber (talk) 03:16, 31 March 2022 (UTC)Reply
The Internet is full of spambots and it would be surprising for a range this huge to carry only benign traffic. I don't have any visibility into Wikimedia logs so can't comment on the actual numbers. Is there any reason why they couldn't be blocked individually like in all the other ranges? In any case, the block reason given doesn't match reality (it's not even weasel worded like the one on EN wiki) and I considered it prudent to try to fix the situation before requesting an exemption from a block that from my POV goes against the guidelines.--MwGamera (talk) 18:02, 4 April 2022 (UTC)Reply
Support Support This block hurts me and other people. HE 6to4 tunnel is necessary for my work, ISPs in my area do not give native IPv6. --Kawtaj (talk) 07:07, 7 May 2022 (UTC)Reply
Support Support This block hurts me, and I expect other people. My ISP doesn’t give good IPv6 access, and HE tunnelserver.org tunnels are my only good option. Lionel Elie Mamane (talk) 01:43, 23 May 2022 (UTC)Reply
This is an open proxy/web host/colocation provided, used by one or more VPN services, if I'm not mistaken. If users with cross-wiki constructive contributions are affected, you can request a global IP block exemption. I can definitely attest to the Hurricane Electric LLC IP ranges being used for abuse and spambots on Miraheze as well. Dmehus (talk) 02:08, 23 May 2022 (UTC)Reply
It is not an open proxy nor a web host. Every user has a separate, identifiable, and individually bannable prefix routed to them (although possibly more than one). There might be, and there likely are, some open proxies, web hosts, VPNs, etc, as well as spambots and other sources of abusive traffic in it, but that doesn't explain why should the whole range be blocked instead of just the networks with those. Or why should it be claimed to be an open proxy if the actual reason for blocking is some actual (ongoing?) cross-network abuse.--MwGamera (talk) 21:02, 27 May 2022 (UTC)Reply
I can only second this request. This range hasn't been blocked until some point in 2020. At least unblock people from editing when logged in. But in general don't impose a general block because most users will be legitimate, like every normal network. Just block /64 or /48 after abuse has been noticed. --Treysis (talk) 09:18, 1 June 2022 (UTC)Reply

Global unblock for 147.161.237.87

[edit]
Status:    In progress

When trying to edit a page, I received the block error "The IP address or range 147.161.237.87 has been globally blocked (disabled) by Jon Kolbert for the following reason(s): Open proxy/Webhost. This block will expire on 15:19, 31 October 2024."

This assessment is incorrect; the IP listed is part of a larger range operated by ZScaler (AS62044, 147.161.236.0/23 as well as many others). The IP range is used for Internet egress for corporate customers, who use ZScaler products for MFA-secured access to internal networks. My employer mandates use of ZScaler and it cannot be disabled on the machine. ZScaler do not operate any open public proxies, nor do they offer "privacy" VPN products, it's purely business use for SMEs & corporates. --Chris W. (talk | WP profile) 13:12, 16 May 2022 (UTC)Reply

Support Support The block reason incorrectly identifies this range as an open proxy. It's neither proxy nor open. I learned in an earlier request that some admins believe the Hurricane Electric's service makes it “like” an open proxy, but note that none of the reasons usually given as the rationale for the no open proxies policy apply to it. There is no anonymity nor particularly high potential of abuse. This should allow to run a sleeper check, if there is indeed sleepers in this range. XJ999 (talk) 21:28, 4 August 2022 (UTC)Reply

Global block for 103.153.2.0/24

[edit]
Status:    In progress

Open proxy. --reNVoy (user talk) 14:10, 3 June 2022 (UTC)Reply

@Renvoy What makes you say this entire range is an open proxy? AntiCompositeNumber (talk) 01:54, 5 June 2022 (UTC)Reply
QBA-bot blocked handful of IPs from that range. Generally there is weird activity that involves LTA Marsuki s.kom + several IPs from that range were indicated as Tor Connection. reNVoy (user talk) 11:28, 5 June 2022 (UTC)Reply

Global block for LTA

[edit]
Status:    In progress

Global Lock evasion and cross-wiki abuse by the LTA MRY. These IPs are also Open Proxies or VPNs. Please Globally Block for at least a year, and run a sleeper check. — The preceding unsigned comment was added by LightandDark2000 (talk) 17:10, 14 July 2022 (UTC)Reply

At least the second one looks like Wikinger to me, though he might certainly be imitated. Can you provide evidence for the requested block duration? ~~~~
User:1234qwer1234qwer4 (talk)
17:18, 1 August 2022 (UTC)Reply

Global block for long-term abuse

[edit]
Status:    In progress

Extreme case of long-term abuse. Almost immediately after any of these long-term blocks expire, this individual targets any and all editors who may have reverted their vandalism in the past and edit-wars with them, with summaries that dox them, with examples including Ponyo, Ymblanter, Mtarch11 - and especially Gadfium. With how aggressive they have behaved toward Gadfium, I honestly would recommend that he contact his local New Zealand authorities. They also target it.Wikipedia & mi.Wikipedia. Ohnoitsjamie has done an exemplary job of addressing this individual on the English Wikipedia, but their conduct on multiple projects needs to be addressed. Just today, they took the opportunity to abuse some more. I request a global block of one-plus year. Botto (talk) 00:01, 18 July 2022 (UTC)Reply

For clarification, this request is not stale. The vandal primarily targets the English Wikipedia and sequentially waits for one of the three blocks to be lifted, before almost immediately going to that part of Auckland and attacking their usual targets -- the next one is 122.56.192.0/20, which expires next Friday. In the meantime, they ocassionally target certain editors on other wikis, as Meta-Wiki contributors Mtarch11 and Daniuu may attest. Botto (talk) 17:38, 1 August 2022 (UTC)Reply
Unfortunately, I can confirm the statement made by colleague Botto. Daniuu (talk) 18:19, 1 August 2022 (UTC)Reply
Yeah I doubt this person will ever want to contribute to Wikipedia or any sister projects in a productive way.StarTrekker (talk) 21:30, 2 August 2022 (UTC)Reply
Primefac extended 122.56.192.0/20 immediately prior to its expiration. The next range to expire will be 115.189.0.0/16, in October. I would otherwise believe this would cut it, but considering this individual's track record and their persistence on other wikis, I would still push for a fresh 1-year-block for all three ranges, so they lose interest. Botto (talk) 18:58, 15 August 2022 (UTC)Reply

Global block for 176.59.32.0/19

[edit]
Status:    In progress

Cross-wiki abuse on 10+ projects. --reNVoy (user talk) 11:17, 30 July 2022 (UTC)Reply

Global block for 36.73.32.0/22

[edit]
Status:    In progress

Cross-wiki abuse. Long-term abuser Casmo. – Symphonium264 (talk) 11:17, 31 July 2022 (UTC)Reply

Global block/unblock for spammers

[edit]
Status:    In progress

Suspected open proxy's, used for spamming purposes on eswikisource or mxwikimedia. --Daniuu (talk) 15:43, 4 August 2022 (UTC)Reply

Global block for 2600:1008:B004:A88D::/64

[edit]
Status:    In progress

Cross-wiki abuse. ---- Jeff G. ツ (please ping or talk to me) 05:02, 8 September 2022 (UTC)Reply

Global block for 49.181.193.224

[edit]
Status:    In progress

Long-term abuse. Cross-wiki abuse. Te Reo Ahitereiria / Basa Pulu Kokos. --SHB2000 (talk | contribs) 08:55, 10 September 2022 (UTC)Reply

Seconded. They've been blocked locally for now but often pop up on other wikis. Graham87 (talk) 09:14, 10 September 2022 (UTC)Reply

Global block for 70.45.219.42

[edit]
Status:    In progress

Cross-wiki abuse. Death threats: 1, 2, 3, 4, 5, and 6. Appears to have been static for at least a year. Part of 70.45.216.0/21 xwiki-contribsSTIP infoWHOISrobtexgblockglistabuselogbullseye. ---- Jeff G. ツ (please ping or talk to me) 18:12, 10 September 2022 (UTC)Reply

Status:    In progress

Cross-wiki abuse. ---- Jeff G. ツ (please ping or talk to me) 00:00, 13 September 2022 (UTC)Reply

Global unblock for 197.210.71.0/24

[edit]
Status:    In progress

Hello, when trying to edit a page, I received the block error "The IP address or range 197.210.71.0/24 has been globally blocked (disabled) by Operator873 for the following reason(s): Open proxy/Webhost. This block will expire on 23 August 2025."

This assessment seems incorrect as this is a range of IP addresses allocated to MTN, a Nigerian internet access provider, including apparently the one that as been allocated to myself. Would it be possible to unlock the IP range? Thanks.--DonCamillo (talk) 08:53, 13 September 2022 (UTC)Reply

Global block for 2001:4451::/32

[edit]
Status:    In progress

Long-term abuse. Cross-wiki abuse. Escalation from global block of 2001:4451:116B:5000::/64. Blocked on 5 wikis (on enwikibooks as a part of 2001:4400::/24). ---- Jeff G. ツ (please ping or talk to me) 13:16, 13 September 2022 (UTC)Reply

Global block for 87.88.168.143

[edit]
Status:    Done

Long-term abuse. Cross-wiki abuse. --Mykola 19:12, 14 September 2022 (UTC)Reply

Robot clerk note: Done by AntiCompositeNumber. MajavahBot (talk) 19:25, 14 September 2022 (UTC)Reply

Global block for 2402:800:620f:92f4::/64

[edit]
Status:    In progress

Cross-wiki abuse. ---- Jeff G. ツ (please ping or talk to me) 23:28, 14 September 2022 (UTC)Reply

Global block for 116.103.149.140

[edit]
Status:    In progress

Spambot. Also a filter check and update would be handy since these texts slip through crosswiki see here and here. --- Hoyanova (talk) 06:23, 15 September 2022 (UTC)Reply

Global block for 175.210.204.58

[edit]
Status:    In progress

Long-term abuse. Public VPN(VPNgate VPN). Lock Evasion:User:フアン_ファン. --Daraku K. (talk) 12:59, 15 September 2022 (UTC)Reply

Global block for 109.25.165.146

[edit]
Status:    In progress

Cross-wiki abuse. Name and date vandalism. --Drummingman (talk) 14:45, 15 September 2022 (UTC)Reply

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

[edit]

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 Huonggiangidol + Huonggiangidol's sockpuppets

[edit]
Status:    In progress
User list

Cross-wiki abuse + viwiki raider KhanhCN Defender1st Minh (talk) 09:11, 17 August 2022 (UTC)Reply

Global lock for Rosenenaidol + Rosenenaidol's sockpuppets

[edit]
Status:    On hold
User list

Cross-wiki abuse (+1 and +2 RfCU) - KhanhCN Defender1st Minh (talk) 14:15, 17 August 2022 (UTC)Reply

Global lock for Mike Matthews17

[edit]
Status:    In progress

Long-term abuse. For the sake of completeness. I've noticed this account through the talk page watchlist and the edits seen are the same as previous socks of Mike Matthews, see en:Wikipedia:Sockpuppet investigations/Mike Matthews17/Archive with this account as an example, and "Geraint Harris2319" followed the same naming pattern as this one. --Iggy the Swan (talk) 16:14, 17 August 2022 (UTC)Reply

Global lock for Baranov107

[edit]
Status:    In progress

Cross-wiki spam. Reverted and warned on multiple wikis. Huñvreüs (talk) 08:11, 20 August 2022 (UTC)Reply

Oppose Oppose surely this is not a regular spambot, user has good contributions over several projects--reNVoy (user talk) 21:10, 11 September 2022 (UTC)Reply
They have no good contributions - they are copyvios and spam link additions, which is why all the URLs are blacklisted. They absolutely need a global lock not just for spamming but breaking the TOU. Praxidicae (talk) 12:15, 12 September 2022 (UTC)Reply
@Renvoy There have been more than 39 records of them adding the same link in more than 10 wikis. I don't think it's simple addition done in good faith. BRP ever 13:22, 12 September 2022 (UTC)Reply

Global lock for Advancetestinglabs

[edit]
Status:    Done
User list

Spam / spambot. all accounts related to each other [2][3] and to globally locked Special:CentralAuth/Tattoomagz3. --Johannnes89 (talk) 18:06, 23 August 2022 (UTC)Reply

Done Ruslik (talk) 20:48, 14 September 2022 (UTC)Reply

Global lock for Wichian Seangngam

[edit]
Status:    In progress

Long-term abuse (maybe) Nakaret (talk) 06:11, 26 August 2022 (UTC)Reply

Global lock for 馮克勁

[edit]
Status:    In progress
User list

Long-term abuse. Cross-wiki abuse. Editing behavior is related to IP like 218.255.156.222, 218.189.215.212. Probably the same sock puppet account series as zh-yue:Wikipedia:持續出沒嘅破壞者/香港藝人明細模破壞者 and en:Wikipedia:LTA/HKGW. --Rastinition (talk) 13:36, 26 August 2022 (UTC)Reply

Global lock for TheDarkCross

[edit]
Status:    Done

Cross-wiki abuse. --𝐖𝐢𝐤𝐢𝐁𝐚𝐲𝐞𝐫 👤💬 07:51, 27 August 2022 (UTC)Reply

Done Ruslik (talk) 20:50, 14 September 2022 (UTC)Reply

Global lock for Mahadeesh2010

[edit]
Status:    Done

Long-term abuse. Lock evasion: Snthilakammarist. --DarkMatterMan4500 (talk) (contribs) 18:32, 27 August 2022 (UTC)Reply

Added 3 additional accounts here. --DarkMatterMan4500 (talk) (contribs) 18:38, 27 August 2022 (UTC)Reply
Done Ruslik (talk) 20:52, 14 September 2022 (UTC)Reply

Global lock for Eiskrahablo socks

[edit]
Status:    Done

Long-term abuse. Sockpuppet of the globally-locked Eiskrahablo. Also see c:Commons:Administrators' noticeboard/User problems#User:Factual Fact Factor. --SHB2000 (talk | contribs) 11:30, 30 August 2022 (UTC)Reply

+3 CU-blocked socks. --SHB2000 (talk | contribs) 10:07, 31 August 2022 (UTC)Reply
Done Ruslik (talk) 20:55, 14 September 2022 (UTC)Reply

Global lock for Huntoftimer

[edit]
Status:    Done

Long-term abuse. Leftover sock of Europefan that appears to have been overlooked. --DarkMatterMan4500 (talk) (contribs) 12:27, 30 August 2022 (UTC)Reply

Done Ruslik (talk) 20:57, 14 September 2022 (UTC)Reply

Global lock for Abdomitwally1008

[edit]
Status:    In progress

Long-term abuse. Lock evasion by Abdo Mitwally. --Njd-de (talk) 16:35, 30 August 2022 (UTC)Reply

Global lock for Janitor102 sock(s)

[edit]
Status:    In progress

Sockpuppet(s) found in enwiki sockpuppet investigation, see w:en:Wikipedia:Sockpuppet investigations/Janitor102. Blablubbs (talk) 23:40, 30 August 2022 (UTC)Reply

Global lock for Omaraldrabee

[edit]
Status:    In progress

Cross-wiki abuse. Sockpuppetry. ---- Jeff G. ツ (please ping or talk to me) 11:27, 31 August 2022 (UTC)Reply

@Jeff G. Who's the sockmaster? AntiCompositeNumber (talk) 02:32, 8 September 2022 (UTC)Reply
@AntiCompositeNumber and @Alaa: It appears to be Iyadaldarabea911. See also إياد عماد الدرابيع. Pinging @وسام as blocking Admin on arwiki. -- Jeff G. ツ (please ping or talk to me) 04:05, 8 September 2022 (UTC)Reply

Global lock for Joe Morgan3108

[edit]
Status:    In progress

Long-term abuse. Sockpuppet of Mike Matthews17. --Johannnes89 (talk) 12:32, 31 August 2022 (UTC)Reply

Strong support per request & bullet point 7 on the Global locks page despite editing on just 1 project. Iggy the Swan (talk) 16:00, 31 August 2022 (UTC)Reply
There is no global ban for LTA Mike Matthews 17. But there is a large number of Mike Matthews17 sockpuppets blocked for crosswiki abuse so there is no reason to wait for this account to vandalise other wikis as well. Johannnes89 (talk) 21:40, 31 August 2022 (UTC)Reply
Oops, didn't read bullet point 7 properly, which I thought it was describing lock evasion. Well spotted, Iggy the Swan (talk) 18:25, 1 September 2022 (UTC)Reply
Status:    In progress

Long-term abuse. --EstrellaSuecia (talk) 21:42, 2 September 2022 (UTC)Reply

Global lock for Stubes99 sock(s)

[edit]
Status:    In progress

Sockpuppet(s) found in enwiki sockpuppet investigation, see w:en:Wikipedia:Sockpuppet investigations/Stubes99. RoySmith (talk) 23:04, 2 September 2022 (UTC)Reply

Global lock for CAROLlNE

[edit]
Status:    In progress

Long-term abuse. Lock evasion: ZestyLemonz. --DarkMatterMan4500 (talk) (contribs) 12:36, 3 September 2022 (UTC)Reply

Global lock for Premanidhi premanidhi

[edit]
Status:    In progress

Sock of previously locked user, see Special:CentralAuth/PremanidhiMajhi and Special:CentralAuth/Premanidhi offici --Yeeno (talk) 18:10, 4 September 2022 (UTC)Reply

Global lock for Cheng123xx

[edit]
Status:    In progress

Lock evasion: Abcdefghixx / NgaiHingMansion per Commons AN request. Have been blocked on commonswiki. --SCP-2000 03:13, 5 September 2022 (UTC)Reply

Global lock for sockpuppets of Triasemmy6,472,301

[edit]
Status:    In progress

All of these are sockpuppets of the cross-wiki vandal Triasemmy6,472,301 (see commons:Category:Sockpuppets of Triasemmy6,472,301). --Horcrux (talk) 12:04, 5 September 2022 (UTC)Reply

Global lock for Shovon00

[edit]
Status:    In progress

Cross-wiki abuse. Sock puppeteer —MdsShakil (talk) 09:57, 6 September 2022 (UTC)Reply

@MdsShakil Are these the only accounts, or are there others? Can you be more specific about the nature of the abuse? AntiCompositeNumber (talk) 03:21, 7 September 2022 (UTC)Reply
@AntiCompositeNumber Edits were made from these two accounts on bnwiki, so the CU checked and confirmed them. They using their two accounts for self promotions/promotional purposes in various wikis. —MdsShakil (talk) 13:08, 7 September 2022 (UTC)Reply

Global lock for Fabiennebaumgartner

[edit]
Status:    In progress

Compromised account. m:Special:GlobalRenameQueue/request/96863/ --Cabayi (talk) 13:55, 7 September 2022 (UTC)Reply

Santali Wikipedia spam

[edit]
Status:    In progress

https://sat.wikipedia.org/wiki/%E1%B1%AE%E1%B1%A1%E1%B1%9F%E1%B1%9E_%E1%B1%9A%E1%B1%A5%E1%B1%A6 I can nominate this article because the spammer keeps taking the deletion request down --Trade (talk) 13:58, 9 September 2022 (UTC)Reply

Decided to fix this. --DarkMatterMan4500 (talk) (contribs) 14:07, 9 September 2022 (UTC)Reply

Global lock for cross-wiki abuse and LTA sock

[edit]
Status:    Done

Same user of Special:CentralAuth/Cyberpunk2077JohnnySilverhand,also,please check sleepers and block IP/IP range(s) when account not stale.--MCC214#ex umbra in solem 14:22, 9 September 2022 (UTC)Reply

Robot clerk note: Done by AmandaNP. MajavahBot (talk) 06:25, 15 September 2022 (UTC)Reply

Global lock for MetaContributor

[edit]
Status:    In progress

Long-term abuse. Parvej Husen Talukder. --—MdsShakil (talk) 16:43, 9 September 2022 (UTC)Reply

Global lock for Rhinofax22

[edit]
Status:    In progress

Long-term abuse. Lock evasion: Agustin Sepulveda Venegas 2004 Fan. --DarkMatterMan4500 (talk) (contribs) 13:40, 10 September 2022 (UTC)Reply

Global lock for Dineshs01102000

[edit]
Status:    In progress

Cross-wiki abuse. Sockpuppetry. See c:Commons:Requests for checkuser/Case/Dineshs01102000. ---- Jeff G. ツ (please ping or talk to me) 19:11, 10 September 2022 (UTC)Reply

Global lock for Parsa 22au

[edit]
Status:    In progress

Cross-wiki harassment ~ ToBeFree (talk) 20:16, 10 September 2022 (UTC)Reply

Global lock for Deeeck

[edit]
Status:    In progress

Cross-wiki abuse. --SHB2000 (talk | contribs) 03:25, 11 September 2022 (UTC)Reply

Global lock for 12 ( Music )

[edit]
Status:    In progress

LTA: en:Wikipedia:Sockpuppet investigations/Alex9777777. Courtesy ping: @Achim55:.--jdx Re: 06:42, 12 September 2022 (UTC)Reply

Same xwiki Aleksej Pechkurov/Lovifm spam from Lock all:; see also https://be.wikipedia.org/w/index.php?title=Адмысловае:AbuseLog&wpSearchFilter=8. ~~~~
User:1234qwer1234qwer4 (talk)
11:58, 12 September 2022 (UTC)Reply

Global lock for Vecnai

[edit]
Status:    In progress

LTA - reincarnation of locked cross wiki falsifcation vandal Arthur Brum. See also here --- Hoyanova (talk) 07:40, 12 September 2022 (UTC)Reply

Global lock for Symon Sadik sock(s)

[edit]
Status:    In progress

Sockpuppet(s) found in enwiki sockpuppet investigation, see w:en:Wikipedia:Sockpuppet investigations/Symon Sadik. Bbb23 (talk) 12:56, 12 September 2022 (UTC)Reply

Global lock for Donny Tromboni

[edit]
Status:    In progress

Long-term abuse. Lock evasion: Honest Yusuf Cricket. --DarkMatterMan4500 (talk) (contribs) 14:03, 12 September 2022 (UTC)Reply

Global lock for The Train Master sock(s)

[edit]
Status:    In progress

Sockpuppet(s) found in enwiki sockpuppet investigation, see w:en:Wikipedia:Sockpuppet investigations/The Train Master. Bbb23 (talk) 23:06, 12 September 2022 (UTC)Reply

Global lock for cross-wiki abuse and LTA sock

[edit]
Status:    In progress

Same user of Special:CentralAuth/R1t5,also,please check sleepers and block IP/IP range(s) when account not stale. --MCC214#ex umbra in solem 10:59, 13 September 2022 (UTC)Reply

Global lock for Dashboard breaker

[edit]
Status:    In progress

Long-term abuse. Lock evasion: Evlekis. --DarkMatterMan4500 (talk) (contribs) 12:53, 13 September 2022 (UTC)Reply

Status:    In progress

Lock evasion: Wikkkj3. --DarkMatterMan4500 (talk) (contribs) 12:55, 13 September 2022 (UTC)Reply

Global lock for Hrdtskx

[edit]
Status:    In progress

Long-term abuse. Kievstar; see also abuse log. --~~~~
User:1234qwer1234qwer4 (talk)
14:39, 13 September 2022 (UTC)Reply

Status:    In progress

Long-term abuse. Foundation banned user. Lock evasion. User:জঙ্গলবাসী. --—Yahya (talkcontribs.) 17:14, 13 September 2022 (UTC)Reply

Global lock for সামাদ ম

[edit]
Status:    In progress

Long-term abuse. Foundation banned user. User:জঙ্গলবাসী. --—Yahya (talkcontribs.) 08:10, 14 September 2022 (UTC)Reply

Global lock for শোভন খান

[edit]
Status:    In progress

Long-term abuse. Foundation banned user. User:জঙ্গলবাসী. --—Yahya (talkcontribs.) 08:12, 14 September 2022 (UTC)Reply

Global lock for かいよー

[edit]
Status:    In progress

Cross-wiki long-term abuse: Sidowpknbkhihj (w:ja:LTA:HEATHROW). blocked on jawiki. and appeared on wikidata and jawikt. --郊外生活Kogaiseikatsu (talk,contribs) 09:57, 14 September 2022 (UTC)Reply

Global lock/unlock for Farmanda Surash

[edit]
Status:    In progress

Cross-wiki abuse. --Sigwald (talk) 10:01, 14 September 2022 (UTC)Reply

Global lock for YoFhone

[edit]
Status:    In progress

Long-term abuse. Lock evasion: Sinlu22. --DarkMatterMan4500 (talk) (contribs) 12:20, 14 September 2022 (UTC)Reply

Global lock for Marsuki s.kom's socks

[edit]
Status:    In progress
User list
Lock all:

Long-term abuse. Cross-wiki abuse. Abusive username. Please see Wikipedia:Penyalahgunaan jangka panjang/Marsuki s.kom. --··· 🌸 Rachmat04 · 12:55, 14 September 2022 (UTC)Reply

Global lock for Dzambik07

[edit]
Status:    In progress

Cross-wiki fake article creation. Please assist. Thank you. Oleg Yunakov (talk) 13:13, 14 September 2022 (UTC)Reply

Status:    In progress

Long-term abuse. User:জঙ্গলবাসী, foundation ban. --—Yahya (talkcontribs.) 16:06, 14 September 2022 (UTC)Reply

Global lock for Artems ruswian

[edit]
Status:    Done

Long-term abuse. Marat Gubaiev. --Mykola 16:21, 14 September 2022 (UTC)Reply

Robot clerk note: Done by Hasley. MajavahBot (talk) 16:55, 14 September 2022 (UTC)Reply

Global lock

[edit]
Status:    In progress

Long-term abuse. Abusive username. --Mykola 20:02, 14 September 2022 (UTC)Reply

Global lock for Snthilakammarist sock(s)

[edit]
Status:    In progress

Sockpuppet(s) found in enwiki sockpuppet investigation, see w:en:Wikipedia:Sockpuppet investigations/Snthilakammarist. Bbb23 (talk) 20:06, 14 September 2022 (UTC)Reply

Status:    In progress

Long-term abuse. Girma adnew. Classic "hi hi hi" and repeated letter edit summaries. --~~~~
User:1234qwer1234qwer4 (talk)
20:57, 14 September 2022 (UTC)Reply

Global lock for BillyTasman3

[edit]
Status:    In progress

Spam / spambot. --reNVoy (user talk) 21:51, 14 September 2022 (UTC)Reply

Global lock for Fools' target

[edit]
Status:    In progress

Same MO of LTA Risto hot sir and its socks. Sock Patinoitunut runomies was globally locked on September 12, 2022 at 1.41 PM by Hasley. Just like other socks it originates from Estonian Wikiquote.

Previously locked socks of Risto hot sir include:

  • Anssi Puro
  • Arvatkaa Kuka
  • Funky kicker
  • Geopoeg
  • Iva-Rekola
  • Jalo Taisto
  • Kalle Perälahti
  • Kalsarimyrkyttäjä
  • Kampissa pistäytynyt
  • Kotkan lusija
  • Lotto-Svärd
  • Minä muka
  • Palon Taavi
  • Patinoitunut runomies
  • Retsinakanister
  • Risto Rekola
  • Roope poor
  • Se Soome Mooses
  • Saita Matias
  • Servon Petteri
  • Stryknin
  • Vilho-Veli
  • Örkkiryssä

Global lock for BeanFan2027

[edit]
Status:    Done

Cross-wiki abuse. --Ilovemydoodle (talk) 23:37, 14 September 2022 (UTC)Reply

Robot clerk note: Done by AmandaNP. MajavahBot (talk) 00:05, 15 September 2022 (UTC)Reply

Global lock for cross-wiki abuse and LTA sock

[edit]
Status:    In progress

Same user of Special:CentralAuth/千村狐免, Special:CentralAuth/Kapol6360 or copycat,also,please check sleepers and block IP/IP range(s) when account not stale.--MCC214#ex umbra in solem 05:41, 15 September 2022 (UTC)Reply

The bottom two are Animal Jumping 2, but the first one just looks like a common vandal. What evidence do you have that it is a sock? -- Amanda (she/her) 06:06, 15 September 2022 (UTC)Reply
AmandaNP,zh.wiki abuse log catch record and autoblock top user,filter said top user personal attack the globally banned user in Village pump.--MCC214#ex umbra in solem 08:56, 15 September 2022 (UTC)Reply

Global lock for 2 spambot accounts

[edit]
Status:    In progress

Spambot accounts, blocked on nl.wiktionary after attempts to add spampages. --MarcoSwart (talk) 07:35, 15 September 2022 (UTC)Reply

Status:    In progress

Long-term abuse. @AmandaNP: This User is supects Sockpuppet account of Adam Chacko , I Request to you please globally lock this account. --Aviram NoSurprisesPlease 08:16, 15 September 2022 (UTC)Reply

Status:    In progress

Long-term abuse. CJEDJCRobertiPARMMSCTBrown2000s-2010s-2020s. --~~~~
User:1234qwer1234qwer4 (talk)
09:22, 15 September 2022 (UTC)Reply

Global lock for সামাদ ব

[edit]
Status:    In progress

Long-term abuse. User:জঙ্গলবাসী, foundation ban. --—Yahya (talkcontribs.) 09:24, 15 September 2022 (UTC)Reply

Status:    In progress

Long-term abuse. ja:LTA:SUMOSONG. --Daraku K. (talk) 12:54, 15 September 2022 (UTC)Reply

Global lock for Porapole

[edit]
Status:    In progress

Lock all:

Lock Evasion:User:フアン_ファン. --Daraku K. (talk) 13:01, 15 September 2022 (UTC)Reply

Global lock for GisJo

[edit]
Status:    In progress

Cross-wiki abuse. ---- Jeff G. ツ (please ping or talk to me) 14:03, 15 September 2022 (UTC)Reply

See also

[edit]

User:Seudo/Test3/Archivefooter