Steward requests/Checkuser

This is an archived version of this page, as edited by Automatik (talk | contribs) at 21:08, 18 May 2019 (→‎Brunehault@fr.wiktionary). It may differ significantly from the current version.
Shortcut:
SRCU
Checkuser icons
These indicators are used by CheckUsers and stewards for easier skimming of their notes, actions and comments.
{{Confirmed}}:  Confirmed {{MoreInfo}}: MoreInfo Additional information needed
{{Likely}}: Likely Likely {{Deferred}}: Deferred Deferred to
{{Possible}}: Possible Possible {{Completed}}: Completed Completed
{{Unlikely}}: Unlikely Unlikely {{TakeNote}}: Note Note:
{{Unrelated}}: Unrelated Unrelated {{Doing}}: Doing...
{{Inconclusive}}: Inconclusive Inconclusive {{StaleIP}}: Stale
{{Declined}}:  Declined {{Fishing}}: Fishing CheckUser is not for fishing
{{Pixiedust}}: Pixiedust CheckUser is not magic pixie dust {{8ball}}: 8ball The CheckUser Magic 8-Ball says
{{Duck}}:  It looks like a duck to me {{Crystalball}}: Crystalball CheckUser is not a crystal ball

This page is for requesting CheckUser information on a wiki with no local CheckUsers (see also requesting checkuser access). Make sure to follow the following instructions, or your request may not be processed in a timely manner.

Before making a request:

  1. Make sure you have a good reason for the check. It will only be accepted to counter vandalism or disruption to Wikimedia wikis. Valid reasons include needing a block of the underlying IP or IP range, disruptive sockpuppetry, vote-stacking, and similar disruption where the technical evidence from running a check would prevent or reduce further disruption.
  2. Be specific in your reasons. Ambiguous or insufficient reasons will cause delays. Explain the disruption and why you believe the accounts are related, ideally using diff links or other evidence.
  3. Make sure there are no local checkusers.
  4. Please ensure that the check hasn't already been done:


How to make a request

How to make a request:

  • Place your request at the bottom of the section, using the template below (see also {{srcu}} help).
    === Username@xx.project ===
    {{CU request
     |status          = <!--don't change this line-->
     |language code   = 
     |project shortcut= 
     |user name1      = 
     |user name2      = 
     |user name3      = 
    <!-- Max 10 users -->
     |discussion      = [[Example]]<!-- local confirmation link / local policy link -->
     |reason          = Reasons here. ~~~~
    }}
    

    For example:

    === Example@en.wikipedia ===
    {{CU request
     |status          = <!--don't change this line-->
     |language code   = en
     |project shortcut= w
     |user name1      = Example
     |user name2      = Foo
     |user name3      = Bar
    <!-- Max 10 users -->
     |discussion      = [[:w:en:Example]]<!-- local confirmation link / local policy link -->
     |reason          = Reasons here. ~~~~
    }}
    
  • Specify the wiki(s) you want to perform the check on.
Cross-wiki requests
Meta-Wiki requests

Requests

Vijay bramhane@mr.wikipedia, hi.wikipedia

