Steward requests/Global: Difference between revisions

From Meta, a Wikimedia project coordination wiki
Browse history interactively
← Older editNewer edit →
Content deleted Content added
VisualWikitext
MCC214 (talk | contribs)
3,015 edits
Reporting 私房肉排蓋飯 (TwinkleGlobal)
MCC214 (talk | contribs)
3,015 edits
Line 249: Line 249:
{{Status}}
{{Status}}
*{{LockHide|1=私房肉排蓋飯}}
*{{LockHide|1=私房肉排蓋飯}}
Same user of [[Special:CentralAuth/Xayahrainie43],also,please check sleepers and block IP/IP range(s) when account not stale. --'''<font size="3.5">[[User:MCC214|<font color="#0af">MCC214</font>]][[Special:Contributions/MCC214|#]][[User Talk:MCC214|<font color="#3CB371">ex umbra in solem</font>]]</font>''' 10:56, 19 September 2022 (UTC)
Same user of [[Special:CentralAuth/Xayahrainie43]],also,please check sleepers and block IP/IP range(s) when account not stale.--'''<font size="3.5">[[User:MCC214|<font color="#0af">MCC214</font>]][[Special:Contributions/MCC214|#]][[User Talk:MCC214|<font color="#3CB371">ex umbra in solem</font>]]</font>''' 10:56, 19 September 2022 (UTC)


== See also ==
== See also ==

Revision as of 10:57, 19 September 2022

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 unblock for 147.161.237.87

Status:    On hold

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]
@Jon Kolbert: --Alaa :)..! 14:04, 18 September 2022 (UTC)[reply]

Global unblock for 197.210.71.0/24

Status:    On hold

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]

@Operator873: --Alaa :)..! 13:55, 18 September 2022 (UTC)[reply]

Global block for 79.46.25.22

Status:    On hold

Cross-wiki abuse. --Quinlan83 (talk) 17:34, 16 September 2022 (UTC)[reply]

Examples, please? --Alaa :)..! 09:32, 18 September 2022 (UTC)[reply]

Global block for 45.232.250.66

Status:    In progress

Long-term abuse. Proxy. GRP. (See Incubator abuse log for last one.). --~~~~
User:1234qwer1234qwer4 (talk) 17:20, 18 September 2022 (UTC)[reply]

+1. ~~~~
User:1234qwer1234qwer4 (talk) 17:52, 18 September 2022 (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 Huonggiangidol + Huonggiangidol's sockpuppets

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

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

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

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 Wichian Seangngam

Status:    In progress

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

Global lock for 馮克勁

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 Premanidhi premanidhi

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

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

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

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]

Santali Wikipedia spam

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 Rhinofax22

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

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 12 ( Music )

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

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)

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

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)

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

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

Status:    In progress

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

Global lock for Hrdtskx

Status:    In progress

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

Global lock/unlock for Farmanda Surash

Status:    In progress

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

Global lock for Marsuki s.kom's socks

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 spam-only accounts

Status:    In progress

Lock all:

--Supertoff (talk) 16:35, 15 September 2022 (UTC)[reply]

Global lock for 落葉飛仙

Status:    In progress

LTA, see previously locked accounts [1][2]. --Johannnes89 (talk) 20:19, 15 September 2022 (UTC)[reply]

Global lock for LTA

Status:    In progress

Lock all:

LTA - Resurfaced today on nl-wiki and en-wiki. Reincarnation and sleepers (privacy violations were oversighted) of globally locked user 19Francis65 (talk • contribs • block • xwiki-contribs • xwiki-date (alt) • CA • ST • lwcheckuser). Privacy violations and conspiracy theories. Expands crosswiki. See also here and recent checkuser on en-wiki --- Hoyanova (talk) 08:31, 16 September 2022 (UTC)[reply]

Global lock for cross-wiki abuse and LTA sock

Status:    In progress

Same user of Special:CentralAuth/顓如,also,please check sleepers and block IP/IP range(s) when account not stale.--MCC214#ex umbra in solem 11:02, 17 September 2022 (UTC)[reply]

Global lock for MELT1917

Status:    Not done

Crosswiki vandalism, but appears to be in good standing at zhwiki. But permablocked for vandalism in several other wikis. Not sure how to deal with a situation like this. --EstrellaSuecia (talk) 13:34, 18 September 2022 (UTC)[reply]

Not done -- Amanda (she/her) 05:39, 19 September 2022 (UTC)[reply]

Global lock for Schiacciatina66

Status:    Done

Long-term abuse: A1cb3 (CU confirmed). --Mtarch11 (talk) 14:14, 18 September 2022 (UTC)[reply]

Robot clerk note: Done by AmandaNP. MajavahBot (talk) 05:45, 19 September 2022 (UTC)[reply]

Global lock for Gamer10101 sock(s)

Status:    In progress

Sockpuppet(s) found in enwiki sockpuppet investigation, see w:en:Wikipedia:Sockpuppet investigations/Gamer10101. Bbb23 (talk) 15:05, 18 September 2022 (UTC)[reply]

Global lock for LTA sockpuppet

Status:    In progress
Long-term, cross-wiki abuse(ja:LTA:IKE). --Y-route (talk) 17:26, 18 September 2022 (UTC)[reply]

Global lock for Dinglefart McDeluxe

Status:    Done

Block evasion, Mr. Wet Poopy Diaper Ass. --–FlyingAce✈hello 03:51, 19 September 2022 (UTC)[reply]

Robot clerk note: Done by Hasley. MajavahBot (talk) 04:05, 19 September 2022 (UTC)[reply]

Global lock for LTA:IKE

Status:    In progress

Long-term abuse. Abusive username. --Syunsyunminmin 🗨️talk 07:06, 19 September 2022 (UTC)+1 account.--Syunsyunminmin 🗨️talk 07:23, 19 September 2022 (UTC)[reply]

Global lock for Market updates

Status:    In progress

Spam / spambot. --SHB2000 (talk | contribs) 07:25, 19 September 2022 (UTC)[reply]

Global lock for DigitalAgencyDubai

Status:    In progress

Spam / spambot. --SHB2000 (talk | contribs) 08:15, 19 September 2022 (UTC)[reply]

Global lock for cross-wiki abuse and LTA sock

Status:    In progress

Lock all:

Same user of Special:CentralAuth/右孔丘,also,please check sleepers and block IP/IP range(s) when account not stale. --MCC214#ex umbra in solem 10:40, 19 September 2022 (UTC)[reply]

Global lock for cross-wiki abuse and LTA sock

Status:    In progress

Same user of Special:CentralAuth/Xayahrainie43,also,please check sleepers and block IP/IP range(s) when account not stale.--MCC214#ex umbra in solem 10:56, 19 September 2022 (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=23826323"