Jump to content

Wikipedia:Requests for checkuser/Case/CBFan

From Wikipedia, the free encyclopedia

CBFan (2nd)[edit]

Looks like this may be another block evading sock puppet, but I'm not certain enough to block without a check-user. - Philippe | Talk 16:07, 1 February 2008 (UTC)[reply]

  • Comment: The user has now admitted that this was a sock. I'd still like a C/U, though, for documentation purposes since it's a block evasion. - Philippe | Talk 13:26, 2 February 2008 (UTC)[reply]
 Confirmed Blnguyen (bananabucket) 03:40, 4 February 2008 (UTC)[reply]
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/CBFan}}
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.

CBFan[edit]

User:CBFan has been blocked by User:Spartaz, and carries quite a block log. His userpage states he's from the United Kingdom, and the IPs above resolve to Tivoli, in the UK. The edit summaries of the IPs have a quite distinct tone that I associate with CBFan. In addition, they seem to indicate that they're all by the same editor with comments such as "I've already told you this" from an IP that has never previously edited the page. I have sprotected the page for the duration of CBFan's block as a temporary measure but am happy to lift that protection if these are not found to be block-evading IP edits. - Philippe | Talk 19:28, 20 January 2008 (UTC)[reply]

information Note: per policy, I'm commenting regarding IP addresses due to the nature of the disruption involved here.
 Confirmed
 IP blocked - one other from a different range not mentioned here and used for evasion - Alison 20:25, 20 January 2008 (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.