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: a28994a16e5152f1

Jump to content

Wikipedia:Requests for checkuser/Case/ThePackLeader

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/ThePackLeader}}
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.
  • Code letter: B

Buzybeez (talk · contribs) appears to be a sock-puppet of ThePackLeader (talk · contribs) based on the timing of the creation of the accounts, as well as the type of edits made. ThePackLeader (talk · contribs) was blocked as a single purpose account that was making disruptive edits at the ArbCom Enforcement noticeboard per the remedies of the ArbCom case. Buzybeez (talk · contribs)'s first edits were on the talk page of the article in question, and as soon as he could do so (after the 4 day restriction on new accounts), s/he began editing the main article (St Christopher Iba Mar Diop College of Medicine) with disruptive edits, such as deletion of the {{unaccredited}} template. An admin declined to block Buzybeez (talk · contribs) as a disruptive WP:SPA per the terms of the ArbCom case, as s/he has edited a couple of other articles in-between, and suggested a RFCU to determine if sockpuppetry was involved, so that the user could be blocked as a ban-evading puppet. Leuko 23:38, 17 July 2007 (UTC)reply

Red X Unrelated. --jpgordon 20:17, 18 July 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.