Wikipedia:Requests for checkuser/Case/Kungfoofighting1

From Wikipedia, the free encyclopedia

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/Kungfoofighting1}}
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.

[edit] Kungfoofighting1

  • Code letter: E

Burntsauce was revert warring with several editors on the Terry Gerin article:

A couple of days later User:Kungfoofighting1 first appeared to make a revision on the Terry Gerin article back to the revision by Burntsauce [1]. Kungfoofighting1 was reverted twice by bots for vandalism before he started reporting these as "errors".

Kungfoofighting1 then committed 3RR on Terry Gerin, as reported on the 3RR report I filed.

It was determined that he was to be given a final warning because of his "new" status and the fact the warning was given almost at the same time as the revert.

Furthur evidence of this being a sockpuppet of Burntsauce was suggested when Burntsauce returned from a 3-day hiatus from editing with his first edit to Kungfoofighting1's talk page only an hour after Kungfoofighting1's first edit with Burntsauce making personal attacks against those he revert warred with. — Moe ε 19:24, 21 August 2007 (UTC)

Update: Kungfoofighting1 has committed 3RR again:
And I have reported it to WP:AN/3RR. — Moe ε 17:10, 24 August 2007 (UTC)
Unlikely, but since there are proxies involved it's hard to tell. However, Kungfoofighting1 (talk · contribs) seems to have had a few other socks operating off his proxies:
--Deskana (apples) 21:46, 25 August 2007 (UTC)
Clerk note: Above accounts blocked by Deskana. WjBscribe 00:49, 26 August 2007 (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.