Jump to content

Steward requests/Global

From Meta, a Wikimedia project coordination wiki
This is an archived version of this page, as edited by PlyrStar93 (talk | contribs) at 02:47, 28 August 2019 (Lisamol). It may differ significantly from the current version.

Latest comment: 6 years ago by PlyrStar93 in topic Requests for global (un)lock and (un)hiding


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 (except temporary accounts).

Cross-wiki requests
Meta-Wiki requests


Requests for global (un)block

Global unblock for 151.48.0.0/17

Status:    In progress


Facts:13th june a steward (masti) blocked this italian ip range globally for six months with the motivation 'Cross-wiki spam: spambot'.There was not a spambot which is a computer making automatical spam edits but just a troll who abused account creation.The steward also blocked about twenty fake accounts created from that ip range whose only edits were message spamming in various wikipedias.I have seen that the messages were invitations to many users to join a votation in it.wikipedia.org which was closed short after so probably the abuser would have stopped anyway.But yet the block is still active for about 33000 ips until december.
Considerations:a global block is useful to protect wikipedia but this kind of block exceeds this need.It is excessive both because the abuser has apparently no more reasons to continue his abuse and because to stop his abuse it was sufficient preventing users from that ip range from creating new accounts instead of blocking completely the possibility to edit anything.I know that every block causes unavoidably some collateral damage but in this case the collateral damage is too high but most important it is not necessary.I would not be asking to unblock the ip range if the problem was a spambot or an anonymous user who spammed his messages from various ip addresses from this range.I am asking to unblock the ip range because the abuser used the new accounts he continued creating to spam messages.
Request:imho the most proper solution which both protects wikipedia from the abuser's possible return and makes the least possible collateral damage for the remaining 33000 innocent users is globally blocking new account creations but allowing editing from ips.In this way users can continue contributing anonymously and it would be even easier checking possible disruptive edits by keeping an eye on the ip range.Also consider that this italian ip range is maybe the most common provided by the telecommunication company 'Wind' and that a large part of italian contributors are currently prevented from editing for no justified reason.It is still possible that some users from this ip range will commit some abuse but no ip range contains zero percent of abuse and from this ip range no more abuse than from any other ip range is committed.You can check the contributions from the blocked ip range in it.wikipedia.org to verify my affirmation.So please review this six months global block and change its settings to allow normal users to make their usual constructive edits while preventing the abuser from creating new accounts.
LuluGigi (talk) 09:39, 2 August 2019 (UTC)Reply

Global block for proxies

Status:    In progress

All proxies with edits in multiple projects. Rafael (stanglavine) msg 16:56, 2 August 2019 (UTC)Reply

Global block for 2600:1700:8b60:ca00::/64

Status:    In progress

Cross wiki abuse; BLP violations. --Zaxxon0 (talk) 10:23, 3 August 2019 (UTC)Reply

Global block for Year LTA

Status:    In progress

Persistent cross-wiki vandalism for the past several months (going back more than a year on en.wiki). This person has vandalized en.wiki, es.wiki, pt.wiki, fr.wiki, de.wiki, and Simple Wikipedia recently (other sites are probably affected as well). Most of the abuse involves date-changing vandalism and BLP vandalism (including attacks). The LTA appears to be the only person using this range, and there are almost no positive contributions on any wiki in the past year. After being rangeblocked on en.wiki in June, they took their vandalism cross-wiki again, most notably on simple.wiki. Please block the range (set to "anon-only") for at least 6 months. LightandDark2000 🌀 (talk) 17:45, 5 August 2019 (UTC)Reply

Global block Proxies/Spambots

Status:    In progress

[1] [2] [3] --WikiBayer 👤💬 19:08, 7 August 2019 (UTC)Reply

[4]--WikiBayer 👤💬 19:40, 7 August 2019 (UTC)Reply

Proxys (Spambots) --WikiBayer 👤💬 08:22, 10 August 2019 (UTC)Reply

Global block for 125.27.0.0/16

Status:    In progress

Proxys abuse only [5] --WikiBayer 👤💬 19:56, 7 August 2019 (UTC)Reply

