Steward requests/Global: Difference between revisions

From Meta, a Wikimedia project coordination wiki
< Steward requests
Latest comment: 5 years ago by علاء in topic Requests for global (un)block
Browse history interactively
← Older editNewer edit →
Content deleted Content added
VisualWikitext
Line 322: Line 322:


=== Global block for [[Special:Contributions/124.239.251.20|124.239.251.20]] ===
=== Global block for [[Special:Contributions/124.239.251.20|124.239.251.20]] ===
{{Status}} <!-- Do not remove this template -->
{{Status|done}} <!-- Do not remove this template -->
* {{Luxotool|124.239.251.20}}
* {{Luxotool|124.239.251.20}}
Repeated cross-wiki vandalism after block on 31 March 2018. Removes infoboxes, makes pseudo-valuable modifications to templates: diffs [https://commons.wikimedia.org/w/index.php?title=Беларусь&curid=281554&diff=310415046&oldid=303337937], [https://ru.wikipedia.org/w/index.php?title=%D0%A8%D0%B0%D0%B1%D0%BB%D0%BE%D0%BD:%D0%A2%D0%B0%D0%BD%D0%BA&diff=93828917&oldid=92199206]. --[[User:Jarash|Jarash]] 11:13, 10 July 2018 (UTC)
Repeated cross-wiki vandalism after block on 31 March 2018. Removes infoboxes, makes pseudo-valuable modifications to templates: diffs [https://commons.wikimedia.org/w/index.php?title=Беларусь&curid=281554&diff=310415046&oldid=303337937], [https://ru.wikipedia.org/w/index.php?title=%D0%A8%D0%B0%D0%B1%D0%BB%D0%BE%D0%BD:%D0%A2%D0%B0%D0%BD%D0%BA&diff=93828917&oldid=92199206]. --[[User:Jarash|Jarash]] 11:13, 10 July 2018 (UTC)
:{{done}} for 3 months '''--'''[[User:علاء |<font size="3" face="Script MT Bold" style="color:black;">Alaa</font> ]] [[User_talk:علاء |:)..!]] 21:39, 13 July 2018 (UTC)


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

Revision as of 21:39, 13 July 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

Latest comment: 5 years ago18 comments7 people in discussion
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 85.118.80.0/22

Status:    In progress

Cross-wiki vandalism.   — Jeff G. ツ 09:27, 24 June 2018 (UTC)Reply

Global block for 95.26.124.172

Status:    In progress

Hello.
This is the new IP of the cross-wiki long-term abuser (since at least mid-June 2017) who is described in Steward requests/Global/2018-05#Global block for 95.26.0.0/16.
So far, the new IP has attacked only one project, but usually this abuser is keeping one IP for several days and, when active, is quickly attacking several projects.
Note: IP range blocks would be inefficient (cf. this request) and a global filter would be inefficient (cf. this request).
Regards --NicoScribe (talk) 14:54, 26 June 2018 (UTC)Reply

@NicoScribe: 1 edit since 25 June?! --Alaa :)..! 05:59, 27 June 2018 (UTC)Reply
@علاء: yes, but:
So, I can't report the problem here as soon as I detect a new IP, to slow down this cross-wiki long-term abuser (and avoid a vandalism wave today or tomorrow)? If I have to wait the end of a vandalism wave before reporting the problem here, does it slow down this cross-wiki long-term abuser? --NicoScribe (talk) 08:16, 27 June 2018 (UTC)Reply
@علاء: In the end, 95.26.124.172 has done 8 edits in 4 projects stretched on 3 days. But it is too late now, because:
--NicoScribe (talk) 15:07, 1 July 2018 (UTC) → 20:29, 2 July 2018 (UTC)Reply

@NicoScribe: this section of Steward_requests/Global is about blocks for IP addresses and their ranges, not for sockpuppet investigations or chasing individual baddies in any way. If you see another abusive IP—especially in a completely different network—then just open a new request. Note that 176.59.32.0/19 belongs to Tele2 Russia Groups that is a mobile provider and individual IPs are volatile. Incnis Mrsi (talk) 11:37, 3 July 2018 (UTC)Reply

