Jump to content

Steward requests/Global/2016-12

Add links
From Meta, a Wikimedia project coordination wiki

Requests for global (un)block

Global block for 36.250.86.194

Status:    Done

Again the chinese cross-wiki vandal Szm020730. Thanks in advance. --UAwiki (talk) 00:04, 1 December 2016 (UTC)

Done. RadiX∞ 02:56, 1 December 2016 (UTC)

Global block for 218.5.161.177

Status:    Done

Chinese vandal 020730szm, here more info, thanks in advance. --UAwiki (talk) 18:57, 2 December 2016 (UTC)

Done --Jyothis (talk) 19:06, 2 December 2016 (UTC)

Global block for User:Zanimum

Status:    Done

Hi... so, that LinkedIn hack a few months ago, that revealed the passwords people were using many years ago? I presume my password then, there, was my Wikipedia password. Someone edited a lot of pages on Scientology and other topics with my account, and a global block was placed.

I'd like to change my password and continue editing with the account that I've used since 2002. Pretty please? -- 2605:8D80:6C3:A358:A442:8E12:E191:544D 00:37, 2 December 2016 (UTC)

On a desktop at work, I'm noticing that the edits were all simply removing links to the main page, en mass, around 170 of them. I'd be curious to know what the heck that was even about, what the goal was. Anyway, it wasn't me. -- 198.96.114.20 13:15, 2 December 2016 (UTC)
And I'm just reading further, that only IP addresses can be blocked? The block log entry makes it look like it's my account. Was there malicious activity from this corporate IP range? -- 198.96.114.20 13:16, 2 December 2016 (UTC)
For your information, we cannot block an account globally but we can lock it. A lock prevents logging in while a block prevents editing (I am describing this loosely, there are other differences and nuances). The Zanimum account is locked globally and blocked locally at the English Wikipedia. In order to unlock the account you would need to demonstrate that it is your account. It is probably most expedient for you to work with a trusted administrator at en.wiki to convince them that you are the owner of the account and in control of it. They can then request a Steward to unlock the account. QuiteUnusual (talk) 14:36, 2 December 2016 (UTC)
Thanks for the information! I've posted on the Admin noticeboard on en.wp, as I'm not sure who to approach among the sysops otherwise. While I am a sysops myself, I haven't been active in dispute moderation or anything like that recently, to know anyone in particular to ask. -- 198.96.114.148 16:20, 2 December 2016 (UTC)
Some time ago, Zanimum put his email address (and his real name, Nicholas Moreau) on his userpage, so I've sent an email to that address saying "please confirm that you're the one using this IP". If I get a confirmatory response, I'll leave a note here. Presumably you stewards won't unlock until you can confirm that Nicholas Moreau is really able to control the account (i.e. it won't be compromised again), so I've unblocked because there's no point to it. If I shouldn't have done that, please let me know at my en:wp talk and I'll reinstate the block. Nyttend (talk) 17:15, 2 December 2016 (UTC)
Just seeing the update here. Since Nyttend's post, I've replied to his email. Further confirmation that that email is mine, I just remembered it's on the WMF regional contact press page. -- 198.96.114.148 19:26, 2 December 2016 (UTC)
And confirmation from me that I've gotten the email. I won't say that it's time to unlock because I don't know the procedure, but I am convinced that this is the account owner, so please go ahead with the next step in the getting-unlocked process. How does one confirm that one's in control of an account if it's locked? If you can't log in, I don't see how you could change the password or do anything else that would involve controlling it. Nyttend (talk) 22:01, 2 December 2016 (UTC)
PS, just to make it 100% sure that disruption won't happen, what if I reblock the account and then you unlock it? Presumably any other wikis' Zanimum accounts have been blocked by now if they disrupted anything, so unlocking won't by itself be a problem. This way, Nicholas can log in, he can send me an email saying "I've changed my password and am in control of the account", and I can unblock him. Nyttend (talk) 22:09, 2 December 2016 (UTC)
Since the account still has sysop privileges, the disruption could continue through a block. I've unlocked the account now; the people behind these compromises seem to have stopped, so I don't think there's much risk of further abuse. If there is, I'll be here for a while and can re-lock as needed. – Ajraddatz (talk) 22:12, 2 December 2016 (UTC)
Ajraddatz, I got Zanimum's email and have unblocked him; all should be good. If there had been significant risk of abuse between the time of unlock and the time when he regained control, would it have worked to desysop the account, and then you could have resysopped it as soon as I'd confirmed that he was back in control of his account? Maybe it's not precisely in line with policy, but if this were purely an en:wp thing, I'd say that it was in line with the en:WP:IAR policy; I'm just not clear if global steward actions have a similar policy. Nyttend (talk) 00:22, 3 December 2016 (UTC)
If there had been risk, I would have asked a local bureaucrat to desysop before unlocking. Our policy allows us to take any actions in emergencies, but I might have a hard time explaining why I performed an action that a local user could do (desysopping) in response to a situation that I intentionally created (unlocking). But, it does seem like the "hackers" have stopped for now, so the risk seemed pretty low - and it's all clear now. Thanks for your help with this. – Ajraddatz (talk) 01:04, 3 December 2016 (UTC)

Hi all, thanks for your help! I've just changed the password to something with no resemblance to any previous password, numbers and letters, mixed cases. Sending Nyttend an email now. Thanks again to everyone for your assistance and patience! -- Zanimum (talk) 22:39, 2 December 2016 (UTC)

Glad to hear it. Section resolved :-) – Ajraddatz (talk) 22:40, 2 December 2016 (UTC)

Global block for User:175.44.6.0/23

Status:    Done

I am looking at Commons and enWP and seeing that we have spambots operating in the area through IP addresses; fortunately at this stage blacklists and spam filters are catching edits. Would a steward please run a CU check of a couple of places, 1) looking for logged in spambots, and 2) check whether a range block can be undertaken (hard or soft). Thanks for your consideration.  — billinghurst sDrewth 00:25, 4 December 2016 (UTC)

Soft-blocked three months, as there seemed to be no legitimate activity. Savhñ 12:21, 5 December 2016 (UTC)

Global block for User:195.211.29.234

Status:    Done

Cross wiki spam: Wikidata (d:Special:Undelete/User:195.211.29.234) and on the English Wiktionary at least.--Jasper Deng (talk) 08:54, 8 December 2016 (UTC)

