Wikipedia:Sockpuppet investigations/Orchomen

Orchomen

Orchomen (talk⁺ · tag · contribs · deleted contribs · logs · filter log · block user · spi block · block log · CA · CheckUser(log) · investigate · cuwiki)

Populated account categories: confirmed · suspected

For archived investigations, see Wikipedia:Sockpuppet investigations/Orchomen/Archive.

This case's socks should have their talk page and email access revoked due to abuse.

01 December 2021

– This SPI case is open.

Suspected sockpuppets

2001:8F8:1F33:E54E:2:4:2C8:C570/32 (talk⁺ · tag · contribs · filter log · WHOIS · RBLs · proxy check · block user · spi block · block log · cross-wiki contribs · CheckUser (log))
31.219.85.253 (talk⁺ · tag · contribs · filter log · WHOIS · RBLs · proxy check · block user · spi block · block log · cross-wiki contribs · CheckUser (log))
Tools: Editor interaction utility • Interaction Timeline • User compare report Auto-generated every hour.

reverting to a Lirae22 edit
reverting to a Lirae22 edit
restoring talk page comments by Ingvario
A bunch of edits hounding Comradeka, who was in a dispute with Ingvario and publicly called out Lirae22 as a sock: [1], [2], [3], [4], [5], [6], and [7]

Orchomen appears to back editing from one IPv4 (Special:Contributions/31.219.85.253) and a dynamic set of IPv6s in the Special:Contributions/2001:8F8:1F33:3909:2:1:14D:66DC/32 range. There are definitely some recent edits by unrelated users in that 32 range, but I don't know if it's possible to capture the problematic edits in any tighter range. Firefangledfeathers 04:14, 1 December 2021 (UTC)[reply]

Pinging User:Comradeka, who's getting the worst of it right now. Firefangledfeathers 04:26, 1 December 2021 (UTC)[reply]

@Sro23: understood. What can I do to help whac? Is it worth it to list individual IPv6s or /64s here? Firefangledfeathers 03:13, 2 December 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

I have a feeling you're going to have a difficult time finding an admin comfortable with blocking that wide a range. We usually just end up playing whac a mole with this one. Sro23 (talk) 03:09, 2 December 2021 (UTC)[reply]
At this point, you'll get more of an immediate response at AIV. Next time he shows up you can report straight to AIV along with a link to this SPI. Sro23 (talk) 03:17, 2 December 2021 (UTC)[reply]

06 December 2021

– A user has requested CheckUser. An SPI clerk will shortly look at the case and endorse or decline the request.

Suspected sockpuppets

CreecregofLife (talk⁺ · tag · contribs · deleted contribs · logs · filter log · block user · spi block · block log · CA · CheckUser(log) · investigate · cuwiki)
2001:8f8:1f20:cc4c:2:1:3885:7f10 (talk⁺ · tag · contribs · filter log · WHOIS · RBLs · proxy check · block user · spi block · block log · cross-wiki contribs · CheckUser (log))
2001:8f8:1f21:86c:2:1:393b:aa85 (talk⁺ · tag · contribs · filter log · WHOIS · RBLs · proxy check · block user · spi block · block log · cross-wiki contribs · CheckUser (log))
Tools: Editor interaction utility • Interaction Timeline • User compare report Auto-generated every hour.

IPs geolocate to the UAE, Orchomen's favorite place. Amaury • 18:01, 6 December 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

Nope, that account is not one of mine. Look harder @Amaury:. I'm just fucking with you for old times sake. He's collateral damage. 2001:8F8:1F21:86C:2:1:393B:AA85 (talk) 18:14, 6 December 2021 (UTC)[reply]