Wikipedia:Sockpuppet investigations/Nuclearram/Archive

01 November 2014

 * Suspected sockpuppets


 * User compare report Auto-generated every hour.
 * Editor interaction utility

Pracharak0 is currently blocked for editwarring, the IP has continued this editwar and is an obvious duck.Pracharak0 edit. Sock edit. Darkness Shines (talk) 19:21, 1 November 2014 (UTC)

Obvious loud WP:QUACK first he used the IP addresses after his each edit at Indo-Pakistani Air War of 1965 to hide them from the watchlist (with fake edit summaries from his account and IP) to introduce factual errors which sources did not say, now that he's blocked after violating 3RR, he reverted again by resetting his IP; IP sock behaviour and block evasion. I don't know if semi protection will work as sockmaster's edits span over other articles too in similar fashion. lTopGunl (talk) 19:22, 1 November 2014 (UTC)

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've blocked each IP for one week. I've added a week to User:Pracharak0's block for the evasion.--Bbb23 (talk) 20:40, 2 November 2014 (UTC)

04 November 2014

 * Suspected sockpuppets




 * User compare report Auto-generated every hour.
 * Editor interaction utility

The IPs listed are WP:DUCK socks of Nuclearram for sure as they have supported him since over a year very obviously on all his POV editwars Indian subcontinent , IP comes joins in now after a few days for similar revert. Also removed the same content from South Asia article and continues to remove. This was done before in the support of the same editor at PNS Ghazi. And a year ago at Operation Chengiz Khan where IP removed the content and Nuclearram 'rewrote' it. Nuclearram is clearly socking with IPs and goes away just within the threshold limit of editors' suspicions and comes back months later to do the same. He's not here to create an encyclopedia at all.

Now for the connection to the sockmaster (or now Nuclearram should probably be called the sockmaster since he's the older account), his lying edit summaries match word by word with his: claims minor edit when it is a major POV redo - Nuclearram did exact same claimed a minor edit while adding personal commentary / OR and both prefer Indian POV by hook or crook. The IP range is also the very same in addition to that so I did not care to request a CU for the user account but feel free to change that if needed. -- lTopGunl (talk) 01:41, 4 November 2014 (UTC)

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

 * Nuclearram is ✅ as the master, no comments on IPs. Materialscientist (talk) 12:05, 5 November 2014 (UTC)
 * The account is blocked and tagged, 1.22.128.204 hasn't edited since December 2013, and the 1.23.105.XXX IPs are now caught in a range block. I'm closing the case now. Mike V  •  Talk  18:33, 5 November 2014 (UTC)

18 November 2014

 * Suspected sockpuppets




 * User compare report Auto-generated every hour.
 * Editor interaction utility

Some favourite articles between the sockmaster and a sock of his with this editor. Some of the articles have long gaps, but as per original behavioural evidence of this editor, he goes away for even a year to come back later to sock. The sockmaster disrupts slowly so it might match too. What triggered me to file this report is this. Exact same source falsification as Pracharak0 (sock of Nuclearram) even when the source title itself reads the opposite. Sock or not, this was plain vandalism anyway. lTopGunl (talk) 19:59, 18 November 2014 (UTC)
 * Noting personal attacks in response to notification . -- lTopGunl (talk) 23:18, 18 November 2014 (UTC)

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

 * . Materialscientist (talk) 03:38, 19 November 2014 (UTC)
 * Given the checkuser evidence and the insufficient behavioral evidence, I'm closing this case with no action taken. Mike V  •  Talk  21:27, 20 November 2014 (UTC)

08 December 2014

 * Suspected sockpuppets




 * User compare report Auto-generated every hour.
 * Editor interaction utility

Matches whois and range with another of his confirmed IPs in my last reports old current. Same WP:DUCK behaviour and edit summaries like 'me' (I guess he meant 'minor edit' which usually does when making controversial changes and is his give away. See last reports if more evidence on that is needed). He hops IPs once blocked so might need a range block. <b style="color:#060">lTopGunl</b> (<b style="color:#000">talk</b>) 11:03, 8 December 2014 (UTC)
 * I've added a second IP that is now active .. told you so. I know when it's him, and the diffs are clear. -- <b style="color:#060">lTopGunl</b> (<b style="color:#000">talk</b>) 04:11, 9 December 2014 (UTC)
 * , I didn't make a CU request (you added CU declined without a request for CU). I only gave behavioural evidence and I connected an IP with another IP (which is already behaviourally connected to an account) with open 'whois' information. The one WP:DUCK edit it made was today, don't know how that counts as stale... -- <b style="color:#060">lTopGunl</b> (<b style="color:#000">talk</b>) 13:47, 8 December 2014 (UTC)

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

 * We don't connect accounts with IPs, thus no CU. As to blocking, this IP is stale and made only one edit. Materialscientist (talk) 11:19, 8 December 2014 (UTC)
 * Closing, both IPs are stale now (and I agree they were probably being used by this master). Callanecc (talk • contribs • logs) 02:05, 13 December 2014 (UTC)