Steward requests/Checkuser

From Meta, a Wikimedia project coordination wiki
Jump to navigation Jump to search
Requests and proposals Steward requests (Checkuser) latest archive
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}}: Symbol wait.svg Doing...
{{Inconclusive}}: Inconclusive Inconclusive {{StaleIP}}: Stale
{{Declined}}: 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 or policies.
  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



Autoblocks aren't configurable through wiki interface; it is configuration settings. — regards, Revi 07:14, 12 February 2019 (UTC)
Let me try to explain it in a clearer manner. This user is socking prolifically, the list of socks are found here. Based on local Checkuser policy [1], a CU can be conducted to find out the underlying IP / ranges of IP of all the accounts and then do a CU block (which must then be oversighted) to prevent new socks accounts to be created from the IP / ranges. This is what we are requesting. Anymore details do co-ordinate with Techyan. I am here to just explain on behalf what exactly is needed in more details. Best Regards, --Cohaf (talk) 18:39, 12 February 2019 (UTC)


  1. 检查已封禁的账户所使用的IP,便于延长自动封禁
    Check the IP addresses of blocked users, so as to extend the autoblock(s) accordingly
@Techyan: can you list the most recent 2 - 3 socks this user is using, sorry I am not that well to go through the list. Thanks.--Cohaf (talk) 18:53, 12 February 2019 (UTC)
Not stale:Alberteffendy22333 (talk • contribs • block • x-wiki • CA • ST • lwcheckuser),Alberteffendy40555 (talk • contribs • block • x-wiki • CA • ST • lwcheckuser),Alberteffendy50999 (talk • contribs • block • x-wiki • CA • ST • lwcheckuser),Alberteffendy70335 (talk • contribs • block • x-wiki • CA • ST • lwcheckuser),Alberteffendy89995 (talk • contribs • block • x-wiki • CA • ST • lwcheckuser),Alberteffendy90233 (talk • contribs • block • x-wiki • CA • ST • lwcheckuser),Alberteffendy90551 (talk • contribs • block • x-wiki • CA • ST • lwcheckuser),Alberteffendy92996 (talk • contribs • block • x-wiki • CA • ST • lwcheckuser),Alberteffendy92999 (talk • contribs • block • x-wiki • CA • ST • lwcheckuser),Alberteffendy95881 (talk • contribs • block • x-wiki • CA • ST • lwcheckuser),Albert20229 (talk • contribs • block • x-wiki • CA • ST • lwcheckuser).--MCC214#ex umbra in solem 11:29, 16 February 2019 (UTC)
On hold pending some related internal discussions. — regards, Revi 03:15, 13 February 2019 (UTC)
@-revi and Cohaf: Ctrl+F on this page and look for keyword "Albert". All recently discovered socks edited this page. Please block their IPs if what they are using are concentrate enough, or more ideally, all of them are using the same IP, and immediately oversight block logs - that's what we have always been done on zhwiki. --TechyanTalk) 03:42, 15 February 2019 (UTC)
It is allowed to block the underlying IP or range of IPs to prevent abuse, as specified in the Access to nonpublic personal data policy s.4(b)(v) - "the public, when it is a necessary and incidental consequence of blocking a sockpuppet or other abusive account". It is more complicated in this case because it is against our policies to take actions that a sysop could take (local blocks) when there are local admins who could perform them. This request is still on hold for the time being, as it is still under discussion. – Ajraddatz (talk) 00:23, 16 February 2019 (UTC)
Question Question: It seems that "extend the auto block" means "check the IP and enforce the CU block (if possible)". I have checked the log and I've found out that some stewards had done something similar before (though some of the logs have been removed). --云间守望 13:59, 18 February 2019 (UTC)


  • I added 2 more seems related accounts. ΣανμοσαThe Trve Lawe of free Monarchies 13:08, 2 March 2019 (UTC)
  • Please check if not only the accounts have any relations, but also there are any sockpuppets. ΣανμοσαThe Trve Lawe of free Monarchies 01:57, 3 March 2019 (UTC)
  • Add.--MCC214#ex umbra in solem 09:02, 5 March 2019 (UTC)
  • Add one.--MCC214#ex umbra in solem 09:15, 7 March 2019 (UTC)
Symbol wait.svg Doing... --Alaa :)..! 19:56, 14 March 2019 (UTC)
  • @علاء:I'm sorry but 20 hours passed since last reply so I did this comment to notify, please forgive me for bothering.-- CreampieGolden State Finals Champion 16:03, 15 March 2019 (UTC)

Hello @Hamish: it's Time2wait.svg On hold pending some related internal discussions --Alaa :)..! 23:17, 15 March 2019 (UTC)

    • @علاء:Copy that, sorry again for disturbing.-- CreampieGolden State Finals Champion 04:49, 16 March 2019 (UTC)


  •  Confirmed 命運石之門0, 白銀紫天使, 清朝(1636), 藍色水玲瓏, 台灣奇案, 七人幫, 藍色水玲瓏2, 麻將之王, 心電圖, Blue Crystal 060606
  • Possible Possible Tt334

This is 100% technical analysis and does not include behavioral evidence (For CUwiki ref. special:permalink/30486)--Alaa :)..! 16:58, 19 March 2019 (UTC)

Reported back. -★- PlyrStar93 Message me. 17:09, 19 March 2019 (UTC)
علاء,Blue Crystal 060606?--MCC214#ex umbra in solem 09:52, 20 March 2019 (UTC)
@MCC214: sorry I forget to added it. Done now --Alaa :)..! 11:58, 20 March 2019 (UTC)
Thanks, reported additional account back.--Cohaf (talk) 08:34, 21 March 2019 (UTC)

See also[edit]