From Wikipedia, the free encyclopedia


Alex Neman

Alex Neman ( talk + · tag · contribs · deleted contribs · logs · filter log · block user · spi block · block log · CA · CheckUser( log· investigate · cuwiki)

29 January 2020

Suspected sockpuppets


Hello, the user Alex Neman which has been previously blocked is now suspected to be contributing as オートカー, giving the very similar edit patterns and edit summary. He has previously "announced" that he would retire from Wikipedia though. Need any actions? 114.5.211.196 ( talk) 13:02, 29 January 2020 (UTC) reply

Copied from my talk page at User talk:Dreamy Jazz/Archive 5#Another sockpuppet of Alex Neman. Posting here to centralise and as I won't be able to deal with it for a little bit. 13:10, 29 January 2020 (UTC) Dreamy Jazz 🎷 talk to me | my contributions 13:10, 29 January 2020 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments

  •  Confirmed,  Blocked and tagged ST47 ( talk) 16:56, 29 January 2020 (UTC) reply

30 January 2020

Suspected sockpuppets

Most probably the same IP user as Alex Neman (located in Surabaya, Indonesia, where he currently resided). Diff. See also 202.67.40.1 and 202.67.40.242. 114.5.211.196 ( talk) 11:07, 30 January 2020 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments

  • The IP edits are now stale. Closing. —  JJMC89( T· C) 05:51, 3 February 2020 (UTC) reply

31 January 2020

Suspected sockpuppets

Same as above. 182.30.204.161 ( talk) 15:51, 31 January 2020 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

The registered user looks like a WP:DUCK quacking in a megaphone to me. -- Java Hurricane 14:36, 2 February 2020 (UTC) reply

Clerk, CheckUser, and/or patrolling admin comments

  • Account already  Blocked and tagged.  IP blocked. —  JJMC89( T· C) 05:51, 3 February 2020 (UTC) reply

1 February 2020

Suspected sockpuppets

Same as above. 182.30.204.161 ( talk) 04:54, 2 February 2020 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments

  •  IP blocked —  JJMC89( T· C) 05:51, 3 February 2020 (UTC) reply


03 February 2020

Suspected sockpuppets


Well, I think the name and all of the edits at Suzuki Carry should be enough evidence.  Mr.choppers |  ✎  05:31, 3 February 2020 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments

  •  Blocked and tagged —  JJMC89( T· C) 05:51, 3 February 2020 (UTC) reply

3 February 2020

Suspected sockpuppets


Quite obvious. Just in case he uses this account again (he's already blocked on Indonesian Wikipedia). 182.30.204.161 ( talk) 08:16, 3 February 2020 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments

  • Originally, I closed this with no action with the reasoning "since there's no edits since 2010, there's no need to deal with it in 2020"; however, I noticed that this sockmaster has a habit of reviving decade-old sleeper accounts, e.g. [1]. I will make an exception in this case, but we should generally avoid reporting accounts that have not edited in years.  Blocked without tags. Mz7 ( talk) 08:29, 3 February 2020 (UTC) reply

3 February 2020

Suspected sockpuppets


Still messing with the Suzuki Carry gallery after 2-week protection, among other disruptive edits. Possible range-block required for all IPs. 182.30.204.161 ( talk) 16:10, 3 February 2020 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments

  • A range block was set for both ranges - closing. Mz7 ( talk) 20:05, 5 February 2020 (UTC) reply

4 February 2020

Suspected sockpuppets


Registered using Japanese name and reverting all of the edits. 182.30.204.161 ( talk) 06:20, 4 February 2020 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

WP:DUCK, we had another similar sockpuppet a few days back. -- Java Hurricane 06:55, 4 February 2020 (UTC) reply

Clerk, CheckUser, and/or patrolling admin comments

  • Both have been blocked, closing. Mz7 ( talk) 20:05, 5 February 2020 (UTC) reply

5 February 2020

Suspected sockpuppets


Same per above. 182.30.204.161 ( talk) 14:37, 5 February 2020 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Please unrevoke talk page and email access of Alex Neman ( talk) to make unblock request. So that I can edit using that account. 202.67.40.232 ( talk) 15:03, 5 February 2020 (UTC) reply

@ 202.67.40.232: Based on your actions lately (disruptive edits, clearly not here to build an encyclopedia, per history of articles edited appears to be evading block and sockpuppeting), I think it's nearly not possible for you to unblock your user page. Not that we want to keep you blocked, but look at your actions. 182.30.204.161 ( talk) 15:09, 5 February 2020 (UTC) reply
I wish that I still want to make good edits on Wikipedia. 202.67.40.232 ( talk) 15:12, 5 February 2020 (UTC) reply
@ 202.67.40.232: Just ask an admin to request an unblock, hope they will lift your block in the slightest. 182.30.204.161 ( talk) 15:17, 5 February 2020 (UTC) reply
And the IP has been rangeblocked. -- Java Hurricane 15:47, 5 February 2020 (UTC) reply

Clerk, CheckUser, and/or patrolling admin comments

  • Part of a range block - closing. Mz7 ( talk) 20:05, 5 February 2020 (UTC) reply

7 February 2020

Suspected sockpuppets


IP located in Surabaya, which is the same city as above IPs. 182.30.204.161 ( talk) 03:34, 7 February 2020 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments

  • Now stale, closing. Mz7 ( talk) 03:31, 10 February 2020 (UTC) reply

10 February 2020

Suspected sockpuppets


Restored previous edits of 202.67.40.232. 182.30.204.161 ( talk) 13:43, 10 February 2020 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments


information Administrator note IP blocked 3 months. Same as the range block. Dreamy Jazz 🎷 talk to me | my contributions 16:08, 10 February 2020 (UTC) reply

13 February 2020

Suspected sockpuppets

Same type of edits as previous IPs, e.g. in the Honda Mobilio article: diff by 103.44.37.150, diff by 202.67.46.23 and diff by カーアップローダー 182.30.204.161 ( talk) 23:49, 13 February 2020 (UTC) reply

Continuous editing with ever-changing IPs from the same location (Surabaya). Compare this, this and this Consider to block the 202.67.40.0/21, 202.67.46.0/22 and 114.5.241.0/22 ranges and protect the articles that have been edited. 182.30.204.161 ( talk) 16:48, 14 February 2020 (UTC) reply

Suspicious edit summary: diff. Another reversion: diff. Insisting that his edits are "good enough": diff. Range-block is the only option. 182.30.204.161 ( talk) 07:51, 15 February 2020 (UTC) reply

This and this. 182.30.204.161 ( talk) 01:27, 16 February 2020 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

182.30.204.161 Please stop reverting my edits. My edits are good enough. 114.142.169.18 ( talk) 05.14, 15 February 2020 (UTC)

Nope, you're avoiding the block. Unless you want to appeal the block, I will keep doing the same thing. It's that simple. 182.30.204.161 ( talk) 05:51, 15 February 2020 (UTC) reply

Clerk, CheckUser, and/or patrolling admin comments

Unless diffs are provided, this report will be closed.-- Bbb23 ( talk) 19:04, 13 February 2020 (UTC) reply

  • I've made 2 heavier rangeblocks. We'll have to see how things go for now. -- Amanda (aka DQ) 05:30, 16 February 2020 (UTC) reply

16 February 2020

Suspected sockpuppets

The contributions say it all. Already blocked in Indonesian Wikipedia. 125.166.61.80 ( talk) 15:32, 16 February 2020 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments


17 February 2020

Suspected sockpuppets

Keep doing edits that related to car images: diff. 125.166.61.80 ( talk) 05:45, 17 February 2020 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments


18 February 2020

Suspected sockpuppets

Keep doing edits that related to car images: diff. Other edits: this, this and this 180.244.231.134 ( talk) 14:28, 18 February 2020 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments

  • Insufficient evidence (only diffs of IPs). Closing. Bbb23 ( talk) 18:06, 18 February 2020 (UTC) reply

19 February 2020

Suspected sockpuppets

Changing most images in the Toyota Allion article: diff, which is similar case in Suzuki Carry article: diff. Uploader of the pictures is named as Alex Neman: one example. Like Ivanvector said, although his edits are not considered as vandalism, he sorely lacks competence. 180.244.231.134 ( talk) 16:25, 19 February 2020 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments


22 February 2020

Suspected sockpuppets

Registered from Japanese wiki: check this, similar to اليكس نيمان. Same edit pattern: diff1 and diff2. 180.244.231.134 ( talk) 23:56, 21 February 2020 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments

  • The puppet is now blocked. Closing. Bbb23 ( talk) 01:47, 22 February 2020 (UTC) reply

23 February 2020

Suspected sockpuppets

WP:DUCK. Usual editing pattern, usual pages, restoring blocked sockpuppet's edits. Looks like the sockmaster is using mobile IPs after getting rangeblocked on his PC IPs. Please rangeblock for a while. Java Hurricane 16:48, 23 February 2020 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments

  • Rangeblock not feasible, IP blocked, closing. qedk ( t c) 10:47, 24 February 2020 (UTC) reply
  • @ QEDK: You blocked 36.82.28.192 instead of 36.82.28.208. Was that intentional? ‐‐ 1997kB ( talk) 16:14, 26 February 2020 (UTC) reply
  • @ 1997kB: I have no clue how that happened... the innocent IP is now unblocked, no point blocking this as no more edits since, if they act up @ JavaHurricane: feel free to drop a note at my TP. -- qedk ( t c) 16:22, 26 February 2020 (UTC) reply

29 February 2020

Suspected sockpuppets

Very similar edit patterns: this with this, and this with this 182.30.85.63 ( talk) 16:05, 29 February 2020 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

The "technically indistinguishable" account has been blocked by Materialscientist after I reported the user on WP:AIV. It could have been blocked only on the basis of username in any case as it is "Alex Neman" written in Devanagari script (the one used for Hindi and most other Indian languages). -- Java Hurricane 16:06, 2 March 2020 (UTC) reply

And the original listed account above is "Alexander Neman" in Chinese. ωικιωαrrιor ᑫᑫ1ᑫ 16:16, 4 March 2020 (UTC) reply

Clerk, CheckUser, and/or patrolling admin comments

Dreamy Jazz, there are a ton of accounts on this range, so a sleeper check is a good idea. Typically, if a master is repeatedly reported on behavioural evidence and a CU has not been run recently in the SPI archive, it it good to request a CU look at it. TonyBallioni ( talk) 00:41, 1 March 2020 (UTC) reply
TonyBallioni, sure thanks for the advice. I'll keep that in mind. Dreamy Jazz 🎷 talk to me | my contributions 00:42, 1 March 2020 (UTC) reply

09 March 2020

Suspected sockpuppets

IP geolocates to Surabaya, which is already known to be the city of residence of the sockmaster. Moreover, the IP is taking an interest in pages edited by the master. Quack!   Sounds like a duck quacking into a megaphone to me Java Hurricane 11:58, 9 March 2020 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments

  • The /16 doesn't seem to have much traffic by Alex at this time, and therefore, it's not appropriate to proceed with a block. We may need to head towards edit filters. -- Amanda (aka DQ) 13:50, 9 March 2020 (UTC) reply

19 March 2020

Suspected sockpuppets

On Daihatsu Ayla: editing in simple English structure like every other edit Alex Neman did. @ JavaHurricane: 182.30.214.245 ( talk) 09:05, 19 March 2020 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

All edits reverted. Asking for CU to check for sleepers. -- Java Hurricane 09:40, 19 March 2020 (UTC) reply

Clerk, CheckUser, and/or patrolling admin comments


23 March 2020

Suspected sockpuppets

On Daihatsu Ayla: Restored previous IP (have been rangeblocked) edits diff. IP located in Surabaya 182.30.12.31 ( talk) 13:13, 23 March 2020 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments

  • IP now blocked as part of a range block. Closing. Bbb23 ( talk) 13:54, 31 March 2020 (UTC) reply

4 May 2020

Suspected sockpuppets

@ JavaHurricane: IP located in Surabaya and performed similar edit styles in Suzuki Carry, Adland, and other articles. 182.30.133.131 ( talk) 07:28, 4 May 2020 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

This does not seem like Alex. The IP's main interest seems to be music rather than automobiles, but I am not sure that it is not Alex either. Java Hurricane 07:59, 4 May 2020 (UTC) reply

@ JavaHurricane: The edit histories for J.CO Donuts, Wewe Gombel and Adland probably show the evidence though. 182.30.133.131 ( talk) 08:07, 4 May 2020 (UTC) reply
Yeah, I got it wrong. Looks like a WP:DUCK case. Java Hurricane 08:51, 4 May 2020 (UTC) reply
All edits have been reverted per WP:BANREVERT, as Alex Neman is currently under a WP:3X ban from editing Wikipedia. Java Hurricane 08:58, 4 May 2020 (UTC) reply

Clerk, CheckUser, and/or patrolling admin comments

  • The IP edits aren't recent enogh to block. —  JJMC89( T· C) 07:47, 5 May 2020 (UTC) reply

9 May 2020

Suspected sockpuppets

@ JavaHurricane: IP located in Jakarta, but the editing patterns are similar to previous IPs (editing gallery formats). 182.30.133.131 ( talk) 11:13, 9 May 2020 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments


30 May 2020

Suspected sockpuppets

IP located in Surabaya (hometown of Alex), and his edits are quite obvious. 182.30.137.85 ( talk) 11:54, 30 May 2020 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments


1 July 2020

Suspected sockpuppets

@ Favonian: IP located in Surabaya (hometown of Alex), and WP:BMB. 182.30.80.146 ( talk) 04:55, 1 July 2020 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments

  •  Additional information needed - Need more information - I see that these IPs are from the sockmaster's location and have an overlap in interest on various cars, but not clear how this is characteristic of them. I also note that the ranges these IPs are from ( Special:Contributions/116.206.40.0/24 and Special:Contributions/202.67.40.0/23) have a decent amount of other activity; I'm hesitant to rangeblock, and since this appears to be a dynamic IP I doubt per-IP blocks will be very effective. GeneralNotability ( talk) 00:38, 7 July 2020 (UTC) reply
  • I've redone my original range blocks for longer. -- Amanda (aka DQ) 02:20, 7 July 2020 (UTC) reply

13 August 2020

Suspected sockpuppets

IP located in Surabaya (see past cases), and editing patterns are also familiar. 182.30.204.77 ( talk) 04:11, 13 August 2020 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments


13 December 2020

Suspected sockpuppets

Three-time edit (two of them were reverts) regarding car galleries in Honda Accord article ( diff 1, diff 2, diff 3). All IPs located in Surabaya (see past cases). The 140.0.0.0/16 range had also been blocked before for 6 months. *Update: 3 more IPs has been added above. 182.30.143.27 ( talk) 09:32, 18 December 2020 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments

  • Looks like Neman, all right. Blocked 140.0.0.0/16 and 182.1.99.6/19 for six months each. AmandaNP has already hit 116.206.40.0/23 with a rangeblock as well. Closing. GeneralNotability ( talk) 22:29, 20 December 2020 (UTC) reply

21 December 2020

Suspected sockpuppets

Obvious block evasion. The "182.1.x.x" range is a bit tricky. 182.30.143.27 ( talk) 13:21, 21 December 2020 (UTC) reply

Insisting on changing car images for no strong reasons, as always. IP located in Surabaya. Andra Febrian ( talk) 16:38, 7 January 2021 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims. The user appears to be block evading by using a proxy. In addition to this, all of the IPs appear to come from Singapore. Maybe block these existing IPs and search for similar edits, or IPs used to make similar edits from Singapore. EGL1234 ( talk) 15:48, 10 January 2021 (UTC) reply

Clerk, CheckUser, and/or patrolling admin comments

  •  Clerk note: Not clear there's anything useful to do here. None of these IPs have edited in weeks, and I'd have to block 182.1.64.0/18 to do anything useful, which is way too wide a range to consider. If you could identify some specific pages that are common targets, semi-protection might be a better tool. Closing with no action taken. -- RoySmith (talk) 21:08, 4 February 2021 (UTC) reply

8 April 2021

Suspected sockpuppets

Back and forth changing some images of their own (mainly infobox ones) without prior discussions: [2], [3] 182.30.82.165 ( talk) 02:43, 8 April 2021 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments

  • Range is Special:Contributions/158.140.187.192/26. Cabayi ( talk) 08:16, 9 April 2021 (UTC) reply
  • CheckUser requested and endorsed by clerk - There's no doubt that a good chunk (maybe half) of the traffic on 158.140.187.192/26 is Alex, but there's also a lot that looks legit. It's no wonder this case has languished on the open queue for so long. I know /26 is quite narrow, but I'm still loathe to block if half the traffic is legit. I'm hoping CU can provide some insight on the wisdom of a year-long range block. -- RoySmith (talk) 01:55, 4 June 2021 (UTC) reply
    • @ RoySmith: I'm not terribly familiar with this case and I don't see any info on cuwiki, so I really can't tell which user on the range is the target. There are many, as you suspected, and several who I don't think are related (including one very old account) match the behaviour I can glean from the archives. From what I've seen there, Alex Neman is a person with access to many internet connections and/or an ISP with loose range assignments, so if they're blocked here they'll quickly move on to another. For that reason I'd recommend against a long block. But if you think the behaviour matches then a block is warranted. Ivanvector ( Talk/ Edits) 15:46, 5 June 2021 (UTC) reply
    • @ AmandaNP: pinging you for a second opinion, you seem to be most familiar with this case recently. Roy: Amanda's not around a lot, don't feel like you need to wait. Ivanvector ( Talk/ Edits) 15:49, 5 June 2021 (UTC) reply
      • I do see a crap ton of colleterial. If it's only anon edits that are disruptive then maybe a block anon only but allowing account creation? @ Ivanvector: -- Amanda (aka DQ) 16:41, 5 June 2021 (UTC) reply
        • Sorry, yes, I assumed since RoySmith was talking about a rangeblock that it would be anon-only. Don't hardblock this range. Ivanvector ( Talk/ Edits) 16:49, 5 June 2021 (UTC) reply
          Ivanvector, That falls into the category of "Things I expected to hear but hoped I was wrong". I'm going to close this with no action, but take a look at spreading some semi-protection around. -- RoySmith (talk) 22:16, 5 June 2021 (UTC) reply
          • @ RoySmith: just in case I'm in too deep and used unrecognized checkuser jargon there, by "hardblock" I meant checking the "Apply block to logged-in users from this IP address" box in the block screen. I realize now that "hardblock" means something else in terms of the block policy, and I'll try not to do that again. I think a (anon-only) rangeblock is warranted, if you think the behaviour matches, and I think Amanda was agreeing with me on that. Ivanvector ( Talk/ Edits) 00:31, 6 June 2021 (UTC) reply
            Ivanvector, Yes, I understood what you meant by hardblock. I was mostly considering what you said about Alex appearing to have many internet connections available so a short block here (say, a week or a month) would just transiently move them to another connection, which seemed kind of pointless. -- RoySmith (talk) 00:57, 6 June 2021 (UTC) reply

17 June 2021

Suspected sockpuppets

Same editing pattern as previous IPs, such as changing gallery parameters. 182.29.1.237 ( talk) 04:56, 17 June 2021 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments

  • There's not enough to go on here. Which "previous IP"? There's been so many. And this report filed by an IP, so I can't even have a conversation about it. I'm going to close this with no action taken. As I mentioned back in April, this guy is using so many IPs, blocking is pointless. If you can identify specific pages that have been frequent targets, WP:RFPP will probably be more useful. -- RoySmith (talk) 18:41, 11 July 2021 (UTC) reply

10 January 2023

Suspected sockpuppets

This is very likely a sockpuppet of Alex Neman. His location (Surabaya, Indonesia) and editing behaviour (mostly on automobiles) is very suspiciously similar to Alex's. Very recently he was editing under another sockpuppet IP (158.140.167.100) until it was banned last month. Surely something can be done to prevent this guy from continuously creating new IP's to edit under? He's very disruptive with his constant unexplained edits. Democfest ( talk) 09:20, 10 January 2023 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments

Callanecc ( talkcontribslogs) 11:40, 10 January 2023 (UTC) reply

11 January 2023

Suspected sockpuppets

Again, same user making disruptive edits on the same automotive pages. Same location (Surabaya, Indonesia) again. Blatantly obvious. Was literally banned again yesterday under 202.67.40.253 Democfest ( talk) 04:18, 11 January 2023 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments


13 January 2023

Suspected sockpuppets

Not completely certain if these IPs are sockpuppets of Alex; slightly different location, albeit still very close to their original city (Surabaya, Indonesia) but their editing pattern and behaviour (again, predominantly on articles about Japanese automobiles) is very very similar, almost identical to their previous banned sockpuppet accounts. Also, they seem to have popped up immediately after their previous IP was banned. Worth a check Democfest ( talk) 01:59, 13 January 2023 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments


13 January 2023

Suspected sockpuppets

This is definitely him. Same location (Surabaya) and same editing behaviour Democfest ( talk) 02:09, 13 January 2023 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments

  • Blocked for 1 week. I haven't blocked the range yet as they've only used that IP. Closing. Callanecc ( talkcontribslogs) 11:10, 13 January 2023 (UTC) reply

18 January 2023

Suspected sockpuppets

Slightly different locations but still very close in proximity to Alex's original location (Surabaya). Very similar editing behaviour - constant reverts and disruptive. All suspiciously popped up after previous IPs were banned. Worth a check Democfest ( talk) 06:42, 18 January 2023 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments


23 January 2023

Suspected sockpuppets

Not completely certain about this one but his editing behaviour is again very similar to Alex's, focusing predominantly on Japanese/korean cars and having the same erratic, mass edits everyday. Suspiciously restores edits of Alex's previously banned sockpuppet IP's which leads me to believe it could be the same guy behind this account. Democfest ( talk) 06:48, 23 January 2023 (UTC) reply

In this instance, he keeps insisting on replacing the existing image in the "fifth generation" section infobox of the Honda Odyssey (international) article. Alex's previously banned IP ( 114.79.23.176) removed it first on the 18th January for no particular reason. The infobox image was restored shortly after, before AutomobileFan2023 came in to remove the image from the infobox once again on the 22nd January. Bear in mind that Alex was continuously doing this on his other IP accounts before; 18th January, 18th Janaury as a couple of references. For a completely new account to simply repeat and continue the behaviour of previously banned IP accounts is very suspicious
Also, the general editing behaviour of AutomobileFan2023 suggests that it could quite easily be another one of Alex's sockpuppet accounts. Most suspiciously, the account has the exact same interest in editing only Japanese/Korean car articles, and it seemed to have popped up right after after a massive IP range block was applied to prevent Alex from using new IP accounts. Democfest ( talk) 03:05, 25 January 2023 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments


26 January 2023

Suspected sockpuppets

Same location (Surabaya) and same editing behaviour - continuing on changing images for no given reason Democfest ( talk) 10:21, 26 January 2023 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments


27 January 2023

Suspected sockpuppets

Same location (Surabaya), same editing behaviour and patterns Democfest ( talk) 01:26, 27 January 2023 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments


27 January 2023

Suspected sockpuppets

Same location (Surabaya), same disruptive editing behaviour on the same pages Democfest ( talk) 11:38, 27 January 2023 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments


02 February 2023

Suspected sockpuppets

Location is close in proximity to Alex's original city of Surabaya, very similar editing behaviour, popped up not too long after his previous sockpuppet IPs were banned Democfest ( talk) 22:25, 2 February 2023 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments


05 February 2023

Suspected sockpuppets

Same location (Surabaya), same editing behaviour Democfest ( talk) 03:23, 5 February 2023 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments


07 February 2023

Suspected sockpuppets

All in close proximity to original location of Surabaya, very similar editing behaviour Democfest ( talk) 05:36, 7 February 2023 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments


13 February 2023

Suspected sockpuppets

Same location (Surabaya), same editing behaviour Democfest ( talk) 02:59, 13 February 2023 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments


13 February 2023

Suspected sockpuppets

Similar location still close in proximity to original city (Surabaya), same editing patterns and behaviour Democfest ( talk) 14:08, 13 February 2023 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments


19 February 2023

Suspected sockpuppets

Similar/same locations as Alex's original location, same repetitive disruptive editing behaviour on the same pages Democfest ( talk) 11:06, 19 February 2023 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments

  • These are all 🦆 🦆. Unfortunately, the editing spread widely across the range 112.215.241.0/24 suggests that blocking individual IP addresses in that range might possibly just result in the editor moving to another one, whereas blocking the whole range is out of the question, in view of collateral damage. I have therefore put some time into checking all recent editing in that range, and I have placed range blocks on smaller ranges which cover all the editing I have seen in that range by Alex Neman, but no editing by anyone else for at least several months, and in at least one case none for well over a year. I have also done the same for the one other IP address listed in the 112.215.0.0/16 range. At present I don't have time to do similar checking for the other IP addresses listed, but maybe someone else can do it, or I may do it when I do have time. JBW ( talk) 10:36, 22 February 2023 (UTC) reply
  • I have now looked at the range 140.213.0.0/16, which I thought would be easier, because there are only 2 IP addresses listed above, but I found another 6 (140.213.42.124, 140.213.44.252, 140.213.56.13, 140.213.56.15, 140.213.56.217, 140.213.59.128), and there may be more. 140.213.42.0/24 is already blocked by Callanecc , which has just been followed by moving to other IP addresses, and unfortunately that is probably going to continue to happen: the best we can hope to do is slightly slow the editor down by forcing them to keep finding new IP addresses to move to. I have blocked various subranges of 140.213.0.0/16,for times varying from 2 weeks to 3 months, depending on the amount of other editing in the ranges, and therefore the likely amount of collateral damage. The other IP addresses in the list provided above by Democfest were easier to deal with, because there has never been any other editing in the range 115.178.225.248/30, so I was able to block that without worries. (That is assuming that a few edits about noodles were the same person. However, those edits are from one of the IP addresses used by this editor and never before used by anyone, they started 4 minutes after other edits from the same editor on the same IP address, and were followed less than an hour later by more edits from the same person in the same range, so despite the totally different subject matter, I am totally confident that it is the same person.)
  • Since all the IP addresses listed are now covered by various range blocks, I am closing this investigation. JBW ( talk) 15:20, 22 February 2023 (UTC) reply
  • (For what it is worth, I have now seen more noodle-related editing by another one of Alex Neman's IP addresses, on one of the same articles as the one mentioned above, giving yet further evidence that it's the same person. JBW ( talk) 15:29, 22 February 2023 (UTC)) reply

23 February 2023

Suspected sockpuppets

Again - same behaviour and same interest in the same pages. Similar locations as well Democfest ( talk) 02:39, 23 February 2023 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments


28 February 2023

Suspected sockpuppets

Same/similar locations, same editing behaviour on the same pages Democfest ( talk) 01:28, 28 February 2023 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments

  • Lets see. Sorted 12 IPv4 addresses:
115.178.225.67
115.178.225.132
115.178.225.154
115.178.227.127
115.178.227.163
115.178.227.193
115.178.245.150
115.178.246.150
115.178.246.166
115.178.246.170
115.178.249.10
115.178.255.146
Total
affected
Affected
addresses
Given
addresses
Range Contribs
8192 8192 12 115.178.224.0/19 contribs
5120 1024 6 115.178.224.0/22 contribs
4096 6 115.178.240.0/20 contribs
3584 256 3 115.178.225.0/24 contribs
256 3 115.178.227.0/24 contribs
1024 4 115.178.244.0/22 contribs
2048 2 115.178.248.0/21 contribs

115.178.224.0/19 ( block range · block log ( global) · WHOIS (partial)) blocked for one month. Closing. DatGuy Talk Contribs 21:57, 28 February 2023 (UTC) reply


01 March 2023

Suspected sockpuppets

Very similar behaviour, similar location Democfest ( talk) 00:43, 1 March 2023 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments

  • Closing as IP has gone inactive. Spicy ( talk) 15:25, 10 March 2023 (UTC) reply

22 March 2023

Suspected sockpuppets

Same location, same editing behaviour Democfest ( talk) 00:27, 22 March 2023 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

It looks like the edits under 158.140.167.0/24 ( talk · contribs · WHOIS) are overwhelmingly this user, and the IP changes on a daily basis. Is a rangeblock possible here? -- Sable232 ( talk) 21:34, 30 March 2023 (UTC) reply

This guy is a menace. It's both hilarious and pathetic that admins have almost zero power to rangeblock and prevent him from simply creating an infinite number of alternative accounts. Getting blocked is of zero consequence to Alex - Democfest ( talk) 10:23, 31 March 2023 (UTC) reply
Why you always revert my edits? 158.140.167.0 ( talk) 10:42, 31 March 2023 (UTC) reply
Why are you continuously creating new sockpuppet accounts to edit with Alex? You've been banned for a reason, and creating new accounts to get around this will not be tolerated Democfest ( talk) 12:53, 31 March 2023 (UTC) reply

Clerk, CheckUser, and/or patrolling admin comments


01 April 2023

Suspected sockpuppets

Either a sock or a meatpuppet, editing many of the same articles as the sockmaster and IPs, and reinstating the IPs' reverted edits (e.g. [4], [5], [6], [7]). Sable232 ( talk) 00:17, 1 April 2023 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments

  • I am quite confident this is not the same person - if you look at their uploads on Commons, where they are a very established editor, they are consistently taken using different cameras in a different country from Neman's. Editors are allowed to restore edits by a blocked user if they feel they are improvements and are acting on their own accord. However, I would caution Dinkun Chen that if they are doing this because Alex Neman has asked them to, they are violating WP:PROXYING which may lead to sanctions if continued. Closing. Thanks, Spicy ( talk) 18:56, 8 April 2023 (UTC) reply

01 April 2023

Suspected sockpuppets

Defends his own sockpuppet IP accounts and completely outs himself by admitting that he created this account to get involved Democfest ( talk) 15:16, 1 April 2023 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments


01 April 2023

Suspected sockpuppets

Similar location, same behaviour Democfest ( talk) 15:26, 1 April 2023 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments


01 April 2023

Suspected sockpuppets

Using a sockpuppet account to spam messages on talk pages Democfest ( talk) 15:55, 1 April 2023 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments


22 April 2023

Suspected sockpuppets

Significantly different IP addresses but suspiciously still the same editing behaviour. Still the same country as well. Worth a check. It should be noted that like the previous sets of IP addresses Alex used for sockpuppetry, there are probably dozens more out there that haven't been reported yet. It's simply impossible to crack down on all of them Democfest ( talk) 02:16, 22 April 2023 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

There's been a lot of editing from the 2400:9800:0:0:0:0:0:0/32 ( talk · contribs · WHOIS) range lately. It's a wide range though, and it's hard to tell how much possible collateral impact there would be from a rangeblock. This user seems to be pretty adept at changing IPs too. -- Sable232 ( talk) 15:24, 22 April 2023 (UTC) reply

Honestly at this point, i think we just have to accept that collateral blocks are inevitable and have to be accepted. This guy is playing the system like a fiddle. Democfest ( talk) 07:15, 24 April 2023 (UTC) reply

Clerk, CheckUser, and/or patrolling admin comments

  • The IPs haven't edited in weeks, and I'm unwilling to block that wide a range without a compelling analysis. Closing. Bbb23 ( talk) 16:08, 13 May 2023 (UTC) reply

07 September 2023

Suspected sockpuppets

Same/similar location, similar editing behaviour on similar style of pages (automotive) Democfest ( talk) 03:37, 7 September 2023 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments


08 September 2023

Suspected sockpuppets

Same editing behaviour on the same automotive pages. Uses his own wikimedia uploaded images Democfest ( talk) 08:04, 8 September 2023 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments


From Wikipedia, the free encyclopedia


Alex Neman

Alex Neman ( talk + · tag · contribs · deleted contribs · logs · filter log · block user · spi block · block log · CA · CheckUser( log· investigate · cuwiki)

29 January 2020

Suspected sockpuppets


Hello, the user Alex Neman which has been previously blocked is now suspected to be contributing as オートカー, giving the very similar edit patterns and edit summary. He has previously "announced" that he would retire from Wikipedia though. Need any actions? 114.5.211.196 ( talk) 13:02, 29 January 2020 (UTC) reply

Copied from my talk page at User talk:Dreamy Jazz/Archive 5#Another sockpuppet of Alex Neman. Posting here to centralise and as I won't be able to deal with it for a little bit. 13:10, 29 January 2020 (UTC) Dreamy Jazz 🎷 talk to me | my contributions 13:10, 29 January 2020 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments

  •  Confirmed,  Blocked and tagged ST47 ( talk) 16:56, 29 January 2020 (UTC) reply

30 January 2020

Suspected sockpuppets

Most probably the same IP user as Alex Neman (located in Surabaya, Indonesia, where he currently resided). Diff. See also 202.67.40.1 and 202.67.40.242. 114.5.211.196 ( talk) 11:07, 30 January 2020 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments

  • The IP edits are now stale. Closing. —  JJMC89( T· C) 05:51, 3 February 2020 (UTC) reply

31 January 2020

Suspected sockpuppets

Same as above. 182.30.204.161 ( talk) 15:51, 31 January 2020 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

The registered user looks like a WP:DUCK quacking in a megaphone to me. -- Java Hurricane 14:36, 2 February 2020 (UTC) reply

Clerk, CheckUser, and/or patrolling admin comments

  • Account already  Blocked and tagged.  IP blocked. —  JJMC89( T· C) 05:51, 3 February 2020 (UTC) reply

1 February 2020

Suspected sockpuppets

Same as above. 182.30.204.161 ( talk) 04:54, 2 February 2020 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments

  •  IP blocked —  JJMC89( T· C) 05:51, 3 February 2020 (UTC) reply


03 February 2020

Suspected sockpuppets


Well, I think the name and all of the edits at Suzuki Carry should be enough evidence.  Mr.choppers |  ✎  05:31, 3 February 2020 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments

  •  Blocked and tagged —  JJMC89( T· C) 05:51, 3 February 2020 (UTC) reply

3 February 2020

Suspected sockpuppets


Quite obvious. Just in case he uses this account again (he's already blocked on Indonesian Wikipedia). 182.30.204.161 ( talk) 08:16, 3 February 2020 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments

  • Originally, I closed this with no action with the reasoning "since there's no edits since 2010, there's no need to deal with it in 2020"; however, I noticed that this sockmaster has a habit of reviving decade-old sleeper accounts, e.g. [1]. I will make an exception in this case, but we should generally avoid reporting accounts that have not edited in years.  Blocked without tags. Mz7 ( talk) 08:29, 3 February 2020 (UTC) reply

3 February 2020

Suspected sockpuppets


Still messing with the Suzuki Carry gallery after 2-week protection, among other disruptive edits. Possible range-block required for all IPs. 182.30.204.161 ( talk) 16:10, 3 February 2020 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments

  • A range block was set for both ranges - closing. Mz7 ( talk) 20:05, 5 February 2020 (UTC) reply

4 February 2020

Suspected sockpuppets


Registered using Japanese name and reverting all of the edits. 182.30.204.161 ( talk) 06:20, 4 February 2020 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

WP:DUCK, we had another similar sockpuppet a few days back. -- Java Hurricane 06:55, 4 February 2020 (UTC) reply

Clerk, CheckUser, and/or patrolling admin comments

  • Both have been blocked, closing. Mz7 ( talk) 20:05, 5 February 2020 (UTC) reply

5 February 2020

Suspected sockpuppets


Same per above. 182.30.204.161 ( talk) 14:37, 5 February 2020 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Please unrevoke talk page and email access of Alex Neman ( talk) to make unblock request. So that I can edit using that account. 202.67.40.232 ( talk) 15:03, 5 February 2020 (UTC) reply

@ 202.67.40.232: Based on your actions lately (disruptive edits, clearly not here to build an encyclopedia, per history of articles edited appears to be evading block and sockpuppeting), I think it's nearly not possible for you to unblock your user page. Not that we want to keep you blocked, but look at your actions. 182.30.204.161 ( talk) 15:09, 5 February 2020 (UTC) reply
I wish that I still want to make good edits on Wikipedia. 202.67.40.232 ( talk) 15:12, 5 February 2020 (UTC) reply
@ 202.67.40.232: Just ask an admin to request an unblock, hope they will lift your block in the slightest. 182.30.204.161 ( talk) 15:17, 5 February 2020 (UTC) reply
And the IP has been rangeblocked. -- Java Hurricane 15:47, 5 February 2020 (UTC) reply

Clerk, CheckUser, and/or patrolling admin comments

  • Part of a range block - closing. Mz7 ( talk) 20:05, 5 February 2020 (UTC) reply

7 February 2020

Suspected sockpuppets


IP located in Surabaya, which is the same city as above IPs. 182.30.204.161 ( talk) 03:34, 7 February 2020 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments

  • Now stale, closing. Mz7 ( talk) 03:31, 10 February 2020 (UTC) reply

10 February 2020

Suspected sockpuppets


Restored previous edits of 202.67.40.232. 182.30.204.161 ( talk) 13:43, 10 February 2020 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments


information Administrator note IP blocked 3 months. Same as the range block. Dreamy Jazz 🎷 talk to me | my contributions 16:08, 10 February 2020 (UTC) reply

13 February 2020

Suspected sockpuppets

Same type of edits as previous IPs, e.g. in the Honda Mobilio article: diff by 103.44.37.150, diff by 202.67.46.23 and diff by カーアップローダー 182.30.204.161 ( talk) 23:49, 13 February 2020 (UTC) reply

Continuous editing with ever-changing IPs from the same location (Surabaya). Compare this, this and this Consider to block the 202.67.40.0/21, 202.67.46.0/22 and 114.5.241.0/22 ranges and protect the articles that have been edited. 182.30.204.161 ( talk) 16:48, 14 February 2020 (UTC) reply

Suspicious edit summary: diff. Another reversion: diff. Insisting that his edits are "good enough": diff. Range-block is the only option. 182.30.204.161 ( talk) 07:51, 15 February 2020 (UTC) reply

This and this. 182.30.204.161 ( talk) 01:27, 16 February 2020 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

182.30.204.161 Please stop reverting my edits. My edits are good enough. 114.142.169.18 ( talk) 05.14, 15 February 2020 (UTC)

Nope, you're avoiding the block. Unless you want to appeal the block, I will keep doing the same thing. It's that simple. 182.30.204.161 ( talk) 05:51, 15 February 2020 (UTC) reply

Clerk, CheckUser, and/or patrolling admin comments

Unless diffs are provided, this report will be closed.-- Bbb23 ( talk) 19:04, 13 February 2020 (UTC) reply

  • I've made 2 heavier rangeblocks. We'll have to see how things go for now. -- Amanda (aka DQ) 05:30, 16 February 2020 (UTC) reply

16 February 2020

Suspected sockpuppets

The contributions say it all. Already blocked in Indonesian Wikipedia. 125.166.61.80 ( talk) 15:32, 16 February 2020 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments


17 February 2020

Suspected sockpuppets

Keep doing edits that related to car images: diff. 125.166.61.80 ( talk) 05:45, 17 February 2020 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments


18 February 2020

Suspected sockpuppets

Keep doing edits that related to car images: diff. Other edits: this, this and this 180.244.231.134 ( talk) 14:28, 18 February 2020 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments

  • Insufficient evidence (only diffs of IPs). Closing. Bbb23 ( talk) 18:06, 18 February 2020 (UTC) reply

19 February 2020

Suspected sockpuppets

Changing most images in the Toyota Allion article: diff, which is similar case in Suzuki Carry article: diff. Uploader of the pictures is named as Alex Neman: one example. Like Ivanvector said, although his edits are not considered as vandalism, he sorely lacks competence. 180.244.231.134 ( talk) 16:25, 19 February 2020 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments


22 February 2020

Suspected sockpuppets

Registered from Japanese wiki: check this, similar to اليكس نيمان. Same edit pattern: diff1 and diff2. 180.244.231.134 ( talk) 23:56, 21 February 2020 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments

  • The puppet is now blocked. Closing. Bbb23 ( talk) 01:47, 22 February 2020 (UTC) reply

23 February 2020

Suspected sockpuppets

WP:DUCK. Usual editing pattern, usual pages, restoring blocked sockpuppet's edits. Looks like the sockmaster is using mobile IPs after getting rangeblocked on his PC IPs. Please rangeblock for a while. Java Hurricane 16:48, 23 February 2020 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments

  • Rangeblock not feasible, IP blocked, closing. qedk ( t c) 10:47, 24 February 2020 (UTC) reply
  • @ QEDK: You blocked 36.82.28.192 instead of 36.82.28.208. Was that intentional? ‐‐ 1997kB ( talk) 16:14, 26 February 2020 (UTC) reply
  • @ 1997kB: I have no clue how that happened... the innocent IP is now unblocked, no point blocking this as no more edits since, if they act up @ JavaHurricane: feel free to drop a note at my TP. -- qedk ( t c) 16:22, 26 February 2020 (UTC) reply

29 February 2020

Suspected sockpuppets

Very similar edit patterns: this with this, and this with this 182.30.85.63 ( talk) 16:05, 29 February 2020 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

The "technically indistinguishable" account has been blocked by Materialscientist after I reported the user on WP:AIV. It could have been blocked only on the basis of username in any case as it is "Alex Neman" written in Devanagari script (the one used for Hindi and most other Indian languages). -- Java Hurricane 16:06, 2 March 2020 (UTC) reply

And the original listed account above is "Alexander Neman" in Chinese. ωικιωαrrιor ᑫᑫ1ᑫ 16:16, 4 March 2020 (UTC) reply

Clerk, CheckUser, and/or patrolling admin comments

Dreamy Jazz, there are a ton of accounts on this range, so a sleeper check is a good idea. Typically, if a master is repeatedly reported on behavioural evidence and a CU has not been run recently in the SPI archive, it it good to request a CU look at it. TonyBallioni ( talk) 00:41, 1 March 2020 (UTC) reply
TonyBallioni, sure thanks for the advice. I'll keep that in mind. Dreamy Jazz 🎷 talk to me | my contributions 00:42, 1 March 2020 (UTC) reply

09 March 2020

Suspected sockpuppets

IP geolocates to Surabaya, which is already known to be the city of residence of the sockmaster. Moreover, the IP is taking an interest in pages edited by the master. Quack!   Sounds like a duck quacking into a megaphone to me Java Hurricane 11:58, 9 March 2020 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments

  • The /16 doesn't seem to have much traffic by Alex at this time, and therefore, it's not appropriate to proceed with a block. We may need to head towards edit filters. -- Amanda (aka DQ) 13:50, 9 March 2020 (UTC) reply

19 March 2020

Suspected sockpuppets

On Daihatsu Ayla: editing in simple English structure like every other edit Alex Neman did. @ JavaHurricane: 182.30.214.245 ( talk) 09:05, 19 March 2020 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

All edits reverted. Asking for CU to check for sleepers. -- Java Hurricane 09:40, 19 March 2020 (UTC) reply

Clerk, CheckUser, and/or patrolling admin comments


23 March 2020

Suspected sockpuppets

On Daihatsu Ayla: Restored previous IP (have been rangeblocked) edits diff. IP located in Surabaya 182.30.12.31 ( talk) 13:13, 23 March 2020 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments

  • IP now blocked as part of a range block. Closing. Bbb23 ( talk) 13:54, 31 March 2020 (UTC) reply

4 May 2020

Suspected sockpuppets

@ JavaHurricane: IP located in Surabaya and performed similar edit styles in Suzuki Carry, Adland, and other articles. 182.30.133.131 ( talk) 07:28, 4 May 2020 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

This does not seem like Alex. The IP's main interest seems to be music rather than automobiles, but I am not sure that it is not Alex either. Java Hurricane 07:59, 4 May 2020 (UTC) reply

@ JavaHurricane: The edit histories for J.CO Donuts, Wewe Gombel and Adland probably show the evidence though. 182.30.133.131 ( talk) 08:07, 4 May 2020 (UTC) reply
Yeah, I got it wrong. Looks like a WP:DUCK case. Java Hurricane 08:51, 4 May 2020 (UTC) reply
All edits have been reverted per WP:BANREVERT, as Alex Neman is currently under a WP:3X ban from editing Wikipedia. Java Hurricane 08:58, 4 May 2020 (UTC) reply

Clerk, CheckUser, and/or patrolling admin comments

  • The IP edits aren't recent enogh to block. —  JJMC89( T· C) 07:47, 5 May 2020 (UTC) reply

9 May 2020

Suspected sockpuppets

@ JavaHurricane: IP located in Jakarta, but the editing patterns are similar to previous IPs (editing gallery formats). 182.30.133.131 ( talk) 11:13, 9 May 2020 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments


30 May 2020

Suspected sockpuppets

IP located in Surabaya (hometown of Alex), and his edits are quite obvious. 182.30.137.85 ( talk) 11:54, 30 May 2020 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments


1 July 2020

Suspected sockpuppets

@ Favonian: IP located in Surabaya (hometown of Alex), and WP:BMB. 182.30.80.146 ( talk) 04:55, 1 July 2020 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments

  •  Additional information needed - Need more information - I see that these IPs are from the sockmaster's location and have an overlap in interest on various cars, but not clear how this is characteristic of them. I also note that the ranges these IPs are from ( Special:Contributions/116.206.40.0/24 and Special:Contributions/202.67.40.0/23) have a decent amount of other activity; I'm hesitant to rangeblock, and since this appears to be a dynamic IP I doubt per-IP blocks will be very effective. GeneralNotability ( talk) 00:38, 7 July 2020 (UTC) reply
  • I've redone my original range blocks for longer. -- Amanda (aka DQ) 02:20, 7 July 2020 (UTC) reply

13 August 2020

Suspected sockpuppets

IP located in Surabaya (see past cases), and editing patterns are also familiar. 182.30.204.77 ( talk) 04:11, 13 August 2020 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments


13 December 2020

Suspected sockpuppets

Three-time edit (two of them were reverts) regarding car galleries in Honda Accord article ( diff 1, diff 2, diff 3). All IPs located in Surabaya (see past cases). The 140.0.0.0/16 range had also been blocked before for 6 months. *Update: 3 more IPs has been added above. 182.30.143.27 ( talk) 09:32, 18 December 2020 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments

  • Looks like Neman, all right. Blocked 140.0.0.0/16 and 182.1.99.6/19 for six months each. AmandaNP has already hit 116.206.40.0/23 with a rangeblock as well. Closing. GeneralNotability ( talk) 22:29, 20 December 2020 (UTC) reply

21 December 2020

Suspected sockpuppets

Obvious block evasion. The "182.1.x.x" range is a bit tricky. 182.30.143.27 ( talk) 13:21, 21 December 2020 (UTC) reply

Insisting on changing car images for no strong reasons, as always. IP located in Surabaya. Andra Febrian ( talk) 16:38, 7 January 2021 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims. The user appears to be block evading by using a proxy. In addition to this, all of the IPs appear to come from Singapore. Maybe block these existing IPs and search for similar edits, or IPs used to make similar edits from Singapore. EGL1234 ( talk) 15:48, 10 January 2021 (UTC) reply

Clerk, CheckUser, and/or patrolling admin comments

  •  Clerk note: Not clear there's anything useful to do here. None of these IPs have edited in weeks, and I'd have to block 182.1.64.0/18 to do anything useful, which is way too wide a range to consider. If you could identify some specific pages that are common targets, semi-protection might be a better tool. Closing with no action taken. -- RoySmith (talk) 21:08, 4 February 2021 (UTC) reply

8 April 2021

Suspected sockpuppets

Back and forth changing some images of their own (mainly infobox ones) without prior discussions: [2], [3] 182.30.82.165 ( talk) 02:43, 8 April 2021 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments

  • Range is Special:Contributions/158.140.187.192/26. Cabayi ( talk) 08:16, 9 April 2021 (UTC) reply
  • CheckUser requested and endorsed by clerk - There's no doubt that a good chunk (maybe half) of the traffic on 158.140.187.192/26 is Alex, but there's also a lot that looks legit. It's no wonder this case has languished on the open queue for so long. I know /26 is quite narrow, but I'm still loathe to block if half the traffic is legit. I'm hoping CU can provide some insight on the wisdom of a year-long range block. -- RoySmith (talk) 01:55, 4 June 2021 (UTC) reply
    • @ RoySmith: I'm not terribly familiar with this case and I don't see any info on cuwiki, so I really can't tell which user on the range is the target. There are many, as you suspected, and several who I don't think are related (including one very old account) match the behaviour I can glean from the archives. From what I've seen there, Alex Neman is a person with access to many internet connections and/or an ISP with loose range assignments, so if they're blocked here they'll quickly move on to another. For that reason I'd recommend against a long block. But if you think the behaviour matches then a block is warranted. Ivanvector ( Talk/ Edits) 15:46, 5 June 2021 (UTC) reply
    • @ AmandaNP: pinging you for a second opinion, you seem to be most familiar with this case recently. Roy: Amanda's not around a lot, don't feel like you need to wait. Ivanvector ( Talk/ Edits) 15:49, 5 June 2021 (UTC) reply
      • I do see a crap ton of colleterial. If it's only anon edits that are disruptive then maybe a block anon only but allowing account creation? @ Ivanvector: -- Amanda (aka DQ) 16:41, 5 June 2021 (UTC) reply
        • Sorry, yes, I assumed since RoySmith was talking about a rangeblock that it would be anon-only. Don't hardblock this range. Ivanvector ( Talk/ Edits) 16:49, 5 June 2021 (UTC) reply
          Ivanvector, That falls into the category of "Things I expected to hear but hoped I was wrong". I'm going to close this with no action, but take a look at spreading some semi-protection around. -- RoySmith (talk) 22:16, 5 June 2021 (UTC) reply
          • @ RoySmith: just in case I'm in too deep and used unrecognized checkuser jargon there, by "hardblock" I meant checking the "Apply block to logged-in users from this IP address" box in the block screen. I realize now that "hardblock" means something else in terms of the block policy, and I'll try not to do that again. I think a (anon-only) rangeblock is warranted, if you think the behaviour matches, and I think Amanda was agreeing with me on that. Ivanvector ( Talk/ Edits) 00:31, 6 June 2021 (UTC) reply
            Ivanvector, Yes, I understood what you meant by hardblock. I was mostly considering what you said about Alex appearing to have many internet connections available so a short block here (say, a week or a month) would just transiently move them to another connection, which seemed kind of pointless. -- RoySmith (talk) 00:57, 6 June 2021 (UTC) reply

17 June 2021

Suspected sockpuppets

Same editing pattern as previous IPs, such as changing gallery parameters. 182.29.1.237 ( talk) 04:56, 17 June 2021 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments

  • There's not enough to go on here. Which "previous IP"? There's been so many. And this report filed by an IP, so I can't even have a conversation about it. I'm going to close this with no action taken. As I mentioned back in April, this guy is using so many IPs, blocking is pointless. If you can identify specific pages that have been frequent targets, WP:RFPP will probably be more useful. -- RoySmith (talk) 18:41, 11 July 2021 (UTC) reply

10 January 2023

Suspected sockpuppets

This is very likely a sockpuppet of Alex Neman. His location (Surabaya, Indonesia) and editing behaviour (mostly on automobiles) is very suspiciously similar to Alex's. Very recently he was editing under another sockpuppet IP (158.140.167.100) until it was banned last month. Surely something can be done to prevent this guy from continuously creating new IP's to edit under? He's very disruptive with his constant unexplained edits. Democfest ( talk) 09:20, 10 January 2023 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments

Callanecc ( talkcontribslogs) 11:40, 10 January 2023 (UTC) reply

11 January 2023

Suspected sockpuppets

Again, same user making disruptive edits on the same automotive pages. Same location (Surabaya, Indonesia) again. Blatantly obvious. Was literally banned again yesterday under 202.67.40.253 Democfest ( talk) 04:18, 11 January 2023 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments


13 January 2023

Suspected sockpuppets

Not completely certain if these IPs are sockpuppets of Alex; slightly different location, albeit still very close to their original city (Surabaya, Indonesia) but their editing pattern and behaviour (again, predominantly on articles about Japanese automobiles) is very very similar, almost identical to their previous banned sockpuppet accounts. Also, they seem to have popped up immediately after their previous IP was banned. Worth a check Democfest ( talk) 01:59, 13 January 2023 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments


13 January 2023

Suspected sockpuppets

This is definitely him. Same location (Surabaya) and same editing behaviour Democfest ( talk) 02:09, 13 January 2023 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments

  • Blocked for 1 week. I haven't blocked the range yet as they've only used that IP. Closing. Callanecc ( talkcontribslogs) 11:10, 13 January 2023 (UTC) reply

18 January 2023

Suspected sockpuppets

Slightly different locations but still very close in proximity to Alex's original location (Surabaya). Very similar editing behaviour - constant reverts and disruptive. All suspiciously popped up after previous IPs were banned. Worth a check Democfest ( talk) 06:42, 18 January 2023 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments


23 January 2023

Suspected sockpuppets

Not completely certain about this one but his editing behaviour is again very similar to Alex's, focusing predominantly on Japanese/korean cars and having the same erratic, mass edits everyday. Suspiciously restores edits of Alex's previously banned sockpuppet IP's which leads me to believe it could be the same guy behind this account. Democfest ( talk) 06:48, 23 January 2023 (UTC) reply

In this instance, he keeps insisting on replacing the existing image in the "fifth generation" section infobox of the Honda Odyssey (international) article. Alex's previously banned IP ( 114.79.23.176) removed it first on the 18th January for no particular reason. The infobox image was restored shortly after, before AutomobileFan2023 came in to remove the image from the infobox once again on the 22nd January. Bear in mind that Alex was continuously doing this on his other IP accounts before; 18th January, 18th Janaury as a couple of references. For a completely new account to simply repeat and continue the behaviour of previously banned IP accounts is very suspicious
Also, the general editing behaviour of AutomobileFan2023 suggests that it could quite easily be another one of Alex's sockpuppet accounts. Most suspiciously, the account has the exact same interest in editing only Japanese/Korean car articles, and it seemed to have popped up right after after a massive IP range block was applied to prevent Alex from using new IP accounts. Democfest ( talk) 03:05, 25 January 2023 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments


26 January 2023

Suspected sockpuppets

Same location (Surabaya) and same editing behaviour - continuing on changing images for no given reason Democfest ( talk) 10:21, 26 January 2023 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments


27 January 2023

Suspected sockpuppets

Same location (Surabaya), same editing behaviour and patterns Democfest ( talk) 01:26, 27 January 2023 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments


27 January 2023

Suspected sockpuppets

Same location (Surabaya), same disruptive editing behaviour on the same pages Democfest ( talk) 11:38, 27 January 2023 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments


02 February 2023

Suspected sockpuppets

Location is close in proximity to Alex's original city of Surabaya, very similar editing behaviour, popped up not too long after his previous sockpuppet IPs were banned Democfest ( talk) 22:25, 2 February 2023 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments


05 February 2023

Suspected sockpuppets

Same location (Surabaya), same editing behaviour Democfest ( talk) 03:23, 5 February 2023 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments


07 February 2023

Suspected sockpuppets

All in close proximity to original location of Surabaya, very similar editing behaviour Democfest ( talk) 05:36, 7 February 2023 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments


13 February 2023

Suspected sockpuppets

Same location (Surabaya), same editing behaviour Democfest ( talk) 02:59, 13 February 2023 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments


13 February 2023

Suspected sockpuppets

Similar location still close in proximity to original city (Surabaya), same editing patterns and behaviour Democfest ( talk) 14:08, 13 February 2023 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments


19 February 2023

Suspected sockpuppets

Similar/same locations as Alex's original location, same repetitive disruptive editing behaviour on the same pages Democfest ( talk) 11:06, 19 February 2023 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments

  • These are all 🦆 🦆. Unfortunately, the editing spread widely across the range 112.215.241.0/24 suggests that blocking individual IP addresses in that range might possibly just result in the editor moving to another one, whereas blocking the whole range is out of the question, in view of collateral damage. I have therefore put some time into checking all recent editing in that range, and I have placed range blocks on smaller ranges which cover all the editing I have seen in that range by Alex Neman, but no editing by anyone else for at least several months, and in at least one case none for well over a year. I have also done the same for the one other IP address listed in the 112.215.0.0/16 range. At present I don't have time to do similar checking for the other IP addresses listed, but maybe someone else can do it, or I may do it when I do have time. JBW ( talk) 10:36, 22 February 2023 (UTC) reply
  • I have now looked at the range 140.213.0.0/16, which I thought would be easier, because there are only 2 IP addresses listed above, but I found another 6 (140.213.42.124, 140.213.44.252, 140.213.56.13, 140.213.56.15, 140.213.56.217, 140.213.59.128), and there may be more. 140.213.42.0/24 is already blocked by Callanecc , which has just been followed by moving to other IP addresses, and unfortunately that is probably going to continue to happen: the best we can hope to do is slightly slow the editor down by forcing them to keep finding new IP addresses to move to. I have blocked various subranges of 140.213.0.0/16,for times varying from 2 weeks to 3 months, depending on the amount of other editing in the ranges, and therefore the likely amount of collateral damage. The other IP addresses in the list provided above by Democfest were easier to deal with, because there has never been any other editing in the range 115.178.225.248/30, so I was able to block that without worries. (That is assuming that a few edits about noodles were the same person. However, those edits are from one of the IP addresses used by this editor and never before used by anyone, they started 4 minutes after other edits from the same editor on the same IP address, and were followed less than an hour later by more edits from the same person in the same range, so despite the totally different subject matter, I am totally confident that it is the same person.)
  • Since all the IP addresses listed are now covered by various range blocks, I am closing this investigation. JBW ( talk) 15:20, 22 February 2023 (UTC) reply
  • (For what it is worth, I have now seen more noodle-related editing by another one of Alex Neman's IP addresses, on one of the same articles as the one mentioned above, giving yet further evidence that it's the same person. JBW ( talk) 15:29, 22 February 2023 (UTC)) reply

23 February 2023

Suspected sockpuppets

Again - same behaviour and same interest in the same pages. Similar locations as well Democfest ( talk) 02:39, 23 February 2023 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments


28 February 2023

Suspected sockpuppets

Same/similar locations, same editing behaviour on the same pages Democfest ( talk) 01:28, 28 February 2023 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments

  • Lets see. Sorted 12 IPv4 addresses:
115.178.225.67
115.178.225.132
115.178.225.154
115.178.227.127
115.178.227.163
115.178.227.193
115.178.245.150
115.178.246.150
115.178.246.166
115.178.246.170
115.178.249.10
115.178.255.146
Total
affected
Affected
addresses
Given
addresses
Range Contribs
8192 8192 12 115.178.224.0/19 contribs
5120 1024 6 115.178.224.0/22 contribs
4096 6 115.178.240.0/20 contribs
3584 256 3 115.178.225.0/24 contribs
256 3 115.178.227.0/24 contribs
1024 4 115.178.244.0/22 contribs
2048 2 115.178.248.0/21 contribs

115.178.224.0/19 ( block range · block log ( global) · WHOIS (partial)) blocked for one month. Closing. DatGuy Talk Contribs 21:57, 28 February 2023 (UTC) reply


01 March 2023

Suspected sockpuppets

Very similar behaviour, similar location Democfest ( talk) 00:43, 1 March 2023 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments

  • Closing as IP has gone inactive. Spicy ( talk) 15:25, 10 March 2023 (UTC) reply

22 March 2023

Suspected sockpuppets

Same location, same editing behaviour Democfest ( talk) 00:27, 22 March 2023 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

It looks like the edits under 158.140.167.0/24 ( talk · contribs · WHOIS) are overwhelmingly this user, and the IP changes on a daily basis. Is a rangeblock possible here? -- Sable232 ( talk) 21:34, 30 March 2023 (UTC) reply

This guy is a menace. It's both hilarious and pathetic that admins have almost zero power to rangeblock and prevent him from simply creating an infinite number of alternative accounts. Getting blocked is of zero consequence to Alex - Democfest ( talk) 10:23, 31 March 2023 (UTC) reply
Why you always revert my edits? 158.140.167.0 ( talk) 10:42, 31 March 2023 (UTC) reply
Why are you continuously creating new sockpuppet accounts to edit with Alex? You've been banned for a reason, and creating new accounts to get around this will not be tolerated Democfest ( talk) 12:53, 31 March 2023 (UTC) reply

Clerk, CheckUser, and/or patrolling admin comments


01 April 2023

Suspected sockpuppets

Either a sock or a meatpuppet, editing many of the same articles as the sockmaster and IPs, and reinstating the IPs' reverted edits (e.g. [4], [5], [6], [7]). Sable232 ( talk) 00:17, 1 April 2023 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments

  • I am quite confident this is not the same person - if you look at their uploads on Commons, where they are a very established editor, they are consistently taken using different cameras in a different country from Neman's. Editors are allowed to restore edits by a blocked user if they feel they are improvements and are acting on their own accord. However, I would caution Dinkun Chen that if they are doing this because Alex Neman has asked them to, they are violating WP:PROXYING which may lead to sanctions if continued. Closing. Thanks, Spicy ( talk) 18:56, 8 April 2023 (UTC) reply

01 April 2023

Suspected sockpuppets

Defends his own sockpuppet IP accounts and completely outs himself by admitting that he created this account to get involved Democfest ( talk) 15:16, 1 April 2023 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments


01 April 2023

Suspected sockpuppets

Similar location, same behaviour Democfest ( talk) 15:26, 1 April 2023 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments


01 April 2023

Suspected sockpuppets

Using a sockpuppet account to spam messages on talk pages Democfest ( talk) 15:55, 1 April 2023 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments


22 April 2023

Suspected sockpuppets

Significantly different IP addresses but suspiciously still the same editing behaviour. Still the same country as well. Worth a check. It should be noted that like the previous sets of IP addresses Alex used for sockpuppetry, there are probably dozens more out there that haven't been reported yet. It's simply impossible to crack down on all of them Democfest ( talk) 02:16, 22 April 2023 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

There's been a lot of editing from the 2400:9800:0:0:0:0:0:0/32 ( talk · contribs · WHOIS) range lately. It's a wide range though, and it's hard to tell how much possible collateral impact there would be from a rangeblock. This user seems to be pretty adept at changing IPs too. -- Sable232 ( talk) 15:24, 22 April 2023 (UTC) reply

Honestly at this point, i think we just have to accept that collateral blocks are inevitable and have to be accepted. This guy is playing the system like a fiddle. Democfest ( talk) 07:15, 24 April 2023 (UTC) reply

Clerk, CheckUser, and/or patrolling admin comments

  • The IPs haven't edited in weeks, and I'm unwilling to block that wide a range without a compelling analysis. Closing. Bbb23 ( talk) 16:08, 13 May 2023 (UTC) reply

07 September 2023

Suspected sockpuppets

Same/similar location, similar editing behaviour on similar style of pages (automotive) Democfest ( talk) 03:37, 7 September 2023 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments


08 September 2023

Suspected sockpuppets

Same editing behaviour on the same automotive pages. Uses his own wikimedia uploaded images Democfest ( talk) 08:04, 8 September 2023 (UTC) reply

Comments by other users

Accused parties may also comment/discuss in this section below. See Defending yourself against claims.

Clerk, CheckUser, and/or patrolling admin comments



Videos

Youtube | Vimeo | Bing

Websites

Google | Yahoo | Bing

Encyclopedia

Google | Yahoo | Bing

Facebook