577:
accounts have been editing, and it has been conclusively demonstrated by time stamps that
Moorsmur and Inniverse are different editors. MuZemike's past allegation that I am a sock of Azviz has already been confuted, yet here he is again accusing me of being related to accounts Azvis through two accounts that I have no relation to. It appears to me that my only “crime” has been to be previously active on the “deletion patrol”, and that I may have been overzealous in my removal of some prods. Since being unblocked several months ago, I have stayed away from over-involving myself in the deletion process of articles, but even so, I have been blocked by the same admin once again. I suggest that because my home city has been publicly disclosed it has made me an easy target to be linked with anyone else who geolocates to the same city as me. A sober second look at all of the facts leading up to this block will reveal that this block is unfair and unjustified. I request, in the spirit of fairness and good faith, that I be unblocked.
565:(that I am not a sock puppet of Azviz). Third, I question the reliability of the checkuser data when the clerk has provided no details of the alleged links between the accounts. In other examples I have seen the clerk write details of the checkuser data when an IP match is not “confirmed”. The type of information I would be very interested in seeing is, for example, do the IP's for these accounts belong to the same IP range, IP provider, or do they just geolocate to the same municipality, province, or region of the country. The reason that I am asking for this further information is that I find it unusual that no further comments were given by the checkuser, other than it is
378:
CheckUser be required to confirm this?) - is there a very large rangeblock in place (please do not post details here of specific IPs for your own privacy)? Or does the whole city share the same small range of IPs? I live in an area with a population of about 1/3 million - and yet even a rangeblock with a fair range would not get most of us - in fact, I'd be surprised if it affected many people in the street in which I live! Could you please give us some more information to enable us to see that this has been confirmed --
561:
am requesting that an uninvolved admin take a serious and objective review of my block. First, the blocking admin, KWW, has a conflict of interest in this matter, and therefore, it was improper of him to block my account (his previous block of my account was reversed over his objection). Second, the reason that the blocking admin has given for the block (that I am a sock puppet of Azviz) is contrary to the findings confirmed
1153:
1092:
933:
671:
990:
830:
726:
475:
198:
33:
420:
original block, no one ever disputed that. He was unblocked after confirming his real-life identity to
Georgewilliamherbert. Now, we catch him socking . We could block him as a sockmaster, or, since rampant socking is a part of Azviz's behavioural pattern, block him based on new confirmation of him behaviourally matching Azviz. I chose the latter.—
560:
I truly believe in the
Knowledge (XXG) project, and that is why I am making one more appeal to the reasonable editors of Knowledge (XXG). (My other option would be to just open a new account, but then I would be editing in violation of a block and I want to work within the rules, not against them.) I
576:
I cannot help but wonder if there is any possibility that the scenario scripted between
Moorsmur and Macpl is a setup. It is no secret that my place of residence is in Calgary, which is a high-tech city of over one million people. I have had no involvement in any of the articles that either of these
288:
be the disruptive editor
Moorsmur. Check the editing records for June 30th! The block is improper because it was placed by an editor who has a clear conflict in this matter, there is no connection between myself and Moorsmur, and it is also improper because it is indefinite. Even if Moorsmur were my
337:
You'll have to explain to me why simultaneous editing proves anything at all. Are we to presume that you aren't capable of using two browser windows at once? That you cannot own a laptop and a desktop? That you never edit from an area where multiple computers are simultaneously available? Note that
118:
It appears that no one has read, or taken into consideration, my comments posted in the ANI on
September 11th. I have demonstrated conclusively that I can not be the same editor as Moorsmur due to the concurrent editing that occurred on June 30th. It is also abundantly clear that KWW has a conflict
283:
It has previously been confirmed that (due to my editing location) a checkuser will always provide a “false positive” (i.e. “likely”) result when matched with Azviz, just as it would for any other editor who lives in the same million-plus population city as I do. KWW and MuZemike are both aware of
356:
I confess full ignorance of your case, but I must ask how temporary block periods for deliberate sockpuppetry (I realize you are disputing this occurred, of course) are pursuant to policy. I am not aware of any particular policy that dictates sockmasters should necessarily be blocked temporarily
419:
is the geographic region, not a particular IP range. That's not the real issue, though: even given the vagueness of data on Azviz, the data on
Moorsmur and Macpl is fresh. Here's our situation: Inniverse has always been a good behavioural match for Azviz, and, despite all the discussion on the
377:
that shows that "It has previously been confirmed that (due to my editing location) a checkuser will always provide a “false positive” (i.e. “likely”) result when matched with Azviz, just as it would for any other editor who lives in the same million-plus population city as I do" (or would a
16:
This is my talk page and I do not wish to use it as a forum for public discussions as it has been so used in the past. For that reason I will not reply to messages in this forum. If you must post a necessary message, do not be insulted if I read and remove it. My removal of your post is my
1177:
until a consensus is reached, and anyone, including you, is welcome to contribute to the discussion. The nomination will explain the policies and guidelines which are of concern. The discussion focuses on high-quality evidence and our policies and guidelines.
1115:
1118:
until a consensus is reached, and anyone is welcome to contribute to the discussion. The nomination will explain the policies and guidelines which are of concern. The discussion focuses on high-quality evidence and our policies and guidelines.
959:
until a consensus is reached, and anyone is welcome to contribute to the discussion. The nomination will explain the policies and guidelines which are of concern. The discussion focuses on high-quality evidence and our policies and guidelines.
697:
until a consensus is reached, and anyone is welcome to contribute to the discussion. The nomination will explain the policies and guidelines which are of concern. The discussion focuses on high-quality evidence and our policies and guidelines.
701:
Users may edit the article during the discussion, including to improve the article to address concerns raised in the discussion. However, do not remove the article-for-deletion template from the top of the article.
1181:
Users may edit the article during the discussion, including to improve the article to address concerns raised in the discussion. However, do not remove the article-for-deletion notice from the top of the article.
1122:
Users may edit the article during the discussion, including to improve the article to address concerns raised in the discussion. However, do not remove the article-for-deletion notice from the top of the article.
963:
Users may edit the article during the discussion, including to improve the article to address concerns raised in the discussion. However, do not remove the article-for-deletion notice from the top of the article.
17:
acknowledgment that it has been received. If I choose to reply, I will reply on your talk page (and it goes without saying that I will be watching or otherwise monitoring your talk page after I post a message).
694:
1174:
956:
119:
in this matter as he was the blocking admin who then had his block overturned after the review, and as such ,he should not be involved in deciding the issue in this matter.
648:
Pointing out that the unblock summary was a bit misleading: The process you went through with
Georgewilliamherbert has not actually established that you are "not Avziz".
640:
template again. If you make too many unconvincing or disruptive unblock requests, you may be prevented from editing this page until your block has expired.
329:
template again. If you make too many unconvincing or disruptive unblock requests, you may be prevented from editing this page until your block has expired.
189:
template again. If you make too many unconvincing or disruptive unblock requests, you may be prevented from editing this page until your block has expired.
1164:
1104:
945:
683:
131:
138:- and it was clarified there that this included the current account. As such, the block appears to be valid and so I am declining this unblock request. --
574:"likely" does not equal "confirmed", and he time stamps for the different sock edits that Inniverse refers to suggests that Kww's block is incorrect.”
1056:
897:
793:
415:
It's a fair statement that
Inniverse would always match Azviz at this point. Checkuser data against Azviz is old, and all we really have on Azviz
515:
238:
73:
625:
314:
174:
452:
I'm not privy to the exact contents. GWH has been asked to forward any information he might have to Arbcom in case this winds up there.—
289:
sock, then pursuant to policy, Moorsmur should be blocked indefinite while the sock master should have a definite block period imposed.
436:
Did
Inniverse confirm past IP addresses to Georgewilliamherbert? That would help. Inniverse was asked, but refused to publicize them. ~
398:
158:
1060:
901:
797:
1099:
1083:
678:
662:
510:
233:
68:
300:
This clearly needs admins with checkuser to review. Please address your unblock request directly to the arbitration committee
609:
1048:
1001:
979:
889:
841:
819:
785:
737:
715:
1052:
893:
789:
1168:
1108:
949:
687:
488:
211:
46:
482:
284:
this unfortunate fact and are using it to have me blocked even though the editing evidence conclusively shows that I
205:
40:
1190:
487:
Other administrators may also review this block, but should not override the decision without good reason (see the
210:
Other administrators may also review this block, but should not override the decision without good reason (see the
45:
Other administrators may also review this block, but should not override the decision without good reason (see the
136:
Likely that the following three accounts are socks of each other, based on checkuser data and behavioural evidence
876:
588:
I appreciate you wanting to work within the rules. As you have ALREADY been advised, you cannot be unblocked
529:
252:
87:
1159:
1143:
837:
823:
772:
1035:
392:
152:
1064:
905:
801:
1186:
940:
924:
733:
719:
997:
983:
1017:
While all constructive contributions to Knowledge (XXG) are appreciated, content or articles may be
858:
While all constructive contributions to Knowledge (XXG) are appreciated, content or articles may be
754:
While all constructive contributions to Knowledge (XXG) are appreciated, content or articles may be
596:. You have been advised of this multiple times, and repeated requests will not change that fact. (
593:
706:
649:
597:
442:
362:
1009:
Non-notable athlete. Hasn't been the subject of significant coverage in reliable sources, fails
1130:
1031:
872:
768:
381:
141:
374:
634:
323:
183:
1018:
1010:
859:
850:
755:
746:
1116:
Knowledge (XXG):Articles for deletion/List of Transformers spacecraft (2nd nomination)
1072:
969:
913:
809:
493:
216:
51:
18:
703:
604:
457:
437:
425:
358:
347:
1126:
301:
338:
the problem here is not that you matched with Azviz, but that you matched with
1041:
Please consider improving the article to address the issues raised. Removing
882:
Please consider improving the article to address the issues raised. Removing
853:- bowler hasn't been the subject of significant coverage in reliable sources.
778:
Please consider improving the article to address the issues raised. Removing
1068:
965:
909:
805:
749:- bowler hasn't been the subject of significant coverage in reliable sources
357:
rather than indefinitely. This may, however, be me overlooking something. -
453:
421:
343:
1194:
1136:
1076:
973:
917:
813:
709:
654:
615:
461:
447:
429:
404:
366:
351:
304:
164:
26:
695:
Knowledge (XXG):Articles for deletion/List of Transformers spacecraft
988:
828:
724:
567:“likely... based on checkuser data and behavioural evidence”
473:
196:
31:
1175:
Knowledge (XXG):Articles for deletion/Surface to Air (film)
569:. As has already been pointed out by a non-involved editor
1163:
is suitable for inclusion in Knowledge (XXG) according to
1103:
is suitable for inclusion in Knowledge (XXG) according to
944:
is suitable for inclusion in Knowledge (XXG) according to
682:
is suitable for inclusion in Knowledge (XXG) according to
622:
If you want to make any further unblock requests, please
311:
If you want to make any further unblock requests, please
171:
If you want to make any further unblock requests, please
642:
Do not remove this unblock review while you are blocked.
592:
an unblock request; you must make your case directly to
331:
Do not remove this unblock review while you are blocked.
191:
Do not remove this unblock review while you are blocked.
1157:
A discussion is taking place as to whether the article
1097:
A discussion is taking place as to whether the article
1059:
process can result in deletion without discussion, and
957:
Knowledge (XXG):Articles for deletion/George Frilingos
938:
A discussion is taking place as to whether the article
900:
process can result in deletion without discussion, and
796:
process can result in deletion without discussion, and
676:
A discussion is taking place as to whether the article
570:
562:
543:
539:
533:
524:
520:
506:
502:
498:
266:
262:
256:
247:
243:
229:
225:
221:
101:
97:
91:
82:
78:
64:
60:
56:
1024:
You may prevent the proposed deletion by removing the
865:
You may prevent the proposed deletion by removing the
761:
You may prevent the proposed deletion by removing the
481:
This user's unblock request has been reviewed by an
204:
This user's unblock request has been reviewed by an
39:
This user's unblock request has been reviewed by an
8:
1165:Knowledge (XXG)'s policies and guidelines
1105:Knowledge (XXG)'s policies and guidelines
946:Knowledge (XXG)'s policies and guidelines
684:Knowledge (XXG)'s policies and guidelines
1030:notice, but please explain why in your
871:notice, but please explain why in your
767:notice, but please explain why in your
7:
1019:deleted for any of several reasons
1004:because of the following concern:
860:deleted for any of several reasons
844:because of the following concern:
756:deleted for any of several reasons
740:because of the following concern:
14:
1173:The article will be discussed at
1114:The article will be discussed at
955:The article will be discussed at
693:The article will be discussed at
1151:
1090:
931:
669:
1100:List of Transformers spacecraft
1084:List of Transformers spacecraft
679:List of Transformers spacecraft
663:List of Transformers spacecraft
462:00:18, 15 September 2010 (UTC)
448:00:08, 15 September 2010 (UTC)
430:23:12, 14 September 2010 (UTC)
405:23:00, 14 September 2010 (UTC)
367:22:56, 14 September 2010 (UTC)
352:22:49, 14 September 2010 (UTC)
305:15:39, 17 September 2010 (UTC)
165:21:05, 14 September 2010 (UTC)
1:
1137:14:42, 22 December 2017 (UTC)
710:08:12, 20 December 2012 (UTC)
1077:10:33, 2 February 2014 (UTC)
974:00:59, 24 January 2014 (UTC)
918:02:48, 16 January 2014 (UTC)
814:02:44, 16 January 2014 (UTC)
655:20:43, 20 October 2010 (UTC)
616:22:55, 20 October 2010 (UTC)
1063:allows discussion to reach
1044:{{proposed deletion/dated}}
1027:{{proposed deletion/dated}}
904:allows discussion to reach
885:{{proposed deletion/dated}}
868:{{proposed deletion/dated}}
800:allows discussion to reach
781:{{proposed deletion/dated}}
764:{{proposed deletion/dated}}
485:, who declined the request.
208:, who declined the request.
43:, who declined the request.
27:23:26, 14 August 2010 (UTC)
1210:
1195:15:56, 26 April 2022 (UTC)
1055:exist. In particular, the
896:exist. In particular, the
792:exist. In particular, the
134:includes the CU statement
1049:proposed deletion process
890:proposed deletion process
786:proposed deletion process
626:guide to appealing blocks
315:guide to appealing blocks
175:guide to appealing blocks
1167:or whether it should be
1107:or whether it should be
948:or whether it should be
686:or whether it should be
22:
1036:the article's talk page
877:the article's talk page
773:the article's talk page
993:
833:
729:
478:
201:
36:
1160:Surface to Air (film)
1144:Surface to Air (film)
1061:articles for deletion
1002:proposed for deletion
992:
902:articles for deletion
842:proposed for deletion
838:Brandon Qualischefski
832:
824:Brandon Qualischefski
798:articles for deletion
738:proposed for deletion
728:
530:change block settings
477:
373:Is it possible for a
253:change block settings
200:
88:change block settings
35:
1053:deletion processes
994:
894:deletion processes
834:
790:deletion processes
730:
479:
340:two other accounts
202:
37:
1134:
980:Proposed deletion
820:Proposed deletion
716:Proposed deletion
446:
1201:
1187:The Film Creator
1155:
1154:
1125:
1094:
1093:
1046:
1045:
1029:
1028:
991:
941:George Frilingos
935:
934:
925:George Frilingos
887:
886:
870:
869:
849:Appears to fail
831:
783:
782:
766:
765:
745:Appears to fail
734:George Frilingos
727:
720:George Frilingos
673:
672:
652:
639:
633:
612:
608:
600:
549:
547:
536:
518:
516:deleted contribs
476:
440:
401:
395:
387:
384:
328:
322:
272:
270:
259:
241:
239:deleted contribs
199:
188:
182:
161:
155:
147:
144:
107:
105:
94:
76:
74:deleted contribs
34:
1209:
1208:
1204:
1203:
1202:
1200:
1199:
1198:
1184:
1156:
1152:
1148:
1135:
1095:
1091:
1088:
1057:speedy deletion
1043:
1042:
1026:
1025:
998:Natalie Shelley
989:
987:
984:Natalie Shelley
936:
932:
929:
898:speedy deletion
884:
883:
867:
866:
829:
827:
794:speedy deletion
780:
779:
763:
762:
725:
723:
674:
670:
667:
650:
645:
637:
631:
630:, then use the
619:
610:
602:
598:
579:
537:
527:
513:
496:
489:blocking policy
474:
399:
393:
385:
382:
334:
326:
320:
319:, then use the
308:
291:
260:
250:
236:
219:
212:blocking policy
197:
194:
186:
180:
179:, then use the
168:
159:
153:
145:
142:
121:
95:
85:
71:
54:
47:blocking policy
32:
12:
11:
5:
1207:
1205:
1150:
1149:
1147:
1142:Nomination of
1140:
1124:
1089:
1087:
1082:Nomination of
1080:
1067:for deletion.
1047:will stop the
1015:
1014:
986:
977:
930:
928:
923:Nomination of
921:
908:for deletion.
888:will stop the
856:
855:
826:
817:
804:for deletion.
784:will stop the
752:
751:
722:
713:
668:
666:
661:Nomination of
659:
658:
657:
620:
586:
582:Decline reason
558:
554:Request reason
551:
472:
471:
470:
469:
468:
467:
466:
465:
464:
433:
432:
408:
407:
370:
369:
354:
309:
298:
294:Decline reason
281:
277:Request reason
274:
195:
169:
128:
124:Decline reason
116:
112:Request reason
109:
30:
13:
10:
9:
6:
4:
3:
2:
1206:
1197:
1196:
1192:
1188:
1183:
1179:
1176:
1170:
1166:
1162:
1161:
1145:
1141:
1139:
1138:
1132:
1128:
1120:
1117:
1112:
1110:
1106:
1102:
1101:
1085:
1081:
1079:
1078:
1074:
1070:
1066:
1062:
1058:
1054:
1050:
1039:
1037:
1033:
1022:
1020:
1013:
1012:
1007:
1006:
1005:
1003:
999:
985:
981:
978:
976:
975:
971:
967:
961:
958:
953:
951:
947:
943:
942:
926:
922:
920:
919:
915:
911:
907:
903:
899:
895:
891:
880:
878:
874:
863:
861:
854:
852:
847:
846:
845:
843:
839:
825:
821:
818:
816:
815:
811:
807:
803:
799:
795:
791:
787:
776:
774:
770:
759:
757:
750:
748:
743:
742:
741:
739:
735:
721:
717:
714:
712:
711:
708:
705:
699:
696:
691:
689:
685:
681:
680:
664:
660:
656:
653:
647:
646:
644:
643:
636:
629:
627:
618:
617:
613:
607:
606:
601:
595:
591:
585:
583:
578:
575:
572:
568:
564:
557:
555:
550:
545:
541:
535:
531:
526:
522:
517:
512:
508:
507:global blocks
504:
503:active blocks
500:
495:
490:
486:
484:
483:administrator
463:
459:
455:
451:
450:
449:
444:
439:
435:
434:
431:
427:
423:
418:
414:
413:
412:
411:
410:
409:
406:
402:
396:
390:
389:
388:
376:
372:
371:
368:
364:
360:
355:
353:
349:
345:
341:
336:
335:
333:
332:
325:
318:
316:
307:
306:
303:
297:
295:
290:
287:
280:
278:
273:
268:
264:
258:
254:
249:
245:
240:
235:
231:
230:global blocks
227:
226:active blocks
223:
218:
213:
209:
207:
206:administrator
193:
192:
185:
178:
176:
167:
166:
162:
156:
150:
149:
148:
137:
133:
127:
125:
120:
115:
113:
108:
103:
99:
93:
89:
84:
80:
75:
70:
66:
65:global blocks
62:
61:active blocks
58:
53:
48:
44:
42:
41:administrator
29:
28:
24:
20:
1185:
1180:
1172:
1158:
1146:for deletion
1121:
1113:
1098:
1096:
1086:for deletion
1051:, but other
1040:
1032:edit summary
1023:
1016:
1008:
996:The article
995:
962:
954:
939:
937:
927:for deletion
892:, but other
881:
873:edit summary
864:
857:
848:
836:The article
835:
788:, but other
777:
769:edit summary
760:
753:
744:
732:The article
731:
700:
692:
677:
675:
665:for deletion
641:
623:
621:
603:
589:
587:
581:
580:
573:
566:
559:
553:
552:
525:creation log
492:
480:
416:
380:
379:
339:
330:
312:
310:
299:
293:
292:
285:
282:
276:
275:
248:creation log
215:
203:
190:
172:
170:
140:
139:
135:
129:
123:
122:
117:
111:
110:
83:creation log
50:
38:
15:
594:WP:ARBCOMM
521:filter log
244:filter log
79:filter log
1065:consensus
1000:has been
906:consensus
840:has been
802:consensus
736:has been
624:read the
540:checkuser
499:block log
494:Inniverse
313:read the
263:checkuser
222:block log
217:Inniverse
173:read the
98:checkuser
57:block log
52:Inniverse
19:Inniverse
704:Claritas
651:Amalthea
605:BWilkins
511:contribs
438:Amatulić
400:contribs
359:Vianello
234:contribs
160:contribs
69:contribs
1169:deleted
1127:ZXCVBNM
1109:deleted
950:deleted
688:deleted
635:unblock
534:unblock
417:himself
383:Phantom
324:unblock
302:Spartaz
286:can not
257:unblock
184:unblock
143:Phantom
92:unblock
1034:or on
1011:WP:GNG
875:or on
851:WP:GNG
771:or on
747:WP:GNG
611:←track
628:first
599:talk→
386:Steve
317:first
177:first
146:Steve
1191:talk
1131:TALK
1073:talk
1069:Hack
970:talk
966:Hack
914:talk
910:Hack
810:talk
806:Hack
571:here
563:here
458:talk
443:talk
426:talk
394:talk
375:diff
363:Talk
348:talk
154:talk
130:The
23:talk
982:of
822:of
718:of
590:via
544:log
491:).
454:Kww
422:Kww
344:Kww
267:log
214:).
132:SPI
102:log
49:).
1193:)
1171:.
1111:.
1075:)
1038:.
1021:.
972:)
952:.
916:)
879:.
862:.
812:)
775:.
758:.
690:.
638:}}
632:{{
614:)
584::
556::
538:•
532:•
528:•
523:•
519:•
514:•
509:•
505:•
501:•
460:)
428:)
403:\
365:)
350:)
342:.—
327:}}
321:{{
296::
279::
261:•
255:•
251:•
246:•
242:•
237:•
232:•
228:•
224:•
187:}}
181:{{
163:\
126::
114::
96:•
90:•
86:•
81:•
77:•
72:•
67:•
63:•
59:•
25:)
1189:(
1133:)
1129:(
1071:(
968:(
912:(
808:(
707:§
548:)
546:)
542:(
497:(
456:(
445:)
441:(
424:(
397:|
391:/
361:(
346:(
271:)
269:)
265:(
220:(
157:|
151:/
106:)
104:)
100:(
55:(
21:(
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.