@Incnis Mrsi: thank you for your comments. I am sorry, my request has been imprecise. In fact, I am just requesting a temporary global block for the current IP of this cross-wiki long-term abuser, which is now 176.59.32.149. If this discussion with علاء were finished, I would have mentioned 176.59.32.149 in a new request (instead of mentioning it in this request).
My understanding of the situation is:
  • The investigation (with duck test) has been done in the first request and in the second request. Since (at least) mid-June 2017, this cross-wiki long-term abuser is using 4 IP ranges (83.220.236.0/22 + 95.25.0.0/15 + 176.14.0.0/16 + 176.59.32.0/19). No account is involved. I am not requesting a sockpuppet investigation.
  • The available solutions are:
    1. globally block the IP ranges → would be inefficient (cf. first request)
    2. create a global filter → would be inefficient (cf. second request)
    3. globally block the vandal one IP at a time (this is the only thing that I am requesting here, just a temporary global block for the current IP: 176.59.32.149)
    4. complain to the ISP, like you have suggested in the first request (but I have never done that).
The IP blocks on the English Wikipedia did not slow down this abuser (due to the cross-wiki abuse). I know that individual IP are volatile but usually this abuser is keeping one IP for several days and, in my knowledge, only two IP have been globally blocked so far ([1] and [2]), so I think that the solution n°3 is still worth a try. Are you (and علاء) saying that the solution n°3 would be inefficient too? --NicoScribe (talk) 16:43, 3 July 2018 (UTC)Reply
95.26.124.172 is a “slow” IP address (some friends of mine used Corbina/Beeline in 2008–11), hence it may be blocked. As for Tele2 Russia, in short, is the abuse intense enough to block a mobile IP address globally? They are usually subject to change in few hours, and if we have a dangerous long-time abuser operating from there, then other measures should be tested (such as mapping his IPs and putting infested ranges under anon-only global block). Incnis Mrsi (talk) 18:33, 3 July 2018 (UTC)Reply

@Incnis Mrsi: I don't know. I've made the following list.

The IP are mainly in the second and fourth IP ranges (but I repeat that IP range blocks have been rejected in the first request: too much collateral damage). --NicoScribe (talk) 15:24, 4 July 2018 (UTC)Reply

Global block for 2601:18C:C901:C820::/64

Status:    In progress

Cross-wiki vandalism.   — Jeff G. ツ 17:15, 1 July 2018 (UTC)Reply

The user appears to have moved on to 66.31.222.166 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye and 2601:18C:C901:C820:990B:ECD2:AAFD:DA24 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye.   — Jeff G. ツ 23:55, 1 July 2018 (UTC)Reply

Global block for 66.31.222.166

Status:    In progress

Jeff G. claims cross-wiki vandalism above. I, Incnis Mrsi, see only vandalism in en.Wikipedia. Incnis Mrsi (talk) 08:43, 2 July 2018 (UTC)Reply

@Incnis Mrsi: This vandal did not edit cross-wiki with this IP address, I never claimed it did. However, the IP edit history of en:Wikipedia talk:WikiProject Hawaii/Outreach/News Bureau/Kavebear is quite convincing.   — Jeff G. ツ 12:04, 5 July 2018 (UTC)Reply

Global block for 195.206.3.188

Status:    Not done

Open proxy located in Brescia, Lombardia Region, Italy (IT). --Web Source Self-Management System (talk) 07:44, 10 July 2018 (UTC)Reply

Not done Does not appear to be an open proxy - TNT 💖 20:32, 13 July 2018 (UTC)Reply

Global block for 124.239.251.20

Status:    Done

Repeated cross-wiki vandalism after block on 31 March 2018. Removes infoboxes, makes pseudo-valuable modifications to templates: diffs [3], [4]. --Jarash 11:13, 10 July 2018 (UTC)Reply

Done for 3 months --Alaa :)..! 21:39, 13 July 2018 (UTC)Reply

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

Latest comment: 5 years ago22 comments15 people in discussion
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 Nicolas-Albo

Status:    In progress

Hello.
Nicolas-Albo is a cross-wiki long-term vandal since (at least) September 2017. When someone's first name is not "Nicolas", the vandal adds the first name "Nicolas" in the article. When someone's first name is "Nicolas", the vandal adds invented first name(s) in the article. "-Albo" is perhaps a short form of "Alberto", because sometimes the vandal adds the first name "Alberto" too. Nicolas-Albo is already blocked indefinitely on 4 projects, for vandalism. Nicolas 1993 Albo and Nick 07 1993 are blocked indefinitely on the Spanish Wikipedia because they were doing the same vandalisms on the same articles. I request global locks of the 3 accounts (their last edit has been done on 17 May, but the vandal is still active cross-wiki with his IP).

