Steward requests/Global: Difference between revisions

From Meta, a Wikimedia project coordination wiki
Content deleted Content added
Reporting 39.122.251.170 and 1 other IP (TwinkleGlobal)
Line 197: Line 197:
:Today's spambots. --[[User:Sotiale|Sotiale]] ([[User talk:Sotiale|talk]]) 12:59, 2 January 2020 (UTC)
:Today's spambots. --[[User:Sotiale|Sotiale]] ([[User talk:Sotiale|talk]]) 12:59, 2 January 2020 (UTC)
::{{done}}, plus sleepers, thanks - [[User:QuiteUnusual|QuiteUnusual]] ([[User talk:QuiteUnusual|talk]]) 14:24, 2 January 2020 (UTC)
::{{done}}, plus sleepers, thanks - [[User:QuiteUnusual|QuiteUnusual]] ([[User talk:QuiteUnusual|talk]]) 14:24, 2 January 2020 (UTC)

=== Global lock for xwiki spammer/hoaxster ===
{{status}}
*{{MultiLock|Daniels014|Daniels041|Delegiwa440|Philip Adrian|Philip Opeyemi|Preciousd041|}}
:These accounts are repeatedly spamming a potential hoax (death dates) to their spammy obit blog. I will also be requesting blacklisting. [[User:Praxidicae|Praxidicae]] ([[User talk:Praxidicae|talk]]) 15:47, 2 January 2020 (UTC)


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

Revision as of 15:48, 2 January 2020

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 95.233.239.163

Status:    In progress
Cross wiki persistent addition of unsourced content. --IanDBeacon (talk) 14:38, 19 December 2019 (UTC)[reply]
This is a domestically accessed IP address of a person editing Pokemon and cartoon articles. I would suggest that they will just rotate to another IP address if blocked. One would think that communities would be managing this sort of matter and educating them rather than placing global blocks. @IanDBeacon: What do you think? It doesn't seem to be stewards territory at this time.  — billinghurst sDrewth 06:58, 24 December 2019 (UTC)[reply]

Global block for 2402:800:61A5:C469::/64

Status:    In progress

Crosswiki vandalism, most recently from 2402:800:61a5:c469:e3:e011:9ae7:5ce5 (2402:800:61a5:c469:e3:e011:9ae7:5ce5 xwiki-contribsxwiki-date (alt)STIP infoWHOISrobtexgblockglistabuselogbullseye).   — Jeff G. ツ please ping or talk to me 14:03, 22 December 2019 (UTC)[reply]

These are large wikis and see able to manage occasional spam. 20 edits from Vietnamese telecom, dynamic IP over the course of a two weeks. Suggest that local wikis can manage through normal administrators channels.  — billinghurst sDrewth 09:49, 24 December 2019 (UTC)[reply]
@Billinghurst: Those links don't show the full extent, but these for 2402:800:61A5::/48 xwiki-contribsSTIP infoWHOISrobtexgblockglistabuselogbullseye from Commons, English Wikipedia, Wikidata, and here on Meta do, and they are vandalism only. I reported them to the individual wikis' Admins per your suggestion. I wish we had publicly-accessible tools that allowed analysis of cross-wiki abuse by IPv6 netblocks.   — Jeff G. ツ please ping or talk to me 16:26, 25 December 2019 (UTC)[reply]
@Jeff G.: Geez, I could be happy with the ability to see deleted contributions for a range.  — billinghurst sDrewth 10:13, 26 December 2019 (UTC)[reply]
@Billinghurst: GS and GR could benefit from that, on all wikis.   — Jeff G. ツ please ping or talk to me 16:22, 26 December 2019 (UTC)[reply]

Global block for 91.126.150.251

Status:    In progress

Cross-wiki spam. --Thibaut (talk) 17:43, 27 December 2019 (UTC)[reply]

Comment Comment looks like a static IP with about a week's worth of editing, at fr/es/caWPs. Not sure whether it is better to leave it with wikis or be global. I also flagged the IP edits with caWP where the edits have been primarily.  — billinghurst sDrewth 23:16, 30 December 2019 (UTC)[reply]

