777:, which indeed has not edited in over a year. This is an excellent scenario that I'm glad came up... What's different is that the bot (as opposed to mass message) will include the username in the message, that way you would know it was referring to your alt account and not your primary. The other issue that surfaced just now was that the message was sent users who were renamed but are still active. The logic to detect renames has not been implemented yet, but either way it wouldn't have been caught because there wasn't a previous run to compare to (see #3 above). I have manually gone through and rollbacked the other 7 improperly sent messages. Apologies for the noise :)
957:
855:). E.g. I can add one of my test accounts, then rename it (which I'm able to do), and see if the bot correctly updates the test CheckPage. Similarly I could put the users in the wrong order, add extra whitespace, duplicates, add myself (an admin) and see if the correct adjustments are made. I think this is the only feasible way to run a trial as edits to the actual CheckPage will be infrequent, and I can't assure all scenarios will be covered within a reasonable amount of time
1079:
818:
48:
650:
686:
882:
Those I already sent out via mass message. On that note, I owe those folks 4 more days before removing them from the CheckPage (one week's notice). In the meantime I'll finish what little coding is left to handle renames, then next
Tuesday I'll do a full run in the userspace, and assuming all is well
454:
If the bot is approved, I think I'll first send out a mass message to all 580 inactive users that their access is about to be removed (see #6 above), and then have the bot do it's first run a week later. Moving forward, the bot will generally only be notifying a few users at most per run, and hence
846:
Thanks! I will re-run what I have very soon. This will make only 5 edits (userspace version of the CheckPage, 2 edits for the reports, and 2 for the counts). After that, the bot will update the counts every time someone is added to the CheckPage. I estimate that would involve 5-10 edits per month.
926:
of the CheckPage after a previous run. So just a few days went by, and 8 more users became "inactive"! Right now I'm struggling with some connection issues on my local machine. I might have to run the bot on Tool Labs for the trial. Hopefully I'll have the actual CheckPage updated today, and the
569:
Actually it looks like you can't link directly to a bot's grants page. I've poked some people on IRC about this. I guess take my word for it? :)Also wanted to say I'll be on holiday this Friday through next
Tuesday (8 November). If I don't write back here during that time that is why. Best
1059:
There were some points where I messed up the bot's local cache during testing, which resulted in an inaccurate report. All of that has been sorted out, and I'm happy to do more example tests using a smaller pool of users so that evaluating the bot's actions is easier, should the above be
1040:
For renaming users, I chose not to do an actual rename and pollute the rename log (and have to undo a rename of my test account). Instead, following the logic in #6 of the function details, I've changed the "last run" datestamp (stored on the filesystem) to a time in the past, before
437:
Since this will require the bot have admin rights, I'm getting a head start by opening the BRFA while I finish implementing some functionality (specifically renamed users, #3 above). All other functionality should be good to go, see the edits on the test CheckPage:
553:. So the only admin-y thing it can do is edit protected pages. What's also really cool is we can restrict usage to the IP range of Tool Labs (which I think is just one single IP). I have not done this yet as I'm currently doing testing from my local machine
340:
The bot keeps track of users who were present on the CheckPage on the last run. It will only rename the account if it sees that one of the previous users has been renamed since the last run. This addresses the concern of where an account is
993:
to the report and the bot's cache, so that they can be properly notified (see above, the original mass message sent out did not indicate it was the user's alternate account). Again I synced the actual CheckPage with these changes
729:
A one-time or once a year run will indeed do a lot of cleanup with a single edit, but the hope is to fully automate the process. Things like renamed users are more time-sensitive, and there's little concern of
362:
The reason for removing inactive users is purely to keep the CheckPage tidy. It has grown to be quite large and hard to manage, so we want to remove users who evidently are no longer using the software.
608:
Thank you! I have modified the estimate, though it honestly is a complete guess. The first go around I'm going to personally mass message all 580 inactive users, then run the bot a week later
183:
672:
Go ahead and send out your MassMessage - as that is really not a function of the bot - but may reveal if there are unknown community issues. Please link to this BRFA in your MassMessage. —
246:
906:
How is this going? I looked over the bot's edits, and they seemed odd to say the least. There's obviously more than 8 editors who are inactive on the CheckPage. Am I missing soemthing? ~
847:
Updating the CheckPage itself is the only complicated task, and the only one requiring the admin bit. Cleanup there would only happen maybe a few times per month at most (see
745:
510:
1006:). The bot's local cache has been updated, so when it is ran a week from now, any of those alt accounts that still have not edited would be removed from the CheckPage.
538:- do you plan on using OAUTH, BotPasswords or the legacy authentication system? If OAUTH or BotPasswords - please link to your consumer/botpasswords configuration. —
619:
581:
495:
1091:
938:
917:
894:
877:
866:
708:
564:
505:
805:
788:
1124:
500:
828:
in userspace, and run the job. After running, if you are comfortable with the results use your exiting admin account to sync this in to the check page. —
377:. This is purely for routine maintenance and is not indicative of wrongdoing on your part. You may regain access at any time by simply requesting it at
752:
The message is a worded a little oddly given that it appears to have been sent to users whom are not inactive. :D Otherwise, carry on with the task. --
407:
The same processing will be done on the bot section of the CheckPage, but currently there is not consensus to remove inactive bots. Instead the same
734:, so I think a higher frequency is desirable. ListManBot, who did all of the same tasks except removing inactive/blocked users, ran once a week
724:
485:
468:
250:
1071:
603:
523:
490:
242:
834:
678:
662:
544:
1060:
insufficient. I can however say with confidence that the bot is stable and in my opinion ready for production. Thank you for your time!
641:
319:
1014:
986:
The bot was ran again, this time looking at inactive users (this was done as a separate edit so that the trail is easier to evaluate):
594:, just a little note but shouldnt the "Estimated number of pages affected:" include user talk pages for your one week removal notices?
1033:
990:
1003:
On the next run, no changes to the CheckPage were made, only the notifications of inactivity were sent out to the alt accounts (e.g.
761:
995:
975:
73:
1027:
987:
982:
731:
441:
439:
1056:. If we'd like to do a real rename test, we can, but hopefully this diff asserts the bot is capable of properly handling renames.
1054:
1024:
978:
972:
448:
388:
883:
I'll manually sync with the actual CheckPage. From there I'll run the userspace tests described above, and report back here :)
848:
444:
415:
408:
851:
to the CheckPage). 1,000 edits will take many years :)Instead I recommend emulating all the scenarios in the bot's userspace (
852:
822:
Approved for trial (1000 edits). Please provide a link to the relevant contributions and/or diffs when the trial is complete.
419:
423:
21:
694:
153:
88:
374:
233:
1010:
431:
141:
83:
923:
550:
322:). The only new functionality is to automatically revoke inactive and blocked users. The specifics are as follows:
998:
1004:
264:
1 (CheckPage), 4 in the bot's userspace, and maybe 0-2 user talk pages per run (see #6 in the function details)
118:
224:
165:
103:
147:
93:
974:. This edit also illustrates how it sorted the list. I have synced these changes to the actual CheckPage
476:
373:
may be revoked. If you do not resume editing within the next week your username will be removed from the
213:
359:
Inactive is defined as one year of no editing activity (not any logged action, since AWB is for editing)
964:
177:
113:
720:
370:
171:
108:
871:
That is fine, I left the edit count high in case you wanted to send out the editor notifications. —
529:
402:
will comment if they are on the auto-revoked page, indicating to admins it may be a speedy approval
971:
First, the bot was ran to remove admins and indefinitely blocked users (blocked over a year ago):
159:
98:
332:
The prose within the CheckPage will remain untouched (text above and/or below the list of users)
1032:
Handling whitespace, sorting, duplicates, and respecting text before/after the list of users
963:
This was done in several steps, I will try to carefully explain. All tests were done against
715:
This sounds a reasonable thing to do. Even just one run, or once per year should declutter.
599:
135:
78:
716:
208:
247:
Knowledge:Bureaucrats'_noticeboard/Archive_21#Request_for_bureaucrats_promoting_candidates
8:
1106:
411:
will be generated for bots as if they had been removed, again serving only as a reference
58:
40:
773:
Sorry about that! The mass message system followed a redirect of your alternate account
395:
378:
927:
other aspects of the trial (testing that renames are properly done) will soon follow
631:
369:
Hello ! This message is to inform you that due to editing inactivity, your access to
1064:
931:
901:
887:
859:
825:
781:
738:
701:
669:
627:
612:
595:
591:
574:
557:
535:
461:
365:
One week prior to revoking the bot will issue a talk page notice with the content:
130:
59:
511:
Wikipedia_talk:Requests_for_adminship#New_adminbot_request_-_AWB_access_management
443:(editing of the bot section has since been disabled). The reports can be found at
774:
342:
309:
387:
If they do not resume editing they will removed from the CheckPage and added to
1019:
Some more examples, using a smaller example list of users for easier analysis:
801:
757:
626:
Came here because of noticeboard announcements. Looks like a useful task; the
496:
Knowledge:Village_pump_(proposals)#New_adminbot_request_-_AWB_access_management
17:
1118:
1086:
907:
872:
841:
829:
673:
657:
539:
518:
399:
268:
630:
is an experienced and trusted user. Don't see any problems going forward. -
501:
Wikipedia_talk:AutoWikiBrowser#New_adminbot_request_-_AWB_access_management
506:
Wikipedia_talk:Requests_for_permissions#Proposal_for_automatic_revocation
219:
797:
768:
753:
1099:
The above discussion is preserved as an archive of the debate.
350:
Remove admins from the list since they automatically have access
1023:
Removing admins, indefinitely blocked users and inactive users
353:
Remove users who have been indefinitely blocked for over a year
1105:
To request review of this BRFA, please start a new section at
649:
39:
To request review of this BRFA, please start a new section at
1009:
For bots, editing of the CheckPage has been disabled in the
329:
Make all formatting consistent (whitespace, newlines, etc)
195:
314:
654:
On hold until 09NOV2016 to allow for community comments
549:
Currently using BotPasswords. The grants are listed at
491:
Knowledge:Bot_owners'_noticeboard#New_adminbot_request
243:
Special:Permalink/747216495#New bot task for AWB pages
1049:
1043:
414:
The counts of users/bots with access are written to
345:'d and the new account should not have access to AWB
240:Links to relevant discussions (where appropriate):
1116:
33:The following discussion is an archived debate.
486:Knowledge:Bots/Requests for approval/Adminbots
326:Alphabetize the list and remove any duplicates
824:. For trial, please make a complete copy of
251:Knowledge:Bots/Requests_for_approval/AWBCPBot
1125:Approved Knowledge bot requests for approval
391:, which will serve as a reference for admins
236:and counts the number of users with access
394:When new requests for access are made at
796:. I will go make an edit over there. --
449:User:MusikBot II/AWBListMan/Report/User
389:User:MusikBot II/AWBListMan/Report/User
14:
1117:
1053:. After running the bot again we have
445:User:MusikBot II/AWBListMan/Report/Bot
416:User:MusikBot II/AWBListMan/User count
853:User:MusikBot II/AWBListMan/CheckPage
430:Functionality can also be tweaked at
420:User:MusikBot II/AWBListMan/Bot count
424:Knowledge:AutoWikiBrowser/User count
337:Update to reflect any user renames
308:Most functionality takes over what
262:Estimated number of pages affected:
27:
432:User:MusikBot II/AWBListMan/config
194:03:47, Tuesday, November 1, 2016 (
28:
1136:
1013:, so only a report was generated
455:mass message will not be needed.
202:Automatic, Supervised, or Manual:
45:The result of the discussion was
1077:
955:
816:
684:
648:
551:Special:BotPasswords/MusikBot II
422:. This will be transcluded in {{
46:
977:. Then the edit to update the
481:Community notifications sent:
13:
1:
1072:20:58, 25 November 2016 (UTC)
939:19:30, 16 November 2016 (UTC)
918:11:43, 16 November 2016 (UTC)
895:23:37, 11 November 2016 (UTC)
878:23:12, 11 November 2016 (UTC)
867:23:02, 11 November 2016 (UTC)
835:14:30, 11 November 2016 (UTC)
1092:01:36, 4 December 2016 (UTC)
806:00:09, 9 November 2016 (UTC)
789:00:02, 9 November 2016 (UTC)
762:23:43, 8 November 2016 (UTC)
746:00:03, 9 November 2016 (UTC)
725:00:44, 7 November 2016 (UTC)
709:23:38, 8 November 2016 (UTC)
693:Mass message has been sent (
679:02:01, 6 November 2016 (UTC)
663:02:15, 5 November 2016 (UTC)
642:01:49, 4 November 2016 (UTC)
620:20:18, 1 November 2016 (UTC)
604:19:51, 1 November 2016 (UTC)
582:00:08, 3 November 2016 (UTC)
565:18:10, 1 November 2016 (UTC)
545:14:02, 1 November 2016 (UTC)
524:04:20, 1 November 2016 (UTC)
469:20:18, 1 November 2016 (UTC)
7:
999:Special:PermaLink/751455529
991:restored alternate accounts
10:
1141:
1085:Will need +sysop, +bot. —
997:. And the updated report:
965:User:MusikBot II/CheckPage
732:impact on site performance
1102:Please do not modify it.
36:Please do not modify it.
922:It was going off of a
356:Remove inactive users
294:Already has a bot flag
1036:(no change to report)
22:Requests for approval
209:Programming language
269:Exclusion compliant
849:ListManBot's edits
230:Function overview:
915:
306:Function details:
1132:
1104:
1089:
1081:
1080:
1070:
1069:
1067:
1052:
1046:
959:
958:
937:
936:
934:
911:
905:
893:
892:
890:
875:
865:
864:
862:
845:
832:
820:
819:
787:
786:
784:
772:
744:
743:
741:
707:
706:
704:
692:
688:
687:
676:
660:
652:
639:
638:
635:
618:
617:
615:
580:
579:
577:
563:
562:
560:
542:
521:
467:
466:
464:
317:
188:
187:
50:
49:
38:
1140:
1139:
1135:
1134:
1133:
1131:
1130:
1129:
1115:
1114:
1113:
1100:
1087:
1078:
1065:
1063:
1061:
1048:
1047:was renamed to
1042:
961:Trial complete.
956:
932:
930:
928:
914:
899:
888:
886:
884:
873:
860:
858:
856:
839:
830:
817:
782:
780:
778:
766:
739:
737:
735:
717:Graeme Bartlett
702:
700:
698:
685:
683:
674:
658:
636:
633:
632:
613:
611:
609:
575:
573:
571:
558:
556:
554:
540:
532:
519:
479:
462:
460:
458:
371:AutoWikiBrowser
313:
310:User:ListManBot
256:Edit period(s):
133:
129:
124:
63:
47:
34:
26:
25:
24:
12:
11:
5:
1138:
1128:
1127:
1112:
1111:
1095:
1094:
1038:
1037:
1030:
1017:
1016:
1007:
1001:
984:
954:
952:
951:
950:
949:
948:
947:
946:
945:
944:
943:
942:
941:
912:
813:
812:
811:
810:
809:
808:
795:
750:
749:
748:
713:
712:
711:
666:
665:
645:
644:
624:
623:
622:
588:
587:
586:
585:
584:
531:
528:
527:
526:
514:
513:
508:
503:
498:
493:
488:
478:
475:
473:
428:
427:
412:
405:
404:
403:
392:
385:
384:
383:
363:
360:
354:
351:
348:
347:
346:
335:
334:
333:
327:
232:Maintains the
123:
122:
116:
111:
106:
101:
96:
91:
86:
81:
76:
74:Approved BRFAs
71:
64:
62:
57:
56:
55:
29:
18:Knowledge:Bots
15:
9:
6:
4:
3:
2:
1137:
1126:
1123:
1122:
1120:
1110:
1108:
1103:
1097:
1096:
1093:
1090:
1084:
1076:
1075:
1074:
1073:
1068:
1057:
1055:
1051:
1045:
1035:
1031:
1029:
1026:
1022:
1021:
1020:
1015:
1012:
1008:
1005:
1002:
1000:
996:
992:
988:
985:
983:
980:
976:
973:
970:
969:
968:
966:
962:
940:
935:
925:
921:
920:
919:
916:
910:
903:
898:
897:
896:
891:
881:
880:
879:
876:
870:
869:
868:
863:
854:
850:
843:
838:
837:
836:
833:
827:
823:
815:
814:
807:
803:
799:
793:
792:
791:
790:
785:
776:
770:
765:
764:
763:
759:
755:
751:
747:
742:
733:
728:
727:
726:
722:
718:
714:
710:
705:
696:
691:
682:
681:
680:
677:
671:
668:
667:
664:
661:
655:
651:
647:
646:
643:
640:
629:
625:
621:
616:
607:
606:
605:
601:
597:
593:
589:
583:
578:
568:
567:
566:
561:
552:
548:
547:
546:
543:
537:
534:
533:
525:
522:
516:
515:
512:
509:
507:
504:
502:
499:
497:
494:
492:
489:
487:
484:
483:
482:
477:Notifications
474:
471:
470:
465:
456:
452:
450:
446:
442:
440:
435:
433:
425:
421:
417:
413:
410:
406:
401:
397:
393:
390:
386:
382:
380:
376:
372:
367:
366:
364:
361:
358:
357:
355:
352:
349:
344:
339:
338:
336:
331:
330:
328:
325:
324:
323:
321:
316:
311:
307:
303:
301:
298:
295:
291:
289:
286:
283:
279:
277:
274:
271:
270:
265:
263:
259:
258:Twice weekly
257:
253:
252:
248:
244:
241:
237:
235:
234:AWB CheckPage
231:
227:
226:
223:
221:
216:
215:
212:
210:
205:
203:
199:
197:
193:
189:
185:
182:
179:
176:
173:
170:
167:
164:
161:
158:
155:
152:
149:
146:
143:
140:
137:
132:
128:
120:
117:
115:
112:
110:
107:
105:
102:
100:
97:
95:
92:
90:
87:
85:
82:
80:
77:
75:
72:
70:
66:
65:
61:
53:
44:
42:
37:
31:
30:
23:
19:
1101:
1098:
1082:
1058:
1039:
1018:
960:
953:
908:
821:
689:
653:
480:
472:
457:
453:
436:
429:
368:
315:bot operator
305:
304:
299:
296:
293:
292:
287:
284:
281:
280:
275:
272:
267:
266:
261:
260:
255:
254:
239:
238:
229:
228:
218:
217:
207:
206:
201:
200:
191:
190:
180:
174:
168:
162:
156:
150:
144:
138:
126:
125:
68:
51:
35:
32:
1066:MusikAnimal
933:MusikAnimal
902:MusikAnimal
889:MusikAnimal
861:MusikAnimal
783:MusikAnimal
740:MusikAnimal
703:MusikAnimal
670:MusikAnimal
614:MusikAnimal
596:KylieTastic
592:MusikAnimal
576:MusikAnimal
559:MusikAnimal
536:MusikAnimal
463:MusikAnimal
396:WP:PERM/AWB
379:WP:PERM/AWB
220:Source code
192:Time filed:
131:MusikAnimal
60:MusikBot II
775:IznoRepeat
530:Discussion
222:available:
204:Automatic
184:ANI search
178:rights log
166:page moves
154:edit count
114:rights log
104:page moves
1083:Approved.
1034:CheckPage
1025:CheckPage
989:. Here I
826:WP:AWB/CP
375:CheckPage
172:block log
127:Operator:
109:block log
1119:Category
1088:xaosflux
874:xaosflux
842:Xaosflux
831:xaosflux
675:xaosflux
659:xaosflux
541:xaosflux
520:xaosflux
400:MusikBot
343:WP:USURP
297:(Yes/No)
285:(Yes/No)
282:Adminbot
273:(Yes/No)
142:contribs
84:contribs
52:Approved
20: |
1107:WT:BRFA
924:version
695:example
41:WT:BRFA
1050:Ks0alt
1044:Ks5stm
1028:Report
1011:config
979:report
637:ASTILY
409:report
225:GitHub
628:BotOp
320:aware
312:did (
290:Yes
89:count
16:<
802:talk
798:Izno
769:Izno
758:talk
754:Izno
721:talk
690:Done
656:. —
600:talk
447:and
418:and
214:Ruby
211:(s):
160:logs
136:talk
119:flag
99:logs
79:talk
69:BRFA
909:Rob
590:Hi
318:is
302:No
278:No
196:UTC
148:SUL
94:SUL
1121::
1062:—
981::
967::
929:—
913:13
885:—
857:—
804:)
794:Ah
779:—
760:)
736:—
723:)
699:—
697:)
610:—
602:)
572:—
555:—
517:—
459:—
451:.
434:.
426:}}
398:,
249:,
245:,
198:)
1109:.
904::
900:@
844::
840:@
800:(
771::
767:@
756:(
719:(
634:F
598:(
381:.
300::
288::
276::
186:)
181:·
175:·
169:·
163:·
157:·
151:·
145:·
139:·
134:(
121:)
67:(
54:.
43:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.