Done MBisanz talk 13:21, 12 December 2016 (UTC)

Global block for 27.151.170.192

Status:    Done

Cross-wiki vandalism. --jdx Re: 12:59, 11 December 2016 (UTC)

Done MBisanz talk 13:23, 12 December 2016 (UTC)

Global block for User:2003:57:E50C:D968:143C:EF4C:BA06:8ED6

Status:    Not done

Global vandal. Disembodied Soul (talk) 02:29, 4 December 2016 (UTC)

I don't see any edits [1] ✒ Bennylin 11:07, 16 December 2016 (UTC)
The tool seems to be sensitive to the letters in the IPv6 address, so I changed it above. I closed the case since it was almost 2 weeks ago and the IP-address has not since returned. -- Tegel (Talk) 12:36, 16 December 2016 (UTC)

Global block for User:124.148.92.78

Status:    Done

Russavia. --Holder (talk) 07:44, 5 December 2016 (UTC)

Done by WMFOffice. ✒ Bennylin 11:05, 16 December 2016 (UTC)

Global block for 46.4.104.157

Status:    Done

Wikinger. --jdx Re: 11:03, 14 December 2016 (UTC)

Done by MarcoAurelio. ✒ Bennylin 11:05, 16 December 2016 (UTC)

IP address blocked exception

Status:    Done

Dear Stewards teams,

This month, I've been blocked to edit all wikis based on my IP Address. RadiX has been helped me to unblock only my user name. But, sadly it affected all user name if they used our internet connection. It said that the block has been started since 30 August 2016, but I don't know why it only affected our office (Wikimedia Indonesia) recently (this month for sure).

Wikimedia Indonesia is using MyRepublic, one of internet provider in Jakarta, and tomorrow we'll have another WikiLatih for new user. The blocked range is 103.47.133.108/30.

  • WikiLatih is monthly Wikipedia's training event for new users, we've done this event since last year

Here is the full information (I use my bot account to check). Start of block: 30 Agustus 2016 02.31 Expiration of block: 30 Agustus 2017 02.31 You can contact RadiX to discuss the block. You cannot use the "Surel pengguna" feature unless a valid email address is specified in your account preferences and you have not been blocked from using it. Your current IP address is 103.47.133.109, and the blocked range is 103.47.133.108/30. Please include all above details in any queries you make. --Biyanto Rebin (WMID) (talk) 07:39, 16 December 2016 (UTC)

Related Indonesian Wikimedia (WMID) program and this, this was kinda urgent because the program was delayed because of this blocks, I've been talking about this on Stewards channel, but no reply given.--AldNonymousBicara? 08:21, 16 December 2016 (UTC)
Unblocked. Good luck with the WikiTraining tomorrow :) and happy editing. ✒ Bennylin 10:50, 16 December 2016 (UTC)
There's another block at place: 103.47.133.0/24, that will expire in May 2017. Could you see if this also affect your ability to edit? ✒ Bennylin 10:57, 16 December 2016 (UTC)
Thank you @Bennylin:, it doesn't affect ours. --Biyanto Rebin (WMID) (talk) 13:54, 16 December 2016 (UTC)

Global block for 31.184.236.x

Status:    Done
Exapmle of IPs

I suggest a global block for 31.184.236.0/24 because has been abused for spam, for example, per test2wiki:Special:Log/spamblacklist, and multiple blocks on multiple wikis. An example of IP globally blocked is 31.184.236.65, is an open proxy and recently reported spam from stopforumspam. Thanks in advanced. --Ks-M9 [disc.] 23:51, 9 December 2016 (UTC).

Sounds sensible to me, Done for three months. Cheers, Hoo man (talk) 12:02, 17 December 2016 (UTC)

Global block for 75.166.106.158

Status:    Done

A user from Denver seems to have it in for me across several wikis. -- Favonian (talk) 21:09, 16 December 2016 (UTC)

Done, Cheers, Hoo man (talk) 11:45, 17 December 2016 (UTC)

Global block for 213.49.94.60

Status:    Done
@Ajraddatz: same user as usual. Romanophile ♞ (contributions) 21:45, 18 December 2016 (UTC)
Done. – Ajraddatz (talk) 22:03, 18 December 2016 (UTC)

Global block for 120.37.166.230

Status:    Done

Chinese vandal user 020730szm. Cross-wiki abuse, abuse of sockpuppets (these accounts are globally locked). LTA user. --Ks-M9 [disc.] 23:39, 17 December 2016 (UTC).

Done. RadiX∞ 19:08, 18 December 2016 (UTC)

Global block for 94.25.229.72

Status:    Done

Russian IP, done 31 vandalism edits in 15 projects, maybe this user searched some weekend fun, maybe not. Now blocked in some projects. One day? --Plagiat (talk) 19:33, 18 December 2016 (UTC)

Done. RadiX∞ 19:40, 18 December 2016 (UTC)

Global block/unblock for 180.67.41.229

Status:    Done

Cross-wiki vandalism. Keep replacing titles of infobox templates with Korean on different languages of Wikipedia. Have been blocked on kowiki and zhwiki. --Techyan（Talk） 22:00, 18 December 2016 (UTC)

Done MBisanz talk 13:10, 20 December 2016 (UTC)

Global block/unblock for socks of יעל י

Status:    Done

only vandalism.Geagea (talk) 20:19, 15 December 2016 (UTC)

Thanks. Hanay (talk) 14:10, 16 December 2016 (UTC)

Done. Recent IP-addresses and accounts handled. -- Tegel (Talk) 19:04, 16 December 2016 (UTC)
Status:    Done
Done. -- Tegel (Talk) 00:52, 17 December 2016 (UTC)
Status:    Done

Geagea (talk) 23:01, 17 December 2016 (UTC)

Done. Recent IP-addresses and accounts handled. MBisanz talk 13:27, 20 December 2016 (UTC)

Global block for 139.162.241.206

Status:    Done

Only racism edits, has edited earlier with IP addresses 2606:f180:0:c:c:bd14:e800:8e7c 2606:f180:0:95:95:464f:bcda:6537 2606:f180:0:1:1:7eb6:f9eb:a3b6 2606:6000:50c7:4200:61e9:d32e:1171:4821 2606:6000:50c7:4200:1cf7:16af:3712:dfcc Seems like IPv6 address range 2606:F180:0:0:0:0:0:0/32 has been globally blocked by 'Tegel' (expires 14 June 2017). Reverted all edits by this most recent (IPv4) address that hadn't been reverted so far (on many different wikis) --84.250.112.246 17:59, 20 December 2016 (UTC)

