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

29 March 2022[edit]

Suspected sockpuppets[edit]

• Unicorn123SL (talk⁺ · tag · contribs · deleted contribs · logs · filter log · block user · spi block · block log · CA · CheckUser(log) · investigate · cuwiki)
• Democfesty (talk⁺ · tag · contribs · deleted contribs · logs · filter log · block user · spi block · block log · CA · CheckUser(log) · investigate · cuwiki)
• Tools: Editor interaction utility • Interaction Timeline • SPI Tools

CU confirmed here, just making it official. Good hand/bad hand editing [1][2], time wasting trolling over warnings. Really, I don't know what the end game is, but it's clearly not good. Opening the SPI to dot all the Ts and cross all the Is and get everything documented. Thanks. ScottishFinnishRadish (talk) 10:55, 29 March 2022 (UTC)[reply]

Comments by other users[edit]

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

Clerk, CheckUser, and/or patrolling admin comments[edit]

• Blocking and tagging per Special:Diff/1079871843. -- RoySmith (talk) 19:09, 30 March 2022 (UTC)[reply]

31 March 2022[edit]

Suspected sockpuppets[edit]

• Democfest (talk⁺ · tag · contribs · deleted contribs · logs · filter log · block user · spi block · block log · CA · CheckUser(log) · investigate · cuwiki) ( Clerk note: original case name)

• Democfestys (talk⁺ · tag · contribs · deleted contribs · logs · filter log · block user · spi block · block log · CA · CheckUser(log) · investigate · cuwiki)
• Tools: Editor interaction utility • Interaction Timeline • SPI Tools

Ugh, this is a mess. In short, there was a (presumptive) joe-job, followed by an accidental username transcription error, which I failed to catch when blocking. See the longish thread at Special:Permalink/1080317944#Blocked for sockpuppetry for details. Filing this pro-forma. -- RoySmith (talk) 15:05, 31 March 2022 (UTC)[reply]

Comments by other users[edit]

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

Clerk, CheckUser, and/or patrolling admin comments[edit]

• I've retagged the accounts to reflect the correct master. Spicy (talk) 21:47, 2 April 2022 (UTC)[reply]

22 August 2022[edit]

Suspected sockpuppets[edit]

• 125.253.103.44 (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 • SPI Tools

This comment on one of their socks asking the account to be unblocked makes it pretty obvious they are a Unicorn123SL sock, plus their poor grammar and other weird edits (see contribs). 47.227.95.73 (talk) 23:58, 22 August 2022 (UTC)[reply]

Comments by other users[edit]

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

Clerk, CheckUser, and/or patrolling admin comments[edit]

• Duck. Broader range is 125.253.96.0/20. However for now,  Awaiting administrative action - Please block 125.253.103.44 for a week. Thanks, --Jack Frost (talk) 00:51, 23 August 2022 (UTC)[reply]

  Already blocked the IP address as a separate action. I want to be clear, my block of that IP address happened before I saw this SPI and does not necessarily imply this IP address is used by this particular user, it could be a joe-job. After noticing this SPI, I see no sleepers related to Unicorn123SL but can confirm previously blocked users, Train and unicorn fan and Thisuseristrainandunicornfan for what little it is worth. --Yamla (talk) 10:41, 25 August 2022 (UTC)[reply]

• Closing. Thanks, Spicy (talk) 10:46, 25 August 2022 (UTC)[reply]