642:
could probably figure out who goes with whom. I'm wondering how much effort I need to put into connecting those dots, as opposed to just saying "here are suspicious accounts with suspicious behaviors " and letting a CU review it and sort it as they will. What is the best way to organize information in the above 4 categories from the point of view of SPI patrollers? (If there's a help doc that explains this, please point me to it.) Thanks in advance for any guidance,
261:
231:
641:
The SPIs I have in mind are all ARBPIA and could match to any of a half dozen or so sockmasters who have had socks sanctioned in the same relative time period (first half of 2024), some of whom are familiar LTAs. I know there are editors who are much more familiar with these ARBPIA LTAs than I am and
573:
No one except the IP user has said you're a sock and that user hasn't given any basis for calling you that. Possibly the IP user doesn't even know what a sockpuppet is. In any event, in the absence of any reason to give credence to that claim, this discussion has turned out to be off-topic and should
636:
If I think it's a compromised account, or group of compromised accounts, and I don't know who the master is, again: should take a "best guess" and file it under that master, or open an SPI under the oldest account as the master with no sock, or open separate "one-account" SPIs, one for each account?
629:
If I have a group of suspected socks but I think there are multiple possible masters, is it better to just pick a master and list all the socks under that master, or should I try and "best guess" which socks go to which master, and file multiple SPIs, and cross-reference them? Like, "here's a bunch
657:
The answer to #1 is clearly open one SPI and list all the accounts you believe are socks. For the purpose of SPI, we define "the master" as the account which was created first. For cases 2-4, I guess just put it all into one SPI filing. SPI cases get split and merged all the time as information
414:
Thank you for your consideration and guidance. I see no conflict here as the contentious topic itself was not discussed but referenced to document the individuals involvement. As per the guidelines, anonymous shouldn't be editing/undo/reverting more than once every 24hrs. I'd like to report their
750:
The best way to write a good SPI is to stick to hard evidence, which usually means diffs and links to log entries. Where things go off into the weeds is when people write long essays. If presenting the diffs in a table works for you, that's just fine, but the important stuff is the diffs
469:" to provide complete information and not to promote one particular point of view over another. As such, the neutral point of view does not mean the exclusion of certain points of view; rather, it means including all verifiable points of view which have sufficient due
814:
has the log. Everything says to me it's a vanished user, for example one final edit was to add the retired tag. I guess you'd have to assume the log was hidden related to the vanishing. Anyway, the (public) global lock log:
788:
118:
476:
Anon is not following content dispute procedures and did not discuss the validity of content with me on the talk page, nor edited the content constructively. They opted to simply and flatly delete it.
633:
If I have a group of socks but no idea who the master is, is it better to file it under "best guess," or just pick the oldest suspected sock account and file it under that account as a 'new master'?
626:
SPI under the master and list all suspected socks (and then in the filing explain one by one why I think each one is a sock), or should I open multiple SPIs under the same master, one for each sock?
852:. Please also remember that some accounts are locked without prior input on SRG, this is result of stewards performing CU actions through loginwiki or through private email channel. Best regards,
505:. It will then be handled by extendedconfirmed editors in due course. Might take a while. I know it's annoying but the rules are there to reduce disruption and apply to thousands of articles.
441:. So, it falls outside of what either you or IPs are permitted to work on. I have added a template to the talk page notifying users that parts of the article are within scope of
542:
On top of that apparently just mentioning someone said something negative about arabs is invalid. It's genuinely and fundamentally disenfranchising and culturally invalidating.
498:
416:
328:
545:
Arabs and their issues are not valid unless someone external deems so, pending 30 day review and prove your worth with 500 edits (except for anon). It's so disheartening.
372:
That's a content dispute issue, but regardless, the fact that it's about the Arab-Israeli conflict (A contentious topic) means that neither of you should be discussing it.
351:
39:
674:
I've been thinking about similar myself but mostly from a UPE perspective than
Levivich's situation. Do you think a table something like the below would be helpful?
464:
381:
222:
560:
546:
480:
420:
387:
357:
343:
316:
218:
214:
210:
206:
202:
198:
194:
190:
186:
182:
178:
174:
170:
166:
162:
158:
336:
154:
150:
146:
142:
138:
134:
130:
126:
122:
332:
568:
365:
554:
528:
514:
488:
454:
493:
Have a look at the
Further information part of the Warning: active arbitration remedies note at the top of the talk page. The procedure is to
583:
795:. Is there any public information anywhere? I'm specifically wondering if it's locked due to being a compromised account or due to socking.
428:
409:
395:
848:: Vanished users get locked to satisfy IIRC EU laws. You are correct though, such locks made through renaming processes are not logged in
459:
Genuinely asking, what now? Shmuley
Boteach factually said somethings that are with evidence provided. How do I include them? As per the
910:
896:
74:
470:
774:
665:
872:
837:
823:
758:
745:
651:
866:
880:
804:
630:
of socks, I don't know if they're LTA1 or LTA2 or LTA3, but probably one or more of those", what's the best way to file that?
536:
Why am I the sock and not the obviously competent anon? You can visibly see that I'm fumbling around, but in good faith, lol.
80:
310:
Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
230:
609:
Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
274:
24:
298:
736:
This is extremely crude and it depends on the evidence as what makes sense structurally but I hope you get the idea.
637:(E.g., if I think they're compromised but don't know if they're compromised by the same person or different people.)
811:
386:
The addition I made was to document
Shmuley Boteach's media engagement on the topic of the Arab-Israeli conflict.
884:
460:
319:
as a sock, given that I want to remain an IP. He is (only) adding NPOV and non-cited edits to a BLP. Exclusively.
881:
21:34, 20 August 2024 מקף globally renamed Winter queen lizzie to
Vanished user edc8363ad1718beb64ce9d923ab18295
501:. Edit requests most likely to succeed are those that are 'Specific, Uncontroversial, Necessary, Sensible' per
20:
69:
434:
324:
320:
849:
816:
60:
113:
564:
550:
484:
424:
391:
361:
347:
342:
sources are cited within the body of text. I am a geuinely a new user. And sock address of whom?
892:
613:
524:
510:
450:
245:
618:
Hi SPI, can you please give me some guidance about best practices for these kinds of filings:
519:
Yes, or wait until you are extended confirmed. The IP seems to think you are a sock. Are you?
445:. If the ECR violations continue I will request that the page is extendedconfirmed protected.
98:
579:
539:
Read my contributions history, it's me just asking for advice in how to navigate wikipedia.
494:
8:
782:
50:
906:
876:
833:
800:
770:
755:
662:
647:
405:
377:
295:
90:
65:
888:
520:
506:
499:
Knowledge:Requests_for_page_protection#Current_requests_for_edits_to_a_protected_page
446:
46:
787:
Is there a global lock log that says why a particular account was globally locked?
502:
442:
438:
741:
575:
283:
241:
902:
861:
845:
829:
796:
766:
752:
671:
659:
643:
401:
373:
292:
820:
246:
737:
622:
If there are multiple socks and I think it's one master, should I open
291:
IP and brand new user arguing with each other: this is going nowhere.
854:
792:
327:. Warnings don't seem to have an impact. How best to address this?
243:
433:
It's not about what you can see. It is an objective fact that
400:
I suggest you read the comment that I left on your talk page.
247:
791:
has no local or global blocks, and I can't find anything at
356:
information presented are direct extractions from sources.
465:
Knowledge:NPOV means neutral editing, not neutral content
887:. I assumed they just decided to abandon this account.
479:
Do I wait 30 days and 500 edits and add it back in?
15:
789:
User:Vanished user edc8363ad1718beb64ce9d923ab18295
533:Referring to sock puppet, as in a fake account?
27:and anything related to its purposes and tasks.
497:. It can be on the talk page or centrally at
559:I even accurately referenced the content.
271:the page to report suspected sock puppetry.
708:diff/log/other evidence (or ?/possibles)
706:diff/log/other evidence (or ?/possibles)
417:2603:7000:2101:AA00:8463:3822:2153:CF14
329:2603:7000:2101:AA00:8463:3822:2153:CF14
658:emerges, so don't sweat the details.
689:Suspected Master/one of their socks
306:The following discussion is closed.
255:
873:Salomeofjudea → winter queen lizzie
275:Knowledge:Sockpuppet investigations
13:
273:Please instead create a report at
14:
924:
315:I cant seem to report new editor
812:Special:CentralAuth/Leola_Mayert
605:The discussion above is closed.
259:
229:
40:Click here to start a new topic.
325:here - without any edit summary
911:03:56, 17 September 2024 (UTC)
897:03:40, 17 September 2024 (UTC)
867:20:54, 16 September 2024 (UTC)
838:19:34, 16 September 2024 (UTC)
824:18:48, 16 September 2024 (UTC)
805:18:09, 16 September 2024 (UTC)
775:15:22, 15 September 2024 (UTC)
759:21:38, 14 September 2024 (UTC)
746:20:38, 14 September 2024 (UTC)
666:20:10, 14 September 2024 (UTC)
652:18:12, 14 September 2024 (UTC)
1:
584:11:57, 9 September 2024 (UTC)
569:08:38, 9 September 2024 (UTC)
555:08:37, 9 September 2024 (UTC)
529:08:20, 9 September 2024 (UTC)
515:08:19, 9 September 2024 (UTC)
489:08:05, 9 September 2024 (UTC)
455:07:46, 9 September 2024 (UTC)
429:03:28, 9 September 2024 (UTC)
419:) violation of that policy.
410:03:17, 9 September 2024 (UTC)
396:03:17, 9 September 2024 (UTC)
382:03:14, 9 September 2024 (UTC)
366:03:14, 9 September 2024 (UTC)
352:03:12, 9 September 2024 (UTC)
337:03:05, 9 September 2024 (UTC)
299:12:25, 9 September 2024 (UTC)
37:Put new text under old text.
7:
850:meta:Special:Log/globalauth
817:meta:Special:Log/globalauth
45:New to Knowledge? Welcome!
10:
929:
88:
828:I see -- thanks, zzuuzz!
703:Article and/or behaviour
75:Be welcoming to newcomers
25:Sockpuppet investigations
871:That's this one, right?
720:diff/log/other evidence
718:diff/log/other evidence
714:diff/log/other evidence
712:diff/log/other evidence
607:Please do not modify it.
308:Please do not modify it.
877:cloaked rename request
70:avoid personal attacks
810:Whereas someone like
223:Auto-archiving period
495:make an edit request
317:user:Smartiest Marty
614:Paperwork questions
309:
270:
81:dispute resolution
42:
727:
726:
307:
281:
280:
268:
254:
253:
61:Assume good faith
38:
920:
864:
857:
783:Global lock log?
698:Additional info
684:
683:
263:
262:
256:
248:
234:
233:
224:
101:
16:
928:
927:
923:
922:
921:
919:
918:
917:
862:
855:
785:
616:
611:
610:
561:Smartiest Marty
547:Smartiest Marty
481:Smartiest Marty
421:Smartiest Marty
388:Smartiest Marty
358:Smartiest Marty
344:Smartiest Marty
312:
303:
302:
301:
286:
272:
260:
250:
249:
244:
221:
107:
106:
105:
104:
97:
93:
86:
56:
23:for discussing
12:
11:
5:
926:
916:
915:
914:
913:
869:
842:
841:
840:
784:
781:
780:
779:
778:
777:
763:
762:
761:
731:
730:
729:
728:
725:
724:
722:
716:
710:
704:
700:
699:
696:
693:
690:
687:
678:
677:
676:
675:
639:
638:
634:
631:
627:
615:
612:
604:
603:
602:
601:
600:
599:
598:
597:
596:
595:
594:
593:
592:
591:
590:
589:
588:
587:
586:
571:
543:
540:
537:
534:
517:
477:
474:
467:
437:is covered by
370:
369:
368:
313:
304:
290:
289:
288:
287:
285:
282:
279:
278:
266:
264:
252:
251:
242:
240:
239:
236:
235:
109:
108:
103:
102:
94:
89:
87:
85:
84:
77:
72:
63:
57:
55:
54:
43:
34:
33:
30:
29:
28:
9:
6:
4:
3:
2:
925:
912:
908:
904:
900:
899:
898:
894:
890:
886:
885:contributions
882:
878:
874:
870:
868:
865:
859:
858:
851:
847:
843:
839:
835:
831:
827:
826:
825:
822:
818:
813:
809:
808:
807:
806:
802:
798:
794:
790:
776:
772:
768:
764:
760:
757:
754:
749:
748:
747:
743:
739:
735:
734:
733:
732:
723:
721:
717:
715:
711:
709:
705:
702:
701:
697:
694:
691:
688:
686:
685:
682:
681:
680:
679:
673:
669:
668:
667:
664:
661:
656:
655:
654:
653:
649:
645:
635:
632:
628:
625:
621:
620:
619:
608:
585:
581:
577:
572:
570:
566:
562:
558:
557:
556:
552:
548:
544:
541:
538:
535:
532:
531:
530:
526:
522:
518:
516:
512:
508:
504:
500:
496:
492:
491:
490:
486:
482:
478:
475:
472:
468:
466:
462:
458:
457:
456:
452:
448:
444:
440:
436:
432:
431:
430:
426:
422:
418:
413:
412:
411:
407:
403:
399:
398:
397:
393:
389:
385:
384:
383:
379:
375:
371:
367:
363:
359:
355:
354:
353:
349:
345:
341:
340:
339:
338:
334:
330:
326:
322:
318:
311:
300:
297:
294:
276:
265:
258:
257:
238:
237:
232:
228:
220:
216:
212:
208:
204:
200:
196:
192:
188:
184:
180:
176:
172:
168:
164:
160:
156:
152:
148:
144:
140:
136:
132:
128:
124:
120:
117:
115:
111:
110:
100:
96:
95:
92:
82:
78:
76:
73:
71:
67:
64:
62:
59:
58:
52:
48:
47:Learn to edit
44:
41:
36:
35:
32:
31:
26:
22:
18:
17:
889:Sean.hoyland
853:
786:
765:Thanks Roy!
751:themselves.
719:
713:
707:
640:
623:
617:
606:
521:Sean.hoyland
507:Sean.hoyland
447:Sean.hoyland
314:
305:
226:
112:
19:This is the
463:guidaince:
435:the content
284:Suggestion?
576:Largoplazo
695:Editor B
692:Editor A
503:WP:EDITXY
443:WP:ARBECR
439:WP:ARBECR
83:if needed
66:Be polite
21:talk page
903:Levivich
846:Levivich
830:Levivich
797:Levivich
793:meta:SRG
767:Levivich
753:RoySmith
672:RoySmith
660:RoySmith
644:Levivich
402:M.Bitton
374:M.Bitton
293:RoySmith
267:This is
114:Archives
91:Shortcut
51:get help
227:14 days
863:(talk)
821:zzuuzz
756:(talk)
663:(talk)
471:weight
296:(talk)
99:WT:SPI
901:Yup.
819:. --
738:S0091
574:end.
119:Index
79:Seek
907:talk
893:talk
834:talk
801:talk
771:talk
742:talk
648:talk
580:talk
565:talk
551:talk
525:talk
511:talk
485:talk
461:NPOV
451:talk
425:talk
406:talk
392:talk
378:talk
362:talk
348:talk
333:talk
323:and
321:Here
68:and
856:A09
624:one
269:not
909:)
895:)
883:→
879:→
875:→
836:)
803:)
773:)
744:)
650:)
582:)
567:)
553:)
527:)
513:)
487:)
473:."
453:)
427:)
408:)
394:)
380:)
364:)
350:)
335:)
225::
219:25
217:,
215:24
213:,
211:23
209:,
207:22
205:,
203:21
201:,
199:20
197:,
195:19
193:,
191:18
189:,
187:17
185:,
183:16
181:,
179:15
177:,
175:14
173:,
171:13
169:,
167:12
165:,
163:11
161:,
159:10
157:,
153:,
149:,
145:,
141:,
137:,
133:,
129:,
125:,
121:,
49:;
905:(
891:(
860:|
844:@
832:(
799:(
769:(
740:(
670:@
646:(
578:(
563:(
549:(
523:(
509:(
483:(
449:(
423:(
415:(
404:(
390:(
376:(
360:(
346:(
331:(
277:.
155:9
151:8
147:7
143:6
139:5
135:4
131:3
127:2
123:1
116::
53:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.