Welcome to twinme.com on July 6 2009.
This is an internet experiment running to monitor browsing habbits of individuals through wikipedia contents.

Wikipedia:Sockpuppet investigations

From Wikipedia, the free encyclopedia

  (Redirected from Wikipedia:RFCHU)
Jump to: navigation, search


Administrator instructions

WP:RFCU redirects here. You may be looking for Wikipedia:Requests for comment/User conduct (WP:RFC/U), CheckUser policy (Wikipedia:CheckUser), or Wikipedia:Changing username (WP:CHU).
Purpose of this page
Shortcuts:
WP:SPI
WP:RFCU
WP:SSP

Users can request discussion about a possible breach of sock puppetry policy on this page.
For exceptionally sensitive matters (e.g. harassment, privacy), please contact any CheckUser or any Arbitration Committee member, by e-mail  (how to).


Indicators and templates   (v  · e)
These indicators are used by Checkusers, SPI clerks and other patrolling users, to allow easier at-a-glance reading of their notes, actions and comments.
Case decisions:
IP blocked Completed
Information:
More info needed Deferred to
Note In progress
Clerk actions:
Clerk needed Clerk note
Delisted Relisted
Clerk declined Clerk endorsed
Specific to CheckUser:
Confirmed Unrelated
Likely Unlikely
Possible Inconclusive
Declined Unnecessary
Not for fishing Rejected
Not a crystal ball Stale (too old)
Not magic pixie dust 8-Ball says

Sockpuppet investigations (SPI)

  • When two users, accounts, or IPs, are said to be "sock puppets", we simply mean that for Wikipedia editing policy purposes, editors may treat their edits as being effectively written or controlled by the same person.
  • Wikipedia has a strict policy on uses of multiple accounts. This page is used to discuss whether a user is likely to have violated that policy, or breached other restrictions (eg blocks or bans) using multiple accounts.
  • This page is only to evaluate evidence of misuse of multiple accounts and IPs. All other matters may be removed by the clerks.
  • If there is no evidence then nothing will happen. This is explained in the guidance notes under defending yourself.

Evidence

  • Most SPI cases are decided based upon behavioral evidence, that is, the behavior of the accounts, users or IPs concerned.
  • The evidence needs to be quite strong, not just a vague belief or assumption.
  • Certainty may not be possible; it is usual for a decision to be made based upon an experienced user's judgement of likelihood. If the evidence suggests it is likely that abuse has taken place, then action may be taken.

CheckUser

  • In certain cases the CheckUser tool can provide technical information suggesting whether two users are likely to be related, which may help inform a decision. Because this data is usually private, CheckUser evidence may only be requested in very specific circumstances and only very few users (known as "CheckUsers") have access. Any comments by Checkusers will strictly comply with the Foundation's privacy policy.
  • CheckUser does not solve cases. It provides additional evidence of a technical nature that can be considered along with behavioral evidence, and may help clarify whether misuse has taken place.

Deciding whether to ask for CheckUser

You should not usually need CheckUser evidence if:

  • Behavior or other evidence are sufficient for a conclusive decision and CheckUser is unlikely to be needed; or
  • Canvassing or meatpuppetry is suspected, rather than multiple account abuse (sock-puppetry); or
  • The account/s have not edited for many months ("stale")

You may wish to ask for additional CheckUser evidence if:

  • The case matches a valid reason in the CheckUser reasons, the behavioral evidence alone is suggestive but not conclusive, and the case is likely to require evidence from CheckUser for its conclusion; or
  • Additional undetected sock-puppets or abuse are reasonably likely.

  A CheckUser request can always be added for good cause to an existing case, by anyone, at any time.

Other CheckUser requests

This page may also be used for other CheckUser requests unrelated to sock abuse. For example:


Other CheckUser requests unrelated to sock abuse: #Quick CheckUser requests.
Closed cases: Wikipedia:Sockpuppet investigations/SPI/Closed.
Patrolling and clerking: Any capable user may help on cases or ask to be a trainee clerk (More...)

[edit] Search for prior cases

[edit] Instructions

See Requesting a sock puppet investigation (guidance), and Defending yourself against claims.

If you are already familiar with the instructions, create the case by replacing "CASENAME" with the name of the puppet master, or previous case name in the box below. The name given to the case should be the original case name (if any), or the main name the user is known by (do not add the word "user:", or number the cases).

Eg, if the case name is about User:John Doe or the existing case is at Wikipedia:Sockpuppet investigations/John Doe, then you should enter Wikipedia:Sockpuppet investigations/John Doe in the box.

File a request



Quick link: Valid and invalid CheckUser reasons


Then click the button to create a request page (or new section) and follow the instructions there.

[edit] Useful reading

SPI process related  
Background  

[edit] Open cases: not awaiting CheckUser

(view cases)



[edit] Bot-reported cases

(view cases | edit cases )

[edit] 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.

[edit] Awaiting Clerk approval

(view cases)



[edit] Awaiting CheckUser

(view cases)



[edit] Completed cases

[edit] Pending close

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

  • If your case is not showing up here, or this section seems out of date, please click the purge link.

(view cases | edit cases )



[edit] Quick CheckUser requests

This section is only for CheckUser requests unrelated to sockpuppetry.

The following are valid reasons for requesting a quick check:

  • Blocking of underlying IPs for a longer term than afforded by autoblock.
  • Collateral damage checks before hardblocking IPs and ranges.
  • Threats of harm (to self or others), necessitating contact with law enforcement or medical authorities.
  • Checks connected with granting IP block exemption to a user.

Requests to investigate and confirm sockpuppets should be listed in the sockpuppet section above. Quick requests that are actually sockpuppet cases 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}}

[edit] User:Arpierson1993

This quick case is open.

The fourth CU for this user was just completed on July 3rd which resulted in an extend rangeblock of 75.104.192.32/27. However, two new socks have been added to the drawer since that time:

The socks are very easy to spot, but as I'm going to be away for a week or so, this will hopefully limit any further disruption during that time. Jauerbackdude?/dude. 04:43, 6 July 2009 (UTC)

IP blocked. Dominic·t 11:05, 6 July 2009 (UTC)
Personal tools

Visit joltnews for the latest headlines
Visit bloit.com for company information
Geed Media does computer consulting on long island.
This page viewed times. See Logs