Wikipedia:Sockpuppet investigations/Symphony Regalia
Symphony Regalia
Symphony Regalia (talk+ · tag · contribs · deleted contribs · logs · filter log · block user · spi block · block log · CA · CheckUser(log) · investigate · cuwiki)
For archived investigations, see Wikipedia:Sockpuppet investigations/Symphony Regalia/Archive.
21 December 2024
edit– An administrator or SPI clerk requires more information to determine what action to take.
Suspected sockpuppets
edit- Ethiopian_Epic (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
I am sure there are more, if you continued to comb thru the talk pages for first time contributing IP editors casting aspersions.
Symphony Regalia previously received an indefinite editing restriction on the topic Yasuke after arbcom judgement enforced in the first week of November. This is not his first editing restriction on wikipedia and he is known for aggressive and contentious editing on controversial topics in the past, such as COVID19.
Prior to the restriction, Symphony Regalia was making daily contributions to Wikipedia, the majority of which were to Yasuke and Yasuke:Talk[[1]] and related pages (https://en.wikipedia.org/wiki/Assassin%27s_Creed_Shadows, https://en.wikipedia.org/wiki/List_of_foreign-born_samurai_in_Japan) for months on end. As soon as the topic ban was enforced, Symphony Regalia ceased almost all activity on wikipedia -- he made one edit on Dec 6 and otherwise has been radio silent. In his place, several edits with similar tendencies have been contentiously editing the Yasuke main and talk page: a few example diffs: 1 2 3 4
To quote me, IP editor on talk page: "You are the sockpuppet of Ethiopian Epic who is also a sockpuppet of Symphonia Regalia. It is blatantly obvious that you are doing this aggressively after being topic banned on your main. Please note the IP I'm replying to is a Philippines mobile phone IP, a prime _target for an IP masking/dodging. These first time IP editors reverting anyone calling out EEpic are all mobile APAC mobile phone IPs. Symphonia Regalia and Ethiopian Epic both state themselves to be from the APAC region."
Ethiopian Epic and his first time contributor mysterious IP editor defenders are based out of APAC and use phone IPs to edit (EEpic states he is from Hong Kong on his user page).
Deeper investigation into the Ethiopian Epic account contributions shows he first signed up for Wikipedia on Nov 12 the exact same day Symphony Regalia was topic banned, made some trivial edits and reverts to Government of Japan, then immediately dived into editing related articles (Yasuke, Samurai, list of foreign born samurai). Not only is there immense overlap and is the timing suspect, but the POV taken by Ethiopian Epic and pattern of argument is the same as well -- he is aggressive to anyone and repeatedly reverts edits / overwrites edits as much as possible. Ethiopian Epic has in short time already made enemy of many other editors with his behavior and is currently subject of a request for enforcement here: https://en.wikipedia.org/wiki/Wikipedia:Arbitration/Requests/Enforcement#Ethiopian_Epic with several current yasuke page editors coming to agreement that he is being disruptive.
Investigating Symphony Regalia's contributions page shows tremendous overlap in _target pages edited: Yasuke, Assassin's Creed Sahdows, and List of foreign-born samurai in Japan are 90% of his edits for a 4 month period spanning July 2024 to November 2024. Only when the Arbcom case was opened did he cool off on these topics and start editing other pages, but still continued edits to Yasuke until his eventual topic ban on Nov 12. — Preceding unsigned comment added by 23.241.114.128 (talk) 07:55, 21 December 2024 (UTC)
EEpic refuses to discuss topics and will revert at will, stating that there is "Consensus on the talk page" while dodging/ignoring actual discussions. This is highlighted by the fact that instead of trying to cool down the situation when brought to arbitration, he retaliated by opening his own arb request against his accuser immediately. This is the topic of the arbitration request linked above still ongoing.
With all of the above said, I will provide some more diffs of EEpics editing tendencies side by side with some of Symphony Regalia's editing tendencies to draw an even deeper correlation between the two accounts:
EE invoking RFC and removing anything that doesn't fit his personal POV at all times to justify his aggressive reverts without evidence or obvious sourcing: 1 2 3 [2] 4 5 6] 6 7
Please note I am not disputing the content of what he is discussing above but rather his style of argument, such that he constantly invokes personal opinion and uses "consensus" "RFC" and "Sources" as a bludgeoning / fallback to justify aggressive reverts without actually supplying any sources or acknowledging any talk page discussion on consensus. 80%+ of his edits basically amount to him reverting edits and stating that topics are "not up for debate" or "not in agreement with his source/opinion" without any supplemental detail. Aside from having the exact same POV, same pages edited, picking up edits at the exact time Symphony Regalia was topic banned, this pattern of behavior is also essentially the same as Symphony Regalia who tends to use extremely procedural arguments to intimidate opponents and revert their edits, as evidenced here:
In conclusion, I would like to make the following statement: I believe that the above edit diffs show a pattern of behavior that shows a suspicious similarity. Not enough to confirm SP, but enough to garner some interest. Then, combine this with the 90% overlap in edited articles, the aspect of timing, the aspect of aggressive behavior/disruption to fellow editors and I believe it is very clear that this is the same person. I also believe they are participating with IP addresses to try to muddy the water whenever anyone tries to debate with them. Their motivation here is to imply there are more users on "their side" (that being one of disruption, not the POV).
I would also like to highlight that this user is incredibly likely to continue this pattern of behavior and continue with a new account to try to disrupt again. — Preceding unsigned comment added by 23.241.114.128 (talk) 07:39, 21 December 2024 (UTC)
Comments by other users
edit- Accused parties may also comment/discuss in this section below. See Defending yourself against claims.
- Good afternoon, I'm user of Japanese Wikipedia.
I've been silently watching the Yasuke talk page and I can confidently say that Ethiopian Epic is Symphony Regalia, there is the same behavior pattern that on the Japanese Wiki where he was banned and he's still using so-called "residential VPN" (to hide he's using open proxies and can only be detected with tools like SPUR or IPQS, [4][5], CheckUser request) to hide his real identity and appear as multiple users from multiple countries in talk pages.
What behavior pattern you may ask?- Residential proxies IP addresses with positive result on SPUR/IPQS bludgeoning discussions where Symphony Regalia or Ethiopian Epic are present, exactly like on jawiki.
- Retaliation when someone say something about his behavior, sometimes accusing others to be sockpuppets (ja: [6] en: [7][8][9])
- Same reverting rationales
Here's some IP addresses I belive are Symphony/Ethiopian:
I previously filed an SPI but it was dropped, the reason I was given was a previous SPI judgment (though I personally believe it was dropped prematurely), but nevertheless, I would like to provide some comments on this SR account and its similarities to the EE account.
1. Reposting warnings given to them by other users back to said users or to users that they're feuding with.
- SR EN: When the user Xslyq posted a disruptive editing warning to SR's talk page, SR copypasted the warning back to Xslyq's talk page as a form of retaliation.
- SR JP: 1. When the user Pinkpastel posted 3 warnings to SR's talk page in relation to SR changing a page's name without discussion, SR retaliated by doing the same, citing "removing vandalism". 2. When the user Masatami posted a comment to SR's talk page about misusing templates for articles, SR removed the comment, a JP admin Mt.Asahidake reverted those changes and issued a warning, SR retaliated by copypasting the warning to both Masatami (with the wrong name) and Mt.Asahidake. I would like to add that in both instances, SR was given a week ban.
- EE: When the user Nil Einne posted a CT warning to EE's talk page, EE instead copypasted it and used it against the user Tinynanorobots, whom SR has been feuding with previously and currently with this EE account.
2. Retaliatory filings and unfounded socking accusations towards other users he's feuding with.
- Retaliatory filings by SR: [10] in response to [11], [12] in response to the disruptive editing warning by Xslyq above. [13] in regards to a user SR was feuding with at the time.
- Retaliatory fillings by EE: [14] in response to [15], [16] in response to [17], [18] in response to [19] and, of course [20] to this SPI request.
- Socking accusations by SR: [21], [22], [23], [24], [25]
- Socking accusation by EE: [26], [27] I would like to add that 天罰れい子 in 24 and 25 and ぼーしー were accounts SR was feuding with in the Japanese wiki and that he tried to file retaliatory RfCs against them via one of his socks, やまとぉ. The fact that EE included ぼーしー in his SPI request is already suspect enough, given their history.
3. Tendency to scrub warnings from their talk page to hide misconduct.
- SR EN: [28], [29], [30], [31], [32], [33], [34], [35]
- SR JP: [36], [37], [38], [39], [40], [41], [42], [43], [44], [45], [46]
- EE: [47] Scrubbing an edit war warning from Hemiauchenia
4. Gaslighting other users.
- SR: [48] in relation to [49][50][51], This thread in its entirety [52]
- EE: [53],[54],[55], This thread in its entirety [56]
I would include the lawyering and consensus bludgeoning by both accounts, as well as examples of misconduct by his socks on the JP wiki but this comment is already long enough as is and frankly it's a pain to comb through. SR has a history of using socks and without a permanent solution, the issues will keep reappearing, maybe it's high time to hold a discussion with the JP admins regarding this user, since the misconduct has crossed over wikis. 14.192.214.186 (talk) 00:31, 22 December 2024 (UTC)
The IP that posted this User:23.241.114.128, User:14.192.214.186, and ぼーしー are the same person. It's a long term abuser who _targets users Gitz6666, Symphony Regalia, and BrocadeRiverPoems. https://en.wikipedia.org/wiki/Wikipedia:Sockpuppet_investigations/Tofflenheim EEpic (talk) 01:05, 22 December 2024 (UTC)
- If I'm one of the "long term abusers" of BRP, why would I include evidences 10-11 and 21-22, when it is all about SR harassing BRP? FYI, I already expected that you would immediately make this accusation, because it's on point of you to label opponents as such. 14.192.214.186 (talk) 01:40, 22 December 2024 (UTC)
Would the following suffice?
Both accounts pushing for this specific line who served as retainers to lords (including daimyo)
, that and the back and forth with the user Tinynanorobots.14.192.214.186 (talk) 19:40, 23 December 2024 (UTC)
- I already responded to this.[69] I'm not the originator of that line it was added by Hemiauchenia[70] and that information about retainers and nobility has been in the lead for over 10 years as I explained here. My edit restores other changes that are you ignoring.
- This is misleading on purpose and you an obvious IP sock on a proxy.
- https://en.wikipedia.org/wiki/Special:Contributions/14.192.208.3
- https://en.wikipedia.org/wiki/Special:Contributions/14.192.212.242
- https://en.wikipedia.org/wiki/Special:Contributions/14.192.209.218
- https://en.wikipedia.org/wiki/Special:Contributions/14.192.213.32 EEpic (talk) 20:37, 23 December 2024 (UTC)
- Hemiauchenia added paragraphs, not just that single line. You and SR, on the other hand, are fixated on the same line while reverting any changes that TNR did to it. I've been transparent in that I've stated I was the IP that posted the previous SPI request, my IP that's granted by my ISP is dynamic.
- However, the first IP you linked has no relation to me, it's another attempt of "throwing stuff at the wall to see what sticks", much like your previous comment and the one in the other SPI request. I'm more curious on how you got the 3rd IP ready on hand, when it's an IP that SR once replied to. 14.192.214.186 (talk) 22:37, 23 December 2024 (UTC)
- I also added paragraphs which you are ignoring on purpose because the edits don't match. And no, I figured you would say it is your real IP, but it's not.
- https://www.ipqualityscore.com/free-ip-lookup-proxy-vpn-test/lookup/14.192.214.186 which says "PROXY".
- You are a very clear sock abusing proxies. Most of your abuse can be found with https://en.wikipedia.org/w/index.php?title=Special:Contributions/14.192.0.0/16. You just want to _target editing opponents. EEpic (talk) 22:57, 23 December 2024 (UTC)
- Isn't that the exact argument that SR used? To which BRP told SR off for it.
- Also, isn't this section supposed to be defending yourself from accusations, rather than turning accusations back to your accuser? 14.192.214.186 (talk) 02:23, 24 December 2024 (UTC)
- The fact that are you using proxies isn't private information that only one person knows. It can be checked by anyone. You are an IP sock abusing proxies in bad faith.
- https://www.ipqualityscore.com/free-ip-lookup-proxy-vpn-test/lookup/14.192.212.242
- I think your M.O is to _target your editing opponents. EEpic (talk) 04:12, 24 December 2024 (UTC)
Symphony Regalia and Ethiopian Epic don't only have similar interests, they have restored the same lines on three different pages. The "retainers serving daimyos" has already been mentioned. Considering the reasons given for the edits by EE, it seems possible that most of the edits were cover for restoring this one line.[71] His first edit misleadingly claimed to be adding improvments but removed cited information to restore the lead to how it was in September. The first reason he gave was NOR [72] which only applied to material that he had not removed in the first two edits. He later claimed the information was unsourced.[73] When he finally discussed content on the Talk page, he only mentioned samurai serving nobles as attendants and samurai serving daimyos.[74][75] This suggest the other edits were a smoke screen, and the "relationship to nobles" was really what he disagreed about.
SR's last post on List of foreign-born Samurai in Japan [76] was restored as part of EE's first post there.[77]. What makes this interesting is that both SR and EE were both reverting a pro-samurai edit by changing "stipend" and "fought" back to "salary" and "served". This despite both of them otherwise acting as enforcers of the RfC. On Yasuke, SR's first post there was to restore "As a retainer, Yasuke recieved etc"[78] After a RfC, retainer was changed to samurai. Again, EE restored the "As a" version with his first edit to Yasuke.[79]
Regarding the IPs there are several IPs from around the world that either have agreed with EE or EE has agreed with them. This seems similar to what was said in 2020 about SR regarding this diff[80] These IPs only post on one day and never post again, and are often the only ones that agree with EE. As the List of foreign-born samurai has rather a low view rate[81], and the version of the article that they prefer doesn't fit with the typical defintion of a samurai, it is rather odd.[82][83][84] All other IP edtiors on the article try and remove Yasuke. As mentioned in my previous filing, there was an IP that asked a question during the ArbCom process. A user responded to the IP, received a response from a 2nd IP, as if they were the same person.
None of this evidence in itself is proof, but there are a bunch of coincidences that add up. For example:[85] As part of the ANI he brought up the ArbCom case multiple times, this time he canvassed three users who gave evidence against me. However, not Symphony Regalia, who gave the most "evidence" against me. Also, SR also canvassed Gitz when he was involved in a ANI case.[86] Loki and Aquillion also supported SR at that case.[87] Tinynanorobots (talk) 16:56, 26 December 2024 (UTC)
Additional evidence: SR copying a message put on his Talk Page and posting the other user's page[88][89] EE doing the same [90][91]
SR also added the line about Oda's death[92] that EE has restored [93]. SR had also removed a similar line about Yasuke arriving in Japan as a slave.[94] Links have already been shared of EE reverting this. Tinynanorobots (talk) 10:44, 27 December 2024 (UTC
- Not much for me to say besides Tinynanorobots is only posting here because he is upset that admins at AE are not pleased with his editing. It's an attempt to _target his editing opponent. He was directly told at AE by an admin who evaluated even more his evidence
I think that it would be declined if it were an WP:SPI report and the editor should be mindful not to throw sock accusations around willy-nilly
and yet here he is rehashing the same argument. - You are ignoring that the diffs don't match. How many people have restored the same "who served as a samurai" line in various forms? Here's a few but my count it's over 10 editors.
- https://en.wikipedia.org/w/index.php?title=Yasuke&diff=prev&oldid=1257602496
- https://en.wikipedia.org/w/index.php?title=Yasuke&diff=prev&oldid=1262088354
- https://en.wikipedia.org/w/index.php?title=Yasuke&diff=prev&oldid=1236816177
- https://en.wikipedia.org/w/index.php?title=Yasuke&diff=prev&oldid=1241316774
- https://en.wikipedia.org/w/index.php?title=Yasuke&diff=prev&oldid=1245345956
- https://en.wikipedia.org/w/index.php?title=Yasuke&diff=prev&oldid=1245331380
- https://en.wikipedia.org/w/index.php?title=Yasuke&diff=prev&oldid=1245625043
- It's not uncommon for people in the same topic area, in the same dispute. He is also ignoring all the IP editors who agree with his positions.
- https://en.wikipedia.org/wiki/Special:Contributions/183.98.166.195 - here is an IP editor who made one post defending Tinynanorobots, and then got blocked as a proxy.
- More examples:
- I wouldn't be surprised if the IP sock here 14.192.214.186 could be Tinynanorobots. Tinynanorobots has also made many frivolous threads about me that had nothing to do with socking accusations, simply because he didn't like my content position, which is why I read the dispute history. But it highlights that he's attempting the "throw stuff at the wall and see what sticks" strategy which is what he was already lectured about him by an admin
this really appears to me to be "throw stuff at the wall and see if it sticks".
EEpic (talk) 20:38, 26 December 2024 (UTC)- You must have put the in wrong diffs, because most of those don't show what you say. Not all those links show other users restoring "as a samurai." Also, SR is the only one who was tbanned. Aquillion doesn't need a sock. Two of those IPs disagree with me. Tinynanorobots (talk) 10:18, 27 December 2024 (UTC)
- It shows what I want to say and I'm not sure why you're avoiding the question. How many people made a similar serve as a samurai edit? [95][96][97] The "As a" edit was made by other editors too.[98][99] It's not uncommon for people in the same topic area, in the same dispute. You are just throwing stuff at the wall in a long rant with uncivil conspiracy words like "smoke screen" because you want to _target an editing opponent. EEpic (talk) 16:04, 27 December 2024 (UTC)
- You must have put the in wrong diffs, because most of those don't show what you say. Not all those links show other users restoring "as a samurai." Also, SR is the only one who was tbanned. Aquillion doesn't need a sock. Two of those IPs disagree with me. Tinynanorobots (talk) 10:18, 27 December 2024 (UTC)
Clerk, CheckUser, and/or patrolling admin comments
edit- Additional information needed - I ran a CU because I was already suspicious of EE's editing, based on behavior at SPI and AE. Technical data is Inconclusive. Behavioral evidence here is extremely weak: the diffs mostly have to do with shared POV and what is alleged disruptive editing, and not the sort of specific similarity we would base a block on. I will leave this open for a little while if anyone wishes to provide more specific behavioral evidence. Absent such evidence, I will close with no action. No comment with respect to IP address(es). Vanamonde93 (talk) 17:44, 23 December 2024 (UTC)