Wikipedia:Sockpuppet investigations

From Wikipedia, the free encyclopedia

Jump to: navigation, search
Error: syntax error
This message box is using an invalid "type=" parameter and needs fixing.

Administrator instructions

Wikipedia:RFCU redirects here. You may be looking for Wikipedia:Requests for comment/User conduct (Wikipedia:RFC/U), CheckUser policy (Wikipedia:CheckUser), or Wikipedia:Changing username (Wikipedia:CHU).
Shortcuts:
Wikipedia:SPI
Wikipedia:RFCU
Wikipedia:SSP
Welcome to Sockpuppet investigations (SPI). Please see the sockpuppet policy for detailed definitions and descriptions of what sockpuppetry is and is not. This is the place to seek help when a user is likely to have violated that policy, breached restrictions (eg blocks or bans) using multiple accounts, for any requests where multiple accounts or underlying IP needs checking, or for any requests via the CheckUser tool.


This message box is using an invalid "type=" parameter and needs fixing.

Contents

CheckUser

CheckUser is a tool that allows authorized users to look at technical information left when a user/IP makes an edit. This technical information can help determine if a single person is using more than one account. Use of the checkuser tool is governed by policies on the English Wikipedia and Wikimedia Foundation levels. For more information, see the Foundation policy, the local policy and the Foundation privacy policy.

When not to request CheckUser

There must be credible evidence supporting the suspicion of sockpuppetry, and good cause why CheckUser is required. Requests for checkuser without evidence will be declined, because CheckUser is not for fishing. CheckUser is also not magic pixie dust, and should not be requested to investigate canvassing or meatpuppetry, alt= Stale account(s) that have not edited for many months, or cases where behavioral evidence is sufficient to decide the matter (see also the link=File:Duck test lolcat.jpg duck test).

Making Quick CheckUser requests

See #Quick CheckUser requests. This page may also be used for other CheckUser requests unrelated to sock abuse, such as:

Evidence and SPI case guidelines

You need to provide evidence showing the accounts or IPs are likely to be sock-puppets and acting in a disruptive or forbidden manner, which other users will then assess. If there is no evidence showing forbidden sock-puppetry, then nothing will happen and the case is likely to be speedily closed by the SPI clerks. Most SPI cases are decided based upon behavioral evidence, that is, the behavior of the accounts or IPs concerned. This evidence needs to be explicit; that is, use verifiable evidence in the form of diffs, links to the pages in which the sock puppetry is occurring, and reasonable deductions and impressions drawn from said evidence. Evidence solely consisting of vague beliefs or assumptions will be rejected.

Some general guidelines when making your SPI case:

  • Remember to always assume good faith when possible.
  • After submitting a case, consider notifying the suspected accounts by adding {{subst:socksuspectnotice|PUPPETMASTER}} ~~~~ to the bottom of their talk pages. Notification is not mandatory, and may, in some instances, lead to further disruption or provide a sockpuppeteer with guidance on how to avoid detection.
  • Do not use any section headers ("===") on case pages as this will break the report templates and mess up the formatting.
  • Keep it simple. Simple, concisely presented evidence leads to a quickly resolved case.
  • After administrators and/or checkusers have reviewed the case, it will be closed and archived by an SPI clerk. (Administrators may mark a case closed using {{SPIclose}}.)

Submitting an SPI case

This message box is using an invalid "type=" parameter and needs fixing.
Create the case by replacing "SOCKMASTER" in the white box below with the user name of the oldest account, or the previous case name, and then clicking the button under the box. Note that these buttons may be used either for creating a new case or reopening an old one. For example, if the case name is about User:John Doe or a prior case is at Wikipedia:Sockpuppet investigations/John Doe, then you should enter Wikipedia:Sockpuppet investigations/John Doe in the white box, and then click the button under the box. You will be taken to the next page, where there is a form to fill out giving the details of your report.
Start an SPI case WITHOUT a CheckUser request Start an SPI case WITH a CheckUser request
<inputbox> type=comment bgcolor=#dcffe0 buttonlabel=Use this button for most investigations editintro=Wikipedia:Sockpuppet investigations/SPI/Inputbox instructions for ordinary use preload=Wikipedia:Sockpuppet investigations/SPI/Inputbox blank report for ordinary use default=Wikipedia:Sockpuppet investigations/SOCKMASTER summary=New report created or added minor=no </inputbox> <inputbox> type=comment bgcolor=#dcffe0 buttonlabel=Use this button to ask for CheckUser evidence as well editintro=Wikipedia:Sockpuppet investigations/SPI/Inputbox instructions for CU request preload=Wikipedia:Sockpuppet investigations/SPI/Inputbox blank report for CU request default=Wikipedia:Sockpuppet investigations/SOCKMASTER summary=New report created or added minor=no </inputbox>

Administrators' instructions

