Steward requests/Checkuser

From Meta, a Wikimedia project coordination wiki
This is an archived version of this page, as edited by 春卷柯南 (talk | contribs) at 13:07, 10 September 2021 (→‎O0yiu0o@zh.wikipedia). 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

Suresuremoon@zh.wikipedia

Hi. I hope you can explain why this checkuser should be processed. For example, it would be nice to explain why this can't be a duck, and what's obscure. --Sotiale (talk) 12:27, 6 September 2021 (UTC)[reply]
Judged from past experience, they could also be a meat. A checkuser would be preferred than a duck. Itcfangye (talk) 11:28, 7 September 2021 (UTC)[reply]
If this is meat, you can't find their relationship as a checkuser. In order for this request to be processed, you just need to explain why they were hard to see as duck. As long as this is explained, this request can be processed. --Sotiale (talk) 13:05, 8 September 2021 (UTC)[reply]
Local admin reviewed this case and marked as a duck. Consider it withdrawn? Itcfangye (talk) 09:41, 9 September 2021 (UTC)[reply]

Tuankiet2021@global

More than a spammer, Tuankiet2021 looks like a new editor doing the usual novice mistakes trying to write about non-notable subjects and being mad at them articles being deleted. I see that both have contributed to vi:Võ Tuấn Kiệt and apparently Simplevtk is asking for the article to be restored at vi:Wikipedia:Ứng cử viên bài viết tốt/Võ Tuấn Kiệt which could mean sock or meat puppetry. If they're being disruptive, local blocks could be issued. It doesn't look like CheckUser would be needed here. In any case, the only projects where Tuankiet2021 and Simplevtk have both edited (and where a comparison could be performed) are vi.wikipedia and ko.wikipedia. Both have their own local checkusers. This request is therefore declined. —MarcoAurelio (talk) 11:02, 9 September 2021 (UTC)[reply]
Nidezmusic (talk contribs deleted contribs logs block user block log CentralAuth AllContribs checkuser investigate)
Nguyenxuanphuc2021 (talk contribs deleted contribs logs block user block log CentralAuth AllContribs checkuser investigate)
I found some other accounts here, but won't bother you anymore.
Unnamed UserName me 16:50, 9 September 2021 (UTC)[reply]

星辰傳@zh.wikipedia

Not done. The sleepers check is implemented very limitedly to prevent users who continue to create accounts for a long time, including LTAs, from causing disturbance in the project. I'm not sure if this is the case that sleepers check is possible. --Sotiale (talk) 12:24, 9 September 2021 (UTC)[reply]

O0yiu0o@zh.wikipedia

Comment Comment I didn't find a relevant discussion on local HAM page. Can't decide if there is consensus. --Super Wang (Chinese Wikimedian since 2009 | Greetings from Dalian) 23:01, 9 September 2021 (UTC)[reply]
This is a general CU request from the sysop. If time is urgent, maybe not much discussion is needed? AnYiLinTalk 01:40, 10 September 2021 (UTC)[reply]
I don't think that it is an urgent case, we can keep the article on hold until the CU process is complete. I hold the same suspicion after reviewing their editing history, but can't confirm if they are obvious sockpuppets to each other. Inputs from HAM may be necessary. --Spring Roll Conan ( Teahouse · Contributions ) 13:07, 10 September 2021 (UTC)[reply]

See also