Warning: file_put_contents(/opt/frankenphp/design.onmedianet.com/storage/proxy/cache/ffee16a5bbf76e505065c31ce7df3a21.html): Failed to open stream: No space left on device in /opt/frankenphp/design.onmedianet.com/app/src/Arsae/CacheManager.php on line 36

Warning: http_response_code(): Cannot set response code - headers already sent (output started at /opt/frankenphp/design.onmedianet.com/app/src/Arsae/CacheManager.php:36) in /opt/frankenphp/design.onmedianet.com/app/src/Models/Response.php on line 17

Warning: Cannot modify header information - headers already sent by (output started at /opt/frankenphp/design.onmedianet.com/app/src/Arsae/CacheManager.php:36) in /opt/frankenphp/design.onmedianet.com/app/src/Models/Response.php on line 20
Wikipedia:Sockpuppet investigations/SPI/CheckUser criteria - Wikipedia Jump to content

Wikipedia:Sockpuppet investigations/SPI/CheckUser criteria

From Wikipedia, the free encyclopedia
In these cases, file a case and request a check
Evasion of ArbCom or Wikimedia Foundation bans or remedies Link to the closed case. Supply evidence to show the active user is the banned party.
Ongoing, serious pattern of vandalism involving dozens of incidents Supply diffs of the vandalism.
Possible vote fraud Link to the vote(s).
3RR violation using sockpuppets Link to four or more diffs showing the 3RR violation.
Evasion of community-based bans or blocks Link to block log of the original account. Supply evidence to show the user is the banned or blocked party.
Likely undetected or "sleeper" socks, getting an IP block (of a repeat sock-user) Link to or point to a possible reason, or if enough socks exist, the archive.
'Messy' and complex cases where behavior alone cannot determine which accounts are socks. Link to diffs that show the likelihood that each account listed could be a possible sockpuppet.
You believe a check is warranted anyway Give a brief summary of the situation, link to further discussions, and supply supporting diffs.