Wikipedia:Requests for checkuser/Case/Executor-usa

If you are creating a new request about this user, please add it to the top of the page, above this notice. Don't forget to add {{Wikipedia:Requests for checkuser/Case/Executor-usa}} to the checkuser page here. Previous requests (shown below), and this box, will be automatically hidden on Requests for checkuser (but will still appear here).

The following discussion is preserved as an archive of a Request for checkuser. Please do not modify it.

Waffleknocka / Executor-usa

• Executor-usa (talk · contribs)
• Waffleknocka (talk · contribs)

I suspect that these are the same user, though I'm not sure which is the sock and which the puppet. Executor-USA was banned for legal threats and should have been banned for vandalising the article OITC fraud (currently deleted, though a ongoing deletion review is likely to result in the article being recreated at a less POV name). At the same time, Waffleknocka created a POV fork (now also deleted) of the deleted article, plus a related article which I'm nominating for deletion. Both users have the same writing style and an apparently identical agenda. I suspect that Waffleknocka is a sock of Executor-USA. I believe that we are likely to see more vandalism/threats from this source if and when the disputed article is recreated, and in advance of that I'd like to confirm whether we do in fact have a sockpuppet issue here. -- ChrisO 12:22, 7 May 2006 (UTC)

I've discovered that Waffleknocka is/has been using an open proxy server in Cambodia (which I've now blocked indefinitely). I'd be interested to know if Executor-USA is also using an open proxy. Could whoever runs CheckUser please also Google the IP address that it produces to see whether it's on any proxy lists? -- ChrisO 10:26, 8 May 2006 (UTC)

Nope. Nothing showed up. He's been unbanned, incidentally. Mackensen (talk) 11:14, 9 May 2006 (UTC)

The above discussion is preserved as an archive of the Request for checkuser. Please do not modify it.
Subsequent requests related to this user should be made above, in a new section.