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 03:46, 21 August 2019 (Global lock for sock of George reeves). It may differ significantly from the current version.

Latest comment: 7 years ago by SCP-2000 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

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

Global unlock for innocent users

Status:    In progress

Both users were locked as the result of a recent check on an LTA on Chinese Wikipedia. However, we are confident that both users are NOT the LTA himself for clear behavioral evidence. Please unlock these accounts immediately or it would be definitely bad for newbies. --TechyanTalk14:06, 16 August 2019 (UTC)Reply

I don't know are they innocent or not, however, there is a huge local discussion where many users expresses their faith that the user is innocent. I have no comments on this case but I wish that the stewards can make a through investigation and hope that this can be resolved as soon as possible. I hope that more information can be given (like the ISPs / UA used) and how the stewards make determination that the users are socks of NDC. Thanks much. --Cohaf (talk) 11:02, 17 August 2019 (UTC)Reply
The first user is (from CU point of view) indistinguishable from 哀悼中國共產黨竊國70週年: the same IP, the same UA string and created just a few hours apart. Ruslik (talk) 08:02, 18 August 2019 (UTC)Reply
@Ruslik0:Thanks for your reply. First, 应援小嵩鼠 have just edited the pages about the singer 許嵩 and 娱乐新闻 have just edited the page about the actor 陳嘉俊. Their editing behavior is different from Nipponese Dog Calvero. Second, 应援小嵩鼠 said that he lives in Mainland China that he use Simplified Chinese to edit and he needs to use different proxies to edit Wikipedia. So 应援小嵩鼠 and 哀悼中國共產黨竊國70週年 IP may same. Third, 应援小嵩鼠 is his third account. His first account 音樂人許嵩 and second account 許嵩和格洛米 is blocked because he used the misleading username and violate w:zh-tw:WP:UN. So he created third account and the same created time is a coincidence. Please unlock user 应援小嵩鼠 and 娱乐新闻. Thank you! (edited at 1:43 p.m UTC in 20 Aug)--SCP-2000 (talk) 12:56, 19 August 2019 (UTC)Reply
@Ruslik0:Could you unlock these account repidly? Thank you!--SCP-2000 (talk) 03:40, 21 August 2019 (UTC)Reply

Global lock for socks of locked Garwel

Status:    Done

Lock evasion. Please also monitor c:Category:Sockpuppets of Garwel.   — Jeff G. ツ please ping or talk to me 03:11, 18 August 2019 (UTC)Reply

Done Ruslik (talk) 19:54, 20 August 2019 (UTC)Reply
@Ruslik: Thanks!   — Jeff G. ツ please ping or talk to me 22:25, 20 August 2019 (UTC)Reply

Global lock for Albert_Giban86 and socks

Status:    In progress

Main account was only blocked on one project, but sockpuppets involved in cross-wiki abuse. See commons:Category:Sockpuppets_of_Albert_Giban86 (Gimbalpapuaalbert Papuaalbertgiban has already been locked). --94rain Talk 06:21, 18 August 2019 (UTC)Reply

Global lock for Wonderfool socks

Status:    In progress

Lock allGlobal block all:

These appear to be socks of Wonderfool and the others recently discovered (Cyckleletya, ChubbEdtres, Brusher21a, Mookar21a, and Lifer616) have already been locked by Ruslik0. Please see the enwiki Sockpuppet Investigation. --TheSandDoctor Talk 16:18, 18 August 2019 (UTC)Reply

Global lock for 2 spambot accounts

Status:    In progress

Lock allGlobal block all:

Spambot accounts, blocked on nl.wiktionary after attempts to add blacklisted links. --MarcoSwart (talk) 08:05, 19 August 2019 (UTC)Reply

Global lock for cross-wiki abuse and LTA 顓如

Status:    In progress

Lock allGlobal block all:

[7].--MCC214#ex umbra in solem 10:08, 19 August 2019 (UTC)Reply

Global lock for Abdullah Zubayer/Borhankhan01 socks

Status:    In progress
Same xwiki vanity spam promoting Vahdat Rahimi and Hojat Rahimi/RadioJavan. All of which are title blacklisted. Praxidicae (talk) 17:58, 19 August 2019 (UTC)Reply

Global lock for King of Bir Tawil

Status:    In progress

Cross wiki vandalism; inserting hoaxes. --Zaxxon0 (talk) 01:15, 20 August 2019 (UTC)Reply

Global lock for LuzCrump473

Status:    In progress

Spambot, probably a bunch connected. Thanks, Vermont (talk) 02:10, 20 August 2019 (UTC)Reply

Global lock for Ola Doglover

Status:    In progress

Cross-wiki spammer. --Graham87 (talk) 04:21, 20 August 2019 (UTC)Reply

Global lock for more Frankie De Pyae socks

Status:    In progress
Praxidicae (talk) 10:54, 20 August 2019 (UTC)Reply

Global lock for Prince-au-Léogâne LTA sock

Status:    In progress

Obvious sock of the Prince-au-Léogâne LTA that has been spamming the projects for well over a decade. Subsequent socks have been locked. See w:en:Wikipedia:Sockpuppet investigations/Prince-au-Léogâne/Archive and Steward_requests/Global/2018-12#Global_lock_for_cross-wiki_spammers. --Hiàn (talk) 12:03, 20 August 2019 (UTC)Reply

Global lock for King Saifonce

Status:    In progress

Crosswiki vandalism in the form of shameless inept self-promotion.   — Jeff G. ツ please ping or talk to me 13:40, 20 August 2019 (UTC)Reply

Global lock for Lvslopgh ceqgscwxliou

Status:    In progress

abuse only crosswiki
(sock of Moundantoine (global block user) see here--WikiBayer 👤💬 17:27, 20 August 2019 (UTC)Reply

Global lock for Adolfery

Status:    In progress

Holocaust denialism.   — Jeff G. ツ please ping or talk to me 22:31, 20 August 2019 (UTC)Reply

Global lock for 烂维1

Status:    In progress

Long-term abuse --94rain Talk 01:12, 21 August 2019 (UTC)Reply

Global lock for various accounts

Status:    In progress

Lock allGlobal block all:

Cross-wiki abuse. -★- PlyrStar93 Message me. 01:31, 21 August 2019 (UTC)Reply

Global lock for spambots

Status:    In progress

Spambot, probably a bunch more. Vermont (talk) 01:40, 21 August 2019 (UTC)Reply

Global lock for socks of George reeves

Status:    In progress

Lock allGlobal block all:

Long-term abuse. -★- PlyrStar93 Message me. 03:33, 21 August 2019 (UTC)Reply

See also