Wikipedia:Requests for checkuser/Case/TheMadTim

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/TheMadTim}}
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] TheMadTim

Possible abusive sockpuppets or impersonator. Of perma banned sockpuppeteer user:TheMadTim. --Karatekid7 00:39, 23 May 2006 (UTC)

Admin User:GraemeL confirmed that the last of these was an open proxy. All of the other IP addresses appear in Spam blacklists but without knowing which port the proxy server is running on, it would be impossible for me to confirm that they are proxies. Strange pattern when a new user comes on knowledgeable of my edit history and very aware of wikipedia policy. --Karatekid7 01:20, 23 May 2006 (UTC)
Not that the edits are definitely not from the areas, but I think there is something very dodgy here. --Karatekid7 02:46, 23 May 2006 (UTC)

Unrelated TheMadTim has created a number of sockpuppets, but the above do not appear to be directly connected to him. He was responsible for the following socks, however:

As for the proxies, check with the open proxy project. Essjay (TalkConnect) 05:30, 23 May 2006 (UTC)

Ok thanks, I tried that the open proxy project with no success, do they do a complete port scan?

These two confirmed sockpuppets of theMadTim (talkcontribslogsblock userblock log) I think would better show the pattern of vandalism in the socks that I have shown. --Karatekid7 09:42, 23 May 2006 (UTC)

are some more. Karatekid7 23:29, 23 May 2006 (UTC)

some more likely socks of this disruptive user. Karatekid7 20:58, 24 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.