English Wikipedia has its own CU and therefore cannot be checked from SPI: you need to request CU on enwiki using enwiki process. (Not doing check now since I'm typing with my phone) — regards, Revi 12:13, 11 May 2019 (UTC)[reply]
@-revi: on enwiki they are already confirmed and blocked the link is given above, but enwiki investigation could not confirm one more account because of lack of technical information. So, I am requesting here to run CU on mrwiki and hiwiki where you might have plenty of technical information about that particular account. and I am requesting here,
  • Check other projects where they are active mrwiki and hiwiki and if they have more related accounts.
  • There is a strong behavioral evidence that they are related to other active accounts on mrwiki, and I want to know if that is true. (I got it, my bad, corrected the way I had filled the request template!) QueerEcofeminist "cite! even if you fight"!!! [they/them/their] 18:04, 11 May 2019 (UTC)[reply]
Claiming this, waiting for enwiki CU for some more info. — regards, Revi 06:00, 13 May 2019 (UTC)[reply]

Brunehault@fr.wiktionary

  Confirmed As well as Tazoa Trekhei, Constance de Planque, Méta Kitrina, Koalabray, Tiotiotyx, Lou Write, Hendiadyne, Jbviguier and Frago Syriani. Ruslik (talk) 19:37, 18 May 2019 (UTC)[reply]
Ruslik thank you. That is insane how many accounts this contributor can create. — Automatik (talk) 21:08, 18 May 2019 (UTC)[reply]

Caverdom@commonswiki

enwiki and Commons have their own CU. There is no global CU. You have to exactly specify the project names if you want this CU to run (of course, projects without local CU). Closed. — regards, Revi 08:04, 16 May 2019 (UTC)[reply]
@-revi: does this mean that if a user has been blocked for harassing a user on one project, they are free to continue their harassing on another project? Is there no way to deal with that? Alexis Jazz (talk) 08:15, 16 May 2019 (UTC)[reply]
I don't know why you are inferring such conclusion: If they edited other project, you can ask for a CU there. In this case I can see some edits on either enwiki or Commons: both have their own CU so this is effectively outside the Stewards jurisdiction. — regards, Revi 09:42, 16 May 2019 (UTC)[reply]
If you have read the header of this page,

This page is for requesting CheckUser information on a wiki with no local CheckUsers

— enwiki and commons both have local CUs. It's therefore outside the scope of SRCU. — regards, Revi 10:06, 16 May 2019 (UTC)[reply]
Since they're obvious LTA's, just go to SRG to get them locked. SRCU is usually for checking accounts on projects where there are no local CheckUsers. Vermont (talk) 09:52, 16 May 2019 (UTC)[reply]
@-revi: Nsmutte's enwiki socks don't have a Commons account attached. Caverdom doesn't have an enwiki account attached. (which, in itself, is kinda suspect) So neither Commons or enwiki would be able to confirm Caverdom is another Nsmutte sock, if I understand correctly. Both have meta accounts though. But if those can't be checked, the user effectively couldn't be stopped. Alexis Jazz (talk) 13:01, 16 May 2019 (UTC)[reply]
See the header and you will be able to find the correct location to file a CU request on meta. — regards, Revi 13:03, 16 May 2019 (UTC)[reply]
@-revi: I actually did initially arrive at Meta:Requests for CheckUser information, but thought that page was only for abuse on meta. Alexis Jazz (talk) 13:16, 16 May 2019 (UTC)[reply]
Meta as a project has its own CU thus Stewards usually (practically never) do not perform CU on Meta. — regards, Revi 13:18, 16 May 2019 (UTC)[reply]

  Comment @-revi: not disputing the decision to not CU, though noting the local meta effect of Omkaram12 and Cranxi. I think that there is the need for xwiki coordination between stewards and CUs to identify the underlying aspects to insert preventative measures.  — billinghurst sDrewth 10:15, 16 May 2019 (UTC)[reply]

I've done some checks as a Meta CU, and there isn't much that can be done in this case. Abuse is coming from multiple ranges without much overlap. – Ajraddatz (talk) 21:12, 16 May 2019 (UTC)[reply]
  • Commenting because -revi pointed this to me: Nsmutte socks can be locked/generally are when someone requests. Speaking only to the en.wiki ranges I have seen, there isn't much that can be done technically to prevent it because the collateral damage is too large. Generally, stewards will not assign themselves local CU on projects with CUs, and in my view this is a good thing. We can and do share data through a variety of means, but this also isn't a case that is particularly complex. The LTA announces itself very easily and they are almost always blocked and checked on local projects, and stewards will ordinarily lock. Alexis Jazz, the best thing to do would be to report to SRG, where a steward can run a loginwiki checkuser on the accounts and prevent xwiki disruption through locks. TonyBallioni (talk) 21:24, 17 May 2019 (UTC)[reply]

See also