Wikipedia:Sockpuppet investigations/Demoreasimpson16/Archive

Suspected sockpuppets



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

Similar behavior on editing radio station articles without using any edit summaries, and adding non-free logos from Commons uploaded by its master. theinstantmatrix (talk) 14:57, 25 March 2018 (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

 * IP blocked for 3 months. Case closed.  Vanjagenije  (talk)  09:56, 1 April 2018 (UTC)

Suspected sockpuppets



 * Tools: Editor interaction utility • Interaction Timeline • User compare report Auto-generated every hour.

From the original User:Demoreasimpson account, the others frequent the same radio station pages 1, 2. (along with many others) having the same behavioral patterns (blanking, etc.) and obviously naming of accounts. You can see from this history that the 50.88.77.248 IP address was used between the User:Demoreasimpson and User:Demoreasimpson291 accounts. Here, the User:Demoreasimpson and User:Demoreasimpson291 accounts are used with the 50.88.77.248 IP spaced in between, along with the Kangaroo18 account spaced in between.

The others are, admittedly, "gut feelings" on my part from other pages where the User:Demoreasimpson291 comes into contact with one of them. Could be unrelated, not sure, but worth checking.

A note, User:Demoreasimpson previous used User:Demoreasimpson16 (probably others) as part of previous sockpuppetry. So, it might be of use to double check those accounts with the new accounts to see if there is any crossover.  Neutralhomer •  Talk  • 01:03 on November 24, 2018 (UTC) )
 * Covering all bases: I have notified of this SPI as he was the blocking admin on the User:Demoreasimpson and User:Demoreasimpson16 accounts. -  Neutralhomer  •  Talk  • 01:08 on November 24, 2018 (UTC)


 * My apologizes for the case misnaming. I added an extra "User" on accident, didn't know it would goof EVERYTHING.  I thought linking to the main User:Demoreasimpson account was the correct sockpuppeteer account.  Again, my apologizes.  Thanks to  for the CU/SPI and  for correcting my mistakes. -  Neutralhomer  •  Talk  • 19:29 on November 24, 2018 (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
Please fix this.--Bbb23 (talk) 01:16, 24 November 2018 (UTC)
 * ✅. Sir Sputnik (talk) 16:13, 24 November 2018 (UTC)
 * Demoreasimpson291 is ✅, blocked and tagged. There is insufficient evidence to check the other users. Please move case to Demoreasimpson16. Sorry for the extra work.--Bbb23 (talk) 18:23, 24 November 2018 (UTC)
 * ✅, closing. GABgab 22:41, 24 November 2018 (UTC)

Suspected sockpuppets



 * Tools: Editor interaction utility • Interaction Timeline • User compare report Auto-generated every hour.

New obvious sock popped up, clear from the name it's another Demora sock (the Demoreasimpson291 was the previously blocked). Asking for a more wide-range checkuser this time to check for sleeper accounts. Pinging. -  Neutralhomer •  Talk  • 21:44 on December 1, 2018 (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

 * Both are confirmed, of course. I sweeped a /36 range on IPv6 and found nothing I was particularly confident about, would like Bbb23 to take another look, as he seems to be more familiar with the case.  I went ahead and blocked Demorea2020 while I was looking.  Courcelles (talk) 20:19, 2 December 2018 (UTC)
 * I don't think a recheck was necessary, but I found nothing. Closing.--Bbb23 (talk) 14:19, 3 December 2018 (UTC)

Suspected sockpuppets



 * Tools: Editor interaction utility • Interaction Timeline • User compare report Auto-generated every hour.

Yet another obvious sock of Demoreasimpson16. Please see the archive of this SPI for more obvious socks. Can we get a range block too? Pinging as he was the original blocking admin on the Demoreasimpson16 account. -  Neutralhomer •  Talk  • 00:24 on December 12, 2018 (UTC)
 * This user is still active and unblocked. A little help? -  Neutralhomer  •  Talk  • 20:19 on December 27, 2018 (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

 * . Sir Sputnik (talk) 04:19, 29 December 2018 (UTC)
 * Thank you, . Much appreciated. -  Neutralhomer  •  Talk  • 07:25 on December 29, 2018 (UTC)

Suspected sockpuppets



 * Tools: Editor interaction utility • Interaction Timeline • User compare report Auto-generated every hour.

Obvious sockpuppet is obvious. Seriously though: this is, yet another, sockpuppet from Demorea. Clearly he isn't getting the message. Could we get an actual CU to check for sleepers (unlike previous SPIs) and possibly a long-standing rangeblock? These whack-a-mole blocks clearly aren't working. -  Neutralhomer •  Talk  • 12:05 on April 8, 2019 (UTC)
 * I have notified as he was the original blocking editor on the original Demoreasimpson16 account. -  Neutralhomer  •  Talk  • 12:08 on April 8, 2019 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''


 * ,, : With due respect to Bbb23, I have asked for CUs on each of the CUs for Demorea's socks and each time he has refused to check them or said there was no reason to check them. I am respectfully asking that a CU be ran. -  Neutralhomer  •  Talk  • 00:26 on April 9, 2019 (UTC)

Clerk, CheckUser, and/or patrolling admin comments

 * , leaving open because requester asks for CU for sleepercheck. ST47 (talk) 16:08, 8 April 2019 (UTC)
 * - per comments The SandDoctor  Talk 18:44, 8 April 2019 (UTC)
 * Based on the history of this case, there is no reason to run a check. Closing.--Bbb23 (talk) 19:03, 8 April 2019 (UTC)

Suspected sockpuppets



 * Tools: Editor interaction utility • Interaction Timeline • User compare report Auto-generated every hour.

Another obvious sock is obvious. The last sock (DemoreaBigD2020) was blocked not even 24 hours ago (as of this filing). I am, again, respectfully requesting a checkuser be ran on this current sock and the previous sock and the range they are on. Thank you. -  Neutralhomer •  Talk  • 06:07 on April 10, 2019 (UTC)
 * I have added DemoreaBigD2020 to this SPI, even though it was previously blocked in a previous SPI, for easier access of clerks, CUs, and admins. -  Neutralhomer •  Talk  • 06:07 on April 10, 2019 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''
 * Blocked User:DemoreaBigger2020 CambridgeBayWeather, Uqaqtuq (talk), Sunasuttuq 07:32, 10 April 2019 (UTC)

Suspected sockpuppets



 * Tools: Editor interaction utility • Interaction Timeline • User compare report Auto-generated every hour.

Another obvious sock. But I would like to point out that the edit's made by 2603:9001:3A00:A600:6D0B:F0BE:ECC0:B327 on April 13 at 11:03 (EST) happened immediately before Demoreasimpson17's edit's at 11:05 (EST). Since the named account was created on April 12 at 15:50 (EST) when 2603:9001:3A00:A600:6D0B:F0BE:ECC0:B327 began editing, I request a checkuser be done there (yeah, I know about the AN discussion) and to the previous IP as well. If we can stop this vandal, we can stop this once and for all. -  Neutralhomer •  Talk  • 19:54 on April 13, 2019 (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

 * Account, 2603:9001:3a00:a600::/65. GABgab 20:45, 13 April 2019 (UTC)