Global block GRP evasion

Status:    In progress

Ban evasion of GRP - see history of s:wt:Administrators' noticeboard --DannyS712 (talk) 00:51, 8 August 2019 (UTC)Reply

See contributions on simple english wikipedia. Thanks, --DannyS712 (talk) 23:55, 12 August 2019 (UTC)Reply

Ban evasion by George Reeves Person.   — Jeff G. ツ please ping or talk to me 15:10, 18 August 2019 (UTC)Reply

Global block for 185.174.156.0/22

Status:    In progress

Abused webhost/proxy (HostRoyale). --Zaxxon0 (talk) 09:26, 9 August 2019 (UTC)Reply

Global block for 45.70.0.0/17

Status:    In progress

Proxies Spambots and abuse only. https://tools.wmflabs.org/meta/stalktoy/45.70.0.0%2F17 --WikiBayer 👤💬 08:30, 10 August 2019 (UTC)Reply

Global block for Proxies Spambots

Status:    In progress

See here [6] --WikiBayer 👤💬 11:41, 11 August 2019 (UTC)Reply

Global block for 143.255.56.0/22

Status:    In progress

Abused webhost/proxy. (HostDime) --Zaxxon0 (talk) 02:49, 15 August 2019 (UTC)Reply

Global block for 202.53.48.106

Status:    In progress

Cross-wiki vandalism. --Xiplus (talk) 09:17, 19 August 2019 (UTC)Reply

Global block for 71.55.69.90

Status:    In progress

Crosswiki vandalism.   — Jeff G. ツ please ping or talk to me 13:09, 20 August 2019 (UTC)Reply

Global locks & blocks for a spammer

Status:    In progress

Crosswiki vandalism. See also c:Commons:Requests for checkuser/Case/Ludovic5443.   — Jeff G. ツ please ping or talk to me 16:26, 21 August 2019 (UTC)Reply

Global block for George Reeves Person

Status:    In progress

George Reeves Person, as usual. Nigos (talk) 00:07, 22 August 2019 (UTC)Reply

Global block for 155.205.200.42

Status:    In progress

Crosswiki vandalism.   — Jeff G. ツ please ping or talk to me 05:56, 22 August 2019 (UTC)Reply

Global block for 74.82.60.190

Status:    In progress

Long-term abuse and cross-wiki abuse User:Vainevery [7] using IP,see same edit in zh:Template:HITO流行音樂獎海外歌手(新加坡)(74.82.60.190,[8],Vainevery,[9]),zh:Template:KKBOX數位音樂風雲榜年度十大風雲歌手(74.82.60.190,[10],Vainevery,[11]),zh:Template:新城勁爆全國歌手大獎(74.82.60.190,[12],Vainevery,[13]),zh:Template:全球流行音樂金榜年度最佳男歌手(74.82.60.190,[14],Vainevery,[15]) and zh:Template:唱工委音乐奖年度最佳男歌手(74.82.60.190,[16],Vainevery,[17]).--MCC214 # ex umbra in solem 11:32, 22 August 2019 (UTC)Reply

Global block for 2600:387:6:902:0:0:0:7

Status:    In progress

Crosswiki vandalism.   — Jeff G. ツ please ping or talk to me 16:37, 22 August 2019 (UTC)Reply

Global block for 144.121.121.99

Status:    In progress

Crosswiki vandalism.   — Jeff G. ツ please ping or talk to me 16:46, 22 August 2019 (UTC)Reply

Global block for 172.69.134.10

Status:    In progress

Proxy: Cloudflare. See Steward requests/Global/2019-08#Global block for all IPv4s under AS13335 (CloudFlare). --云间 守望 05:58, 23 August 2019 (UTC)Reply

Global Block for sock

Status:    In progress

Denver LTA perp. --IanDBeacon (talk) 19:32, 23 August 2019 (UTC)Reply

Status:    In progress

Crosswiki vandalism.   — Jeff G. ツ please ping or talk to me 17:11, 24 August 2019 (UTC)Reply