EDIT: 2606:6000:50C7:4200:0:0:0:0/64 seems to be globally blocked too (thank you). --84.250.112.246 18:00, 20 December 2016 (UTC)
I too observed his edits againts some peole. Please block this ip--Shriheeran (talk) 07:20, 21 December 2016 (UTC)
Done--Shanmugamp7 (talk) 05:57, 23 December 2016 (UTC)

Global block for User:58.140.235.59

Status:    Done
58.140.231.133 #
58.140.228.222 #
58.140.230.90 #
58.140.228.104 #
58.140.239.69 #
58.140.226.241 #
58.140.180.73 #
218.237.202.76 #
218.237.202.123 #

Reason: global vandalism. IP [58.140.235.59] did acts of vandalism in wikis that have not any admins, so we can't block this IP locally. Thus I request blocking it. I think it's a same person with previous one. Nuevo Paso (talk) 07:11, 5 December 2016 (UTC)

Add '222.112.120.151' # Nuevo Paso (talk) 09:00, 7 December 2016 (UTC)
58.140.X.X, These are dynamic, so blocking individual ips' wont be effective, the range is pretty big, so cant block it globally. On the 218.237.X.X range, i don't see any recent edits, so not blocking it, Blocked 222.112.120.151 for a month, Please try some alternate solutions like abusefilter, Global blocking might not be much useful on dynamic ip's.--Shanmugamp7 (talk) 06:11, 23 December 2016 (UTC)

Global block for 122.154.146.218

Status:    Done

Confirmed open proxy and recently reported forum spam source (click "IP info" for more information). --Francisco (talk) 10:13, 19 December 2016 (UTC)

Done by Vito --Melos (talk) 18:46, 21 December 2016 (UTC)

Global block for anothe sock of User:יעל י

Status:    Done

Already blocked in Commons and he.wiki. Geagea (talk) 16:56, 22 December 2016 (UTC)

Done. locked, Global block is not available for user accounts--Shanmugamp7 (talk) 06:22, 23 December 2016 (UTC)

Global block for 121.94.173.145

Status:    Done

Also:

Open proxies, 1st on port 80, 2nd on port 3128 and 3rd, AFAIR, on port 8080. --jdx Re: 17:01, 22 December 2016 (UTC)

Done--Shanmugamp7 (talk) 06:24, 23 December 2016 (UTC)

Global block for 62.235.177.130

Status:    Done
@Ajraddatz: same user as usual. — (((Romanophile))) ♞ (contributions) 06:45, 24 December 2016 (UTC)
Done. – Ajraddatz (talk) 17:53, 24 December 2016 (UTC)

Global block for 62.235.180.5

Status:    Done
@Ajraddatz: same user as usual. — (((Romanophile))) ♞ (contributions) 06:45, 24 December 2016 (UTC)
Done, thanks. – Ajraddatz (talk) 07:43, 24 December 2016 (UTC)

Global block for 83.134.147.65 & 213.49.62.10

Status:    Not done
@Ajraddatz: same user as usual. — (((Romanophile))) ♞ (contributions) 09:18, 28 December 2016 (UTC)
Gonna hold off on this one while the local admin sorts it out. – Ajraddatz (talk) 17:54, 28 December 2016 (UTC)

Global block for 54.146.52.0

Status:    Done

IP sock of Wikinger. Vandalism on Meta, and many wikis and persistent trolling on ta:user talk:Shanmugamp7. Thanks. --Ks-M9 [disc.] 14:50, 27 December 2016 (UTC).

Self closure - done by Vituzzu. --Ks-M9 [disc.] 01:26, 28 December 2016 (UTC).

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

Global lock for 影武者(Nipponese Dog Calvero)

Status:    Done

--Lanwi1(Talk) 15:58, 30 November 2016 (UTC)

Done Ruslik (talk) 16:27, 30 November 2016 (UTC)

Global lock for Albert20009's sockpuppet

Status:    Done

--Lanwi1(Talk) 15:58, 30 November 2016 (UTC)

Done Ruslik (talk) 16:28, 30 November 2016 (UTC)

Global lock for 影武者(Nipponese Dog Calvero)

Status:    Done

--Lanwi1(Talk) 21:52, 30 November 2016 (UTC)

Done. RadiX∞ 02:53, 1 December 2016 (UTC)

Global lock for 影武者(Nipponese Dog Calvero)

Status:    Done

--Lanwi1(Talk) 21:52, 30 November 2016 (UTC)

Done. RadiX∞ 02:53, 1 December 2016 (UTC)

Global lock for Ajent A90

Status:    Done

Obvious IP sock of LTA Wikinger, with cross-wiki abuse on other wikis. -- Favonian (talk) 09:02, 2 December 2016 (UTC)

Done--Shanmugamp7 (talk) 12:41, 2 December 2016 (UTC)

Global lock for 影武者(Nipponese Dog Calvero)

Status:    Done

--Lanwi1(Talk) 17:40, 2 December 2016 (UTC)

add--Lanwi1(Talk) 02:59, 3 December 2016 (UTC)

add--Lanwi1(Talk) 08:14, 3 December 2016 (UTC)

Done. RadiX∞ 17:47, 3 December 2016 (UTC)

Global lock for Armyboy2

Status:    Done

Reasons, etc, --This user has been blocked on three different wikis.

Done Ruslik (talk) 17:30, 3 December 2016 (UTC)

Global lock for I feel bad for the Vikings defense.

Status:    Done

Sock of Starship9000. lNeverCry 23:23, 3 December 2016 (UTC)

Done. Trijnsteltalk 23:38, 3 December 2016 (UTC)

Global lock for 影武者(Nipponese Dog Calvero)

Status:    Done

--Lanwi1(Talk) 22:53, 3 December 2016 (UTC)

Done Ruslik (talk) 15:43, 4 December 2016 (UTC)

Global lock for 影武者(Nipponese Dog Calvero)

Status:    Done

--Lanwi1(Talk) 22:53, 3 December 2016 (UTC)

Done Ruslik (talk) 15:43, 4 December 2016 (UTC)

Global lock for 影武者(Nipponese Dog Calvero)

Status:    Done

--Lanwi1(Talk) 04:41, 5 December 2016 (UTC)

