Wikipedia:Sockpuppet investigations/Mystic212/Archive

Suspected sockpuppets



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

Mystic212 has a long history of changing image sizes in articles to large fixed sizes, eg, and. The articles are mostly about UK companies. I explained why not to do this, repeatedly, on his talk page. Note this user has multiple vandalism warnings and previous blocks. Today, new user Myoshormus212 was created and started the same image size changes, eg and  (EAT restaurant article again). Same types of changes to UK company articles, and extremely similar username pattern. I suspect this is Mystic212 trying to evade an imminent block on their previous account. Railfan23 (talk) 15:19, 10 December 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

 * ✅. Courcelles (talk) 15:34, 10 December 2018 (UTC)
 * SOck indeffed. Master blocked for 5 days. CLosing.  Vanjagenije  (talk)  22:51, 10 December 2018 (UTC)

Suspected sockpuppets



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

Username, edits on sowiki, etc. This account is blocked on sowiki as a sock of Episilon212. Vermont (talk) 11:36, 8 January 2019 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''
 * Episilon212 is the first account I noticed while patrolling the Somali Wikipedia (see CentralAuth, also the first account registered), which I requested a steward block for copyright violations as they were machine translating enwiki articles. Immediately after that account was blocked, they returned with Fortunia212, who was then blocked on sowiki as well. From there, the other socks were made. I recommend it be blocked. Also please see meta:Steward requests/Miscellaneous for a more accurate history of the issue. Thanks, Vermont (talk) 03:05, 9 January 2019 (UTC)
 * This too: Milyan212. Vermont (talk) 10:53, 16 January 2019 (UTC)

Clerk, CheckUser, and/or patrolling admin comments

 * , you may want to have a look at this one. —DoRD (talk)​ 13:09, 8 January 2019 (UTC)
 * - Katietalk 16:02, 8 January 2019 (UTC)
 * Okay. This is tough because there are events and account creation for them on some of these ranges, but I think I've got it sorted. These accounts are ✅ to each other:
 * (previously confirmed)
 * (previously confirmed)
 * (previously confirmed)


 * is ✅ from this group.
 * is to Mystic212 and Myoshormus212 but there's a significant technical difference, not to mention a behavioral one. I'm inclined to leave this account unblocked for now pending more evidence.
 * Confirmed accounts blocked and tagged, including the master. Katietalk 16:25, 8 January 2019 (UTC)
 * Did you intend to close the case before addressing Vermont's comment? The last submission of evidence was made after Katie checked and noted her inclination not to block Episilon212. I haven't looked at the merits of the request; I'm just wondering if you had already found it not meritorious. Kevin ( aka L235 ·&#32; t ·&#32; c) 17:42, 13 January 2019 (UTC)
 * I must've missed his comment, thanks for pointing that out . Self-reverted. -- The SandDoctor Talk 17:44, 13 January 2019 (UTC)


 * Global action was taken against this set of accounts - closing. NativeForeigner Talk 05:37, 25 February 2019 (UTC)