Jump to content

Steward requests/Global: Difference between revisions

From Meta, a Wikimedia project coordination wiki
< Steward requests
Latest comment: 5 years ago by Future Perfect at Sunrise in topic Requests for global (un)lock and (un)hiding
Browse history interactively
← Older editNewer edit →
Content deleted Content added
VisualWikitext
Line 296: Line 296:
{{status}} <!-- do not remove this template -->
{{status}} <!-- do not remove this template -->
*{{LockHide|Rheinbacher}} --[[User:Hedwig in Washington|Hedwig in Washington]] ([[User talk:Hedwig in Washington|talk]]) 16:05, 9 January 2019 (UTC)
*{{LockHide|Rheinbacher}} --[[User:Hedwig in Washington|Hedwig in Washington]] ([[User talk:Hedwig in Washington|talk]]) 16:05, 9 January 2019 (UTC)

=== Global lock for [[User:Jampal abhrishrek|Jampal abhrishrek]] ===
{{status}} <!-- do not remove this template -->
*{{LockHide|Jampal abhrishrek}}
Obvious Wikinger sock, impersonating similarly-named but unrelated [[:en:User:Jampal abhrishek]]. [[User:Future Perfect at Sunrise|Fut.Perf.]] [[User talk:Future Perfect at Sunrise|☼]] 20:41, 9 January 2019 (UTC)


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

Revision as of 20:41, 9 January 2019

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

Latest comment: 5 years ago38 comments21 people in discussion
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 240[59]:0:0:0::/16 or a large number of subnets within this range

Status:    In progress

