Jump to content

User:GeneralNotability/clerk

From Wikipedia, the free encyclopedia

Cases

[edit]

{{subst:User:GeneralNotability/ClerkAtWork}}

Archivings

[edit]
Signed off.

old

[edit]
old

May 24, 2020

[edit]

Welcome to the SPI clerk team! We're delighted to have you.

If you haven't already done so, please read Wikipedia:Sockpuppet investigations/SPI/Clerk and checkuser procedures and (mostly as background) Wikipedia:Sockpuppet investigations/SPI/Administrators instructions.

If you don't have these scripts yet, please install them now:

lazyCheckCUStaleness = false;
maxUsersCUStaleness = 100;
mw.loader.load('/w/index.php?title=User:Writ Keeper/Scripts/cuStaleness.js&action=raw&ctype=text/javascript');
mw.loader.load('/w/index.php?title=User:Writ Keeper/Scripts/sockStaleness.js&action=raw&ctype=text/javascript');

Also, while not mandatory, these scripts are very useful and I strongly recommend them:

Kevin (aka L235 · t · c) 18:06, 24 May 2020 (UTC)

L235, policies read and understood, scripts installed. creffett (talk) 19:55, 24 May 2020 (UTC)

I've sent you a brief quiz about the SPI procedures and your interpretation of them (privately per BEANS). Give me a ping (on-wiki or directly) when you get to it, but take your time, nothing urgent there. Kevin (aka L235 · t · c) 02:20, 25 May 2020 (UTC)

May 25

[edit]

Tools:

  1. For working with single IP addresses and ranges:
    1. Proxy checker: (link) endlessly useful
    2. Wikimedia whois: (link) I use this every day
    3. Stalk Toy: (link) This tool will give you the global outlook on accounts and IP addresses on most projects. It is also useful for finding nested IP blocks...for example if a IPv4 /16 range has blocks on any of its subranges or single IP addresses then this will show them to you. Also useful for pinhole access detection: If a hardblock exists on a range but smaller ranges or single IPs have anonblocks then those are undesired access pinholes unless it is by design (you may need to check with the blocking admin to see if it is).
    4. ISP Rangefinder: (link) I don't use this personally but others find it helpful
    5. IP Range Resolver: (link) I don't use this personally but others find it helpful
    6. Rangeblock Calculator (IPv4 and IPv6): (link) very helpful, you can paste in a bunch of IP addresses and extraneous text and it will parse the IP addresses and find the link
  2. For working with accounts and comparing editors:
    1. Pages created: (link) Get pages that have been created by a user
    2. Get distinct authors: (link)
    3. Edit summary search: (link) (may miss some)
    4. Editor Interaction Analyzer 1: (link) (may miss some)
    5. Editor Interaction Analyzer 2: (link)
    6. Intersecting Contribs: (link)
    7. Timecard: (link)
  • Spend some time looking at SPI cases to see how the scripts work and try out some of the tools to gain familiarity.
  • The above is not an exhaustive list by any means. If you have any favorite scripts or tools that you believe will come in handy with SPI work that are not listed above, then please list them below.

Kevin (aka L235 · t · c) 17:40, 25 May 2020 (UTC)