Wikipedia:Sockpuppet investigations/Fly High in the Sky/Archive

Suspected sockpuppets



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

This user showed up shortly before the IP was blocked, but well after the IP started editing. It's suspicious for their first few edits to be on the IP's user talk page. They also both write in the same broken English. Both claim to be English (the IP here and the account on their userpage). I think the behavioral evidence is conclusive. I wouldn't normally report this as an instance of socking but here they are clearly evading the block on the IP. It also somewhat looks like a good-hand bad-hand kind of situation. Jasper Deng (talk) 22:27, 31 March 2019 (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
I help with Unicorns is ✅ to. . .  In the future, whenever you file a report where there is a named account and one or more IPs, the named account should always be the master. It's irrelevant who edited first and who you think is evading whom. Thanks. Please merge this into the correct case.--Bbb23 (talk) 23:44, 31 March 2019 (UTC)
 * ✅. Sir Sputnik (talk) 01:55, 1 April 2019 (UTC)

Suspected sockpuppets



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

Block evasion. Here are some examples:. It's probably the same person, but I'm requesting Check User just to confirm. Even if they turn out to be unrelated, the sock puppet needs to be still blocked for WP:VOA. Woshiyiweizhongguoren (🇨🇳) 22:08, 9 April 2019 (UTC)

Comments by other users
''Accused parties may also comment/discuss in this section below. See Defending yourself against claims.''
 * Any sleeper accounts? Woshiyiweizhongguoren (🇨🇳) 23:08, 9 April 2019 (UTC)

Clerk, CheckUser, and/or patrolling admin comments

 * This is obvious enough to not require CU attention. . Sir Sputnik (talk) 22:48, 9 April 2019 (UTC)
 * This was done without CU evidence, so no. Sir Sputnik (talk) 19:33, 10 April 2019 (UTC)

Suspected sockpuppets



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

After the recent activity on some 2019 hurricane/cyclone season articles this week, I cannot help but notice that the newest VOA accounts seem to be behaviorally related to this sockmaster. There is definitely some quacking here. The first 2 accounts listed have already been CU-linked; however, I would also like to say that they are probably socks of Fly High in the Sky, given their editing behavior, username patterns, articles (areas) of interest, and personal attacks. For example, this attack by one of the newer accounts, with its broken English, is awfully similar to an older threat by the sockmaster to hack someone's account, as well as being similar to other personal attacks made more recently by this person's socks (including an IP sock). This is much too similar to be a mere coincidence. The second pair of accounts, namely, the "Hurricanelover101" pair, are obviously related to each other, given the behavior (such as these edits ), but a CU was never run on those accounts to establish who the actual master was. Since the vandalism on the second pair came soon after the socks Hurricane Bunter and Vand3lsB0T were indeffed, not to mention that they target the same kind of articles, I'm inclined to believe that they are also related to Fly High in the Sky.  Light and Dark2000  🌀 (talk) 08:38, 14 April 2019 (UTC)
 * Please run a sleeper check and block the underlying IP(s) of the sock accounts, because this person has been persistently socking for a while now, and it's clear that they are not going to stop their disruptive behavior unless further action is taken.  Light and Dark2000  🌀 (talk) 08:38, 14 April 2019 (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

 * No action is necessary. Closing. Bbb23 (talk) 13:28, 14 April 2019 (UTC)

Suspected sockpuppets

 * (listed for reference)
 * (listed for reference)
 * (listed for reference)


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

. The account in question is an obvious sock of Hurricane Name Changers Alert, given these edits. The socks probably belong to Fly High in the Sky, given the behavior (you can see the 14 April 2019 case for more details). Please run a sleeper check. The "newest" account was a sleeper that was dormant for 5 months, and given the recent activity, it's likely that this sockmaster has more accounts out there.  Light and Dark2000  🌀 (talk) 03:10, 15 April 2019 (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

 * These are all already blocked, and another CU has already looked at them before this SPI was filed, so I don't see the need to redo the work here. Closing. TonyBallioni (talk) 03:37, 15 April 2019 (UTC)

Suspected sockpuppets



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

The user has had a history of having sockpuppet accounts that mainly edit hurricane and airline articles (see contributions for other suspected socks here with this IP address as well as with this IP, and leaves messages attacking a user using offensive language on their talk pages here and here. All IP socks and the one I am currently reporting have been geolocated to the same place. Rosalina2427  (talk to me) 15:01, 1 November 2019 (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

 * blocked for 3 months. Ivanvector (Talk/Edits) 15:53, 1 November 2019 (UTC)