419:
ALT TEXT: Checkuser is a tool that allows authorized users to look at technical information from the server logs themselves, which can provide evidence whether two users, or a user and an IP, are likely to have any connection, and can be used to investigate disruption, "sleepers", returned banned
393:
have to defend yourself against other claims, however bad, or engage in discussion about them. You may wish to note that the claim is not relevant to sock puppetry. Claims and issues that are not relevant to account and IP abuse will almost always be ignored by the clerks and checkusers, and will
74:
Advertising
Knowledge articles to your friends, family members, or communities of people who agree with you, so that they come to Knowledge and support your side of a debate and give the appearance of consensus is strongly discouraged. Discussions in which violations of this nature are found will
524:
to take privacy very seriously, so the answer will often be one word, such as "likely", "confirmed", or "unrelated". The privacy policy allows for considerable disclosure but in most cases this is used judiciously. If the checkuser feels more information is needed, especially in serious cases of
130:
Identifying sock puppetry is not always a simple matter. There is often an element of judgement and assessment of evidence. You need to provide evidence showing the accounts or IPs are acting in a disruptive or forbidden manner, which other users will then assess. If there is a good case that
415:
is a tool used to obtain technical evidence related to a sock-puppetry allegation. It will not be used without good cause, which you must clearly demonstrate. If your request is agreed by a clerk or administrator, then they will tag the request for CheckUser attention.
50:
A sockpuppet inquiry case may only be opened if there is evidence or good cause to suspect that there has been abuse of multiple accounts, or IPs. The
English Knowledge's policy on sock puppetry holds that, whilst merely owning multiple accounts or IPs is acceptable,
295:, create the case by replacing "CASENAME" with the name of the puppet master, or previous case name. 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").
503:
of a checkuser request may be courteous but is not currently seen as essential; the user knows an SPI case has been set up, the evidence within that case, including the need for further technical evidence, is assessed within that, on its
384:
If an accusation on this page is "bad faith" (an editor making a fake case for an "attack" or to prevent their own editing being examined) then you may wish to say so briefly, but cases on this page will be decided based upon
794:
67:". Meatpuppets are not regular Wikipedians who happen to agree with each other; they are accounts set up by separate individuals for the sole purpose of supporting one another. For the purposes of upholding policy, Knowledge
420:
users, and the like. Because
Checkuser is both powerful and involves access to privacy-restricted information, its use is strictly limited by policy to cases where it is necessary, appropriate, and there is good cause.
147:
In general, cases are opened for current active issues, not closed ones. Exceptions are infrequent, usually when there is a serious issue such as accusations of admin puppetry or a likelihood of serious future issues.
78:
439:
be used unless there is good cause, and the final decision belongs to those users trusted with the tool. If you feel that
Checkuser is needed and appropriate, please read below before making your request.
47:"—is in violation of the project's communal norms. Editors who are filing an SPI request ought to be fully familiar with Knowledge's sock puppetry policy since complex sock puppetry cases occur regularly.
63:
Sometimes users who appear to work with a common agenda are not sockpuppets (one user, multiple accounts), but multiple users editing with the sole purpose of backing each other up, often called "
112:
Using an alternate account to mislead others or otherwise artificially stir up controversy by making disruptive edits with one account and normal ones with another account (known as "
135:
from the server logs may be needed to resolve the case, you may request that a checkuser add this evidence to the case. They will only do so if they feel it is appropriate. (See
346:
If you are accused of puppetry, stay calm and don't take the accusations too personally. If you have not abused multiple accounts or IPs and have not breached the policy on
68:
318:
and not get distracted from the case. As the case progresses you may update your evidence or statement as needed, to add new evidence or relevant information.
55:. As a rule of thumb, if you suspect the use of multiple accounts or IPs in a manner that is affecting the encyclopedia, an investigation ought to be filed.
247:, and the user has not had a sock puppet case under this or any other (known) identity, then the case name will be the name of the oldest-created account.
188:
Do not post private information, emails, logs, etc. on the wiki that are not already on the wiki (if this is a problem, ask before posting your case).
520:
If the request is agreed, a checkuser may look at the server logs, and add comments and evidence as they see fit. Checkuser findings are required by
724:
374:
44:
40:
292:
485:
on an open case if it is necessary. (This is done automatically if you use the "Request CheckUser" box to create your new request.)
195:), and reasonable deductions and impressions drawn from evidence. Do not debate the issue, or respond to others' attempts to do so.
366:
153:
If the evidence is sensitive or the case delicate or likely to be very controversial, seek advice by email from a member of the
341:
736:
58:
675:
File an SPI request without checkuser. For privacy reasons, checkusers will not publicly connect IP addresses to accounts.
28:
17:
354:. If there is a good reason for the evidence provided, point it out in your own section. Sockpuppet inquiry pages are
91:
142:
75:
have the violations stricken from the discussions and sanctions may be applied to protect the project's integrity.
271:, create it as a new page, and add a comment to the effect that that you aren't sure - a clerk will check for you.
814:
378:
84:
261:, under the same name, IP, or a different one, use that name, and add the case as a new report on the same page.
177:
If you have a good case, then take time to write it up, making sure you follow the guidance notes, especially:
606:
Link to block log of the original account. Supply evidence to show the user is the banned or blocked party.
113:
217:
You can add more later, if needed. Do not use any section headers ("===") as this will break the template.
125:
370:
365:
If you are operating a legitimate alternate account and do not want to make this public, then please see
314:
Remember to watch the page in case there are questions or comments about your evidence, and remember to
159:, in order to minimize the risk of unhelpful disruption and "fall-out", whether you are right or wrong.
358:
about account and IP misuse—nothing else. If the evidence is not there, then the case will be closed
198:
Check that the matter is current (right now), and that the user is not already blocked, or reported.
784:
473:
463:
297:
Then click the button to create a request page (or new section) and follow the instructions there.
332:
106:
34:
585:
347:
619:'Messy' and complex cases where behavior alone cannot determine which accounts are socks.
428:
8:
748:
772:
When a case has been decided (whether by patrolling administrator, clerk or checkuser):
514:
This is an anti-abuse measure to prevent wasted time and discourage spurious requests:
571:
Link to the closed case. Supply evidence to show the active user is the banned party.
521:
510:
Your request will be reviewed by a clerk who will update it with any notes they make.
424:
638:
summary of the situation, link to further discussions, and supply supporting diffs.
793:
A second clerk will review the case and (unless there is a concern) archive it to "
565:
525:
abuse, repeat cases, or complex cases, they will use their discretion to say more.
611:
Likely undetected or "sleeper" socks, getting an IP block (of a repeat sock-user)
703:
Initially file an investigation with no check requested, except in severe cases.
432:
412:
202:
132:
43:
on the
English Knowledge, misuse of two or more accounts by the one individual—"
697:
192:
64:
762:
614:
Link to or point to a possible reason, or if enough socks exist, the archive.
808:
183:
95:
517:
The investigating user/s may use
Checkuser anyway, if it is likely to help.
120:
712:
154:
688:
Question about a possible sock puppet related to an open arbitration case
331:
Consider notifying all the users you are accusing using the template {{
727:, or file a case without CU and ask if checkuser should be requested.
53:
utilising them in a disruptive, misleading, or unhelpful manner is not
99:
576:
Ongoing, serious pattern of vandalism involving dozens of incidents
672:
Checkuser to confirm a user has been using a specific IP address
79:
Examples of forbidden uses of multiple accounts or meat-puppetry
708:
Suspected administrator sockpuppetry or multiple account abuse
691:
Request on the arbitration case pages that a checkuser be run.
747:
Access is rarely granted, and not requested here. Please see
401:
493:
CheckUser is appropriate and needed, do so below this tag.
162:
664:
Disruptive "throwaway" account used only for a few edits
598:
Link to four or more diffs showing the 3RR violation.
795:
Knowledge:Sockpuppet investigations/Case name/Archive
512:
Do not do this yourself unless you are an SPI clerk.
683:Such requests are not accepted. Please do not ask.
191:Remember to stick to verifiable evidence (usually
732:Open proxy where you already know the IP address
312:Watch the case while open (and update if needed):
806:
680:Checkuser on yourself to "prove your innocence"
555:In these cases, file a case and request a check
431:, as well as English Knowledge's own individual
744:You want access to the checkuser tool yourself
626:account listed could be a possible sockpuppet.
715:. They may have to desysop the administrator.
622:Link to diffs that show the likelihood that
603:Evasion of community-based bans or blocks
647:In these cases, do not request CheckUser
568:or Wikimedia Foundation bans or remedies
631:You believe a check is warranted anyway
205:evidence to help prove the matter. (See
29:What qualifies as abusive sock puppetry?
435:that supplements these. Checkuser will
102:, evasion, disruption, or other misuse.
39:Whilst merely owning multiple accounts
14:
807:
352:that will almost always be the finding
71:between meatpuppets and sockpuppets.
737:Knowledge:WikiProject on open proxies
533:When to consider requesting CheckUser
497:you may endorse the request yourself.
289:Create the report page (or section):
776:A clerk, CU, or admin will add the
387:evidence of misuse of accounts only
23:
18:Knowledge:Sockpuppet investigations
667:Block. No checkuser is necessary.
659:Block. No checkuser is necessary.
24:
826:
362:any adverse finding of any kind.
342:Defending yourself against claims
175:Write up your evidence statement:
790:template at the top of the case.
656:Obvious, disruptive sock puppet
595:3RR violation using sockpuppets
423:Checkuser is restricted by both
579:Supply diffs of the vandalism.
322:
302:
234:Identify the name for the case:
224:
165:
451:To request CheckUser evidence:
367:alternate account notification
279:
206:
136:
105:Using an alternate account to
13:
1:
720:Other disruption of articles
481:You (or anyone) can do this
407:
143:How to open an investigation
7:
799:Only a clerk should do this
96:multiple article reversions
10:
831:
32:
651:
646:
559:
554:
201:Decide if the case needs
87:more than once in a poll.
700:" use to avoid scrutiny
495:If you are an SPI clerk
139:for more information.)
126:Claims of sock puppetry
35:Knowledge:Sock puppetry
815:Knowledge sockpuppetry
713:Arbitration Committee
590:Link to the vote(s).
291:Using the box on the
253:- If a previous case
155:Arbitration Committee
59:Abusive meat-puppetry
45:abusive sock puppetry
333:subst:uw-socksuspect
251:2nd or further case?
69:does not distinguish
749:Knowledge:CheckUser
489:If you need to say
371:email any checkuser
114:good hand, bad hand
763:After the decision
698:good hand bad hand
381:to ask for help.
92:Knowledge policies
780:parameter to the
759:
758:
755:
754:
642:
641:
550:
549:
522:Foundation policy
445:
444:
339:
338:
218:
184:assume good faith
121:Presenting a case
822:
788:
644:
643:
552:
551:
540:
539:
529:
528:
477:
467:
433:Checkuser policy
429:Checkuser policy
408:
216:
163:
98:, edit-warring,
830:
829:
825:
824:
823:
821:
820:
819:
805:
804:
785:SPI case status
782:
765:
760:
546:How to proceed
534:
474:SPI case status
471:
464:SPI case status
461:
404:
344:
145:
128:
123:
81:
61:
37:
31:
22:
21:
20:
12:
11:
5:
828:
818:
817:
803:
802:
791:
789:
779:
770:
769:
764:
761:
757:
756:
753:
752:
745:
741:
740:
733:
729:
728:
721:
717:
716:
711:Report to the
709:
705:
704:
701:
693:
692:
689:
685:
684:
681:
677:
676:
673:
669:
668:
665:
661:
660:
657:
653:
652:
649:
648:
640:
639:
632:
628:
627:
620:
616:
615:
612:
608:
607:
604:
600:
599:
596:
592:
591:
588:
581:
580:
577:
573:
572:
569:
561:
560:
557:
556:
548:
547:
544:
536:
535:
532:
527:
508:
507:
506:
505:
498:
487:
478:
468:
449:
447:
446:
443:
442:
425:privacy policy
403:
400:
343:
340:
337:
336:
335:|Case name}}.
329:
328:
320:
319:
309:
308:
300:
299:
286:
285:
277:
276:
275:
274:
273:
272:
262:
255:already exists
248:
231:
230:
222:
221:
220:
219:
213:
212:
211:
210:
199:
196:
189:
186:
172:
171:
161:
160:
144:
141:
133:checkuser data
127:
124:
122:
119:
118:
117:
110:
107:avoid scrutiny
103:
90:Circumventing
88:
80:
77:
60:
57:
30:
27:
15:
9:
6:
4:
3:
2:
827:
816:
813:
812:
810:
800:
796:
792:
786:
781:
777:
775:
774:
773:
767:
766:
750:
746:
743:
742:
738:
734:
731:
730:
726:
722:
719:
718:
714:
710:
707:
706:
702:
699:
695:
694:
690:
687:
686:
682:
679:
678:
674:
671:
670:
666:
663:
662:
658:
655:
654:
650:
645:
637:
633:
630:
629:
625:
621:
618:
617:
613:
610:
609:
605:
602:
601:
597:
594:
593:
589:
587:
583:
582:
578:
575:
574:
570:
567:
563:
562:
558:
553:
545:
542:
541:
538:
537:
531:
530:
526:
523:
518:
515:
513:
502:
499:
496:
492:
488:
486:
484:
479:
475:
470:
465:
460:
457:
456:
455:
454:
453:
452:
441:
438:
434:
430:
426:
421:
417:
414:
410:
409:
406:
405:
399:
397:
392:
388:
382:
380:
376:
372:
368:
363:
361:
357:
353:
349:
348:meat-puppetry
334:
330:
326:
323:
321:
317:
313:
310:
306:
303:
301:
298:
294:
293:main SPI page
290:
287:
283:
280:
278:
270:
266:
263:
260:
256:
252:
249:
246:
243:- If it is a
242:
239:
238:
237:
236:
235:
232:
228:
225:
223:
215:
214:
208:
204:
200:
197:
194:
190:
187:
185:
181:
180:
179:
178:
176:
173:
169:
166:
164:
158:
156:
151:
150:
149:
140:
138:
134:
115:
111:
108:
104:
101:
97:
93:
89:
86:
83:
82:
76:
72:
70:
66:
56:
54:
48:
46:
42:
36:
26:
19:
798:
771:
635:
623:
519:
516:
511:
509:
501:Notification
500:
494:
490:
482:
480:
476:|curequest}}
458:
450:
448:
436:
422:
418:
411:
395:
390:
386:
383:
364:
359:
355:
351:
345:
324:
315:
311:
304:
296:
288:
281:
268:
264:
258:
254:
250:
244:
240:
233:
226:
182:Remember to
174:
167:
152:
146:
129:
73:
62:
52:
49:
41:is permitted
38:
25:
696:Suspected "
564:Evasion of
483:at any time
269:aren't sure
137:§ Checkuser
116:" or GHBH).
65:meatpuppets
33:Main page:
723:Report to
586:vote fraud
543:Situation
379:Arbitrator
209:for more.)
584:Possible
413:CheckUser
402:CheckUser
394:often be
389:. You do
377:, or any
316:stay cool
267:- If you
265:Not sure?
259:this user
241:New case?
203:CheckUser
109:of edits.
100:collusion
809:Category
735:List on
245:new case
94:such as
634:Give a
504:merits.
459:Change
396:removed
360:without
350:, then
566:ArbCom
373:, any
369:, and
85:Voting
778:close
768:Close
636:brief
375:Clerk
207:below
193:diffs
157:first
16:<
725:AN/I
624:each
427:and
356:only
257:for
797:".
491:why
469:to
437:not
391:not
282:III
811::
787:}}
783:{{
751:.
739:.
472:{{
466:}}
462:{{
398:.
305:IV
227:II
801:.
327:.
325:V
307:.
284:.
229:.
170:.
168:I
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.