Global block for 85.93.60.86

Status:    In progress

Cross-wiki vandal, same as 85.93.49.238 Zaxxon0 (talk) 19:10, 27 December 2019 (UTC)[reply]

One days activity (8 hours, 4 wikis, 10 edits, just random vandalism), though a previous vandal edit months ago. Has the hallmarks of an open proxy, though low abuse rate. <shrug>  — billinghurst sDrewth 23:23, 30 December 2019 (UTC)[reply]

Global block for 2600:1:9527:6162:9055:6E2A:C91E:A108

Status:    In progress
Long-term abuse. Cross-wiki abuse. Part of an IP range, blocked on en-Wiki which may not be blocked globally due to risk of damage. --IanDBeacon (talk) 00:39, 29 December 2019 (UTC)[reply]
@IanDBeacon: No abuse showing, not certain what is the value of blocking this single IP. What abuse would blocking this IP prevent and when?

IP is a part of a /29 of Sprintlink, Drmies has blocked a /33 for 2 years, so if there is a reason for a block, a range block would seem more appropriate than a single IP. A review of edits in the /33 shows a high amount of abuse and xwiki, though some evidence of reasonable edits in the past few months. I can see value in replicating the /33 block at enWP.  — billinghurst sDrewth 23:43, 30 December 2019 (UTC)[reply]

Global block for 36.229.208.35

Status:    In progress
Cross-wiki abuse. --Xiplus (talk) 05:05, 30 December 2019 (UTC)[reply]
Meant to be a dynamic IP at hinet, though has indications of a proxy. Low level of abuse, though indicators of an LTA utilising. Suggest block it for a month, and see if it goes away.  — billinghurst sDrewth 23:50, 30 December 2019 (UTC)[reply]

Global block for open proxy IP

Status:    In progress
Open proxy. -- Willy1018(talk) 02:54, 2 January 2020 (UTC)[reply]

Global block for 197.38.179.192

Status:    In progress

Global vandalism. One day should be sufficient. Allready blocked by me on de: --Drahreg01 (talk) 11:36, 2 January 2020 (UTC)[reply]

Global block for 203.130.21.234

Status:    In progress
Open proxy. -- Willy1018(talk) 11:36, 2 January 2020 (UTC)[reply]

Global block for open proxies