This is a follow-up to [[Steward_requests/Global/2018-10#Global_block_for_IPv6_range_240[59]:*]]. I strongly believe that all subnets mentioned in the previous request should be blocked as well rather than just the three picked out, especially since the above two in this request, not falling under the list from the previous request, are sources of this spam as well. @Horcrux and Trijnstel: Mahir256 (talk) 06:46, 16 November 2018 (UTC)Reply

I should check for collateral, but as a general comment I'm usual not in favor of blocking such huge IPv6 ranges. Trijnsteltalk 10:08, 16 November 2018 (UTC)Reply
@Trijnstel: The newest incarnation of this spam is on the Romani Wikipedia. You may wish to check whether "User:Wikiromanadm" is the same individual. Mahir256 (talk) 15:36, 16 November 2018 (UTC)Reply
@Sjoerddebruin, Stryn, Ajraddatz, -revi, علاء, HakanIST, and Hoo man: as Wikidata admins and stewards who can tackle the threatening behavior from this individual. Mahir256 (talk) 17:19, 16 November 2018 (UTC)Reply

Global block for 125.212.177.0/20

Status:    In progress

So many IPs of this range are doing vandalism in various wikis, mainly in lists of flags. --Mr. Fulano! Talk 17:09, 24 November 2018 (UTC)Reply

I just came here to report 176 for the same reason. Just blocked 125.212.176.220 on mlwiki -- Razimantv 07:57, 8 December 2018 (UTC)Reply

Global blocks for 107.175.0.0/17 and 107.175.128.0/17

Status:    In progress

(or 107.175.0.0/16 xwiki-contribs • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye)

At meta I am seeing constant spambot infringements from within the /16, and I see that we have previously blocked the /16 before, though when I do some IP checks they seem to be separate /17s though both still seem to be server colo sets. GUC doesn't show that a block would be problematic, so I am asking for both /17s to have an extended block time, maybe a couple of years if that isn't problematic for logged in users (unknown and may be worth checking for account spambots anyway). Thanks or the consideration.  — billinghurst sDrewth 00:56, 26 November 2018 (UTC)Reply

@Billinghurst: GUC works on subnets again? I get 0 results.   — Jeff G. ツ please ping or talk to me 18:21, 30 November 2018 (UTC)Reply
GUC won't show either abusefilter and spamblocklist hits or deleted contributions, and who knows what accounts may be are created within those two ranges. I do know what I see, hence the report, and we do know that there is a history with these ranges.  — billinghurst sDrewth 06:46, 1 December 2018 (UTC)Reply

Global block for 185.158.132.0/22

Status:    In progress

This range is spambot problematic at Meta and has been identified as such previously and now locally blocked until the end of 2020. I will hazard a guess that it is the same xwiki, if it is clear of user accounts, you may wish to consider blacklisting.  — billinghurst sDrewth 01:47, 26 November 2018 (UTC)Reply

Global block for 125.212.128.0/18

Status:    In progress

Cross-wiki vandalism. --jdx Re: 12:28, 26 November 2018 (UTC)Reply

Global unblock for 198.52.128.0/17

Status:    In progress

This IP address was blocked back in 2014 for "webhost Avante Hosting Services + 198.52.217.44". It appears that the IP address in question has been rotated to different users. Charwinger21 (talk) 07:01, 30 November 2018 (UTC)Reply

Specifically, the range was assigned to Carrytel (an ISP) on 2018-05-23. Charwinger21 (talk) 09:19, 1 December 2018 (UTC)Reply

Global block for 2001:4898::/32

Status:    In progress

Abused ip range from a cloud provider XXBlackburnXx (talk) 21:14, 2 December 2018 (UTC)Reply

Global block for several ranges in Jakarta, Indonesia

Status:    In progress

Anon-only for ∼1 month, please. Page blanking. Tries to harass cross-wiki those sysops who block them. Subsumes two requests by Jeff_G. above. Incnis Mrsi (talk) 12:07, 3 December 2018 (UTC)Reply

Global block for 94.130.0.0/16

Status:    In progress

Cross-wiki vandalism. Vermont (talk) 03:12, 6 December 2018 (UTC)Reply

Global block for 2001:b400::/32(Nipponese Dog Calvero (KAGE) used)

Status:    In progress

Cross-wiki LTA 影武者(KAGE) usually used[1].--MCC214Talk with me#Contributions with me 10:05, 6 December 2018 (UTC)Reply

Is MCC214 kidding about /32? Some half-year ago I requested his /40—that is, 28 times smaller—and yet the block was denied. Lurk in archives and learn which range size is typical for a blocked IPv6. Incnis Mrsi (talk) 18:29, 19 December 2018 (UTC)Reply
I see this[2].--MCC214#aut viam inveniam aut faciam 07:19, 20 December 2018 (UTC)Reply
IPv6 KAGE (Nipponese Dog Calvero) used:2001:B400:E2DA:A886:3150:F5EE:68EB:890B[3], 2001:B400:E2D8:ED2F:D48:DE7D:FF3:25C5[4],2001:b400:e252:64c1:4829:4459:9d43:e16a[5],2001:b400:e231:f6ee:b81e:ce55:e7e:926f[6].--MCC214#aut viam inveniam aut faciam 10:18, 27 December 2018 (UTC)Reply

Global block for 2600:8800:3980:2550:0:0:0:0/64

Status:    In progress

Block evasion by MisterAnthony (talk · contribs), same as this recent request but is now using a slightly different IP range. The same Wikidata item that was linked in that request shows the same behaviour from this IP range and there are already a number of local blocks for this range or IPs from this range. - Nikki (talk) 17:45, 6 December 2018 (UTC)Reply

Global block for 125.214.48.0/22

Status:    In progress

Crosswiki vandalism by proxy.   — Jeff G. ツ please ping or talk to me 15:29, 19 December 2018 (UTC)Reply

Global block for 51.68.11.219

Status:    In progress

WDHB. Vermont (talk) 19:45, 21 December 2018 (UTC)Reply

It seems 51.68.0.0/16 is an OVH range, so a webhost/proxy. — surjection ⟨?⟩ 20:25, 21 December 2018 (UTC)Reply
Vermont, you beat me to it. Thanks. Please revdel it all, stewards, and when you place a rangeblock, consider not allowing them to use the talk page, and consider blocking 2602:FFF6:F:0:0:0:0:0/48 as well. Drmies (talk) 21:39, 21 December 2018 (UTC)Reply

Global block for 70.94.106.154

Status:    In progress

Repetitive vandalisms despite many long term blocks (six months on en-WP and one year on fr-WP). For this IP has exclusively been used for vandalisms so far, and in order to protect numerous wikis, I suggest a six months global block. I ping Sammyday and Linedwell from the french Wikipedia.--Braaark (talk) 18:22, 2 January 2019 (UTC)Reply

@Braaark: stopped since 29 Dec 2018 (since 4 days)! --Alaa :)..! 05:22, 3 January 2019 (UTC)Reply

Global block for 2001:EE0:5776:4C60:EC32:3E23:B40:D90F

Vandalism on en.wikipedia.org, simple.wikipedia.org, vi.wikipedia.org, possibly others. Rubbish computer (Talk: Contribs) 20:45, 4 January 2019 (UTC)Reply

Global block for 50.254.21.213

Status:    Done

Cross-wiki vandalism. --Esteban16 (talk) 00:00, 7 January 2019 (UTC)Reply

Done --Alaa :)..! 13:43, 8 January 2019 (UTC)Reply

