If evidence has not shown that sock puppetry has occurred, likewise make a note of that in the same section.Users of social media sites can use more than one account. When blocking accounts, follow the procedures under the Blocking and tagging section and make a note of the blocks under the 'Clerk, patrolling admin and checkuser comments' section of the SPI case page.

Many admins normally apply what is colloquially called the duck test – if it looks like a duck, swims like a duck and quacks like a duck, it's probably a duck. In many cases, sock puppetry can be determined just by behavioral evidence and without the need for technical evidence. In usual SPI cases, where CheckUser is not requested, admins should look carefully and neutrally at the evidence and determine whether the behavioral and other evidence shown makes it very likely that sock puppetry is occurring. It gives a menu of options which help those users deal with sockpuppet cases and case pages.Īdmins often apply what is colloquially called the duck test to determine if sockpuppetry is occurring.

User:GeneralNotability/spihelper, a script which is primarily for clerks, checkusers and patrolling administrators (but can be used by other users).

Special:CentralAuth, quick and easy way to determine edit count and cross-wiki footprint ( much faster than XTools or the Global Contributions tool).

Intersect Contribs, faster than the Editor Interaction Analyzer but without as much detailed information.

Interaction Timeline, primarily designed to combat harassment but potentially useful in other situations, too.

Editor Interaction Analyzer, which shows the common pages that two or more editors have both edited, sorted by minimum time between edits by the users.

'Strike out usernames that have been blocked' from Special:Preferences#mw-prefsection-gadgets (formerly User:NuclearWarfare/Mark-blocked script.js), which indicates if an account has been blocked already, either for a set period of time or indefinitely.

Download sockpuppet