If you wish to help out at SPI, but are unsure how to get started, please read Wikipedia:Sockpuppet investigations/SPI/Administrators instructions. If you need help with anything, please ask one of the active SPI clerks.

See also

Case status summary

Open cases: not awaiting Checkuser

Cases

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 request may only be made by a Clerk or Checkuser.
  • If your case is not showing up here, or this section seems out of date, please click the purge link.

Awaiting clerk approval

Awaiting Checkuser

Cases pending close

Cases here have been closed by users and are awaiting a Clerk to review for formal close and archiving.
<categorytree mode=pages depth=0 hideprefix=yes hideroot=yes namespaces=4>SPI cases pending close</categorytree>

Quick Checkuser requests

This section is for CheckUser requests unrelated to sockpuppetry, such as:

  • Underlying IPs – identification and blocking for a longer term than autoblock.
  • Collateral damage checks – before hardblocking IPs and ranges.
  • Threats of harm (to self or others) – where the location and other details may be needed for law enforcement or medical authorities.
  • IP block exemption checks – before granting IPBE or to confirm proper use.
Requests to investigate and confirm sockpuppetry should be listed in the sockpuppet section above. If posted here, they will be delisted by a clerk without being actioned.

Copy the following template and paste it to the end of this page (quick link to edit) with a useful header and details, then sign using "~~~~" and click "save".

==== HEADER ====
{{SPIquick}}

Ludasaphire

alt= Clerk note: I see no indication for this being a quick case. It does not meet the criteria. Please either provide a reason this should be a quick case or reopen it as a normal case. If no response is provided soon I will simply remove the quick case. --Shirik (Questions or Comments?) 19:20, 11 July 2010 (UTC)
That comment makes it seem as though you may have glanced at my request and not fully understood what I had said, however if that is not the case than I am sorry to misunderstand what you have said above. If you still feel that it should not be a quick checkuser case than perhaps I did too much advance work in my attempt to make it easier for the person who may do it, and provided too much information - in which case let me try this again, much shorter.
An editor named Ludasaphire has created at least three main space articles. These articles are Josh and the Empty Pockets, David Spero and Solomon curve. Based on image uploads it appears this user may be a SPA making COI edits. There are other I.P's and at least one other account that may be related as edit history's show work on only the same article(s). In a traditional sock puppet case I will see a user making edits to one or more accounts under several user names, usually to a mainspace article that is a "hotspot" somehow, in the cases I have seen they are users in edit wars or users trying to save an article from an AFD debate, *and* flat out denying they are the same user. This is *NOT* that kind of case because 1) The mainspace articles, and their related subjects, are of note and not really under fire for any non-notability issues 2) There is not really any question that Ludasaphire is main creator *and* editor on these articles. The checkuser request here is to be just that - a checkuser to see if the "Underlying IPs" are related. As one core example, is Ludasaphire having a conversation with themselves via 98.206.44.74 on Talk:Josh and the Empty Pockets? If not than who is 98.206.44.74 and why have they only contributed to one articles talk page? Beyond that one of the images uploaded by this user contains a "self" license with the photographer listed as the subject of one of the mainspace articles. A quick chekuser may aid in establish if this is, indeed, an SPA making COI edit to COI articles. Soundvisions1 (talk) 03:48, 12 July 2010 (UTC)
The relevant concern for SPI is that the IPs may be connected and there could be bad faith editing. the evidence would be that there is SPA promotional activity and at the same time some of the IPs were SPA editors on the same topic. That would be the SPI concern. The other side is the IP editing is last month, if there is no current concern about socking then it may be best considered closed. I've retitled this for now. If there is a current issue, maybe open it as a normal case requesting checkuser and noting the SPA/promotional situation, to identify whether the accounts and IPs that are involved appear to be connected and if it is, then whether that is the full extent of any disruptive or promotion-related matters. FT2 (Talk | email) 12:47, 22 July 2010 (UTC)
Not fully sure I understand what you are saying because it sounds like a lot of round about double talk - at face value it seems you are saying there may be a concern but because there has not been recent activity to not worry about it and it seems nobody has bothered to do a checkuser because of that. I guess, if that is the case, I will have to play the "not assuming good faith" editor here and move forward by posting a COI/SPA notice on all the I.P's and users associated with this and, though not really considered to matter here, also make an attempt to start the process to reverse the OTRS on the images which triggered my looking into all of this. Thanks. (EDIT: Upon placing COI notices I saw that some of the associated articles were today/yesterday) Soundvisions1 (talk) 03:37, 23 July 2010 (UTC)

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

Click here to purge this page
(For help, see Wikipedia:Purge)
<inputbox> bgcolor=transparent type=fulltext prefix=Wikipedia:Sockpuppet investigations break=yes width=60 searchbuttonlabel=Search all cases and archives </inputbox>
Personal tools