Steward requests/Checkuser: Difference between revisions

: The discussion link seems to be broken. And has there been any recent changes to the clerks system? --[[User:Sotiale|Sotiale]] ([[User talk:Sotiale|talk]]) 11:58, 17 January 2025 (UTC)

: Sorry. I fixed the link already. Because of the community’s consensus and we want to have the CU result ASAP, so I submitted this request directly. This does not imply any change of the clerk system. Thanks. -[[user:Manchiu|Manchiu]] [[user talk:manchiu|(talk)]] 15:00, 17 January 2025 (UTC)

: Hello all. I have been requested to comment here about the status of the clerk system. Currently, there are only two active clerks on zhwiki (3 after Feb. 12th as I will return from WikiBreak, according to my zhwiki user page) from five clerks when the clerk system was originally established. I have recognized the need of additional clerks and will work closely and actively with the clerk team on seeking potential new clerks to join the team. This check is primarily endorsed by community; I support this sleeper check as well, noting the necessity given 夏土贤's frequent sock creations since Dec. 23 of last year. --[[User:ATannedBurger|<font size="0.01%"><math>\int</math></font>]]([[User_talk:ATannedBurger|☎]]) 02:38, 21 January 2025 (UTC)

== See also ==

Revision as of 02:38, 21 January 2025

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:

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.
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.
Make sure there are no local checkusers.
- Wikimedia: meta • commons • species • data
- Wikipedia: ar • bn • ca • cs • da • de • en • es • fa • fi • fr • he • hu • id • it • ja • ko • ml • nl • pl • pt • ru • simple • sl • sr • sv • th • tr • uk • vi • zh
- Wikibooks: en
- Wikinews: en
- Wiktionary: en
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
CheckUser information Global blocks/locks Permissions (global) Permissions (bot) Permissions (other) Username changes/ usurpation requests Miscellaneous requests URL blacklisting Title/username blacklisting Email blacklisting
Meta-Wiki requests
CheckUser information Deletion Permissions Requests for help

Requests

蒙古天驕@zh.wikipedia

Status: In progress

List of users: 蒙古天骄 (contr · deleted · block · log · block log · guc · checkuser · lwcheckuser ); 夏土贤 (contr · deleted · block · log · block log · guc · checkuser · lwcheckuser )

CU log
Discussion: w:zh:Wikipedia:傀儡調查/案件/夏土贤

Reason(s): Requested by local admin. "蒙古天骄" is registered after "夏士贤" was blocked. Ducked by their similar editing contributions in history related articles.

Please refer to local discussions. A sleeper check is requested. Many thanks.-Manchiu (talk) 11:06, 17 January 2025 (UTC) [reply ]

The discussion link seems to be broken. And has there been any recent changes to the clerks system? --Sotiale (talk) 11:58, 17 January 2025 (UTC) [reply ]

Sorry. I fixed the link already. Because of the community’s consensus and we want to have the CU result ASAP, so I submitted this request directly. This does not imply any change of the clerk system. Thanks. -Manchiu (talk) 15:00, 17 January 2025 (UTC) [reply ]

Hello all. I have been requested to comment here about the status of the clerk system. Currently, there are only two active clerks on zhwiki (3 after Feb. 12th as I will return from WikiBreak, according to my zhwiki user page) from five clerks when the clerk system was originally established. I have recognized the need of additional clerks and will work closely and actively with the clerk team on seeking potential new clerks to join the team. This check is primarily endorsed by community; I support this sleeper check as well, noting the necessity given 夏土贤's frequent sock creations since Dec. 23 of last year. --

\int

{\displaystyle \int }(☎) 02:38, 21 January 2025 (UTC) [reply ]