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/Harvardy))
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.

Harvardy[edit]

Two things going on here. First, it is alleged that Harvardy is a sockpuppet of permanbanned user Wik (talk · contribs · deleted contribs · logs · filter log · block user · block log) aka Gzornenplatz (talk · contribs · deleted contribs · logs · filter log · block user · block log). Obviously too old for a direct check but maybe there is buried knowledge about Wik's general geographic location.

Second, irrespective of whether Harvardy is Wik, Harvardy has engaged in edit warring at Micronation (edit | talk | history | protect | delete | links | watch | logs | views) and Empire of Atlantium (edit | talk | history | protect | delete | links | watch | logs | views), two of Wik's favorite topics. However, two of the IPs performing the reverts are in Korea and Germany, making me suspect they are open proxies. Two other IPs are geographically related Canadian ISPs. Harvardy is, of course, asking to be unblocked. The questions here are, is there any corroboration that this might be Wik; has Harvardy been using open proxies; and has Harvardy in general been editing while logged out, using any of these or other IPs? Thatcher131 22:51, 7 November 2006 (UTC)[reply]

 Inconclusive Open proxies blocked (further puppets found on one of them: Ljublonia (talk · contribs), Slovenskidom (talk · contribs), Kaksyjzsfg (talk · contribs)) but there's no strong IP evidence to link Harvardy to any of the IPs. Dmcdevit·t 05:40, 8 November 2006 (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.