Wikipedia:Sockpuppet investigations/FFS19/Archive

Suspected sockpuppets

 * ( originally filed at Sockpuppet investigations/Architect 134)


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

User with bizarre behavior and obvious sock of this or someone, but 100% sure this is a sock. Since they're new, they know already on tagging sock's userpage and gibberish edits on his sandbox for ECP probably. 14.192.212.93 (talk) 11:40, 5 July 2020 (UTC)

Comments by other users

 * Mz7 (talk) 22:10, 5 July 2020 (UTC)
 * FFS19 is ❌ to Architect 134, but is ✅ to the following accounts:
 * I think there is almost certainly another master, but I'm not sure who it is at the moment. For now, I've all the accounts as socks of FFS119.  Please split this into a new case under "FFS19". Mz7 (talk) 22:25, 5 July 2020 (UTC)
 * Case split from Sockpuppet investigations/Architect 134. No further action required, closing. GeneralNotability (talk) 01:42, 6 July 2020 (UTC)
 * I think there is almost certainly another master, but I'm not sure who it is at the moment. For now, I've all the accounts as socks of FFS119.  Please split this into a new case under "FFS19". Mz7 (talk) 22:25, 5 July 2020 (UTC)
 * Case split from Sockpuppet investigations/Architect 134. No further action required, closing. GeneralNotability (talk) 01:42, 6 July 2020 (UTC)
 * I think there is almost certainly another master, but I'm not sure who it is at the moment. For now, I've all the accounts as socks of FFS119.  Please split this into a new case under "FFS19". Mz7 (talk) 22:25, 5 July 2020 (UTC)
 * Case split from Sockpuppet investigations/Architect 134. No further action required, closing. GeneralNotability (talk) 01:42, 6 July 2020 (UTC)

Suspected sockpuppets

 * ( originally filed under this username)


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

Similar user name pattern and same editing in sandbox by just adding and removing the letter "a", see User:Pristine Condition 2020/sandbox and User:Vultr2020/sandbox, along with creating blank User and Talk pages. Seems to be gaming the system to get 10 edits. S0091 (talk) 19:00, 3 July 2020 (UTC)
 * Added a couple more: User:Rackrr2020/sandbox, User:Nightr2020/sandbox. S0091 (talk) 14:28, 5 July 2020 (UTC)
 * Adding a couple more. Different naming schema and they expanded their alphabet beyond the letter "a" but pattern is the same, creating blank user and talk pages, making edits to sandbox by adding removing letters: User:LightyearBreakingFAST/sandbox, User:TelephonepolesIndependent/sandbox.  Another item to note is TelephonepolesIndependent left a warning template on User talk:91.182.24.65.  Pinging  just for awareness since she left a note on TelephonepolesIndependent's talk page. S0091 (talk) 02:10, 6 July 2020 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''
 * Comment I'm very surprised you guys are taking the time to continue this pointless investigation Procmon867 (talk) 16:46, 6 July 2020 (UTC)

Clerk, CheckUser, and/or patrolling admin comments

 * Yes, indeed, I left a note on TelephonepolesIndependent's talkpage, telling them about gaming the autoconfirmed requirements and, to put it bluntly, asking whose sock they were, since this edit showed technical proficiency. The pattern for them all of creating exactly 10 mostly quite pointless edits in the same way seems very clear. I could duckblock, but I think it would be nice to have a checkuser here, for surely there are likely to be still undiscovered sleepers. Bishonen &#124; tålk 08:39, 6 July 2020 (UTC).
 * - Honestly, there are numerous LTA's with this exact or similar behavioral "tells". But the fact that these were all created around the same time, plus the username pattern, makes me believe this is worth a CU. Sro23 (talk) 17:38, 6 July 2020 (UTC)
 * CheckUser is because all of these accounts are using proxies. In my view, the behavior in this case is almost identical to the accounts at Sockpuppet investigations/FFS19. Combined with the proxy use (another trait shared with the FFS19 accounts), . .  Please merge this case into FFS19. Thanks, Mz7 (talk) 18:39, 7 July 2020 (UTC)
 * After further review, Procmon867 is not using a proxy and is ✅ to FFS19. Mz7 (talk) 18:48, 7 July 2020 (UTC)
 * Case merged from Sockpuppet investigations/Vultr2020. Closing. GeneralNotability (talk) 18:48, 7 July 2020 (UTC)

Suspected sockpuppets



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

Same sandbox behaviour, adding and removing "a". S0091 (talk) 23:59, 12 July 2020 (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'd like a CU to take a look here - that behavior isn't unique to this sockmaster. I note that CU has been of mixed usefulness in the archives, but the inconclusiveness has sometimes itself been a data point. GeneralNotability (talk) 20:34, 13 July 2020 (UTC)
 * - Mz7 (talk) 22:36, 13 July 2020 (UTC)
 * Brycenn appears to be unrelated from a technical standpoint to the past FFS19 socks (this time, they're not using an obvious proxy)—however, the account's behavior is indeed similar (gaming autoconfirmed with the letter 'a'), and as GeneralNotability notes, CU has been of mixed usefulness for this master in the past. The account that edited this SPI earlier looks like a WP:DUCK to me based on behavior and CU data, so I blocked it. I will defer to someone else on whether to block Brycenn based on just the gaming. Mz7 (talk) 22:52, 13 July 2020 (UTC)
 * I don't think we should block Brycenn on gaming alone, but I will keep an eye on their contributions since it's never a good sign when someone obviously games ACPERM. Closed without further action. GeneralNotability (talk) 22:56, 13 July 2020 (UTC)