Global block for 84.210.66.167

Status:    Done

Cross-wiki vandalism. --Xiplus (talk) 03:44, 7 January 2019 (UTC)Reply

Done --Alaa :)..! 13:41, 8 January 2019 (UTC)Reply

Global block for 185.50.25.24

Status:    In progress

Cross-wiki vandalism. --Esteban16 (talk) 17:29, 7 January 2019 (UTC)Reply

@Esteban16: Stopped since 24 Nov 2018?! --Alaa :)..! 13:38, 8 January 2019 (UTC)Reply

Global block for Special:Contributions/176.47.100.87

Status:    Done

Cross-wiki date vandalism. NinjaRobotPirate (talk) 12:45, 8 January 2019 (UTC)Reply

Done --Alaa :)..! 13:36, 8 January 2019 (UTC)Reply

Global block for 192.162.165.0/24

Status:    In progress

Seeing repeated xwiki hits through log/spamblacklists for IPs in this range, though I also think that it may be 192.162.164.0/22. If we are able to block it for an extended period without negative consequences, I think that it will have benefits. GUC shows just three live edits in 2014.  — billinghurst sDrewth 10:43, 9 January 2019 (UTC)Reply

Global block for 176.224.232.240

Status:    In progress

Crosswiki vandalism.   — Jeff G. ツ please ping or talk to me 13:22, 9 January 2019 (UTC)Reply

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

Latest comment: 5 years ago38 comments23 people in discussion
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 Satoshi Kondo/WorldCreaterFighter

Status:    In progress
Extended content

After being blocked indefinitely in the English-language Wikipedia because of his massive abuse of sockpuppets and persistent POV edits, he switches to the German Wikipedia and got blocked indefinitely there for massive spamming. Hee keeps creating accounts and edits both with IPs and new sockpuppets for years since 2015, as the List in the English-language Wikipedia of Vanjagenije, Sro23 and GeneralizationsAreBad shows it. --Sonra Mint (talk) 17:11, 6 November 2018 (UTC)Reply

Sonra Mint is itself a sock puppet of user de:Benutzer:Dribbler and blocked in german wikipedia(Special:CentralAuth/Sonra Mint). And i do not know how often i have to say this: I am not WorlCreaterFighter. Look at my english talkpage. I have made a list of my former socks.(talkpage) I have also said that I will not work on these topics anymore. Sonra Mint is possibly related to some of them, as he/she is a confirmed sock aswell. Btw. User Tomurtogo is blocked as sock of Tigril(Tirgil34). Satoshi Kondo (talk) 11:17, 7 November 2018 (UTC)Reply
He(or she) is possibly an albanian user, 310 edits on albanian wiki, also blocked on netherland wiki for sockpuppetry... Satoshi Kondo (talk) 11:08, 7 November 2018 (UTC)Reply

Why am I listed here? I just saw the message in Wiki. Please take me from that list. I have nothing to do with this, or am related with this sock in any way. Regards, Akocsg (talk) 17:09, 10 November 2018 (UTC)Reply

Note: Satoshi Kondo is a contributor to Wikimedia Commons user. Why wasn’t our community notified about this de facto ban proposal? Incnis Mrsi (talk) 12:55, 1 December 2018 (UTC)Reply

Global lock for Arturo socks

Status:    In progress

Lock all:

Long-term abuse. -★- PlyrStar93 →Message me. ← 23:57, 5 January 2019 (UTC)Reply

Global lock for Vandals

Status:    In progress

Global lock/unlock for Reapok

Status:    Done
Done --Alaa :)..! 13:45, 8 January 2019 (UTC)Reply

