Jump to content

Steward requests/Global: Difference between revisions

From Meta, a Wikimedia project coordination wiki
Content deleted Content added
m Marking one request as done - with SRG.js
Reporting Japanese zan (TwinkleGlobal)
Line 137: Line 137:
*{{LockHide|1=Diu Ne Lo mo}}
*{{LockHide|1=Diu Ne Lo mo}}
Cross-wiki abuse. Abusive username. [[user:Manchiu|Manchiu]] [[user talk:manchiu|(talk)]] 02:57, 15 April 2024 (UTC)
Cross-wiki abuse. Abusive username. [[user:Manchiu|Manchiu]] [[user talk:manchiu|(talk)]] 02:57, 15 April 2024 (UTC)

=== Global lock for Japanese zan ===
{{Status}}
*{{LockHide|1=Japanese zan}}
Long-term abuse. Cross-wiki abuse. [[User:20041027 tatsu|''20041027'' 𝓽𝓪𝓽𝓼𝓾]]([[User talk:20041027 tatsu|talk]]) 03:24, 15 April 2024 (UTC)


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

Revision as of 03:24, 15 April 2024

Skip to top
Skip to bottom
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 unblock for 103.60.175.0/24

Status:    On hold

Does not appear to be a webhost or open proxy, to both me and Dane. —‍Mdaniels5757 (talk • contribs) 17:40, 3 April 2024 (UTC)Reply

I've come to the same conclusion. Done and @Elton: FYI. -- Amanda (she/her) 04:08, 4 April 2024 (UTC)Reply
@AmandaNP: I've removed the local Meta-Wiki block accordingly. I'm now curious to what caused this false positive which lead to blocks still active on five other projects, specially enwiki. I personally don't think 103.60.175.0/24 is OP or webhost (after further review), but was led to error by stalktoy results. I would like an explanation from one of you, if you don't mind, to ensure mistakes like this don't happen again in the future. PS: I've set the request 'on hold' only to give you time to reply before this is archived. Thank you in advance. — Elton (talk) 04:39, 4 April 2024 (UTC)Reply
Honestly, I don't know where the evidence first came from to make the block which renders me unable to comment. I mean I could be wrong, but if we are going to get any clarity on this, @ST47 and Dane: would be the two to ping, as they are on a higher skill level than I am with this. I have a feeling though that some website/script that detects proxies may be the cause. -- Amanda (she/her) 04:46, 4 April 2024 (UTC)Reply

Global unblock for Japanese IPs blocked by EPIC after April 10th

Status:    On hold

Japanese IPs blocked by EPIC after April 10th using methods other than "Open proxy"

It includes Nippon Telegraph and Telephone(NTT), KDDI(include Wi2), and SoftBank, which are major Japanese companies that deal with everything from mobile to building communications, and the lock range is too wide, so it would be better to narrow it down. . Also, I don't think it's necessary to block the Japanese version, major other language versions (such as English), and multilingual projects. --Vcvfou698069 (talk) 22:59, 12 April 2024 (UTC)Reply

May I ask why? Yes, some of these ranges are quite large, but before doing the blocks I've already checked for potential collateral damage (which I take into account before placing global blocks). These are already configured in a way that allows logged-in users to edit and they don't seem to have caused any collateral damage as far as I have been seeing. Should that be the case, individual wikis, such as jawiki, can still choose to unblock the ranges locally. I will not decline this, but I would want to see either some valid reasons to unblock or some indication that this affects a large amount of users other than a third-party appeal. EPIC (talk) 00:26, 13 April 2024 (UTC)Reply

Looking at the "xwiki-contribs" for each of these IP ranges, I believe they are IP ranges where one or more meaningful edits have been made even when not logged in. --Vcvfou698069 (talk) 01:12, 13 April 2024 (UTC)Reply

All I can say is; The blocks were a necessary consequence of blocking accounts. Like mentioned, these are configured in such a way that still lets logged-in users edit to avoid causing collateral damage. If the blocks cause too much collateral damage, it's not much harder for us than that we can unblock IPs or ranges when needed. Unless you or someone else is currently affected, there isn't much else to do for now. EPIC (talk) 08:24, 13 April 2024 (UTC)Reply