Done Ruslik (talk) 15:41, 5 December 2016 (UTC)

Global unlock for Rolodata

Status:    Not done

Rolodata (talk · contribs) requested to be unlocked at Requests for comment/Desbloqueo global de Rolodata, but I've closed it as the user is not banned and has not attempted this first procedure even after we've told them to do so first. Previously globally locked as per Steward_requests/Global/2016-08#Global_lock_for_Rolodata. Just moving the request here, not suggesting anything. —MarcoAurelio 16:43, 20 November 2016 (UTC)

Can you translate what they wrote in Spanish? Ruslik (talk) 19:26, 20 November 2016 (UTC)
Translating everything will take me some time. I can post a summary if that's also okay. —MarcoAurelio 14:46, 21 November 2016 (UTC)
Summary:
It's difficult to read a text without paragraphs, but these are some of his reasons:
  • He knows he should've posted at SRG, but he has decided to go on RfC because he wanted to collect comments.
  • He wants to be back because he can't stand/hang on any more time locked out of his account.
  • In a short story, he ackowledges that he was caught vandalizing Wikipedia 9 months ago and he was blocked 2 weeks for that, but he evaded the block and continued vandalizing for longer. He says that he was blocked for a month and did respected that to the end.
  • After the block, he says that everything went worse and started using Wikipedia as a social network and chasing users across several projects for "friendship".
  • He says that he understands that such behaviour was wrong and that he's changed.
If you need details on something, I'll try to assist on that. —MarcoAurelio 19:25, 25 November 2016 (UTC)
I am also not convinced. Ruslik (talk) 16:13, 1 December 2016 (UTC)
Same for me. Linedwell (talk) 08:04, 5 December 2016 (UTC)

Not done —MarcoAurelio 16:00, 7 December 2016 (UTC)

Global lock for User:Salah19965de

Status:    Done

This is cross-wiki date vandal and sock master Aliabbashiraqi79. See en:Wikipedia:Sockpuppet investigations/Aliabbashiraqi79 for more details. Same date changes as other socks: [2], [3]. NinjaRobotPirate (talk) 20:35, 3 December 2016 (UTC)

Done Ruslik (talk) 15:38, 4 December 2016 (UTC)
@Ruslik0: Was the user's account unlocked? There was a brief stop in activity after my report, after which I assume the account was locked. Today, he returned to changing dates on multiple projects: wikidata, wikidata, ar.wiki. NinjaRobotPirate (talk) 01:56, 7 December 2016 (UTC)

Global lock for 影武者(Nipponese Dog Calvero)

Status:    Done

--Lanwi1(Talk) 04:41, 5 December 2016 (UTC)

Done Ruslik (talk) 15:41, 5 December 2016 (UTC)

Global lock for Shorepointcomm

Status:    Done

Cross-wiki spambot. Syum90 (talk) 08:16, 6 December 2016 (UTC)

Done by MarcoAurelio. Linedwell (talk) 11:11, 6 December 2016 (UTC)

Global lock for Sock Puppet Accounts

Status:    Done

Sock puppet accounts. 177.183.24.191 11:42, 8 December 2016 (UTC)

Done Ruslik (talk) 13:17, 8 December 2016 (UTC)

Global lock for Incorrigible Troll is my hovseboy

Status:    Done

Abusing multiple accounts; vandalism-only account; LTA. Syum90 (talk) 09:24, 9 December 2016 (UTC)

Locked. – Ajraddatz (talk) 09:41, 9 December 2016 (UTC)

Global lock for 影武者(Nipponese Dog Calvero)

Status:    Done

--Lanwi1(Talk) 05:31, 10 December 2016 (UTC)

Done, Linedwell (talk) 07:57, 10 December 2016 (UTC)

Global block for sockspuppets of User:יעל י

Status:    Done

Vandalism only account. Global vandal, this time in hebrew projects. Geagea (talk) 23:06, 9 December 2016 (UTC)

Done and english translation is removed. ~ Nahid Talk 18:16, 10 December 2016 (UTC)
Thanks and r=more socks and also all the user names are inappropriate.
Geagea (talk) 01:31, 11 December 2016 (UTC)
Done as well. ~ Nahid Talk 10:24, 11 December 2016 (UTC)
Thanks Nahid. Can you remove the inappropriate user names as well? Geagea (talk) 16:49, 12 December 2016 (UTC)

Global lock for sockpuppet of Styron111

Status:    Done

Globally banned user "Styron111"; request for speedy deletion of all contributions [4] too. tY --91.14.44.114 03:10, 12 December 2016 (UTC)

Done Ruslik (talk) 19:45, 12 December 2016 (UTC)

Global lock for bad users

Status:    Done
  1. 함북연길-It seem's like Unypoly-This user just added a recheck about the block that he's not a Unypoly
  2. 비밀번호-Sock of 슉슉이, I forgot to do this since October.
  3. Tellthetruth7-Vandalism+Sockpuppeter, Long term abuse
  4. Tellthetruth10-sock~up to number 31 of the request.
  5. Tellthetruth12
  6. Tellthetruth13
  7. Tellthetruth15
  8. Tellthetruth16
  9. Tellthetruth17
  10. Tellthetruth18
  11. Tellthetruth19
  12. Tellthetruth20
  13. Tellthetruth21
  14. Tellthetruth22
  15. Tellthetruth24
  16. Tellthetruth25
  17. Tellthetruth26
  18. Tellthetruth27
  19. Tellthetruth28
  20. Tellthetruth29
  21. Tellthetruth3
  22. Tellthetruth30
  23. Tellthetruth31
  24. Tellthetruth32
  25. Tellthetruth33
  26. Tellthetruth34
  27. Tellthetruth5
  28. Tellthetruth6
  29. Tellthetruth7
  30. Tellthetruth7525-Changed his name from 7524 to 7525(Recent)
  31. Tellthetruth8
  32. Tellthetruth9
  33. 자예진-Impersonator+Sock of 정현규 which is globally locked.
  34. 차예진이-Impersonator+Vandalism only account

--Jerrykim306 (talk) 12:46, 22 November 2016 (UTC)

Done ✒ Bennylin 10:46, 16 December 2016 (UTC)

Remove inappropriate user names of User:יעל י sockspuppets

Status:    Done

Can you please remove the inappropriate user names of User:יעל י sockspuppets. They are already globaly blocked.

