Jump to content

Steward requests/Global: Difference between revisions

From Meta, a Wikimedia project coordination wiki
Content deleted Content added
JarBot (talk | contribs)
m Bot: archiving 2 request to Steward requests/Global/2019-05
Line 120: Line 120:
</blockquote>
</blockquote>


In this case, a train service of Deutsche Bank, it makes little sense to block anything for longer than few hours, or even less. Why this block has been placed for so long?
In this case, a train service of Deutsche Bahn (German railway service), it makes little sense to block anything for longer than few hours, or even less. Why this block has been placed for so long?


It is generally not required to log in to the wiki to fix something (even small typo), so I the explanation that I am not affected by this block is unfortunately not enough. I am posting this here again because I do not understand why this request has been closed this way without any better justification than this.
It is generally not required to log in to the wiki to fix something (even small typo), so I the explanation that I am not affected by this block is unfortunately not enough. I am posting this here again because I do not understand why this request has been closed this way without any better justification than this.

Revision as of 20:01, 2 May 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 or accounts; 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 .
Global blocks don't affect Meta-Wiki, so if your IP address or account is blocked, you can still appeal here. IP addresses or accounts 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 or account. Saying an IP or account 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) or accounts 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 or account, if any.

To make a request for the address(es) or account(s) to be blocked or unblocked

Copy the template below to the bottom of this section and explain why the address(es) or account(s) should be blocked/unblocked.
=== Global block/unblock for [[Special:Contributions/Some IP address or account|Some IP address or account]] ===
{{Status}} <!-- Do not remove this template -->
* {{Luxotool|IP address/username}}
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 Bambifan101

Status:    In progress

Same user, different IP. --Zaxxon0 (talk) 19:30, 2 May 2019 (UTC)Reply

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

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 濫用過濾器

Status:    On hold

This username is the Chinese translation of "Abuse filter" but not the exact abuse filter that performs block and therefore was blocked indef on zhwp. Request for global lock to prevent the account from editing on other Chinese projects to pretend to have adminstrative authority. --94rain Talk 13:08, 24 April 2019 (UTC)Reply

Actually no, it will be only available to re-create those with "titleblacklist-override", not everyone. — regards, Revi 10:14, 28 April 2019 (UTC)Reply

Global lock for socks of Pakistanpedia

Status:    In progress

Lock all:

Uploads copyvio from single-purpose accounts, usually to be injected to Wikipedia using IPs. See c:Commons:Administrators'_noticeboard/Blocks_and_protections #Sockpuppets_of_Pakistanpedia and c:Category:Sockpuppets of Pakistanpedia for details (note: I deliberately omitted several accounts from the category, feeling that the case was not strong enough). Incnis Mrsi (talk) 13:57, 27 April 2019 (UTC)Reply

Global lock for LTA socks

Status:    In progress

Lock all:

Long-term abuse. -★- PlyrStar93 Message me. 00:47, 1 May 2019 (UTC)Reply

The first account is a sock of the Fuerdai LTA (BMX on WheeIs). The other accounts are all socks of the LTA Arturo Gustavo. The older Arturo Gustavo accounts are listed first (after the Fuerdai vandal sock), but these need to be Locked as well because this LTA is logging back in to his old accounts (for CU reference, the newer accounts begin with "Volunteer editor Gustavo"). Please also run a sleeper check and Globally Block the underlying IPs (especially the ones listed above), because this LTA is known for cross-wiki trolling. LightandDark2000 🌀 (talk) 02:45, 1 May 2019 (UTC)Reply

Global lock for various accounts

Status:    In progress

Lock all:

Cross-wiki abuse. -★- PlyrStar93 Message me. 03:33, 1 May 2019 (UTC)Reply

Added some more. These are spamming cross-wiki. LightandDark2000 🌀 (talk) 11:27, 1 May 2019 (UTC)Reply

Global lock for Stmarksmissionary and socks

Status:    In progress

Lock all:

Stmarksmissionary and socks sure do have a habit of being blocked on commons and enwiki for sockpuppetry. Based on this and the history of abuse dating back to 2017, I am requesting a lock for Stmarksmissionary and all socks. Please see the enwiki Sockpuppet Investigation and its archives. --TheSandDoctor Talk 07:24, 1 May 2019 (UTC)Reply

Global lock for escoperloit socks

Status:    In progress

Lock all:

Global lock for cross-wiki abuse and LTA Nipponese Dog Calvero (KAGE) sock

Status:    Done

Lock all:

Sock of long-term abuse and cross-wiki abuse Nipponese Dog Calvero[1](KAGE (影武者))[2].--MCC214#ex umbra in solem 10:46, 2 May 2019 (UTC)Reply

Done Ruslik (talk) 16:18, 2 May 2019 (UTC)Reply

Global lock for BunnyFourSeven

Status:    In progress

Long-term abuse (Hoggardhigh). -★- PlyrStar93 Message me. 15:35, 2 May 2019 (UTC)Reply

Global lock for TonyStarkCheeseburger

Status:    In progress

Long-term abuse (FilmLover2016). -★- PlyrStar93 Message me. 15:54, 2 May 2019 (UTC)Reply

Global lock for Nsmutte

Status:    In progress

Lock all:

Long-term abuse. -★- PlyrStar93 Message me. 16:02, 2 May 2019 (UTC)Reply

Global lock for sock of Vhacker Vicky kadian

Status:    In progress

CU confirmed sock of the locked User:Vhacker Vicky kadian. See en:Wikipedia:Sockpuppet investigations/Vhacker Vicky kadian. --Cabayi (talk) 16:28, 2 May 2019 (UTC)Reply

Global lock for SILVASAN and socks

Status:    In progress

Lock all:

Cross-wiki abuse, all these are confirmed accounts. -★- PlyrStar93 Message me. 16:30, 2 May 2019 (UTC)Reply

Global lock for BRM Motorsport Garage

Status:    In progress

Sock of global locked LTA Daniel Fatahillah Abrori [3]. See this edit history [4] and notice his other global locked account BRM Motorsport in that history. Sincerely, Taketa (talk) 17:07, 2 May 2019 (UTC)Reply

Global lock/unlock for UnitedAgain4

Status:    In progress

Latest sock to appear of locked LTA Marquis de la Eirron. Please see the enwiki Sockpuppet Investigation and its archives. --TheSandDoctor Talk 18:16, 2 May 2019 (UTC)Reply

Global lock for Caidin-Johnson and socks

Status:    In progress

Lock all:

There are several locked socks in the archives, however, the master and a number of other socks appear to have been missed. Based on this, I am requesting that the master and socks 2018< be globally locked. Carrot Crash - Beach Ball Bash is the latest sock to emerge as of a little over an hour ago. Please see the enwiki Sockpuppet Investigation, its archives, and LTA case. --TheSandDoctor Talk 18:36, 2 May 2019 (UTC)Reply

Global lock for Denver LTA

Status:    In progress

w:en:WP:LTA/DENVER sock. Block the underlying IP address too, and check for/lock sleepers. --IanDBeacon (talk) 19:08, 2 May 2019 (UTC)Reply

Global unblock for 46.183.103.0/27

Status:    In progress

I am asking about this range because there was no justification provided for this global block in the previous unblock request (Steward_requests/Global/2019-04#Global_unblock_for_46.183.103.0/27). I have also checked resources available to checkusers and I cannot see any information about this particular case for "long term abuse" where. Global block policy says:

Global blocks should be placed with the lowest expiry possible, while still remaining effective. All global blocks should have an expiry (none should be indefinite).

In this case, a train service of Deutsche Bahn (German railway service), it makes little sense to block anything for longer than few hours, or even less. Why this block has been placed for so long?

It is generally not required to log in to the wiki to fix something (even small typo), so I the explanation that I am not affected by this block is unfortunately not enough. I am posting this here again because I do not understand why this request has been closed this way without any better justification than this.

 « Saper // talk »  19:59, 2 May 2019 (UTC)Reply

@Ruslik0:@Alaa:@Ajraddatz:@Seewolf:

See also