Steward requests/Global

(Redirected from SRG)
Latest comment: just now by XXBlackburnXx in topic Requests for global (un)lock and (un)hiding
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; 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 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 217.165.68.97

Status:    In progress

Proxy. Thanks in advance! -- Jeff G. ツ (please ping or talk to me) 13:52, 13 April 2024 (UTC)Reply

Part of 217.165.0.0/16 xwiki-contribsSTIP infoWHOISrobtexgblockglistabuselogbullseye blocked as proxy on viwiki. -- Jeff G. ツ (please ping or talk to me) 13:56, 13 April 2024 (UTC)Reply
Probably a false positive block, none of the proxychecker I use give positive for proxy, so this is likely not or no longer an open proxy. EPIC (talk) 13:57, 13 April 2024 (UTC)Reply

Global block for 164.90.222.51

Status:    Done

Open proxy. XXBlackburnXx (talk) 23:49, 13 April 2024 (UTC)Reply

  Done EPIC (talk) 23:51, 13 April 2024 (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 unlock for users locked by EPIC after April 10th

Status:    Not done

Among the users (Japanese and alphanumeric notation) that EPIC locked for simple "Long-term abuse" after April 10th, the following are excluded. User that are locally blocked, have a edit article history of vandalism, include a jawp administrator name, or have a Japanese sex act name.
The reason for not listing them is because there are too many, and to prevent disclosure of the list of organization members and the relationship between real names and handle names.
The scope of locking is so wide that it covers all wikis, so I don't think it's necessary to lock the Japanese version, major other language versions (such as English), and multilingual projects.--Vcvfou698069 (talk) 23:34, 12 April 2024 (UTC)Reply

@Vcvfou698069 You do realize that stewards have access to info that you don't. The locks are most likely preventing abuse, "organization members", what? Seawolf35 (talk) 23:47, 12 April 2024 (UTC)Reply
  Not done, there are reasons why we issue out locks, even those which are not for users that "have an edit article history of vandalism, include a jawp administrator name, or have a Japanese sex act name". You were already questioned through email and if you have any questions, feel free to email us at stewards wikimedia.org. Until then, no accounts will be unlocked. EPIC (talk) 23:55, 12 April 2024 (UTC)Reply
Many locked lists of people's names also appear to me to be disclosing a list of private members of some organization (such as company employees).--Vcvfou698069 (talk) 23:55, 12 April 2024 (UTC)Reply
All I can say is that these accounts were locked as part of a massive LTA farm from an LTA who had been creating a massive amount of accounts on non-Japanese small wikis, particularly Wiktionaries, so the usernames weren't anything particularly meaningful and mostly seem to consist of different random names. In other words, no innocent users from jawiki or Japanese projects were affected as far as I'm aware, because I'm quite sure that I excluded those. I can unlock if highly needed, but you need to provide a valid reason for us to do so. EPIC (talk) 00:38, 13 April 2024 (UTC)Reply
Someone was trying to dilute the relationships between names by distributing the private names of company employees or other organization members across multiple wikis, but someone else made them visible. looks like it failed --Vcvfou698069 (talk) 01:04, 13 April 2024 (UTC)Reply
So why should we unlock, given that they are LTA accounts? If the problem is some of the usernames, unlocking them will not hide them or get rid of them, but rather just spread them further. EPIC (talk) 05:49, 13 April 2024 (UTC)Reply
@Vcvfou698069: If the problem seemed to have been that I accidentally locked two of your alternative accounts, then I apologize and I have now unlocked both of them. Was that the main reason why you made this request? EPIC (talk) 05:56, 13 April 2024 (UTC)Reply
That's what I think after looking at the area around the log that got caught up in the block, so I don't think the problem has been solved yet.--Vcvfou698069 (talk) 06:18, 13 April 2024 (UTC)Reply
What problem? If there are any further innocent accounts that accidentally caught up, they can send a lock appeal to us and I would be happy to unlock if so. Other than that there isn't much left to do here given that the locks were made on LTA accounts. EPIC (talk) 08:02, 13 April 2024 (UTC)Reply
  Closed as not actionable, since you did not specify which account(s) you want to request unlock for. Please note that you can start another request, either here or privately. If you wish, you may appeal this decision at Stewards' noticeboard (please @ping prior participants above) or privately contacting stewards (you can email us directly at stewards wikimedia org). Thank you for your understanding. — Elton (talk) 16:27, 13 April 2024 (UTC)Reply

Global lock/unlock for Gordito1869

Status:    In progress

Long term abuse with multiple blocks on Commons and dewiki. See especially the comments on the deleted talk page after the block c:User talk:Gordito1869. I am not sure if this is fine for a global lock or needs to go through the global ban process. --GPSLeo (talk) 13:43, 13 April 2024 (UTC)Reply

I'm not sure about a global lock either, this feels a bit weak to me. This user has been editing on two main wikis, both of which they have local blocks on, which might be enough given that they are not actively editing or being abusive on other wikis and the blocks on their two main wikis seem to have been preventative enough. EPIC (talk) 13:47, 13 April 2024 (UTC)Reply

Global lock for Goodcleaner

Status:    Not done

Link spammer. Seawolf35 (talk) 16:22, 13 April 2024 (UTC)Reply

  Not done - not xwiki, enwiki can handle this. – Ajraddatz (talk) 16:25, 13 April 2024 (UTC)Reply

Global lock for Eoffice eklavya

Status:    Done

Cross wiki spam. Seawolf35 (talk) 17:41, 13 April 2024 (UTC)Reply

  Done EPIC (talk) 17:43, 13 April 2024 (UTC)Reply

Global lock for Adinio112

Status:    Done

Cross-wiki abuse. Seawolf35 (talk) 17:46, 13 April 2024 (UTC)Reply

  DoneAjraddatz (talk) 17:50, 13 April 2024 (UTC)Reply

Global lock for NicoleW20Milhoess

Status:    Done

Long-term abuse related with Irisvalverde1. Francisco (talk) 17:50, 13 April 2024 (UTC)Reply

  Done EPIC (talk) 17:51, 13 April 2024 (UTC)Reply

Global lock for Agnieszka1235

Status:    Done

Lock all:

Long-term abuse. Cross-wiki abuse. Yesterday on Simple, IP 31.0.41.56 caught my eye randomly changing dates to a song[1], after I had reverted them a few times on various articles Agnieszka1235 appears and starts making the same date-changing edits[2], (I had checked the EN articles prior to reverting and the prev versions matched those at EN)

I had pinged Binksternet whom I remembered had dealings with a date changing vandal on EN years ago and they had confirmed this was them again[3],

They've also been using 31.0.42.75 this morning and 31.0.41.56 this afternoon and have been active on different projects[4], Many thanks, Kind Regards,. –Davey2010Talk 18:03, 13 April 2024 (UTC)Reply

  Done, given that multiple wikis have blocked the 31.0.0.0/17 I went ahead and blocked that. EPIC (talk) 18:09, 13 April 2024 (UTC)Reply
Fantastic many thanks for your swift help it's greatly appreciated, Thanks, Warm Regards, –Davey2010Talk 20:33, 13 April 2024 (UTC)Reply

Global lock for 사다쯔카라카라카이쟈쿠라쿠시푸

Status:    Done

Long-term abuse. LTA sock of 보민개, uploading file for kowiki vandalism. LR0725 ( Talk / Contribs ) 18:15, 13 April 2024 (UTC)Reply

  Done EPIC (talk) 18:26, 13 April 2024 (UTC)Reply

Global lock for Julie55345390878

Status:    Done

Spam-only account: spambot. Seawolf35 (talk) 20:47, 13 April 2024 (UTC)Reply

  Done EPIC (talk) 20:53, 13 April 2024 (UTC)Reply

Global lock for TinaLangwell

Status:    Done

Spam / spambot. 𝐖𝐢𝐤𝐢𝐁𝐚𝐲𝐞𝐫 👤💬 23:16, 13 April 2024 (UTC)Reply

  Done EPIC (talk) 23:42, 13 April 2024 (UTC)Reply

Global lock for DefaultGoogleWebpage201204321

Status:    In progress

Long-term abuse. XXBlackburnXx (talk) 00:06, 14 April 2024 (UTC)Reply

See also