Wikipedia:Sockpuppet investigations/Yusaya 4531/Archive

Suspected sockpuppets

 * ( original case name)
 * ( original case name)

username and behavioral similarity makes these users WP:DUCKs of whatever the oldest account here is. Global locks requested due to prior xwiki abuse – dudhhr talk contribs (he/they) 13:44, 12 August 2023 (UTC)


 * Please nuke their contribs as well - they've made quite a bit of crap in their userspace with Hangul Syllables. – dudhhr talk contribs (he/they) 13:46, 12 August 2023 (UTC)
 * Older master is User:Yusaya Takei - can this case be moved there? – dudhhr talk contribs (he/they) 13:54, 12 August 2023 (UTC)
 * @Dudhhr Locked as requested, still neeed a checkuser? -Lemonaka‎  02:44, 13 August 2023 (UTC)
 * CU is not needed. – dudhhr talk contribs (he/they) 03:11, 13 August 2023 (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

 * See below. Spicy (talk) 16:35, 18 August 2023 (UTC)

Suspected sockpuppets

 * ( originally filed under this user)

Both disruptively editing the teahouse, both creating various test pages around Hangul syllables. obvious WP:DUCK is obvious Lavalizard101 (talk) 13:50, 12 August 2023 (UTC)
 * Actually noticed an older master Special:Contributions/Yusaya Takei. Lavalizard101 (talk) 13:53, 12 August 2023 (UTC)
 * can a clerk please merge this with WP:Sockpuppet investigations/Yusaya 4522. Lavalizard101 (talk) 14:13, 12 August 2023 (UTC)

Comments by other users

 * Accused parties may also comment/discuss in this section below. See Defending yourself against claims.
 * this is a Duplicate of WP:Sockpuppet investigations/Yusaya 4522. – dudhhr talk contribs (he/they) 13:56, 12 August 2023 (UTC)
 * Didn't notice there was case already under another name. Came from the teahouse after the disruption there and didn't look into it that much and after creating this report. Lavalizard101 (talk) 13:58, 12 August 2023 (UTC)

Clerk, CheckUser, and/or patrolling admin comments

 * Merged cases, moved case to oldest known account. Everyone is locked, nothing more to do here. Spicy (talk) 16:34, 18 August 2023 (UTC)

Suspected sockpuppets
Ducky name and same disruptive Hangul edits. Please nuke creations. CU requested as this LTA frequently creates multiple socks simultaneously. – dudhhr talkcontribssheher 05:14, 4 November 2023 (UTC)

Comments by other users

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

Can you revoke TPA? They've made 301 edits to their user talk page since being blocked. – dudhhr talkcontribssheher 23:26, 4 November 2023 (UTC)


 * Sorry for the ping, I didn't realize you weren't an administrator. – dudhhr talkcontribssheher 20:12, 6 November 2023 (UTC)

Clerk, CheckUser, and/or patrolling admin comments

 * Already blocked, tagged, closing. MarioGom (talk) 09:35, 4 November 2023 (UTC)

Suspected sockpuppets
Both the IPv4 and the IPv6 use the name: diff:ipv6, diff:ipv4. Both edited and are editing each other's talk pages, talk page edits of both (all edits) are mostly DUCK with what I remember from previous accounts and IPs. – 2804:F14:8090:C501:686B:E2D5:C69E:9592 (talk) 05:16, 8 April 2024 (UTC)


 * Hm, I hadn't noticed how few accounts there are in this SPI, actually - and no IPs. I previously saw this user before they started creating accounts and documented them on Alexf's talk page(for some reason). Looks like a lot of the previous IP's edits are now deleted. Hopefully it's still obvious. – 2804:F14:8090:C501:686B:E2D5:C69E:9592 (talk) 05:26, 8 April 2024 (UTC)

Comments by other users

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

(same user as the IP who reported) This is now stale, there have been no further DUCK edits from IPs in the /32(IPv6) and /16(IPv4) ranges since I made this report - it also seems like this was the first time they used these ranges for this, though I obviously cannot see deleted contributions. I'd close this to help reduce the backlog, but I don't know how, and I suspect the filters wouldn't let me anyways. – 2804:F14:80AD:C201:A1F1:53F1:AD24:FA49 (talk) 10:01, 20 April 2024 (UTC)


 * (also the same user as the IP who commented above) Maybe I jinxed it - the IPv6's /32 is active again and another IPv4 not in the /16 range is as well (126.33.160.97)... oh well.
 * – 143.208.239.166 (talk) 01:31, 21 April 2024 (UTC)
 * I'll just note that the admin @Utcursch has been deleting most of the user talk pages and subpages that prompted me to make this report (they were tagged for speedy deletion), so if anyone handles this in the future they will have to look at the deleted contributions.
 * That said, I'm not really sure what an appropriate block would be anymore, since from the IPs on the 8th to the IPs today is a pretty big jump for blocks to seem reasonable, even if the IPs are from the same ISP. – 143.208.239.166 (talk) 03:19, 21 April 2024 (UTC)
 * Update: Been a bit, looking at this again a /36 range which covers all the IPv6 that still have user talk edits (and the initial IPv6) has been blocked for 61 days by @JBW for possibly unrelated reasons. There has been no further disruption from the 2 /16 IPv4 ranges contributions (if it wasn't all deleted) either - so I think this can be closed.
 * – 2804:F14:80EE:5A01:F151:38D2:AA6E:399F (talk) 21:15, 3 May 2024 (UTC)

Clerk, CheckUser, and/or patrolling admin comments

 * There's no doubt whatever that both of these were Yusaya 4531, but, as the IP editor above has said, there have been no recent related edits from the relevant IP ranges, and the IPv6 range is blocked, so there's nothing more to be done. Close. JBW (talk) 09:32, 7 May 2024 (UTC)