1057:(crossposted from ameliorate's talk page): I do think we need to think a little more about how to implement this though. For example, all those extra queued pages are not going to be much use for preparing updates ahead of time because there is nowhere to include the credits. I'm now thinking maybe we should just duplicate the "next update" page completely on each queue page and then just get the bot to select the hook section from the page. IMO things would be a lot more straightforward that way.
1255:
1277:
1137:
47:
1077:). The only alternative for credits is that we have a list on the main Next update page for each queue, but I think you are right that it would be better to maintain consistent formatting across the DYK pages. Also, the update would still have to be prepared on the unprotected Next update, it isn't fair to the non-admins who help with the next update occasionally otherwise.
1072:
My biggest fear there is that someone will change the formatting of the page for whatever reason, and if they don't know what they're doing it will cause problems (we get this now with the various helper bots that malfunction every time someone changes instructions to not a subst a template or alters
860:
still uses the old system and someone might try to re-synch them up or otherwise change the timestamp template. Thus, a note should be added indicating that changes to that template (and the counter / queues) could mess up the bot. Finally, it'd probably be a good idea to revise the instructions for
1030:
If it does post to AN the message will ask that it be removed from the board after the update is done. This is necessary as the bot will have to detect an HTML comment in the message to know if has already posted, otherwise it will make a new post every 5 minutes. So theoretically the posts will be
947:
I think a notice somewhat "early" is better than "late". So an hour or two to go before update due and there's still nothing in next update means at least there is time to get the pipeline filled... given the volume of suggestions the point here is to never miss an update even by an hour so the
627:
I'd suggest it start pinging people madly if we're getting close to update time and the queues are empty. Once this has been running for a while people will tend to rely on it (as with every other adminbot we have), so it needs to have something in place to counter that.
973:
Question: if this works, will there be thought given to how notification/credits might be automated too? tis' a bit trickier to do since there are a fair few permutations of nom/author/selfnom/conom/hook tweaker :)... etc... And archiving too, of course.
189:
The Did you know template is supposed to be swapped once every 6 hours, however due to a lack of administrators working in the area it is often late which results in a backlog of articles and expiring nominations. This is where this bot comes in.
323:. An admin would have to copy vandalism from the Next update to the queue for it to get onto the main template (and the chances of that happening are the same as the chances of it happening with the current process).
844:- Since the queue page which admins need to put hooks onto for the next update increases by one each time (until it hits '6' and resets to '1') I'd suggest putting links to the current 'next update queue' on
558:
What about adding the notification tag to the article talk page and the nominating and writing users' talk pages? Will/can the bot do that? I know anyone can, but the bot doing it would be easier.
493:
Yes, that seems to be how it works. A follow-up question would be, what happens if the queues are all out-of-date or empty? Would the bot add blank or uncomplete stuff to the Main Page in that case?
948:
maximum number of suggestions are achieved. Heck... I'd say if the pipeline (which is 6 units long) ever falls to less than 2 units ready to go some sort of notice somewhere might be in order... ++
225:
This allows for up to 5 batches of hooks to be set out and for the bot to update them without any further administrator action. The bot will only act on a batch in the queue if it is tagged with
861:
manual updates to include info on updating the counter so that if the bot is ever down / someone has to do a manual update it can be performed in a way that won't then throw the bot off. --
1325:
1155:
In addition, please add {{Sign3647}} to the edit summaries. @BAG members: Please remember to specify a template to use when you approve a trial for an adminbot! Per
575:
This bot won't be doing anything outside of admin operation, however I do have another unprivileged bot planned that will do various other DYK maintenance tasks.
21:
853:
214:
848:
and various other 'high visibility' spots so people can easily check what is 'on deck'. Similarly, a category could be transcluded through {{
889:
Any comments (from the botop or others...) on what it should do if the queue is empty close to update time? (wrt. comments a bit higher up)
525:
483:
87:
1210:
There's no "SQL query" requirement, just that the bot edits must be clearly marked. Putting "Bot edit" in the summary is sufficient. --
1097:
one hour before the update is due if the next queue isn't approved and works if the queue pages are replicas of the next update page.
1330:
912:
726:. I have the feeling that this is slowly going to turn into an rfa :-( It is very hard to read the real concerns inside the votes --
300:
282:
195:
82:
303:
doesn't affect what the bot copies, an administrator has to copy the hooks from that page to one of the fully protected queues;
414:
448:
Hopefully the implementation with the different queues will be a successful one. The rollout with instructions should be made
117:
243:
857:
856:
containing the timestamp as a single number, which is a fairly new change. It seems to have been accepted, but the similar
1190:
Bot policy says trialed adminbots are to be run with edits clearly marked as such, so it can be separated by a SQL query.
1141:
Approved for trial (14 days). Please provide a link to the relevant contributions and/or diffs when the trial is complete.
320:
316:
312:
308:
304:
1115:
102:
471:: An admin needs to update the queues, correct? So all this bot would do is update the main page at the correct time?
202:
1290:
337:
I should read more. ;) I don't see any issues, the noticeboards should be spammed and the code should be reviewed.
1007:
keep posting to AN whenever DYK was getting behind schedule. It was getting really annoying for a while. Posts on
983:
957:
879:
437:
521:
479:
1296:
1269:
1239:
1219:
1205:
1185:
1174:
1149:
1130:
1106:
1086:
1066:
1040:
1025:
986:
960:
942:
928:
898:
882:
865:
830:
808:
768:
748:
734:
714:
690:
658:
637:
622:
602:
584:
566:
544:
530:
504:
488:
463:
440:
420:
401:
384:
361:
343:
332:
294:
669:
764:
97:
1121:
Since the discussion has abated could this be approved for a trial? Unless there are outstanding concerns.
852:}} to display all pages which are currently marked to be auto-updated by the bot. Also, the bot relies on
380:
236:
218:
92:
862:
781:
if(!preg_match("/\{\{DYKbotdo\}\}/i",$ queue)) die("Hooks have not been approved by an administrator.");
706:
157:
77:
1156:
908:
607:
Nothing. If the queues are empty, the bot should not have {{DYKbotdo}} on it, so it would not update.
845:
397:
145:
777:
if(!preg_match("/{{DYKbotdo}}/i",$ queue)) die("Hooks have not been approved by an administrator.");
1062:
654:
514:
472:
1215:
1016:
683:
598:
564:
210:
If the template needs to be updated it copies the hooks from the queue page to the main template
849:
727:
376:
229:
17:
1263:
1124:
1100:
1080:
1034:
922:
824:
742:
699:
698:: Always thought this was the best way to do it. It reduces the burden of the DYK Admins --
578:
538:
355:
326:
130:
58:
1074:
938:
894:
633:
393:
1224:
It still makes it helpful... Is there any harm to it? It helps when reviewing the edits.
1094:
1008:
916:
1287:
1058:
1000:
650:
500:
459:
410:
1319:
1211:
1013:
999:
Please don't post to AN. The reason that obnoxious color-changing box transcluded on
979:
953:
875:
677:
594:
559:
433:
1232:
1198:
1180:
1167:
1144:
801:
615:
338:
289:
510:
1011:
aren't archived for 48 hours, such messages will be irrelevant after 20 minutes.
760:
513:, it only works if {{DYKbotdo}} is placed on the page. Is that still the case?
46:
934:
890:
629:
593:
What's it going to do if the queues are empty and an update is almost due? --
1284:
495:
454:
739:
While I am happy with the level of support this has got, I have to agree.
975:
949:
871:
429:
790:$ content = preg_replace("/\{\{DYKbotdo\}\}/i", "", "$ create_content");
1225:
1191:
1160:
919:
after the update is a certain period of time late, an hour? Two hours?
794:
608:
786:$ content = preg_replace("/{{DYKbotdo}}/i", "", "$ create_content");
271:. It will of course need further community discussion and approval.
201:
Once completed an administrator copies the hooks over to one of the
349:
933:
I think an AN post if there's an hour to go would be a good idea.
264:
and a run before it was suggested that multiple queues be used;
1304:
The above discussion is preserved as an archive of the debate.
246:) and has done three successful trial runs from my account;
1003:
and various other locations was created was so that people
649:- looks like a step forward. Certainly worth a try anyway.
375:- seems like a good use of limited admin bot functions. --
235:. The queue that the bot will utilise next is dictated by
666:- finally, something to help you poor DYK admins... :) —
207:
The bot checks once every 5 minutes if the update is due
269:
267:
265:
262:
260:
258:
256:
253:
251:
249:
247:
112:
107:
72:
171:
Run on a 5 minute crontab, 4 edits once every 6 hours
239:
which the bot increases by one as it updates itself.
1310:
Subsequent comments should be made in a new section.
773:
Regarding the code, here are some problems I found:
42:
Subsequent comments should be made in a new section.
1326:Approved Knowledge (XXG) bot requests for approval
870:Those seem good things to note/do/watch out for ++
428:... DYK has wanted a bot to help since... 2006! ++
242:This has been accepted by those involved in DYK (
36:The following discussion is an archived debate.
8:
724:This is not a vote. It is a discussion
288:Should at least be semi-protected, no?
854:Template:Did you know/Next update/Time
215:Template:Did you know/Next update/Time
166:(e.g. Continuous, daily, one time run)
858:Template:In the news/Next update/Time
7:
907:I changed my test copy to post to
392:, looks a good application to me.
28:
913:Template:Did you know/Next update
301:Template:Did you know/Next update
213:It then clears the queue, resets
196:Template:Did you know/Next update
44:The result of the discussion was
1275:
1253:
1135:
915:. Perhaps it could also post to
194:Any user fills or helps to fill
45:
139:Automatic or Manually Assisted:
1073:the formatting of a page like
1:
1297:11:41, 25 November 2008 (UTC)
1270:14:50, 22 November 2008 (UTC)
321:Template:Did you know/Queue/5
317:Template:Did you know/Queue/4
313:Template:Did you know/Queue/3
309:Template:Did you know/Queue/2
305:Template:Did you know/Queue/1
1331:Knowledge (XXG) Did you know
1240:23:15, 8 November 2008 (UTC)
1220:23:12, 8 November 2008 (UTC)
1206:15:36, 8 November 2008 (UTC)
1186:06:54, 8 November 2008 (UTC)
1175:04:28, 8 November 2008 (UTC)
1150:03:21, 8 November 2008 (UTC)
1131:14:26, 7 November 2008 (UTC)
1107:16:29, 1 November 2008 (UTC)
1087:05:54, 1 November 2008 (UTC)
1067:09:56, 31 October 2008 (UTC)
1041:04:38, 1 November 2008 (UTC)
1026:04:12, 1 November 2008 (UTC)
987:03:41, 30 October 2008 (UTC)
961:03:41, 30 October 2008 (UTC)
943:06:40, 29 October 2008 (UTC)
929:00:41, 29 October 2008 (UTC)
899:22:44, 28 October 2008 (UTC)
883:03:41, 30 October 2008 (UTC)
866:18:18, 28 October 2008 (UTC)
831:12:55, 28 October 2008 (UTC)
809:12:20, 28 October 2008 (UTC)
769:12:05, 28 October 2008 (UTC)
749:10:12, 28 October 2008 (UTC)
735:08:29, 28 October 2008 (UTC)
715:05:34, 28 October 2008 (UTC)
691:05:11, 28 October 2008 (UTC)
659:02:53, 28 October 2008 (UTC)
638:05:18, 28 October 2008 (UTC)
623:00:17, 28 October 2008 (UTC)
603:20:48, 27 October 2008 (UTC)
585:02:42, 28 October 2008 (UTC)
567:20:47, 27 October 2008 (UTC)
545:02:42, 28 October 2008 (UTC)
531:20:38, 27 October 2008 (UTC)
505:20:22, 27 October 2008 (UTC)
489:20:18, 27 October 2008 (UTC)
464:20:10, 27 October 2008 (UTC)
441:19:14, 27 October 2008 (UTC)
421:18:50, 27 October 2008 (UTC)
402:18:27, 27 October 2008 (UTC)
385:18:01, 27 October 2008 (UTC)
362:12:48, 27 October 2008 (UTC)
344:12:31, 27 October 2008 (UTC)
333:12:12, 27 October 2008 (UTC)
295:12:06, 27 October 2008 (UTC)
1143:To be run on your account.
452:simple/easy to understand.
1347:
1031:removed after 20 minutes.
150:PHP using ClueBot classes
1307:Please do not modify it.
1159:, this must be done so!
1157:Knowledge (XXG):ADMINBOT
909:Knowledge (XXG) talk:DYK
535:This is still the case.
283:Did you know/Next update
39:Please do not modify it.
759:Seems fine. No issues.
156:Automatically updating
237:User:DYKadminBot/count
175:Already has a bot flag
1093:The bot now posts to
779:should be changed to
158:Template:Did you know
22:Requests for approval
911:and leave a note on
846:Template:DYK-Refresh
348:Source is available
146:Programming Language
18:Knowledge (XXG):Bots
1116:BAGAssistanceNeeded
1075:Knowledge (XXG):CHU
217:and increments the
1283:+admin approved --
1095:Knowledge (XXG):AN
1009:Knowledge (XXG):AN
917:Knowledge (XXG):AN
1295:
1236:
1202:
1184:
1171:
1148:
805:
619:
419:
342:
293:
187:Function Details:
154:Function Summary:
1338:
1309:
1293:
1279:
1278:
1268:
1266:
1265:User:Ameliorate!
1257:
1256:
1237:
1234:
1230:
1203:
1200:
1196:
1183:
1172:
1169:
1165:
1147:
1139:
1138:
1129:
1127:
1126:User:Ameliorate!
1120:
1114:
1105:
1103:
1102:User:Ameliorate!
1085:
1083:
1082:User:Ameliorate!
1039:
1037:
1036:User:Ameliorate!
1024:
927:
925:
924:User:Ameliorate!
829:
827:
826:User:Ameliorate!
806:
803:
799:
747:
745:
744:User:Ameliorate!
731:
689:
680:
675:
620:
617:
613:
583:
581:
580:User:Ameliorate!
562:
543:
541:
540:User:Ameliorate!
517:
475:
413:
409:Great solution.
373:support this bot
360:
358:
357:User:Ameliorate!
341:
331:
329:
328:User:Ameliorate!
292:
287:
281:
234:
228:
135:
133:
132:User:Ameliorate!
49:
41:
1346:
1345:
1341:
1340:
1339:
1337:
1336:
1335:
1316:
1315:
1314:
1305:
1276:
1264:
1261:
1259:Trial complete.
1254:
1235:clamation point
1233:
1226:
1201:clamation point
1199:
1192:
1170:clamation point
1168:
1161:
1136:
1125:
1122:
1118:
1112:
1101:
1098:
1081:
1078:
1035:
1032:
1012:
923:
920:
825:
822:
821:Fixed. Thanks,
804:clamation point
802:
795:
791:
787:
782:
778:
743:
740:
729:
686:
678:
670:
667:
618:clamation point
616:
609:
579:
576:
560:
539:
536:
528:
515:
486:
473:
356:
353:
327:
324:
285:
279:
277:
244:discussion here
232:
226:
131:
128:
123:
62:
37:
26:
25:
24:
12:
11:
5:
1344:
1342:
1334:
1333:
1328:
1318:
1317:
1313:
1312:
1300:
1299:
1251:
1250:
1249:
1248:
1247:
1246:
1245:
1244:
1243:
1242:
1110:
1109:
1090:
1089:
1052:
1051:
1050:
1049:
1048:
1047:
1046:
1045:
1044:
1043:
1001:Talk:Main Page
990:
989:
970:
969:
968:
967:
966:
965:
964:
963:
902:
901:
887:
886:
885:
838:
837:
836:
835:
834:
833:
814:
813:
812:
811:
792:
789:
785:
783:
780:
776:
771:
756:
755:
754:
753:
752:
751:
718:
717:
710:
703:
693:
684:
661:
644:
643:
642:
641:
640:
590:
589:
588:
587:
570:
569:
553:
552:
551:
550:
549:
548:
547:
526:
516:NuclearWarfare
484:
474:NuclearWarfare
466:
443:
423:
416:Ici pour humor
404:
387:
369:
368:
367:
366:
365:
364:
276:
273:
223:
222:
211:
208:
205:
199:
163:Edit period(s)
122:
121:
115:
110:
105:
100:
95:
90:
85:
80:
75:
73:Approved BRFAs
70:
63:
61:
56:
55:
54:
32:
30:
27:
15:
14:
13:
10:
9:
6:
4:
3:
2:
1343:
1332:
1329:
1327:
1324:
1323:
1321:
1311:
1308:
1302:
1301:
1298:
1292:
1289:
1286:
1282:
1274:
1273:
1272:
1271:
1267:
1260:
1241:
1238:
1231:
1229:
1223:
1222:
1221:
1217:
1213:
1209:
1208:
1207:
1204:
1197:
1195:
1189:
1188:
1187:
1182:
1178:
1177:
1176:
1173:
1166:
1164:
1158:
1154:
1153:
1152:
1151:
1146:
1142:
1133:
1132:
1128:
1117:
1108:
1104:
1096:
1092:
1091:
1088:
1084:
1076:
1071:
1070:
1069:
1068:
1064:
1060:
1056:
1042:
1038:
1029:
1028:
1027:
1023:
1022:
1020:
1015:
1010:
1006:
1002:
998:
997:
996:
995:
994:
993:
992:
991:
988:
985:
981:
977:
972:
971:
962:
959:
955:
951:
946:
945:
944:
940:
936:
932:
931:
930:
926:
918:
914:
910:
906:
905:
904:
903:
900:
896:
892:
888:
884:
881:
877:
873:
869:
868:
867:
864:
859:
855:
851:
847:
843:
840:
839:
832:
828:
820:
819:
818:
817:
816:
815:
810:
807:
800:
798:
793:
784:
775:
774:
772:
770:
766:
762:
758:
757:
750:
746:
738:
737:
736:
733:
732:
725:
722:
721:
720:
719:
716:
712:
711:
708:
705:
704:
701:
697:
694:
692:
688:
687:
681:
679:for President
676:
674:
665:
662:
660:
656:
652:
648:
645:
639:
635:
631:
626:
625:
624:
621:
614:
612:
606:
605:
604:
600:
596:
592:
591:
586:
582:
574:
573:
572:
571:
568:
565:
563:
557:
554:
546:
542:
534:
533:
532:
529:
524:
523:
522:
518:
512:
509:According to
508:
507:
506:
502:
498:
497:
492:
491:
490:
487:
482:
481:
480:
476:
470:
467:
465:
461:
457:
456:
451:
447:
444:
442:
439:
435:
431:
427:
424:
422:
418:
417:
412:
408:
405:
403:
399:
395:
391:
388:
386:
382:
378:
374:
371:
370:
363:
359:
351:
347:
346:
345:
340:
336:
335:
334:
330:
322:
318:
314:
310:
306:
302:
299:
298:
297:
296:
291:
284:
274:
272:
270:
268:
266:
263:
261:
259:
257:
254:
252:
250:
248:
245:
240:
238:
231:
220:
216:
212:
209:
206:
204:
200:
197:
193:
192:
191:
188:
184:
182:
179:
176:
172:
170:
167:
164:
160:
159:
155:
151:
149:
147:
142:
140:
136:
134:
127:
119:
116:
114:
111:
109:
106:
104:
101:
99:
96:
94:
91:
89:
86:
84:
81:
79:
76:
74:
71:
69:
65:
64:
60:
57:
52:
48:
43:
40:
34:
33:
31:
23:
19:
1306:
1303:
1280:
1258:
1252:
1227:
1193:
1162:
1140:
1134:
1111:
1054:
1053:
1018:
1017:
1004:
841:
796:
728:
723:
707:
700:
695:
682:
672:
663:
646:
610:
555:
520:
519:
494:
478:
477:
468:
453:
449:
445:
425:
415:
406:
389:
377:Rocksanddirt
372:
278:
241:
224:
186:
185:
180:
177:
174:
173:
168:
165:
162:
161:
153:
152:
144:
143:
138:
137:
125:
124:
67:
50:
38:
35:
29:
685:Vote for Ed
394:Tim Vickers
59:DYKadminBot
1320:Categories
1179:Um, what?
275:Discussion
198:with hooks
141:Automatic
113:rights log
103:page moves
1281:Approved.
1059:Gatoclass
651:Gatoclass
411:Elucidate
126:Operator:
108:block log
1212:Carnildo
1055:Comment:
1005:wouldn't
850:DYKbotdo
842:Comments
709:Cherian
595:Carnildo
561:Reywas92
446:Support.
230:DYKbotdo
83:contribs
51:Approved
20: |
696:Support
664:Support
647:Support
556:Comment
527:My work
485:My work
469:Comment
426:support
407:Support
390:Support
219:counter
1294:(st47)
761:Stifle
221:by one
203:queues
1288:ʎʇɹoɟ
1285:uǝʌǝs
935:Giggy
891:Giggy
730:Chris
630:Giggy
178:(Y/N)
88:count
16:<
1216:talk
1063:talk
939:talk
895:talk
765:talk
702:Tinu
655:talk
634:talk
599:talk
511:this
501:talk
496:Cirt
460:talk
455:Cirt
450:very
398:talk
381:talk
350:here
255:and
148:(s):
118:flag
98:logs
78:talk
68:BRFA
1021:man
1014:Mr.
976:Lar
950:Lar
872:Lar
863:CBD
788:to
668:Ed
430:Lar
93:SUL
1322::
1291:ʇs
1262:~
1218:)
1181:BJ
1145:BJ
1123:~
1119:}}
1113:{{
1099:~
1079:~
1065:)
1033:~
1019:Z-
978::
974:++
952::
941:)
921:~
897:)
874::
823:~
767:)
741:~
713:-
657:)
636:)
601:)
577:~
537:~
503:)
462:)
432::
400:)
383:)
354:~
352:.
339:BJ
325:~
319:,
315:,
311:,
307:,
290:BJ
286:}}
280:{{
233:}}
227:{{
183:N
129:~
1228:X
1214:(
1194:X
1163:X
1061:(
984:c
982:/
980:t
958:c
956:/
954:t
937:(
893:(
880:c
878:/
876:t
797:X
763:(
673:7
671:1
653:(
632:(
611:X
597:(
499:(
458:(
438:c
436:/
434:t
396:(
379:(
181::
169::
120:)
66:(
53:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
