Wikipedia:Sockpuppet investigations/Richeagleeye/Archive

Suspected sockpuppets



 * User compare report Auto-generated every hour.
 * Editor interaction utility

Quack! Two accounts created 22 hours apart with very similar usernames, and Richeaglenoble'snedits on the morning September 11 (a string of nonsense edits to their own talk page clearly designed to become autoconfirmed and get around the semi-protection on the Goguryeo) look almost identical to Richeagleeye's entire edit history. Requesting CU for confirmation, and also to find sleepers because the Richeaglenoble account is primarily active on an article that was semi-protected because of "persistent sockpuppetry" (in a topic area that has been swarming with sock-farms for more than a decade) and their early edits show a precocious awareness of how to get around said page protection. (This is his modus operandi: on September 6 Richeaglenoble did the same on ja.wiki to get around the semi-protection on an article he wanted to edit.) Hijiri 88 ( 聖やや ) 23:52, 12 September 2017 (UTC) Hijiri 88 ( 聖やや ) 23:52, 12 September 2017 (UTC)
 * Note It's entirely possible the Richeaglenoble account will be CIR-blocked for persistent copyright-infringement before anyone looks at this SPI. But this SPI should still go ahead anyway for reasons that should be obvious to anyone whose opinion counts. Hijiri 88 ( 聖やや ) 00:08, 13 September 2017 (UTC)
 * Shit, you're right. Any idea how I do that now I've already opened the SPI? Templates have been very difficult for me lately, for whatever reason.
 * I'll get it. NinjaRobotPirate (talk) 09:57, 14 September 2017 (UTC)


 * The Richeaglenoble account has been indefinitely blocked by SpacemanSpiff for a bunch of other reasons, but as I said above the SPI should run its course because an indef block is pretty meaningless when the subject already has another account (or, I suspect, several other accounts) that isn't also blocked. Hijiri 88 ( 聖やや ) 13:21, 15 September 2017 (UTC)
 * Well, there's definitely block-evasion, if not abuse of multiple named accounts (see my talk page). I strongly suspect that the reason for the two accounts being created near-simultaneously was for the purpose of edit-warring on a page that was semi-protected. (FWIW, Bish told me in an email that she suspects the REE account was created and abandoned for whatever reason, possibly forgetting the password, but I don't necessarily buy that -- it seems just as likely that they decided they didn't like the username or one of a dozen or so other "good-faith" possibilities, in which case a user who was blocked for a bunch of abuses now has access to an account that hasn't been CU-blocked yet.) Hijiri 88 ( 聖やや ) 23:17, 15 September 2017 (UTC)
 * Hijiri, that may be so but there really is no reason to run CU. We know that they're the same, don't we? And the one account is blocked--so if the other, who hasn't made article edits, starts screwing around in article space, we'll know too. The block evasion pertains to the IPs--well, CU can't do all that much to prevent that, and in any case there also it's plain as daylight. Now, go perfect your Japanese! ;) Drmies (talk) 23:28, 15 September 2017 (UTC)
 * Meh. I still think the fact that he knew in advance that he wouldn't be able to edit the Goguryeo article until he made a bunch of nonsense edits to his own talk page indicates he has been here before. I guess reading some of the discussions spinning out of ARBPIA3, which led to SPAs making five hundred nonsense edits to their own talk pages, has put me on high alert about this kind of behaviour, though. (He also claims to have been pushing his agenda on his blog as early as 2008, which makes it seem really unlikely he never tried to edit the main online forum for Korean nationalists to "teach the world" about the "real history" before the end of last month.)
 * But if I can't convince you I guess I can't convince you. I'll keep an eye out for any more convincing evidence, anyway, and get back to trying to improve my "terrible Japanese" that has caused me to "misread" his edits to ja.wiki anyway. Man, if only it weren't for my "Chinese heritage" preventing me from learning to read and write Japanese correctly! Wait... ;)
 * Hijiri 88 ( 聖やや ) 00:10, 16 September 2017 (UTC)
 * I think you missed something here. Yes, both of the socks are currently blocked, but the main account isn't. It hasn't edited since the other accounts were created, so "they probably forgot the password for the Richeagleeye account" might be a reason to decline, but saying that they are all already blocked doesn't seem like it would be. Hijiri 88 ( 聖やや ) 08:01, 30 September 2017 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''

Added User:Plqaws12312 confirmed by an admin Ponyo.―― Phoenix7777 (talk) 23:36, 22 September 2017 (UTC)

