Phoenix2923 ( talk ⁺ · tag · contribs · deleted contribs · logs · filter log · block user · spi block · block log · CA · CheckUser( log) · investigate · cuwiki)

30 April 2011

Suspected sockpuppets

• The REAL Dux ( talk ⁺ · tag · contribs · deleted contribs · logs · filter log · block user · spi block · block log · CA · CheckUser( log) · investigate · cuwiki)

• User compare report Auto-generated every hour.

Please list evidence below this line. Remember to sign at the end of your section with 4 tilde characters "~~~~"

Both editors have been exclusively involved with the article Frank Dux, specifically the talk page. You'll see in Phoenix2923's second edit, when confronted by Niteshift36 regarding the reliability of sources, he asked who Niteshift36 was. In his next edit he commented on Niteshift36's group affiliations. This questioning of Niteshift36 and his credibility continues, and his conflict with Niteshift36 escalated (just look over the whole of that article talk page, there would be too many diffs to bother with, and also the resultant ANI report). Phoenix2923 continued to participate on the talk page of the article for a total of 10 days, before his activity ended on January 26.

Then after 4 months of no activity, Phoenix2923 returns, at 21:22, April 28, 2011, and literally one minute later a new editor appears named The REAL Dux who claims to be Frank Dux himself. One of his first actions is to ask why his court records weren't accepted as a reliable source (which is the exact thing that Phoenix2923 had been arguing about for days), and demanded to know who Niteshift36 was and what his affiliations were (just as Phoenix2923 did). Both editors have targeted the same people and focused on the same subjects.

Phoenix2923 is now indefinitely blocked for his persistent personal attacks. The REAL Dux was blocked for making legal threats, but was unblocked after retracting them. (I was actually the person who unblocked him.) But I think that it's worth checking into whether The REAL Dux is actually Phoenix2923 under a different account, the behavioral evidence seems strong enough to warrant it. Atama 頭 00:16, 30 April 2011 (UTC) reply

Comments by other users

Obviously, I support this SPI. There is a strong change that IP editor 76.22.87.15 is involved. There was a SPI related to this article before, where sockblocking happened. [1]. User:Avianraptor, User:Avianraptor2, User:Justice4allseeker were all blocked as socks, all trying to argue the same material that Phoenix2923 and RealDux have been arguing.

Yes. Notice 76's edits from a couple of years ago, [2] making the same arguments. Should this SPI instead be a re-opening of that case? ← Baseball Bugs ^{What's up, Doc?} carrots→ 00:45, 30 April 2011 (UTC) reply

Clerk, CheckUser, and/or patrolling admin comments

•  Clerk endorsed - Likely; CU to clarify. — HelloAnnyong ^{(say whaaat?!)} 01:26, 30 April 2011 (UTC) reply
  •  Possible - Same geographic area, different ISPs/computers. No comment on any IPs mentioned. TN X Man 03:17, 30 April 2011 (UTC) reply
    • I'm going to sleep on this since it's so late where I am, but thank you for checking on this. -- Atama 頭 08:12, 30 April 2011 (UTC) reply
    • I just can't reconcile how an editor can come back from a 4 month hiatus to post one minute before another editor joins the same page, to take on the same cause and go after the same people, without there being some collusion involved ( WP:SOCK or WP:MEAT). The REAL Dux suggested that Phoenix2923 was a fan who had the article watchlisted, but that doesn't explain how Phoenix2923 returned a minute before The REAL Dux started posting. Since the technical data doesn't rule out sockpuppetry I feel confident in blocking The REAL Dux for abuse of multiple accounts, and I've done so. Thank you again. -- Atama 頭 17:17, 30 April 2011 (UTC) reply