Global block for 108.185.158.33

Status:    In progress

Cross-wiki vandalism, just recently after a 2 week gblock. --Zaxxon0 (talk) 20:04, 25 August 2019 (UTC)Reply

Global block for 74.12.123.253

Status:    In progress

Bell Canada vandal using a new IP. For further information just take a look at this short summary made by NicoScribe (talk · contribs) 2 months ago. --Montgomery (talk) 08:31, 26 August 2019 (UTC)Reply

Global block for extremely disruptive LTA

Status:    In progress
The moment this last global block expired, they immediately started vandalizing again. Praxidicae (talk) 21:07, 26 August 2019 (UTC)Reply

Global block for 103.242.22.234

Status:    In progress

Crosswiki vandalism.   — Jeff G. ツ please ping or talk to me 01:43, 27 August 2019 (UTC)Reply

Global block for 96.77.249.9

Status:    In progress

Crosswiki vandalism.   — Jeff G. ツ please ping or talk to me 01:52, 27 August 2019 (UTC)Reply

Global block for 2402:1980:253:4a8b::1

Status:    In progress

Crosswiki vandalism.   — Jeff G. ツ please ping or talk to me 11:25, 27 August 2019 (UTC)Reply

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

Global lock for Isechika/Masato Koizumi

Status:    In progress

Isechika, Koizumi PT. ARTIKEL PILIHAN MAKMUR (talk) 21:06, 21 August 2019 (UTC)Reply

Global lock for spammers

Status:    In progress

Lock allGlobal block all:

Praxidicae (talk) 13:56, 23 August 2019 (UTC)Reply

Global lock for GavinUiw45196041

Status:    In progress

Spam only account, --—Ah3kal (talk) 14:24, 23 August 2019 (UTC)Reply

Global lock for spammers (2)

Status:    In progress

Spam only account,—Ah3kal (talk) 14:29, 23 August 2019 (UTC)Reply

Global lock for xwiki lta

Status:    In progress
See Atomsalebpizza1994 etc...Praxidicae (talk) 14:38, 23 August 2019 (UTC)Reply

Global lock for Kuldeep sah

Status:    In progress

Long-term abuse, sock of Yash gawli. -★- PlyrStar93 Message me. 16:59, 23 August 2019 (UTC)Reply

Global lock/unlock for New York and Chicago

Status:    In progress

crosswiki vandlism, --WikiBayer 👤💬 18:30, 23 August 2019 (UTC)Reply

Global lock for xwiki spammer

Status:    In progress
Praxidicae (talk) 18:50, 23 August 2019 (UTC)Reply

Global lock for cross-wiki abuse and LTA Xayahrainie43 sock

Status:    In progress

Lock allGlobal block all:

Sock of long-term abuse and cross-wiki abuse Xayahrainie43[18],also,I hope to check whether there have sleepers and block their IP(s)/IP range(s) if they have create account,here are some other recently created that still have data available,thanks.--MCC214 # ex umbra in solem 10:51, 24 August 2019 (UTC)Reply

Global lock for cross-wiki abuse and LTA Jessechi sock

Status:    In progress

Lock allGlobal block all:

Sock of long-term abuse and cross-wiki abuse Jessechi[19].--MCC214 # ex umbra in solem 11:05, 24 August 2019 (UTC)Reply

Global lock for LTA Shaunak Chakraborty sock

Status:    In progress

Obvious sock of Annoimot, the Shaunak Chakraborty LTA. Cross-wiki abuse. --Hiàn (talk)/editing on mobile account. 15:21, 24 August 2019 (UTC)Reply

Global lock for crosswiki spammer

Status:    In progress

Creating the same page Bhuwari dham across many wikis, meta included, indef in enwikinews for spam. Crosswiki spam.--Cohaf (talk) 17:49, 24 August 2019 (UTC)Reply

+1--Cohaf (talk) 06:18, 26 August 2019 (UTC)Reply

Global lock for JeramyWallis42

Status:    In progress

