Wikipedia:Requests for checkuser/Case/Rikara

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


[edit] Rikara

main edit links history watch
Filed: 15:47, 12 April 2008 (UTC)
  • Supporting evidence: User's first edits and general editing habits match those of the puppetmaster and his longer-used sock Karaku (talk • contribs • logs • block user • block log • checkuser).
    • First edit removing content in Code Lyoko and pushing for on-hiatus - [1], edits by Rikara and Karaku [2] [3]
    • Second edit trying to reinforce editor's original opinion on Talk:Garage Kids - [4], Rikara does same - [5]
    • Use of construction and/or inuse templates on newly created pages - [6], Karaku's last edit of a new page [7]
    • Identical habits in signing posts: dash before signing. [8] [9] [10]
    • Other editors agree that the two are likely one and the same: Seraphim Whipp, Gwernol

I am requesting checkuser because this user is quite obviously Rikara, editing while their block remains in effect (runs out on the 22nd). They're restoring the same edits as before and I'm already fed up with trying to work with this editor; as the talk pages of the first two accounts show, it is basically impossible. All I can say in their favor is that they've figured out the constant spewing of expletives and all-caps edit summaries weren't helping and are trying to avoid that. — Trust not the Penguin (T | C) 15:47, 12 April 2008 (UTC)

  • Confirmed all. Thatcher 13:10, 13 April 2008 (UTC)


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.