Wikipedia:Sockpuppet investigations/Symphony Regalia/Archive

Suspected sockpuppets



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

See (long history of doing) as a mirror image of this post at the sockpuppeteer's talk and WP:AN3, where the sockpuppeteer was blocked for WP:IDHT disruptive posting. Note similarity in edit summaries: IP, Sypmhony Regalia SR 2 (why specifically use edit warring, as opposed to reverting?).

If a link can be demonstrated, SR's current block should be lengthened far beyond the current 1 week. Caradhras Aiguo ( leave language ) 21:19, 1 May 2020 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''
 * It's worth noting that two similar edits were made by Ip's over at American-born Chinese several months ago that were also re-instating edits by the same user. Diffs |2, |3. While these edits were initially dismissed and confused with the completely different modus operandi of the Architect sock (which is to get users blocked for edit warring into further grief), The similarites between the two ip edits and the ones currently under investigation are striking. Hemiauchenia (talk) 21:31, 1 May 2020 (UTC)
 * The reason that this was initially filed was that I thought that Karikodex was a Sockpuppet of Symphony, as they were making bogus warnings on the talkpage of an admin that Symphony had been discussing with before he was blocked diffs 1 2 3 I had no idea about Architect (who is a troll with a specific modus operandi to pretend to be a sock of users blocked for edit warring), so I then opened the sockpuppet investigation under symphony's name. The majority of architect's sockpuppet investigations are opened in the name of the edit warrer, as this is usually the most parsimonious suggestion to anyone involved in the initial editing dispute. I then filed a second sockpuppet dispute as I again didn't understand Architect's modus operandi and thought Symphony was therefore a sock of architect, this was then summarily closed as it clearly wasn't architect. I then had a discussion with ST47 about it, which cleared things up. Hope that helps. Hemiauchenia (talk) 16:16, 11 May 2020 (UTC)

Clerk, CheckUser, and/or patrolling admin comments

 * Wondering how a complaint about Symphony Regalia managed to get filed under Architect 134, I came across this comment by User:ST47 from March, who said 'none of the listed evidence relates in any way to this case'. User:Hemiauchenia, the person who opened the SPI against Symphony Regalia, must have thought they could be the same person as User:Karicodex who is blocked as a sock of Architect 134. All that I get from the March report is that Karicodex made some comments in a thread where Symphony Regalia was participating. Since Architect 134 seems to swoop down to cause trouble in any dispute that is going on, their presence in the thread doesn't prove anything. There is not yet anything behavioral I can see which would justify a check on Symphony Regalia. I recommend this complaint be closed. Symphony Regalia can be a big waste of time but the WP:GS/COVID sanctions can be used by any admin who thinks that action should be taken. EdJohnston (talk) 15:58, 11 May 2020 (UTC)
 * Note: The IP range has been blocked as a a cloud services provider which acts as an open proxy. ST47 (talk) 16:04, 11 May 2020 (UTC)
 * Closing. Nothing further to do here. The SandDoctor  Talk 19:06, 16 May 2020 (UTC)