Remarks about the IP ranges used by Nicolas-Albo
The "duck test" is clear with the Chilean IP listed below, in the 4 ranges. For instance, in this article's history, you can see Nicolas-Albo and several IP (bypassing the account's block); in this article's history, you can see Nicolas-Albo, Nick 07 1993 and several IP (bypassing the account's block); in this article's history, you can see Nicolas 1993 Albo, Nick 07 1993 and several IP (bypassing the account's block). These 4 IP ranges can not be blocked, because legitimate contributors are using them too. But I want to mention the IP ranges here, and I will request future blocks of the vandal one IP at a time, if necessary.
List of Chilean IP in the range 191.116.0.0/16
IP luxotool projects days
ip 191.116.87.237 191.116.87.237 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye 1 22 April
ip 191.116.29.94 191.116.29.94 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye 1 22 April
ip 191.116.44.110 191.116.44.110 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye 1 23 April
ip 191.116.102.97 191.116.102.97 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye 4 23 April
ip 191.116.21.48 191.116.21.48 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye 1 24 April
ip 191.116.51.251 191.116.51.251 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye 2 5 May
ip 191.116.116.200 191.116.116.200 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye 3 9 May
ip 191.116.188.179 191.116.188.179 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye 1 10 May
ip 191.116.10.101 191.116.10.101 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye 1 10 May
ip 191.116.71.148 191.116.71.148 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye 1 20 May
ip 191.116.112.44 191.116.112.44 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye 1 20 May
ip 191.116.85.15 191.116.85.15 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye 4 21 May
ip 191.116.77.89 191.116.77.89 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye 1 22 May
ip 191.116.54.92 191.116.54.92 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye 2 22 May
ip 191.116.50.140 191.116.50.140 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye 1 22 May
ip 191.116.36.99 191.116.36.99 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye 2 23 May
ip 191.116.81.154 191.116.81.154 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye 1 23 May
ip 191.116.75.235 191.116.75.235 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye 3 24 May
ip 191.116.114.31 191.116.114.31 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye 1 24 May
ip 191.116.14.27 191.116.14.27 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye 4 30 May
ip 191.116.24.131 191.116.24.131 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye 1 30 May
ip 191.116.12.56 191.116.12.56 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye 2 30 May
ip 191.116.36.102 191.116.36.102 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye 3 30 May
ip 191.116.23.44 191.116.23.44 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye 1 30 May
ip 191.116.26.34 191.116.26.34 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye 4 30-31 May
ip 191.116.239.128 191.116.239.128 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye 1 7 June
ip 191.116.209.82 191.116.209.82 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye 6 14-15 June
ip 191.116.195.48 191.116.195.48 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye 2 30 June
ip 191.116.240.217 191.116.240.217 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye 2 10 July
ip 191.116.155.209 191.116.155.209 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye 3 11-12 July
List of Chilean IP in the range 191.119.0.0/16
IP luxotool projects days
ip 191.119.130.107 191.119.130.107 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye 1 22 April
ip 191.119.30.201 191.119.30.201 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye 1 22 April
ip 191.119.20.209 191.119.20.209 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye 1 23 April
ip 191.119.41.61 191.119.41.61 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye 1 23-24 April
ip 191.119.65.173 191.119.65.173 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye 1 25 April
ip 191.119.119.95 191.119.119.95 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye 2 4 May
ip 191.119.81.66 191.119.81.66 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye 2 20-21 May
ip 191.119.114.186 191.119.114.186 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye 1 21 May
ip 191.119.53.28 191.119.53.28 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye 3 21 May
ip 191.119.27.180 191.119.27.180 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye 1 22 May
ip 191.119.66.111 191.119.66.111 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye 1 22 May
ip 191.119.24.125 191.119.24.125 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye 3 29-30 May
ip 191.119.116.12 191.119.116.12 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye 2 31 May
ip 191.119.31.90 191.119.31.90 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye 1 5 June
ip 191.119.22.101 191.119.22.101 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye 2 14 June
ip 191.119.159.64 191.119.159.64 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye 1 24 June
ip 191.119.113.206 191.119.113.206 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye 1 29 June
ip 191.119.119.235 191.119.119.235 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye 2 29 June
ip 191.119.153.203 191.119.153.203 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye 1 30 June
ip 191.119.207.54 191.119.207.54 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye 1 11 July
ip 191.119.138.11 191.119.138.11 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye 2 11 July
List of Chilean IP in the range 191.125.0.0/16
IP luxotool projects days
ip 191.125.129.135 191.125.129.135 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye 2 17 May
ip 191.125.177.144 191.125.177.144 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye 2 17 May
ip 191.125.58.87 191.125.58.87 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye 4 17 May
ip 191.125.55.125 191.125.55.125 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye 3 17 May
ip 191.125.182.5 191.125.182.5 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye 1 19 June
ip 191.125.25.168 191.125.25.168 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye 1 22 June
ip 191.125.162.210 191.125.162.210 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye 1 23 June
List of Chilean IP in the range 191.126.0.0/16
IP luxotool projects days
ip 191.126.9.222 191.126.9.222 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye 1 12 April
ip 191.126.187.206 191.126.187.206 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye 1 16 May
ip 191.126.160.98 191.126.160.98 xwiki-contribs • xwiki-date (alt) • ST • IP info • WHOIS • robtex • gblock • glist • abuselog • bullseye 2 7-8 July

