Wikipedia:Requests for checkuser/Case/Hemanshu

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/Hemanshu}}
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.
  • Supporting evidence:
See Wikipedia:Suspected sock puppets/Hemanshu. Looks to be a case of block evasion by Hemanshu. The newly-created account has a monobook.cs that is identical to that of Hemanshu, and it is making similar edits to the year articles, like 2009. (Hemanshu was edit-warring on the month entries in 2012, which is what led to his three recent blocks, the last of which was for one week and began on 31 December). Since a case on desysopping Hemanshu has been filed with Arbcom, it is desirable to have as good evidence on this as possible. Though a block based on the SSP report could be justified, evidence does not seem good enough for an indef. Checkusers might have more luck in determining this for sure, and should anyway do a check in case this is used as evidence for Arbcom. EdJohnston (talk) 19:24, 3 January 2009 (UTC)[reply]
 Confirmed. Nishkid64 (Make articles, not wikidrama) 19:53, 3 January 2009 (UTC)[reply]
Ed - just to let you know that this is already being handled by the Arbitration Committee so it should probably be left in their hands for now. Ryan PostlethwaiteSee the mess I've created or let's have banter 20:06, 3 January 2009 (UTC)[reply]

information Note: Socks and sleepers indef'd. Hemanshu's block length under discussion. All socks tagged.RlevseTalk 22:51, 3 January 2009 (UTC)[reply]

He was desyssoped and I've extended his block for 10 days from today.RlevseTalk 03:48, 4 January 2009 (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.