Geagea (talk) 03:38, 15 December 2016 (UTC)

Done by NahidSultan. ✒ Bennylin 12:05, 16 December 2016 (UTC)
Status:    In progress
Sorry, inappropriate usernames did not removed from edit summaries see her. I have done so in commons but can't do it in other wikis. Geagea (talk) 15:31, 16 December 2016 (UTC)

Global lock for user:Jpairconditioning

Status:    Done

Spam only account  — billinghurst sDrewth 12:14, 16 December 2016 (UTC)

Done. RadiX∞ 12:33, 16 December 2016 (UTC)

Global lock/unlock for JuniorX2

Status:    Done

An editor with a history of extensive sockpuppetry on English Wikipedia has had numerous accounts blocked, as you can see at en:Category:Wikipedia sockpuppets of Sarojupreti and en:Category:Suspected Wikipedia sockpuppets of Sarojupreti. One of those accounts is JuniorX2. The block settings include email access being disabled, apparently because of abuse of emails from some of the sockpuppets in the past. He has now taken to evading the email block on English Wikipedia by using email from meta to canvas administrators in connection with the block on English Wikipedia. The account has a history of being blocked on other projects too, as can be seen here: [5] [6] [7]. I have not checked every project, so that may not be a complete list of the blocks. Other accounts of the same sockpuppeteer have also been blocked on more than one project, and some of them are already globally locked because of cross-wiki abuse: see Special:CentralAuth/Red_Rose62, Special:CentralAuth/Rishi_Singh_Rathod and Special:CentralAuth/Tiger_Gang. I have checked only a small minority of the known sockpuppets, so this is likely to nowhere near a complete list of global locks: I give it just for illustration.

Would it be possible to put a global lock without email access on JuniorX2, or maybe even on all the accounts? --JamesBWatson (talk) 14:52, 16 December 2016 (UTC)

Done Ruslik (talk) 19:17, 16 December 2016 (UTC)

Global lock/unlock for 2009szm

Status:    Done

An other sockpuppet of Long-term vandal user 020730szm (globally locked). Continued cross-wiki abuse by this sockmaster. --Ks-M9 [disc.] 01:09, 17 December 2016 (UTC).

Done Ruslik (talk) 08:06, 17 December 2016 (UTC)

Global lock for LTA accounts

Status:    Done

LTA Wikinger socks. Vandalism on meta, plwiki, etc. --Ks-M9 [disc.] 09:31, 18 December 2016 (UTC).

Done by Tegel. Ruslik (talk) 18:43, 18 December 2016 (UTC)

Global lock for K0m3k3n4k

Status:    Done

Username spam or spambot Murbaut (talk) 14:04, 17 December 2016 (UTC)

Done Ruslik (talk) 11:09, 19 December 2016 (UTC)

Global lock for Albert20009's sockpuppet

Status:    Done

--Lanwi1(Talk) 10:50, 19 December 2016 (UTC)

Done Ruslik (talk) 11:01, 19 December 2016 (UTC)

Global lock for "Taxi Langkawi Holiday"

Status:    Done

Taxi Langkawi Holiday
Spam only account, and returning visitor.  — billinghurst sDrewth 23:15, 19 December 2016 (UTC)

Done, best regards, —MarcoAurelio 11:19, 20 December 2016 (UTC)

Global lock for sockpuppets of Messina

Status:    Done

sockpuppets of global banned user Messina --DCB (talk) 20:07, 20 December 2016 (UTC)

Done--Vituzzu (talk) 20:30, 20 December 2016 (UTC)

Global unlock for JuniorX2

Status:    Done

Hi, i was unknown of the policies earlier. I've done mistakes as being newbie. I really apologies for that. I want to fresh start again with productive edits without creating new socks. So, please provide me last chance. --JuniorX2

Oppose. Last sock was locked (which had global ipblock exemption!) yesterday, x-wiki sock puppetry (commons, enwiki, simpleenwiki, meta). --Steinsplitter (talk) 13:15, 19 December 2016 (UTC)
Locked for 3 edits on enwiki out of a few thousands. This lock indeed deserves investigation, also to me it seems more than suspicious, especially since there were no blocks in place on the main wikis of activity. --Vogone (talk) 13:28, 19 December 2016 (UTC)
Note that his real name on his userpage is "Raaza Upreti" and a sock locked is named Raaza Upreti. The lock is correct for me. --Ks-M9 [disc.] 13:48, 19 December 2016 (UTC).
Since when do we lock accounts for the mere (past) usage of multiple accounts? There is no point in Global locks justifying a lock for this. --Vogone (talk) 14:15, 19 December 2016 (UTC)
There's a significant amount of disruption and abuse of process from JuniorX2 - see the list of sockpuppets confirmed on English Wikipedia here and the extensive work here explaining policies to this user. This is not 'newbie mistakes' but wilful disruption. Nick (talk) 14:22, 19 December 2016 (UTC)
Again, do you have such evidence for his main wikis maiwiki and newiki? Unless you have, there are no grounds for a global lock but only for a local block on the English language Wikipedia. --Vogone (talk) 14:33, 19 December 2016 (UTC)
en:Wikipedia:Sockpuppet investigations/Sarojupreti/Archive, c:Category:Sockpuppets of Sarojupreti. Please look up the sock edits, wilful x-wiki disruption, it is enough for a global lock per standard practice. --Steinsplitter (talk) 15:07, 19 December 2016 (UTC)
@Steinsplitter: Is it possible to unblock this user on a single project for sometime, and depending on this editing style decide the future course of action? --Muzammil (talk) 15:52, 19 December 2016 (UTC)
@Ruslik0: This lock is plainly wrong and I would argue against the policy. Users with thousands of edits should not be peremptorily locked. Socking is NOT against policy, and local wikis should be able to manage. We have a policy for global blocking, and that should be the avenue used here, if it is required. — The preceding unsigned comment was added by Billinghurst (talk) 23:22 19 dic 2016 (UTC)
To note, to quote case history where Jimbo shouted and the account of Thekohser was locked, and then after discussion was unlocked, and then relocked and unlocked after later discussion. Please also note global block and global bans policies.  — billinghurst sDrewth 15:08, 20 December 2016 (UTC)
This account was locked for cross-wiki abuse in accordance with the policy. He used the e-mail feature on meta to harass e-mail enwiki administrators after being told not to do this. In addition several of his accounts are already locked and blocked on multiple projects. Ruslik (talk) 19:18, 21 December 2016 (UTC)
Sorry, but the policy doesn't say "Annoying users may be locked." anywhere. Nor has a local block on meta ever been imposed, which is quite strange considering an "email abuse" on meta was your reason to lock this account. --Vogone (talk) 19:38, 21 December 2016 (UTC)
  • Support Support @Ruslik0: I fully support Vogone's statements. The user is in good standing in a wiki, and was not given clear opportunity to contest this account lock, by either the proposer or by you the steward. There is a clear lack of natural justice. The xwiki abuse statement needs to be considered more holistically than a straight abuser of services. I ask for you to unlock this account and request the original proposer take this via Global block policy. This could have been managed by a steward giving clear and specific instruction to the user about their behaviour (been there, done that). Clear conditions to the user about the unlock should be identified. Local blocks could and should have been utilised here for local abuse; instead we have punitive actions. I again ask you as a steward to review your methodology and consider using a more mature approach to resolution.  — billinghurst sDrewth 00:52, 22 December 2016 (UTC)
  • I disagree with a lot of the statements above, but I would have liked to have seen more local blocks, particularly on newiki and maiwiki, before a global lock. --Rschen7754 03:32, 22 December 2016 (UTC)
    A kind of self-fulfilling prophecy? Or which reason would these wikis have had to block/ban this user? I think we should let communities decide individually if they want to ban a certain user or not, rather than imposing account locks which weren't even requested by these communities … --Vogone (talk) 06:45, 22 December 2016 (UTC)
  • Comment. I am surprised that many users who commented here failed to check the facts before making their comments. Some statements that are not true:
    • Locked for 3 edits on enwiki out of a few thousands - Of course, if one forgets about dozens of socket puppets having thousands edits among them.
    • Nor has a local block on meta ever been imposed - Really?
    • This could have been managed by a steward giving clear and specific instruction to the user about their behaviour - After enwiki administrators had tried to do this for several months and failed, would my explanation be effective?
