Jump to content

Wikipedia:Sockpuppet investigations: Difference between revisions

From Wikipedia, the free encyclopedia
Content deleted Content added
Line 35: Line 35:


=== Awaiting Clerk approval ===
=== Awaiting Clerk approval ===
{{SPI|Sumbuddi}}
{{SPI|Brexx}}
{{SPI|Brexx}}
{{SPI|Jvolkblum}}
{{SPI|Jvolkblum}}

Revision as of 21:15, 12 February 2010

This page is for requesting that we investigate whether two or more Wikipedia accounts are being abusively operated by the same person.

Before opening an investigation, you need good reason to suspect sockpuppetry.

  1. Evidence is required. When you open the investigation, you must immediately provide evidence that the suspected sock puppets are connected. The evidence will need to include diffs of edits that suggest the accounts are connected. (This requirement is waived if the edits in question are deleted; in this case just provide the names of the pages that the accounts have been editing.)
  2. You must provide this evidence in a clear way. Vaguely worded submissions will not be investigated. You need to actually show why your suspicion that the accounts are connected is reasonable.
  3. Concision is key. Evidence should be presented in a concise format. Because of the length of the backlog, cases with clear and concise explanations and evidence are handled the most quickly.

Investigations are conducted by a clerk or an administrator, who will compare the accounts' behaviour and determine whether they are probably connected. Upon request, investigations can also be conducted by a checkuser, who can look at technical data behind the accounts in order to determine how likely it is they are connected. CheckUser results are often called technical evidence, in contrast to publicly available behavioural evidence.

Due to Wikipedia's CheckUser policy, checkusers will conduct a technical investigation only if clear, behavioural evidence of sockpuppetry is also submitted; if you ask for technical evidence to be looked at but do not provide behavioural evidence, the investigation may not be allowed to proceed. Additionally, checkusers will not publicly connect an account with an IP address per the privacy policy except in extremely rare circumstances.

How to open an investigation:

To add to an existing investigation (or case), enter the case name in the box below. To create a new investigation, enter the username of the oldest-created registered account (the "sockmaster")—or, if only IP addresses are involved, the IP that made the first relevant edit. Then click "Submit". Note: Do not include "User:" or any other commentary.

For example, if a prior filing was at Wikipedia:Sockpuppet investigations/John Doe, or this is a first filing and the oldest registered account is User:John Doe, you should enter John Doe in the box below.

You will then be taken to another page containing a form you must complete to open the investigation. The process for opening a subsequent investigation on the same user is the same as for creating a new case. Again, do not include "User:" in any of the numbered fields.

If you also wish a checkuser to investigate, change |checkuser=no to |checkuser=yes in the edit box on the next page and explain why you are requesting it.

Note: You can also open an investigation using Twinkle. After installing Twinkle, an "ARV" option will appear in the "TW" tab on any user, user talk, or user contributions page. Clicking on this option and selecting either "Sockpuppeteer" or "Sockpuppet" will allow you to fill in a few simple fields to file a report. The report will be automatically formatted for you.
If you are not autoconfirmed, and the case page is protected or does not exist, please click "show" to the right and use the box below.

Open cases: not awaiting Checkuser

User-reported cases

Template:SPI Template:SPI Template:SPI Template:SPI Template:SPI Template:SPI Template:SPI Template:SPI Template:SPI Template:SPI Template:SPI Template:SPI Template:SPI Template:SPI Template:SPI Template:SPI

Checked cases awaiting administration

Template:SPI Template:SPI

Open cases: awaiting Checkuser processing

Cases in this section have an open request for CheckUser that is being processed. Any user may update or act on this case, and any patroller or clerk may decide the case. However it will not be closed if the Clerks believe any further action is needed.

  • Endorsement or decline of CheckUser may only be made by a Clerk.
  • If your case is not showing up here, or this section seems out of date, please click the purge link.

Awaiting Clerk approval

Template:SPI Template:SPI Template:SPI

Awaiting Checkuser

Template:SPI Template:SPI Template:SPI Template:SPI Template:SPI

Completed cases

Pending close

Cases here have been closed by users and are awaiting a Clerk to review for formal close and archiving. Template:SPI Template:SPI

Quick Checkuser requests

Use this section to request checkuser information relating to a situation that does not involve sock puppetry. You could use this section to request, for example:
  • Underlying IPs of an account, where the autoblock has expired or been ineffective.
  • Collateral damage checks for the informed hardblocking of IPs or ranges.
  • IP block exemption checks before granting IPBE (or to verify it is being used constructively).

For threats of harm (to self or others) you must email emergency@wikimedia.org (see the threats of harm page) and not use this page. Requests to investigate and confirm sockpuppetry should be listed in the sockpuppet section above, and not here (such requests will be summarily removed).

To make a request here, copy the following template and paste it to the end of this section (quick link to edit) – replacing "header" with an informative title, and adding underneath the template any relevant information – then sign using "~~~~", preview, and click "save".

==== HEADER ====
{{SPIquick}}
* {{Checkuser|
username}}

User talk:Wifione unblock request (proxy block)

Can a checkuser read the appeal at User talk:Wifione#Unblock request and take whatever action seems appropriate? He is asking for IPBE due to the proxy block, but won't give his actual block notice due to self-outing concerns. Since his January 2010 edits seem rather precocious, it might be allowable to see if his IP matches that of any past villains, but his recent work looks good to me. If I had to decide this one myself, I'd want him to explain (by email) how come he seems to be using an open proxy. Is that his only available choice for internet access? EdJohnston (talk) 04:49, 11 February 2010 (UTC)[reply]

Wifione should be able to edit now. There is no indication that he was attempting to edit through a proxy. It looks to me like his ISP gave him an IP that was already coincidentally blocked as one, not that he intentionally tried to access it. Dominic·t 05:24, 11 February 2010 (UTC)[reply]

Archived cases

The following are old SPI cases, separated by month:

2009
January February March April
May June July August
September October November December
2010
January February March
April May June
July August September
October November December
Click here to purge this page
(For help, see Wikipedia:Purge)