Steward requests/Checkuser: Difference between revisions

From Meta, a Wikimedia project coordination wiki
Content deleted Content added
Tags: Mobile edit Mobile web edit
Line 277: Line 277:
}}
}}
*No local consensus, a clear editorial dispute exists. {{Fishing}} '''and a weapon for editorial disputes'''. [[User:Damyeon1|Damyeon1]] 07:26, 18 August 2019 (UTC)
*No local consensus, a clear editorial dispute exists. {{Fishing}} '''and a weapon for editorial disputes'''. [[User:Damyeon1|Damyeon1]] 07:26, 18 August 2019 (UTC)
**2 things, I am not sure why {{u|MCC214}} keep on sending discussions to SRCU without adequate local discussions on local page, however, this I can confirm isn't an editorial dispute and I myself would have asked for this CU as the behaviour of this very new account is close to the master but not that close that can be called a duck. I see they are doing some disruptive editing as well. There is no reason why this CU is a weapon for editorial dispute. So I hope {{u|Damyeon1}} can understand and not to put out such statements in the future. Regards,--[[User:Cohaf|Cohaf]] ([[User talk:Cohaf|talk]]) 07:36, 18 August 2019 (UTC)


==See also == <!-- DO NOT EDIT UNDER THIS LINE -->
==See also == <!-- DO NOT EDIT UNDER THIS LINE -->

Revision as of 07:36, 18 August 2019

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

Naughtycaique (愛莎) @zh.wikipedia

Adding Target:

And here are some other recently created that still have data available,steward can choose will do/will not do this request in adding target,thanks.--MCC214#ex umbra in solem 08:53, 10 August 2019 (UTC)[reply]

I suppose MCC214 wanted to ask stewards to decide on your own whether or not block the IPs they used to create accounts. --Super Wang hates PC You hate, too? 08:55, 17 July 2019 (UTC)[reply]
typesetting at this section was carried out.--Hamish 12:15, 17 July 2019 (UTC)[reply]
@MCC214: please rewrite Naughtycaique request + 坦帕灣光芒460 request! as it's kind of mess, and I can't understand exactly what you ask/want! and please avoid such mess in requests! --Alaa :)..! 11:43, 19 July 2019 (UTC)[reply]
علاء, Done.--MCC214#ex umbra in solem 11:45, 19 July 2019 (UTC)[reply]
To make it plain simple: Check all the users named (2nd list are checked last month per Steward_requests/Checkuser/2019-06#劉曉程@zh.wikipedia but needs rechecking) + block underlying IP if there are any + sleepers check. These should be what MCC214 wants Stewards to do. --Cohaf (talk) 12:06, 19 July 2019 (UTC)[reply]
علاء,Reason(s) is Request 1,1. is Request 2,2. is Request 3,3. is Request 4.--MCC214#ex umbra in solem 07:44, 21 July 2019 (UTC)[reply]
What on earth did you mean?? --Super Wang hates PC You hate, too? 23:43, 21 July 2019 (UTC)[reply]
MCC214, could you please stop forwarding local CU discussions onto Meta? Personally speaking, I can't understand neither of your local request nor what you said on meta. I am seriously considering a ban on you for CU-related discussions on zhwiki. --TechyanTalk03:31, 22 July 2019 (UTC)[reply]

Luckydayapple@zh.wikipedia

坦帕灣光芒460@zh.wikipedia

Adding Target:

And here are some other recently created that still have data available.--MCC214#ex umbra in solem 05:14, 9 August 2019 (UTC)[reply]

  • Since I found multiple vandalism in the range of his confirmed IP, I have blocked the range 223.137.161.187/16 at zhwiki. And I noticed this range was used by KAGE, an xwiki LTA, so I request to check that range to decide if the block should be prolonged, or apply blocks at your discretion if the information can't be disclosed.--Hamish 15:31, 8 August 2019 (UTC)[reply]

Everyinvain@zh.wikipedia

  • Comment Comment: Blocking their IP(s)/IP range(s) might be helpful. However, as a local sysop on zhwiki, I don't care about which of them are socks and which are not. That's because they are simply vand-only accounts and our responses could also be very simple: Revert their edits and Block them. --Tiger (talk) 09:11, 11 August 2019 (UTC)[reply]

Jamyangr@zh.wikipedia

FoooSoooooa@zh.wikipedia

Abcde1234512345@zh.wikipedia

There is technical evidence for some of these accounts to be related. I've locked the accounts. – Ajraddatz (talk) 10:42, 17 August 2019 (UTC)[reply]

教學組動三甲班蕭明㛢導師 (蘇俞安) @zh.wikipedia

Comment Comment: This is not a request that has sufficient local consensus. MCC214 brought this request to meta when it was still under discussion. As MCC214 mentioned, stewards may decide whether to do the CU. However, I think we should focus more on those requests that will affect local blocks on users.--Tiger (talk) 11:34, 17 August 2019 (UTC)[reply]

Dragoon17cc@zh.wikipedia

Adding Target:

And here are some other recently created that still have data available.--MCC214#ex umbra in solem 10:53, 17 August 2019 (UTC)[reply]

徐昌昌 (小昌) @zh.wikipedia

瑪卡 (顓如) @zh.wikipedia

CX 466 (3GFRIENDSNSD) @zh.wikipedia

  • No local consensus, a clear editorial dispute exists. Fishing CheckUser is not for fishing and a weapon for editorial disputes. Damyeon1 07:26, 18 August 2019 (UTC)[reply]
    • 2 things, I am not sure why MCC214 keep on sending discussions to SRCU without adequate local discussions on local page, however, this I can confirm isn't an editorial dispute and I myself would have asked for this CU as the behaviour of this very new account is close to the master but not that close that can be called a duck. I see they are doing some disruptive editing as well. There is no reason why this CU is a weapon for editorial dispute. So I hope Damyeon1 can understand and not to put out such statements in the future. Regards,--Cohaf (talk) 07:36, 18 August 2019 (UTC)[reply]

See also