Jump to content

Steward requests/Checkuser

From Meta, a Wikimedia project coordination wiki
This is an archived version of this page, as edited by AmandaNP (talk | contribs) at 06:21, 3 January 2024 (伟大的谢明@zh.wikipedia: d). 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

SotiaIIe@no.wikipedia

Comment: As Heymid is globally locked since two and a half years back, they cannot be confirmed to Heymid, but based on the editing pattern of these accounts they are very likely to be Heymid/CHEEIZY. Same editing pattern on svwiki too. EPIC (talk) 20:46, 28 December 2023 (UTC)[reply]
Unless there is a special need for investigation, it seems like this can just be handled in our SRG, so is there any reason to know if SotiaIIe is the same user as EPIC og EstrellaSuecia 4? --Sotiale (talk) 07:35, 29 December 2023 (UTC)[reply]
Pinging Asav, who initially requested that I request a CheckUser check. Perhaps they can answer your question. EdoAug (talk) 15:27, 29 December 2023 (UTC)[reply]
The purpose is to establish whether there is an IP address than can be blocked, as the user keeps reappearing with new sockpuppets. Asav (talk) 16:54, 29 December 2023 (UTC)[reply]
As mentioned on nowp, judging by the logs here on Meta-Wiki, many of the accounts seem to be created from a dynamic mobile network range in Sweden. Therefore, blocking individual IP addresses would probably not do much in this case. So, rangeblock is a solution, but not a very good one, as this mobile range belongs to a large network provider in Sweden and a rangeblock would therefore affect many users. EPIC (talk) 17:09, 29 December 2023 (UTC)[reply]
 Declined Even before this was posted, 3 stewards had already been involved in checking this on loginwiki. You can safely assume that abusive LTA names get checked faster than a heartbeat after being reported at SRG/IRC. -- Amanda (she/her) 06:03, 3 January 2024 (UTC)[reply]

Banksyfuture@zh.wikipedia

Banksyfuture = Siomaimaster, and I suspect the rest are on proxies, and I think you could just block them. -- Amanda (she/her) 06:13, 3 January 2024 (UTC)[reply]

伟大的谢明@zh.wikipedia

  •  Confirmed 伟大的谢明, Forgive!!youandme!!, Stop deleting, Xx520xx, Xarchangelx, ArchangelXie, MingXieAngelofDeath, MessengerofGodX, Angel of Death Xie. -- Amanda (she/her) 06:21, 3 January 2024 (UTC)

See also