Edge Rewrite
// request.cf · coarse context

A page that knows where it met you.

Only coarse request metadata is shown. This demo does not display or persist visitor IP addresses.

Country
US
Cloudflare location
CMH
Connection
HTTP/2
Language
Not provided

Ray ID: a2705ff5c8b14b67

Jump to content

Wikipedia:Requests for checkuser/Case/TimySmidge

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

First ran into TimySmidge because of a premature RfA that got snowballed. Got more involved with him due to his violation of Fair Use policy with articles in userspace. I suddenly received notices about "his son", User:TimySmidge Jr. I also received an unlogged-in request from the son, asking about retrieving his lost password. Then earlier today, I received a random (and mildly negative) comment from a brand-new user, User:ChristianHJH, alerting me to yet another Smidge sock, (the Harry Potter Fan one). (and I've had experiences with a puppetmaster "alterting" me to their other socks, and there's little reason for any new user to come to me first about such news) The user creation log confirms that "Harry Potter Fan" was created by the original TimySmidge account.

TimySmidge is also involved in a currently open SSP case: Wikipedia:Suspected sock puppets/Peter Vogel. I'd like CheckUser run so we can wipe out all the socks that might be hiding in the drawer. EVula // talk // // 02:47, 28 September 2007 (UTC)reply

Results:

++Lar: t/c 17:26, 28 September 2007 (UTC)reply

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.