Wikipedia:Requests for checkuser/Case/Layla27

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/Layla27}}
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] Layla27


  • Code letter: C
  • Supporting evidence: Recent diffs, including the most obvious socking I've ever seen: Deadly Nukes [1], followed by Ruby Tuesday [2], then Radioactive Menace [3] achieve a 'consensus' on Talk:Nuclear technology, and Radioactive Menace implements it here [4] and then expands [5] into his characteristic rant (we'll ignore the fact that Reagan wasn't president at the time of TMI).

Previous activity includes Liveandletdie [6], [7], [8], [9], [10]: also talk page abuse. Atomic Killer added [11] and [12].

Earlier list of diff's here:Wikipedia:Suspected sock puppets/Layla27

Yet more abusive accounts from this sockmaster, conforming to previous precedent. New accounts reappear every couple of days. This is the third case: all listed are indef blocked. IP 207.197.96.125 (talk contribs logs) from the previous case was unblocked on March 4, and I would strongly suggest that it be re-blocked ACB for a lengthy term. Acroterion (talk) 03:18, 18 March 2008 (UTC)

Added Nobodyknowsyouwhenyouredownandout and Gotmeonmyknees to this request. This is a persistent vandal to pages regarding nuclear power using the same tactics/messages and having user names relating to Cream/Eric Clapton songs/lyrics. He has apparently returned with new socks. Thank you for your assistance in this matter. Lwnf360 (talk) 16:01, 18 March 2008 (UTC)

Note:

  • Undiscovered socks:

IP blocked. Thatcher 23:48, 19 March 2008 (UTC)


[edit] Layla27


Second case here:Wikipedia:Suspected sock puppets/Westinghouse 31

Layla27 and verified sock puppets were blocked for sockpuppetry. A new sockpuppetry case indicates that the behavior has not subsided. Since an unknown number of sock puppets may be in use a category listing the possible sock puppets has been created: Category:Suspected Wikipedia sockpuppets of Layla27. New entries may be added to this list as new sockpuppets are used (after a previous sock puppet has been blocked). Burzum 07:24, 3 December 2007 (UTC)

All of these accounts are now indefinitely blocked for sockpuppetry, but many of them were created in the same period so any remaining unidentified accounts would be able to evade a semi-protection lock. It would be helpful to identify and block any accounts created between 26 November 2007 and now by somebody with matching IPs and if possible to restrict new account creation. One account was created on 18 November 2007, six of these accounts were created on 26 November 2007, and the remaining five were created on 29 November 2007 after the first sockpuppetry case became active. Based on this user's behavior, I think it is likely there are several unused sockpuppet accounts.--Burzum 17:54, 3 December 2007 (UTC)

Updated with 5 new suspected sockpuppet accounts created on 3 December 2007 (all are indefinitely blocked).--Burzum 06:04, 4 December 2007 (UTC)

IP blocked. I don't see any other accounts at the moment. Dmcdevit·t 21:28, 5 December 2007 (UTC)

I've added User:W345thn due to identical diffs here and here at Nuclear safety in the U.S., which match diffs from Rifleinmyhand here at Nuclear technology. The user was blocked 24 hours by TeaDrinker, after repeatedly blanking a report at WP:AIV from Gscshoyru. ZZ Claims ~ Evidence 05:40, 10 December 2007 (UTC)
I'm quite confident of the User:W345thn sock-puppetry and changed the block to indefinite (after the issue was pointed out to me). --TeaDrinker (talk) 05:48, 10 December 2007 (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.