Steward requests/Global: Difference between revisions

From Meta, a Wikimedia project coordination wiki
Content deleted Content added
+request
Line 104: Line 104:
{{status}}
{{status}}
*{{MultiLock|RickyX5113|JonasOlivo2|ReinaldoFrier}} - triggered by filter 1 @it.wb--<span style="font-family: cursive, serif;">[[User talk:Wim b|Wim b]]</span> 14:48, 22 November 2018 (UTC)
*{{MultiLock|RickyX5113|JonasOlivo2|ReinaldoFrier}} - triggered by filter 1 @it.wb--<span style="font-family: cursive, serif;">[[User talk:Wim b|Wim b]]</span> 14:48, 22 November 2018 (UTC)

=== Global lock for compromised accounts ===
{{status}} <!-- do not remove this template -->
{{MultiLock|Mr-Thomas|FritzSolms|Sporkot|GrantyO|SeveredSpirit|Laghlagh|Testcompte8o|Deruike|Bossmaine|UFC head|Fadedbasket|Jewofunk}}
This is a fairly complete list of unlocked accounts which have been compromised by the same vandal on enwiki. The other accounts already locked are Jchahin13, Asenine, Nyllo, Radomil, and Esanchez7587. [[User:Zzuuzz|zzuuzz]] <sup>[[User_talk:Zzuuzz|(talk)]]</sup> 20:27, 22 November 2018 (UTC)


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

Revision as of 20:27, 22 November 2018

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 block for 178.197.227.105

Status:    In progress

Edgar von Webern does not agree with his block on de.wp and is molesting my talk page on various language wikipedias. --Harald Krichel (talk) 10:52, 8 November 2018 (UTC)Reply

This one is solved, there are two more ([see https://fi.wikipedia.org/w/index.php?title=Keskustelu_k%C3%A4ytt%C3%A4j%C3%A4st%C3%A4:Seewolf&action=history]), both pretty stable:

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 2606:6000:50CA:E00:0:0:0:0/64

Status:    In progress

Cross-wiki abuse --XXBlackburnXx (talk) 22:25, 20 November 2018 (UTC)Reply

Global block for 2607:FB90:0:0:0:0:0:0/32

Status:    Done

DeltaQuad has this blocked on en-wiki for the dog and rapper vandal, but their blabbering on WikiSource is probably from WhenHotlineBrings or someone like that. If one of you could block this range, and revdel the childish nonsense on that talk page of mine (and semi-protect it...), that would be great. And if you could semi-protect all those Drmies talk pages on all those projects where I never work, which are just an invitation for this sad person to vandalize, that'd be even greater. Thanks! Drmies (talk) 15:04, 22 November 2018 (UTC)Reply

It's been going on for months xwiki with this range, see the gblock log. Vermont (talk) 15:29, 22 November 2018 (UTC)Reply
Done by Teles for 1 month. Vermont (talk) 16:36, 22 November 2018 (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 Satoshi Kondo/WorldCreaterFighter

Status:    In progress

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

Global lock/unlock for Xayahrainie43

Status:    In progress

Crosswiki abuse, indef enwiki due to CIR issue as well as block evade using IP, indef zhwiki due to DE --Cohaf (talk) 18:05, 12 November 2018 (UTC)Reply

Note, there was a change in behavior which implies that he is not a bot. However, the actions carried out have implied that he is intentionally pushing anti-policy article changes and those changes are detrimental to the quality of articles (including unnecessary changes to navbox and other related issues). There is a high possibility for this kind of vandalism to occur at other projects (en.wikiversity / zh.wikiversity) due to his actions. Note to others: this is a Taiwan IP and his behavior looks like a long term abuser at the zhwiki though not confirmed.--1233 | Questions?| This message is left by him at 18:37, 12 November 2018 (UTC)Reply
Update: after comparing the IP addresses Xayahrainie43 used to evade blocking at enwiki with the IP ranges that LTA using at zhwiki and behavior comparison at zhwiki, we now consider that the link between Xayahrainie43 and that LTA to be around Likely Likely, thanks.--無聊龍 (talk) 04:45, 13 November 2018 (UTC)Reply

Global lock for cross-wiki LTA Jessechi sock

Status:    In progress

--MCC214Talk with me#Contributions with me 10:43, 19 November 2018 (UTC)Reply

Global lock for CentralAm Megatrends

Status:    In progress

LTA, My Royal Young.--SkyGazer 512 (talk) 00:25, 22 November 2018 (UTC)Reply

Global lock

Status:    In progress

LTA, see also en:Wikipedia:Sockpuppet investigations/WhenDatHotlineBling. --IanDBeacon (talk) 02:11, 22 November 2018 (UTC)Reply

Also name hidden (talk • contribs • block • xwiki-contribs • xwiki-date (alt) • CA • ST • lwcheckuser). Nathan2055 (talk) 06:02, 22 November 2018 (UTC)Reply

Global lock for 2 spambots

Status:    In progress

Global lock for Cmdmfmamvam

Status:    In progress

Cross-wiki abuse. Vandalism / non-sense insertion into pages. -★- PlyrStar93 Message me. 03:26, 22 November 2018 (UTC)Reply

Global lock for 3 spambots

Status:    In progress

Global lock for compromised accounts

Status:    In progress

Lock all:

This is a fairly complete list of unlocked accounts which have been compromised by the same vandal on enwiki. The other accounts already locked are Jchahin13, Asenine, Nyllo, Radomil, and Esanchez7587. zzuuzz (talk) 20:27, 22 November 2018 (UTC)Reply

See also