So, I consider that my action was well within the policy. Still I anticipated that this user would eventually requests unlock and was even surprised that he waited for so long. So, I am willing to give him the last chance if he agrees to abide by the following two conditions:
  • He will be limited to only one account of his choice across all SULed Wikimedia projects. No more socks created for any reason. In an unlikely situation the user needs an additional account he shall post a message on Stewards noticeboard requesting a permission.
  • The user will stop sending unsolicited e-mails to administrators and other users on enwiki/commons/(other projects where he is blocked). He agrees to use only official channels for any future unblock requests.
If the user accepts these conditions, he should post a message here and identify an account he wants to use. Any violation of the conditions will lead to a lock (likely forever). Ruslik (talk) 11:38, 22 December 2016 (UTC)
Done Ruslik (talk) 18:06, 22 December 2016 (UTC)
Thank you very much, Ruslik0. WRT your comments about facts, none of the things you linked refer to this account but to older socks (even the one on meta was being blocked merely for being a sock). Of course it is clear to me that enwiki/commonswiki has blocked not only one of his accounts, but the point is newiki/maiwiki have not. Kind regards, --Vogone (talk) 00:57, 23 December 2016 (UTC)

Global lock for Xuvuni

Status:    Done

Sock of Fritella. --Ks-M9 [disc.] 12:27, 21 December 2016 (UTC).

Done Ruslik (talk) 19:08, 21 December 2016 (UTC)

Global lock for GRSBOT

Status:    Done

Long-term abuse: Vhaslhv. --Francisco (talk) 22:17, 21 December 2016 (UTC)

Done--Shanmugamp7 (talk) 06:32, 23 December 2016 (UTC)

Global lock for Mikel Sarwono

Status:    Done

@Shanmugamp7 Cross-wiki vandalism-only account. He's highly a long term abuser of a user whom is beforehand globally locked by a steward, it's User:MIKEL S. SARWONO!

on meta:

03:11, 20 October 2016 Az1568 (talk | contribs) blocked Mikel Sarwono (talk | contribs) with an expiration time of infinite (account creation disabled, email disabled, cannot edit own talk page) (Cross-wiki issues: LTA / Abusing multiple accounts)

on wikipedia:

16:44, 11 July 2016 Bbb23 (talk | contribs) changed block settings for Mikel Sarwono (talk | contribs) with an expiration time of indefinite (account creation blocked, cannot edit own talk page) (Revoking talk page access: inappropriate use of user talk page while blocked: {{checkuserblock-account}})

2602:304:68AD:3220:68BD:8270:2B3:1D04 17:11, 22 December 2016 (UTC)

Done--Shanmugamp7 (talk) 06:34, 23 December 2016 (UTC)

Global lock for ArianaGrandeIsUnattractive

Status:    Not done

@Shanmugamp7 Inapposite username 2602:304:68AD:3220:68BD:8270:2B3:1D04 17:42, 22 December 2016 (UTC)

A Username violation isn't exactly a thing for a lock. 04:26, 23 December 2016 (UTC)
Abusive or offensive usernames can be locked or hidden, i don't think this will fall under that category .--Shanmugamp7 (talk) 06:44, 23 December 2016 (UTC)

Global lock for User:廖羽玄

Status:    Done

crosswiki vandalism --Shizhao (talk) 02:58, 23 December 2016 (UTC)

Done--Shanmugamp7 (talk) 06:42, 23 December 2016 (UTC)

Global lock for Ravishankar001

Status:    Done

X-wikis vandalism-only Account. --Born4People (talk) 09:50, 23 December 2016 (UTC)

Done Ruslik (talk) 19:30, 23 December 2016 (UTC)

Global lock for Sun69hXXX

Status:    Done

X-wiki vandalism-only Account. --Born4People (talk) 04:35, 24 December 2016 (UTC)

Done--Shanmugamp7 (talk) 10:10, 24 December 2016 (UTC)

Global lock for Sandy!4

Status:    Done

X-wiki vandalism-only Account. --Born4People (talk) 04:13, 25 December 2016 (UTC)

Done by steward Shanmugamp7 --Jerrykim306 (talk) 14:33, 25 December 2016 (UTC)

Global lock for User:Ravishankar002

Status:    Done

Sockpuppet of globally blocked "User:Ravishankar001". X-wiki vandalism-only Account. --Born4People (talk) 05:01, 25 December 2016 (UTC)