Status:    In progress
Open proxies, used abusively on Persian Wikipedia. --Ahmadtalk 15:16, 2 January 2020 (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 sock

Status:    In progress

Sock of Sidowpknbkhihj. --Soratako🐙 (talk) 13:55, 30 December 2019 (UTC)[reply]

Confirmation in local. jawiki --Soratako🐙 (talk) 03:18, 31 December 2019 (UTC)[reply]

Global lock for LTA socks

Status:    In progress

Lock all:

Confirmed sockpuppets of ArmanAfifeh (مهیار مهرنیا). See the enwiki's block log. Ahmadtalk 20:47, 30 December 2019 (UTC)[reply]

Global lock for Rameshmurmu953

Status:    In progress

An obvious sock of Special:CentralAuth/Ramesmurmu214, Special:CentralAuth/Rameshmurmu214, Special:CentralAuth/Rameshmurmu899, and Special:CentralAuth/Rameshmurmu257 (the previous globally-locked instance) - continuing disruption on sat-Wiki, Wikidata, and or-Wiki. GermanJoe (talk) 08:03, 31 December 2019 (UTC)[reply]

Global lock

Status:    In progress
Long-term abuse. --~riley (talk) 02:23, 1 January 2020 (UTC)[reply]

Global lock for Feudali is the vanadal of the decade!

Status:    In progress
Long-term abuse. --~riley (talk) 02:23, 1 January 2020 (UTC)[reply]

Global lock for First Vanadal of the 2020s

Status:    In progress
Long-term abuse. --~riley (talk) 02:46, 1 January 2020 (UTC)[reply]

Global lock for In G0D, DrMlES, TBaloney and Praxydicae, I TRUST

Status:    In progress
Long-term abuse. --~riley (talk) 03:18, 1 January 2020 (UTC)[reply]

Global lock for TheFriendlyArturo

Status:    In progress
Long-term abuse. --~riley (talk) 03:35, 1 January 2020 (UTC)[reply]

Global lock

Status:    In progress
Long-term abuse. --~riley (talk) 03:52, 1 January 2020 (UTC)[reply]

Global lock for 24 spambot accounts in de.wikiquote.org

Status:    In progress

Lock all:

Spambots in de.wikiquote.org --P134toP4913 (talk) 06:23, 1 January 2020 (UTC)[reply]

Global lock for NancyAce

Status:    In progress
Long-term abuse. --Masum Reza📞 08:09, 1 January 2020 (UTC)[reply]

Global lock for spambots

Status:    In progress

Lock all:

--𐐎ℹ𝕜ⅈ𝕭𝒂𝕪ⅇ𝕣 👤💬 10:23, 1 January 2020 (UTC)[reply]

Global lock for spambots

Status:    In progress
Today's spambots. --Sotiale (talk) 12:57, 1 January 2020 (UTC)[reply]

Global lock for MarquisWrenfords

Status:    In progress
Spambot(s). --Minorax (talk) 16:23, 1 January 2020 (UTC)[reply]

Global lock for CE1989001 and CE1989001abcd

Status:    In progress

Lock all:

Long-term abuse: Carlos Eduardo1989. --Francisco (talk) 17:13, 1 January 2020 (UTC)[reply]

Global lock for Bishal Khan sock

Status:    In progress
Long-term abuse. This guy just canvassed me on my enwiki of a DR on Commons. All other newly created accounts who participated in that discussion are locked with the reason "LTA: বিশাল খান". Looks like a obvious sock to me. --Masum Reza📞 21:36, 1 January 2020 (UTC)[reply]

Global lock for Yash gawli socks

Status:    In progress
Long-term abuse. Per w:en:Wikipedia:Sockpuppet_investigations/Yash_gawli/Archive. --Masum Reza📞 00:06, 2 January 2020 (UTC)[reply]

Global lock for spammers

Status:    In progress

Lock all:

Crosswiki spam. Up until Markbeck98 are all cross-wiki spam, the others are other CU confirmed accounts to The siner. Please see the enwiki Sockpuppet investigation. --TheSandDoctor Talk 04:40, 2 January 2020 (UTC)[reply]

Global lock for Wikiselim12

Status:    In progress

CU-confirmed sock of Selim Shaikh, a crosswiki sockmaster. See enwiki SPI. --Mz7 (talk) 05:46, 2 January 2020 (UTC)[reply]

Global lock for INTV (Baru)

Status:    In progress
Long-term abuse. --— Tulsi Bhagat (contribs | talk) 08:25, 2 January 2020 (UTC)[reply]

Global lock for sock

Status:    In progress

Sock of デーモン閣下. --Soratako🐙 (talk) 09:58, 2 January 2020 (UTC)[reply]

Global lock for Goldin Finance 117

Status:    Done
Cross-wiki abuse. --94rain Talk 11:55, 2 January 2020 (UTC)[reply]
Done, by Tegel. QuiteUnusual (talk) 15:12, 2 January 2020 (UTC)[reply]

Global lock for MediaBaruAceh

Status:    In progress
Long-term abuse. --— Tulsi Bhagat (contribs | talk) 12:44, 2 January 2020 (UTC)[reply]

Global lock for spambots

Status:    Done
Today's spambots. --Sotiale (talk) 12:59, 2 January 2020 (UTC)[reply]
Done, plus sleepers, thanks - QuiteUnusual (talk) 14:24, 2 January 2020 (UTC)[reply]

Global lock for xwiki spammer/hoaxster

Status:    In progress
These accounts are repeatedly spamming a potential hoax (death dates) to their spammy obit blog. I will also be requesting blacklisting. Praxidicae (talk) 15:47, 2 January 2020 (UTC)[reply]

See also