Regards --NicoScribe (talk) 21:37, 17 June 2018 (UTC) → 16:16, 12 July 2018 (UTC)Reply

Global lock for Hhhggg2

Status:    In progress

Hhhggg's sock puppet goes on to abuse the email feature to spam across multiple projects. --Well-Informed Optimist (talk) 16:25, 19 June 2018 (UTC)Reply

Actually, the master account hasn't been Locked yet. Stewards should consider Locking both accounts and running a sleeper check if there is actual abusse coming from this user. LightandDark2000 (talk) 23:19, 7 July 2018 (UTC)Reply
Sorry, I meant Hhhggg (talk • contribs • block • xwiki-contribs • xwiki-date (alt) • CA • ST • lwcheckuser). That’s locked account. stjn[ru] 19:30, 12 July 2018 (UTC)Reply

Sockpuppet or not, but Hhhggg2 is evidently a non-positively contributing account reportedly sending junk Email to multiple users. Unsure why stewards meditate so long on this case. @Stjn: if I understand correctly, Hhhhggg is unrelated in any way? Could you please remove the {{LockHide}} with this account to avoid misfire? Incnis Mrsi (talk) 19:02, 13 July 2018 (UTC)Reply

Global lock for Washim Rahman

Status:    In progress

The last time I reported this user was not blocked so adding my request again since the suspected sockpuppet has been blocked. There is a long-term and extensive cross-wiki abuse (please see this. Recreating their deleted article en:Prem Khan under various titles please see en:Wikipedia:Sockpuppet investigations/Washim Rahman. Thank you. GSS (talk) 18:26, 23 June 2018 (UTC)Reply

Where is cross-wiki abuse? Ruslik (talk) 20:01, 24 June 2018 (UTC)Reply
Sorry for the late reply, they are using multiple accounts in other languages to promote their subject such as as-wiki (as:প্ৰেম খান), bn-wiki (bn:প্রেম খান), bpy-wiki (bpy:প্রেম খান) etc. please see the history of these articles and repeated attempt to create the same article in en-wiki using multiple accounts. Thank you. GSS (talk) 09:56, 1 July 2018 (UTC)Reply

Global lock for Nikincce

Status:    In progress

Admitted previously undisclosed shared use in this edit.   — Jeff G. ツ 04:20, 25 June 2018 (UTC)Reply

Global lock for Satori&Ascension

Status:    Done

User:冏's socketpuppet doing cross-wiki vandalism.--云间守望 - (Talk with WQL) 04:00, 28 June 2018 (UTC)Reply

Done --Alaa :)..! 21:35, 13 July 2018 (UTC)Reply

Global lock for Bonsoirparis

Status:    Done

Cross-wiki vandalism. --Tractopelle-jaune (talk) 19:12, 13 July 2018 (UTC)Reply

Done - TNT 💖 19:23, 13 July 2018 (UTC)Reply

Global lock for Dopenguins sock

Status:    Done

New sock of Dopenguins. -★- PlyrStar93 →Message me. ← 19:50, 13 July 2018 (UTC)Reply

Done - TNT 💖 20:01, 13 July 2018 (UTC)Reply

Global lock for But where were they going without ever knowing the way?

Status:    Done

Cruizir or imposter. -★- PlyrStar93 →Message me. ← 21:00, 13 July 2018 (UTC)Reply

Done - TNT 💖 21:11, 13 July 2018 (UTC)Reply

Global lock for spambots

Status:    Done

Triggered the global filter 162 in pt.wikinews. --Editor D.S (talk) 21:30, 13 July 2018 (UTC)Reply

Done, reviewing IPs - TNT 💖 21:34, 13 July 2018 (UTC)Reply

See also

Cooperation requests for: comments (local) (global) · translation

Retrieved from "https://meta.wikimedia.org/w/index.php?title=Steward_requests/Global&oldid=18208644"