Done by steward Shanmugamp7 --Jerrykim306 (talk) 14:33, 25 December 2016 (UTC)

Global lock for User:Szm20026

Status:    Done

An other sockpuppet of Long-term vandal user 020730szm (globally locked). Continued cross-wiki abuse by sockmaster. Born4People (talk) 14:01, 26 December 2016 (UTC)

Done Ruslik (talk) 19:48, 26 December 2016 (UTC)

Global block for anothe sock of User:יעל י

Status:    Done

Already blocked in he.wiki.- Vandalism on wikidata. Thanak. Hanay (talk) 20:39, 26 December 2016 (UTC)

Done. —MarcoAurelio 21:45, 26 December 2016 (UTC)

Global block for anothe sock of User:יעל י

Status:    Done

Bandha

Already blocked in he.wiki.- Vandalism on Wikidata. Thanks. Hanay (talk) 15:07, 27 December 2016 (UTC)

Done Ruslik (talk) 19:53, 27 December 2016 (UTC)

Global lock for User:Szm00156

Status:    Done

An other sockpuppet of Long-term vandal user 020730szm (globally locked). X-wiki vandalism-only account. Born4People (talk) 06:58, 28 December 2016 (UTC)

Done Ruslik (talk) 19:00, 28 December 2016 (UTC)

Global lock for Premierfamily set

Status:    Done

xwiki spam; and please check for others in that series. Thx.  — billinghurst sDrewth 11:29, 28 December 2016 (UTC)

Done, locked a bunch of spam accounts in the same range, but the ip range is too big to gblock.--Shanmugamp7 (talk) 12:07, 28 December 2016 (UTC)

Global lock for HunteWinchester123

Status:    Not done

Crosswiki spam on his/her talk pages or sandboxes, about a bunch of non-existing people. Thanks for considering --MBq (talk) 12:13, 28 December 2016 (UTC)

Not done It is not an obvious case. Please, use Global ban. Ruslik (talk) 19:03, 28 December 2016 (UTC)

Global block for another sock of User:יעל י

Status:    Done

Already blocked in he.wiki.- Vandalism on English Wikipedia. User:יעל י is using a small internet service provider called 'Triple C. Since she has a lot of socks and she open more and more, I suggest to do range blocking as follows:

  • 5.22.130.0/24
  • 5.22.134.0/24
  • 141.226.217.0/24
  • 141.226.218.0/24
  • 185.3.146.0/23
  • 46.19.85.0/24
  • 46.19.86.0/24

Thanks. Hanay (talk) 09:23, 28 December 2016 (UTC)

How many people are using these ranges? Ruslik (talk) 19:09, 28 December 2016 (UTC)
@Ruslik0: according to the article in Hebrew wikipedia only few thousand. I added now another user of her User:WWW123PPP vandalism on Commons. Hanay (talk) 09:32, 29 December 2016 (UTC)
Done Ruslik (talk) 16:31, 31 December 2016 (UTC)

Global lock for FREIHEIT

Status:    Withdrawn
The following discussion is closed:

The user appeals for pedophilia legalization in Russian Wikipedia. --Well-Informed Optimist (talk) 07:03, 29 December 2016 (UTC)

As I don't speak Russian and this has legal implications I'm forwarding this to the Office. —MarcoAurelio 22:09, 29 December 2016 (UTC)

Global lock for 影武者(Nipponese Dog Calvero)

Status:    Done

--Lanwi1(Talk) 15:49, 31 December 2016 (UTC)

Done Ruslik (talk) 15:55, 31 December 2016 (UTC)

Global lock for 影武者(Nipponese Dog Calvero)

Status:    Done

--Lanwi1(Talk) 15:49, 31 December 2016 (UTC)

Done Ruslik (talk) 15:55, 31 December 2016 (UTC)

Global lock for 影武者(Nipponese Dog Calvero)

Status:    Done

--Lanwi1(Talk) 16:24, 31 December 2016 (UTC)

Done Ruslik (talk) 16:34, 31 December 2016 (UTC)

Global lock for 影武者(Nipponese Dog Calvero)

Status:    Done

--Lanwi1(Talk) 16:24, 31 December 2016 (UTC)

Done Ruslik (talk) 16:34, 31 December 2016 (UTC)

Global unlock for User:Graaf Statler