Spambot account, blocked on nl.wiktionary after attempts to add blacklisted links. --MarcoSwart (talk) 20:12, 24 August 2019 (UTC)Reply

Global lock for Yash gawli sockpuppet

Status:    In progress

New sock puppet of Yash gawli. Эlcobbola talk 20:57, 24 August 2019 (UTC)Reply

+Sock. Эlcobbola talk 02:27, 25 August 2019 (UTC)Reply
+Sock. Эlcobbola talk 16:38, 25 August 2019 (UTC)Reply
+Sock. Эlcobbola talk 21:39, 26 August 2019 (UTC)Reply

Global lock for Fran25t socks

Status:    In progress

Lock allGlobal block all:

See here. 1989 (talk) 23:27, 24 August 2019 (UTC)Reply

Yeah, forgot to ask for a lock. Two of the CU-confirmed accounts are already globally locked for vandalism – the rest should be, too. This person seems to be targeting people who report his sock puppets. NinjaRobotPirate (talk) 02:26, 25 August 2019 (UTC)Reply

Global lock for impersonation account

Status:    In progress

Impersonation of Bradv, probably an LTA of some sort. Vermont (talk) 00:25, 26 August 2019 (UTC)Reply

Global lock for cross-wiki abuse and LTA 65.49.0.0/17 and 74.82.60.190 sock

Status:    In progress

Lock allGlobal block all:

Sock of long-term abuse and cross-wiki abuse 65.49.0.0/17[20] and 74.82.60.190,also,I hope to check whether there have sleepers and block their IP(s)/IP range(s) if they have create account,here are some other recently created that still have data available,thanks.--MCC214 # ex umbra in solem 10:55, 26 August 2019 (UTC)Reply

Global lock for cross-wiki abuse and LTA

Status:    In progress

Lock allGlobal block all:

Same to This user,also,I hope to check whether there have sleepers and block their IP(s)/IP range(s) if they have create account,thanks.--MCC214 # ex umbra in solem 11:55, 26 August 2019 (UTC)Reply

Global lock for spam-only accounts

Status:    In progress

Lock allGlobal block all:

Spam-only accounts (same person, same edits). Blocked at spanish projects, but continues at Wikidata and Commons. Regards, Rafael (stanglavine) msg 13:40, 26 August 2019 (UTC)Reply

Global lock for sockpuppet

Status:    In progress

Lock allGlobal block all:

Lock evasion of デーモン閣下. --Soratako (talk) 14:45, 26 August 2019 (UTC)Reply

Global lock for various accounts

Status:    In progress

Lock allGlobal block all:

Cross-wiki abuse. -★- PlyrStar93 Message me. 22:28, 26 August 2019 (UTC)Reply

Global lock for spambots

Status:    In progress

Lock allGlobal block all:

--—Ah3kal (talk) 04:20, 27 August 2019 (UTC)Reply

Global lock for Nehal siddiqui122

Status:    In progress

Cross-wiki spammer. --Graham87 (talk) 05:00, 27 August 2019 (UTC)Reply

Global lock for 3 spambot accounts

Status:    In progress

Lock allGlobal block all:

Spambot accounts, blocked on nl.wiktionary after attempts to add blacklisted links or triggering global filters 169 and 72. --MarcoSwart (talk) 06:12, 27 August 2019 (UTC)Reply

Global lock for more Jack Bin spammers

Status:    In progress
See here for reference. Praxidicae (talk) 15:27, 27 August 2019 (UTC)Reply

Global lock for socks of The Train Master

Status:    In progress

Lock allGlobal block all:

Long-term abuse. -★- PlyrStar93 Message me. 02:41, 28 August 2019 (UTC)Reply

Global lock for an account

Status:    In progress

Lock allGlobal block all:

Inappropriate username, clearly some LTA --94rain Talk 02:46, 28 August 2019 (UTC)Reply

Global lock for socks of Shiwam Kumar Sriwastaw

Status:    In progress

Lock allGlobal block all:

Cross-wiki abuse; two accounts confirmed with each other. -★- PlyrStar93 Message me. 02:47, 28 August 2019 (UTC)Reply

See also