Clerk, CheckUser, and/or patrolling admin comments
you mention checkuser, but you didn't request it. NinjaRobotPirate (talk) 05:55, 14 September 2017 (UTC)
 * Yeah, what's the point in running CU here? There's not even any abuse of multiple accounts (yet). And if it starts from the one account that's not blocked, it'll be easy enough to identify. More bothersome are the many IPs bothering Spiffy and Hijiri; if CU ever becomes necessary, those histories might be helpful. Drmies (talk) 23:06, 15 September 2017 (UTC)
 * - the alleged socks are both already indeffed; one is a CU block but I don't know which account they are connected to. Closing. Ivanvector (Talk/Edits) 14:39, 29 September 2017 (UTC)

Suspected sockpuppets





 * User compare report Auto-generated every hour.
 * Editor interaction utility

Common vandalism of articles involving Chinese and Korean culture and attacks on.  General Ization  Talk   20:15, 15 September 2017 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''

This should be merged with Sockpuppet investigations/Richeagleeye. Sorry -- I seriously considered opening the first SPI under the name of the more active account, but I think they are technically required to be under the earliest name. If CU identifies some random older sockmaster, the page will be moved anyway. Hijiri 88 ( 聖やや ) 20:23, 15 September 2017 (UTC)
 * is not and has never been blocked, and has received no warnings on their Talk page. Should they be/have been?  General Ization  Talk   20:28, 15 September 2017 (UTC)
 * The accounts were created at roughly the same time, have near-identical usernames, and both started editing by making ten nonsense edits to their own talk page to get around semi-protection. An admin speculated in an email correspondence with me that the Richeagleeye account was abandoned because they forgot the password or changed their mind on the username or something, and that this is evidence that they are a new user, but I suspect that the two accounts were created to support each other in edit wars, and the Richeagleeye account was specifically made to make enough edits to get around semi-protection and then go dormant until needed. Hijiri 88 ( 聖やや ) 20:36, 15 September 2017 (UTC)

By the way -- there's absolutely zero possibility these IPs are not REN. No one else calls me "Hijili" (apparently the Revised Romanization of the Korean approximation of the Japanese word that I use as my username), the timing is undeniable, and even though the apparently good-faith one Floq initially restored in good faith gave me pause, Kwontack Hang is a Korean nationalist fringe writer of historical works, and REN has demonstrated an interest in the question of whether different ethnic groups that have historically controlled (parts of) China have interbred and become ancestors of the modern Han Chinese. (This is actually, by far, the ugliest part of their edits, as it is the most blatantly fascist/eugenicist of the problems with his edits; the reason it was only briefly brought up on ANI is because "AGF" made it a lot easier to focus on COPYVIO and unambiguous claims about Chinese Wikipedia editors not being trustworthy.) Hijiri 88 ( 聖やや ) 20:30, 15 September 2017 (UTC)
 * Also by the way: I'm not going to go into details, but the account's recent activity on ja.wiki makes it pretty clear that he is primarily acting out of a desire to get under my skin at this point, which "gels" with the IPs attacking my user page here. No idea if any of this is relevant. Hijiri 88 ( 聖やや ) 21:16, 15 September 2017 (UTC)
 * Thanks. I have no objection to the merge you recommended above, but will leave its implementation to a clerk who knows how to do it properly!  General Ization  Talk   21:20, 15 September 2017 (UTC)


 * Obviously no point requesting a block against an IP that's never edited, but 203.109.6.86 is also him, as he's been going after me on ja.wiki. (Laughably, he logged out and posted on my talk page while there was an open unblock request on his talk page.) Leaving this here just for the record, in case any edits by this IP show up. Hijiri 88 ( 聖やや ) 07:50, 16 September 2017 (UTC)
 * Added for completeness' sake. Hijiri 88 ( 聖やや ) 22:29, 16 September 2017 (UTC)
 * Ditto and . See ja:ノート:篁物語. Hijiri 88 ( 聖やや ) 10:29, 18 September 2017 (UTC)


 * Added another. Reverting my edit to a draft I'm working on in my userspace. Hijiri 88 ( 聖やや ) 10:12, 18 September 2017 (UTC)

Clerk, CheckUser, and/or patrolling admin comments

 * This was copied from Sockpuppet investigations/Richeaglenoble. Sro23 (talk) 00:05, 16 September 2017 (UTC)
 * all look like ducks to me. These are pretty big ranges but with not a lot of activity other than this. Let's see:
 * blocked for 1 month.
 * blocked 1 week.
 * blocked 1 week.
 * all others are stale.
 * that the named account is connected to this sockpuppetry case is enough. They've escaped blocking because they don't seem to be using their account on this wiki.
 * @all: If disruption continues or resumes I can adjust these ranges, but closing for now. Ivanvector (Talk/Edits) 15:24, 29 September 2017 (UTC)