Status:    Not done
The following request is closed: Not unlocking, continued cross-wiki harrasment equally including personal attacks in this request. Savhñ 11:17, 20 December 2016 (UTC). Please do not modify it. No further edits should be made to this discussion.
  • Well, I am going to tell you the most strange story of the history of Wikipedia. I was global lockt and I didn't understand a thing of it! Because the reason was absolute nonsense. And, I made this appointment with User: Tegel. And OK it is almost 2017, no problem. But for a few days ago I was challenged by User:Edoderoo to send him a email. So I did. And he began to challenge me and insult with terrible anti-semitism insults (<link to holocaust remembrance website removed> Almost my complete family is killed is Sobobor]), I did n't understand what happened, I was astonished! (And still are, I didn't sleep for nights.) I asked him, what did I do wrong? And he said, you are you're lying to us for years and telling us and told us stories! Who are you really? I said, it is not your business, but I am the youngest son of professor <link removed>. You are a liar, his son died ad the age 14! So, I made a picture with my pasport in my hand, and asked him, do you believe me now? It was absolute silent afterwards. I asked him, what lie did I tell, give me one exempel. Give one edit that was not integer. No answer. They blamed me of copyvio to block and lock me! ! Later I find out that it was for years a rumor on IRC that I was dead and "I" was a troll! I am still waiting for excusese etc. User:Whaledad, ArbCom member and sysop on Wikiquote NL has the copy of this terrible email. And I also started a arbcomcase. Best regards, Martin <family name removed>, life and kicking! PS If any trusted member wants my ID, no problem, aldo Whaledad have seen the picture! By the way, thank you for removing the personal information!
  • PPS I am a checkt user, I identified myself in January 2010 by trusted User:RonaldB, so I really don't understand don't a clou of this strange action. But, now I understand why the compleet bureaucracy always was shouting "troll" without any reason to me. And, I went to ArbCom for this problem, but my friendly request ended up in a corrupt OT block and a Global Lock!
Oppose I was so unlucky to get a few of Statlers mails. The image they painted in my view, was of a user who had completely lost the plot. Letting him go again, will certainly harm the community and possibly the encyclopaedia. The Banner (talk) 22:40, 19 December 2016 (UTC)
Mpffffff The Banner, Ik hoop dat jij je spoedig bij je voorouders vervoegt? I hope you will soon joins your ancestors? Who wrote these words in a email? Wasn't that you? Beste regards, Graaf Statler
Statler better shows those mails I've sent him. He is making an elephant out of a muskito. He is too stupid to recognise anti-semitism, but smart enough to mis-understand a situation in his favour. Now he's lying here hoping people will pity him and give him back his account. Obviously I am not an anti-semite and I did not insult Statler, he wants to read insults in the mails I've sent him. He is also not writing about all claims that he wants to bring down Wikimedia, he wants to bring to court several people that are volunteer here, and I had enough of all his false accusations and halve-spread stories. I don't care that he tries to make me look like the big bad guy, there are plenty of people that have met me IRL and know that I'm not halve as bad as Statler wants to make me look like. But I do care that he is lying here to make himself look good and shiny, where he knows that mails that he says he has as a proof are kept a secret. I'm looking forward to this so called ArbCom case, and besides this, I want to stress that actually all mails are sent outside Wikimedia, so I do not understand why this is a Wikimedia case now. Edoderoo (talk) 23:00, 19 December 2016 (UTC)
Jullie is jodenvolk? I back you pardon? And asking, look it what it means? And repeating it? Graaf Statler
  • Maar degenen die de uitdrukking nu gebruiken weten vaak niet dat deze reactie vóór de Tweede Wereldoorlog, en ook nog daarna, door niet-Joodse Nederlanders werd gebruikt om aan te geven dat zij (als nette mensen) niet met “jullie” doch uitsluitend met “U” wensten te worden aangesproken. En dat je uitsluitend de (minderwaardige) joden met “jullie” mocht aanspreken.
    • Respect dient van twee kanten te komen. Vraag de email-conversatie maar op bij Statler. Hij geeft 'm toch niet, want dan is hij zijn hele onderbouwing kwijt. Edoderoo (talk) 23:30, 19 December 2016 (UTC)
      • Dacht jij dat ik die platte scheldpartijen met opmerkingen als stop maar in je hol bewaarde in mij mailbox Edo? Dat mik ik weg als spam! Mischien heeft Bart of Whaledad nog die rotzooi van jouw, ORTS Edo! Mijnheer begint tegen Bart, dat ik te laf zou zijn hem te mailen, en als ik dat doe spamt hij de boel vol met achterbuurtmails! Leve de ORTS-medewerkers! Geef jij maar eens eerlijk toe dat jij je deerlijk vergist hebt! En hoe zit het nu met die nieuwe baan waar ik maar geen antwoord over krijg? Heb je die nu wel of niet via je Wikimediawerk? Want een antwoord krijg ik maar niet van jouw daarop! Infrieure Jews, daar heb jij het over, en daar spreek ik jouw op aan, Edo!! En op die kruiwagen waarop jij die baan bent binnengereden! Graaf Statler
        • Ik heb jou van buiten Wikimedia gemaild, dus ik begrijp nog steeds niet waarom jij mij via deze weg een oor aan wil naaien. Maar geen probleem, want ik sta hier niet alleen in, dat ik je niet begrijp. En omdat ik niets heb fout gedaan, heb ik ook niets te vrezen. En wat is eigenlijk je vraag hier op Meta? Wil je een unlock voor jezelf, een blokkade voor mij, of wilde je gewoon met de strontemmer rammelen met de helft van een verhaal en volle leugentjes? Edoderoo (talk) 08:50, 20 December 2016 (UTC)
          • Wat nou leugens! Jullie zijn een corrupt zooitje en heel Wikipedia-NL is een grote puinhoop Edo! En dat Wikimedia-NL is niks meer of minder dan een feestcommissie op zoek naar een feest (met dank aan Mark Rutte voor deze opmerking) en een baantjesfabriek! En dát is de waarheid Edo en daarom hebben jullie mij de deur uit gewerkt. Om mij constant de mond te snoeren. Het is een grote vriendjeskliek die elkaar constant de hand boven het hoofd houdt, en Wikipedia-NL is niks meer of minder dan een digitale vuilnisbak met trollaandrijving! En wat ik hier wil lijkt me vrij duidelijk, dat is dat achterlijke lock opgeheven wordt! Ik ben geen vandaal. Graaf Statler.
  • {{case closed}}
    • Wat nou case closed? Jullie naaien mij een blok en een lock aan met een drijfzand-onderbouwing of erger, omdat jullie je totaal niet in mij verdiepen hebben, beledigen in de wilde weg, en ja, ik snap dat jullie dachten dat ik een ander was, en komt dan aankakken dat ik leugens sta te vertellen? Nog steeds Edo? Zou diep, diep door het stof gaan geen beter idee zijn, Edo? Graaf Statler
      • Ik denk dat jij hier zaken loopt te verdraaien. Het blok voor onbepaalde tijd op de Nederlandstalige Wikipedia is nog steeds het resultaat van een blokverzoek op RegBlok, dus geen arbcomblok. Hoe wordt jij hier dan een blok aangenaaid? Ik zie het in ieder geval niet. Gezien je verleden op de Nederlandstalige Wikipedia is het voor mij niet heel gek dat je uiteindelijk daar en elders OT geblokt werd en uiteindelijk globaal bent gelocked. Naar mijn mening zouden de stewards dit verzoek mogen afwijzen, want je hebt geenzins bewezen dat je normaal met anderen om kan gaan (zie ook de diverse "harrasment" bloks). Wiki13 talk 10:07, 20 December 2016 (UTC)
Closing as Not done. The issues leading to the lock have not been addressed, nor are they addressed in the blogpost full of personal attacks linked previously, which I have now removed. As you are blocked on meta for similar incidents, I will proceed to blocking this IP as well. Please refrain from continuing this absurd discussion. Any further serious unlock requests can be addressed to stewards@wikimedia.org, noting they will only be taken into consideration if they do not contain further misinterpretations and personal attacks towards the involved community members. Savhñ 11:17, 20 December 2016 (UTC)
Based on recent events I hereby withdraw the offer that is linked to my talk page above. -- Tegel (Talk) 00:25, 29 December 2016 (UTC)
Retrieved from "https://meta.wikimedia.org/w/index.php?title=Steward_requests/Global/2016-12&oldid=24929310"