Global lock for JaySmith2018 socks

Status:    In progress
There's probably more but these are all obvious JRS socks. Praxidicae (talk) 14:25, 7 January 2019 (UTC)Reply

Global lock for 2 spambot accounts

Status:    Done

Spambot accounts, blocked on nl.wiktionary after triggering filter 195. --MarcoSwart (talk) 22:10, 7 January 2019 (UTC)Reply

Done, Linedwell [talk] 19:37, 8 January 2019 (UTC)Reply

Global lock for Zemwa

Status:    Done

Sock of Sol-lol. Эlcobbola talk 22:29, 7 January 2019 (UTC)Reply

Done Ruslik (talk) 20:59, 8 January 2019 (UTC)Reply

Global lock for cross-wiki LTA Jessechi sock

Status:    In progress

--MCC214#aut viam inveniam aut faciam 07:23, 8 January 2019 (UTC)Reply

Global lock for zh.wikipedia LTA SiuMai sock

Status:    In progress

Cross-wiki use sock.--MCC214#aut viam inveniam aut faciam 07:23, 8 January 2019 (UTC)Reply

Global lock for Xayahrainie43 sock

Status:    Done

--MCC214#aut viam inveniam aut faciam 07:28, 8 January 2019 (UTC)Reply

Done Ruslik (talk) 20:54, 8 January 2019 (UTC)Reply

Global lock for Fiqister

Status:    Done

This account is an obvious sock puppet of the globally locked FaiqAhmed (talk • contribs • block • xwiki-contribs • xwiki-date (alt) • CA • ST • lwcheckuser) account, spamming pages about an organization called "Zindagi Trust". This account has since started spamming Simple English Wikipedia with the same behavior. --Mz7 (talk) 08:15, 8 January 2019 (UTC)Reply

Done Ruslik (talk) 20:58, 8 January 2019 (UTC)Reply

Global lock for 2 spambot accounts

Status:    Done

Spambot accounts, blocked on nl.wiktionary after triggering filter 195, followed by attempts to add blacklisted links. --MarcoSwart (talk) 14:00, 8 January 2019 (UTC)Reply

Done, Linedwell [talk] 19:36, 8 January 2019 (UTC)Reply

Global lock for Watch out for the cr***ir

Status:    Done

Long-term abuse.--SkyGazer 512 (talk) 14:38, 8 January 2019 (UTC)Reply

Done — Defender (talk) 15:16, 8 January 2019 (UTC)Reply

Global lock for spambots

Status:    In progress

Global lock for Areokye

Status:    In progress

block/global lock-evasion, sock-puppet of Reapok (talk · contribs · page moves · block user · block log) --Seb az86556 (talk) 21:23, 8 January 2019 (UTC)Reply

Global lock for LTA Sock

Status:    In progress

LTA sock of User:BMX On WheeIs. Please see en:WP/LTA/BMX. Please run a c/u. --IanDBeacon (talk) 21:25, 8 January 2019 (UTC)Reply

Global lock for sock of Angela Criss/Tamara787

Status:    Done

Long-term abuse. -★- PlyrStar93 →Message me. ← 21:57, 8 January 2019 (UTC)Reply

Done Ruslik (talk) 08:24, 9 January 2019 (UTC)Reply

Global lock for spambot MargartR74 & LayneApplebaum0

Status:    Done
Done Ruslik (talk) 08:28, 9 January 2019 (UTC)Reply

Global lock/unlock for Porn LTA

Status:    Done

Same pattern as before, uploading Goatse on Commons and using proxies to vandalize en-wiki. --funplussmart (talk) 03:45, 9 January 2019 (UTC)Reply

Done Ruslik (talk) 08:22, 9 January 2019 (UTC)Reply

Global lock for spam factory

Status:    In progress

Lock all:

All caught by the abuse filter within the space of a few hours. Leaderboard (talk) 07:28, 9 January 2019 (UTC)Reply

Global lock for Allthingsgo sock

Status:    In progress

Global lock for LTA HHubi sock

Status:    In progress

Global lock for Jampal abhrishrek

Status:    In progress

Obvious Wikinger sock, impersonating similarly-named but unrelated en:User:Jampal abhrishek. Fut.Perf. ☼ 20:41, 9 January 2019 (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=18769798"