Global block for 98.159.226.157

Status:    Done

Open proxy, https://ipcheck.toolforge.org/index.php?ip=98.159.226.157. MathXplore (talk) 01:08, 15 April 2024 (UTC)Reply

Robot clerk note: Done by AmandaNP. MajavahBot (talk) 01:25, 15 April 2024 (UTC)Reply

Global block for 49.104.49.127

Status:    In progress

Long-term abuse. w:ja:LTA:SELFREVERT. Mtarch11 (talk) 03:00, 15 April 2024 (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 Wurstwicht2425

Status:    Done

Impersonation. Seawolf35 (talk) 19:25, 14 April 2024 (UTC)Reply

Done EPIC (talk) 19:32, 14 April 2024 (UTC)Reply

Global lock for Slotgopayx

Status:    Done

Spam-only account: spambot. Casino spambot. Seawolf35 (talk) 21:04, 14 April 2024 (UTC)Reply

Done EPIC (talk) 21:05, 14 April 2024 (UTC)Reply

Global lock for DundeeGayCruiser

Status:    Done

Long-term abuse. User:Dopenguins. Seawolf35 (talk) 21:08, 14 April 2024 (UTC)Reply

Done EPIC (talk) 21:09, 14 April 2024 (UTC)Reply

Global lock for Edu Lude

Status:    Done

Long-term abuse. Cross-wiki abuse. Risto hot sir. A09 (talk) 21:17, 14 April 2024 (UTC)Reply

Done EPIC (talk) 21:20, 14 April 2024 (UTC)Reply

Global lock for Flex Liberia socks

Status:    Not done

Sockpuppets found in enwiki sockpuppet investigation, see w:en:Wikipedia:Sockpuppet investigations/Flex Liberia. Seawolf35 (talk) 21:23, 14 April 2024 (UTC)Reply

Hi, please leave enwiki SPI clerking to CUs and SPI clerks. Both we and enwiki functionaries have had issues with this before, and functionaries at enwiki are generally not very happy with non-clerks/non-CUs clerking SPI and have repeatedly been asking them not to do so when that has happened. But if you would like to help out then please feel free to apply at the SPI clerk noticeboard, thank you. EPIC (talk) 21:44, 14 April 2024 (UTC)Reply

Global lock for XXnonesenseXx socks

Status:    In progress

w:en:WP:LTA/GRP. —Justin (koavf)TCM 23:39, 14 April 2024 (UTC)Reply

Global locks for an LTA

Status:    In progress

Long-term abuse. ClumsyOwlet (talk) 00:53, 15 April 2024 (UTC)Reply

Global lock for SusanneCorner79

Status:    In progress

Spam-only account: spambot. Seawolf35 (talk) 01:02, 15 April 2024 (UTC)Reply

Global lock for SpencerVirtue08

Status:    In progress

User page is the same as SusanneCorner79 (above), spambot? ClumsyOwlet (talk) 01:18, 15 April 2024 (UTC)Reply

Global lock

Status:    Done

LTA (may have been done but not seeing it) Thanks, and be well! - PDLTalk to me!Please don't eat da 🐑! 01:58, 15 April 2024 (UTC)Reply

Done -- Amanda (she/her) 03:08, 15 April 2024 (UTC)Reply

Global lock for Tdtc04g

Status:    In progress

Spam / spambot. Leonidlednev (talk) 02:17, 15 April 2024 (UTC)Reply

Global lock for BMX is on wikibreak right now!

Status:    In progress

Long-term abuse. Codename Noreste 🤔 𝙇𝙖 𝙎𝙪𝙢𝙖 02:34, 15 April 2024 (UTC)Reply

I thought so too, but then I saw this log entry?? ClumsyOwlet (talk) 03:03, 15 April 2024 (UTC)Reply

Global lock for Diu Ne Lo mo

Status:    In progress

Cross-wiki abuse. Abusive username. Manchiu (talk) 02:57, 15 April 2024 (UTC)Reply

Global lock for Japanese zan

Status:    In progress

Long-term abuse. Cross-wiki abuse. 20041027 𝓽𝓪𝓽𝓼𝓾talk03:24, 15 April 2024 (UTC)Reply

See also