Jump to content

Wikipedia:Requests for checkuser/Case/RichSatan

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


  • F:
  • Supporting evidence: [1]

As diff shows, self-confessed sockpuppet of banned user. First CU here. Darkson (BOOM! An interception!) 09:45, 11 April 2008 (UTC)[reply]

 Clerk note: merged with the previous case. -- lucasbfr talk 12:03, 11 April 2008 (UTC)[reply]
It might also be useful to check against:
91.84.70.216 (talk+ · tag · contribs · filter log · WHOIS · RBLs · proxy check · block user · block log · cross-wiki contribs · CheckUser (log))--Cailil talk 21:18, 11 April 2008 (UTC)[reply]


RichSatan has a history of incivility and ad-hominem attacks[2][3] his last edit was Feb 21st 2008. Byaahahaha, a probable sock-puppet[4] was indef blocked by User:SirFozzie on Feb 21st 2008 for vandalism and talk page blanking. IP 91.84.95.68 made the same claims that RichSatan started making in Nov 2008 today, on March 12th 2008 [5]. If these Ips resolve to RichSatan this trolling has been on-going since at least Feb 2007 to the present day.

Connections with Byaahahaha

Talk page blanking and removals of references to RichSatan
[6][7][8][9][10][11] by RichSatan
[12][13] by Byaahahaha

Connections to the IPs

Insistence on the inclusion of unsourced criticism at Talk:Games Workshop
[14][15][16] by RichSatan
[17] by 91.84.95.68
[18] by 82.152.179.208
[19] by 82.152.177.104
[20][21] by 82.153.198.246
[22] by 82.152.178.70
--Cailil talk 19:07, 12 March 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.