31:
1339:
922:
444:
278:
317:
191:
354:– I started working on adding a new function to the bot's framework yesterday, and that function had a syntax error (a missing ".") and then I wasn't paying attention because I hadn't yet coded anything to actually call the function. Sorry about that, and thanks for the heads-up. I've been multi-tasking and working reducing on another backlog so far this morning. Need my coffee to kick in before I get back to coding. –
348:
1253:, notices on article pages are intended to be temporary, only posted while the RM is still open. In contrast, the talk page notices are intended to last forever, or until archived, as a permanent record of historical move requests. Yes, ideally the bot would be smart enough to distinguish between legitimate requests and vandalism, and would revert
1161:
your first edit? The bot would not have edit-warred with you if you had. I guess I need to either bite the bullet and implement code to detect reverts of bot edits, or just pull the plug on notices and just stop posting them altogether. I'm guessing it could take me a couple days or more to implement
597:
would have stopped the bot's edit-warring here. Not sure about how well the bot may handle future requests to move CSS pages, but I'm dropping this from my to-do list and will deal with any new CSS page-move issues as they may happen in the future. Really, these moves are borderline out-of-scope for
168:
specifying a timestamp with a sufficient window to detect the same previous edit that was subsequently reverted will enable the framework to stop apps from edit warring. Not sure what the default timestamp should be (1 day, 1 week?) but the RM app could specify the timestamp of the edit that started
95:
Please could you update the code of your bot so it will add the RM banner just once to each page, for a particular move discussion. Then if it is removed by a human editor, the bot will not edit war. I think this may be the simplest way to avoid many of the problems documented on this page. — Martin
114:
Checking the edit history of pages to see if the bot has previously been reverted is something that could be done, though coding for that isn't a quick 'n easy task. I view this as checking for symptoms. For example you could watch for fuel leaks on the launchpad (symptom) and abort the launch upon
1188:
suggested an edit filter to disallow certain strings commonly used in those mass move vandal requests & regularly affected articles, since that filter was active the vandal appeared to stop doing that until yesterday. If that filter can be modified, that would help stop the bot making loads of
1113:
passed before the revert. I could make the bot wait a full hour before posting these notices, but then I might see people asking me here why the bot is so slow in posting notices. I suppose it's a trade-off. Or maybe increase the delay time for multi-moves with more than a small number of pages
978:
Hi, a vandal has returned to make a vandal mass-move request earlier today on a random talk page. The bot posts on every talk page alerting watchers that they should participate in the original talk page of where the mass move request takes place. After someone removed the mass move request for
973:
115:
detection, but you'll still want to find and fix the source of the leak before restarting the countdown. If this was life and death task I would surely do that, but resources are stretched thin around here, so just keeping this on the back burner for now. –
423:
and making several fixes to address them, my v 7.33 fix of 9 June 2020 didn't address all the remaining scenarios. Also still open is implementing a more robust backup to catch unaddressed issues by making the bot stop
416:
251:
Only then call a new function to get an array of previous editors and edit times (no need to get previous content, I don't think) and check whether the bot was a recent editor, especially with multiple recent
1304:
1299:
629:
each have hundreds of deleted edits (I buried them to remove the clutter in the page histories) dating from 11:06, 16-Oct-2020. This problem persisted for over three days before I was notified here.
412:
1320:
I might could write a bot that patrolled for these by monitoring recent changes in talk namespaces, and parsing out edits ending with standard-format signatures. Would be an interesting project. –
859:
1000:
984:
1309:
497:
530:
Then since there's no notice on the pages; the bot assumes that the discussions have closed and thus removes the templates from the talk pages of the others in this multi-move request.
1315:
557:
added a check to catch requests to move CSS pages, and handle them in a similar way as requests to move Lua modules. I'm not sure whether there's anything more I need to do here. –
1190:
1358:
863:
761:
The bot's edit warring started after the 10:48, 16 October 2020 procedural close and persisted until my 21:00, 19 October 2020 edit, which was the second procedural close. –
1176:
My guess would have been that
Seasider53 is not familiar with the usual behaviour the vandal has been doing this and last year. I actually missed those replies linked from
899:
making changes to your RM after others have !voted, without everyone on board with your changes, is asking for trouble. This started out as a single-page move request, so
420:
1177:
1104:
1261:
a high priority, and I intend to implement that fix before I address the specific issue here any further than I already have by implementing the 20-minute delay. –
575:
indicates the issue continued after I posted my "working on it" message and the warring didn't stop until 4:39, 22 October 2020 which was 5 minutes after the RM at
332:
947:
676:
805:
781:
594:
465:
129:
1143:
I spent thirty minutes reverting them before realising how futile it was, since it will likely happen again. I think we need competent bot owners.
1090:
1072:
1047:
1022:
724:
683:
132:
has convinced me that I need to bump up the priority of this task; seems I'll never plug all the holes enabling the bot to edit-war as users will
1245:
884:
841:
1206:
1131:
987:
for example does not have to manually remove nonsense posted by a good bot themselves which, of course, only edits by it's programming. Thanks,
878:
1171:
1152:
983:
at 10:38 today (UTC). I know this sort of thing does not happen very often but I think that issue should be fixed so that users like me and
941:
915:
1288:
1270:
459:
437:
588:
145:
1233:
1162:
edit-reversion detection handling. The lack of experienced editor/administrator oversight of the RM process at times is frustrating. –
288:
with bot version 8.40. The bot is limited to a maximum of three recent edits to sync modified notices of move discussions on a page. –
124:
1329:
929:
509:
979:
vandalism, the bot removes the transcluded notice off the talk pages from the same group of pages but the text stays put. (Example:
654:
1107:
on other pages in May 2020. A couple of previous vandalism posts of this sort were each reverted after nine minutes. In this case,
285:
1225:
340:
576:
477:
974:
Bot is still not removing notices from multi-move request after someone removes the mass-move request on the original talk page.
963:
793:
607:
827:
815:
363:
405:
617:
672:
without closing the above single-page RM. It would be nice if I could "blacklist" this edit from being allowed to be saved.
514:
660:
483:
866:(initiated 19:07, 18 September 2021 (UTC)) to run normally. I also reverted your bot deny to allow RMCD bot to tidy up. --
1202:
1086:
1043:
996:
626:
493:
572:
566:
549:
1108:
271:
820:
Update: I added a Bot Deny template to the article and talk page. Feel free to remove it when the issue is resolved. –
770:
752:
297:
178:
305:
108:
90:
1279:
posting, obviously: sorry I'm a bit slow) that was probably the reason the bot left the notice in place. cheers,
156:
documents the API for getting the content of pages, including the page history (all revisions). The framework's
851:
622:
489:
328:
69:
64:
59:
799:
369:
214:
1236:, it leaves some behind. If it reverted the whole of its addition, there wouldn't be a problem. cheers,
244:
There's only a need to check for previous bot edits to a page AFTER it has decided it should POST, i.e.
385:
336:
38:
1198:
1082:
1039:
992:
540:
I've made some code changes to accommodate this usage, but still need to make more. Working on it. –
393:
534:
381:
1257:
the vandalism, but... Your struggle with my bot to revert the vandalism has convinced me to make
1158:
1119:
1013:
you've linked the wrong
Struway there, if it's the football-article editing one I'm thinking of.
900:
892:
888:
225:
389:
748:
741:
734:
727:
707:
701:
695:
689:
669:
650:
634:
554:
980:
468:
would have stopped the bot's edit-warring here, if the v 7.60 fix hadn't been implemented. –
533:
So, as with Lua modules, CSS pages are special cases that need special handling. Hmm, I see
1148:
1068:
1018:
401:
233:
I spent some more time thinking about how to do this. Most of the time after the bot gets (
84:
8:
874:
824:
812:
370:
359:
906:
someone had already voted in support of the single-page request is a definite NO-NO!! –
1284:
1241:
1194:
1078:
1054:
1035:
1008:
988:
860:
Talk:Illegal immigrant population of the United States#Requested move 28 September 2021
845:
210:
47:
17:
1316:
Knowledge:Village pump (proposals)/Archive 140#Edit filter to prevent
Signature faking
896:
396:. Is there anything that can be done to stop this, other than closing a discussion? –
183:
1354:
1325:
1266:
1167:
1127:
959:
937:
911:
789:
766:
643:
603:
584:
562:
545:
473:
455:
433:
411:
Belated reply. After becoming aware of this, I cleared out 202 junk bot edits to the
321:
293:
267:
195:
174:
141:
136:
find another way. This is my next significant task, as soon as I make time for it. –
120:
153:
504:
164:
which limits the server to providing only the latest revision. Replacing this with
1144:
1115:
1064:
1029:
1014:
855:
686:
reverting your own RM is OK if others haven't yet participated in the discussion
46:
If you wish to start a new discussion or revive an old one, please do so on the
1183:
867:
835:
821:
809:
103:
864:
Talk:Illegal immigration to the United States#Requested move 18 September 2021
262:
Now just need a solid, uninterrupted chunk of time to focus on coding this. –
1346:
1280:
1250:
1237:
854:) started two parallel discussions about the same proposed move, contrary to
638:
397:
307:
221:
206:
1157:
Oh. So sorry to see you wasted so much time doing that. Why didn't you make
1350:
1321:
1310:
Knowledge:Sockpuppet investigations/Mike
Matthews17/Archive#13 October 2021
1262:
1219:
1163:
1138:
1123:
955:
933:
907:
785:
762:
599:
580:
558:
541:
469:
451:
429:
419:. I'm frustrated that after putting a lot of work time into addressing the
377:
355:
289:
263:
170:
137:
116:
728:
reverted the bot on its
Knowledge:Requested moves/Current discussions page
653:
to "withdraw all these separate requests and renominate them in a single
501:
202:
1345:
by bot v 8.41 to stop edit warring in this scenario – the bot is now on
1338:
1232:
remove the whole of its addition, but on the associated talk page, e.g.
921:
755:
which supersedes this discussion and nobody else has participated here."
443:
277:
661:
Knowledge:Requested moves/Current discussions at 08:37, 16 October 2020
1180:
back in 2020, and there are good points explained there. Additionally
99:
1189:
invalid edits over a small period of time as well. See the relevant
520:
The bot cannot place notices on CSS pages; I see this error message:
730:(at 08:54, 16 October 2020) which is not necessary, but harmless...
862:(which was initiated at 03:32, 28 September 2021 (UTC)), and left
237:) a page it decides that it does not need to POST an update. So
1077:
Seems like that part of the confusion has been solved, I hope.
744:"Procedurally closed in favor of the multi-move request below."
1305:
30 relevant Iggy the Swan edits, 15:14–16:56, 13 October 2021
784:
fixes would have put an end to the Ba'ath Party edit war. –
663:
shows 16 open requested moves for Baath Party related titles
347:
1300:
56 relevant
Seasider53 edits, 10:12–10:35, 13 October 2021
858:
and one or two other guidelines. I've procedurally closed
496:, and the talk pages affected by my multi-move request at
690:
History of the Arab
Socialist Ba'ath Party – Syria Region
928:
by bot version 7.57 – this should have been caught and
751:"the RM from this page, since you opened a newer RM at
948:
Undocumented immigrant population of the United States
1224:
I think the issue is that on the article page, e.g.
1122:, then time to revert would have been 35 minutes. –
1105:
implemented a 20-minute delay before posting notices
804:
Hey, can you take a look at what the bot's doing at
677:§ Multiple requested move sections on the same page
932:and next time this scenario happens it will be. –
259:has made sure the bot is allowed to edit the page.
255:This new function will often be called just after
806:Illegal immigrant population of the United States
753:Talk:Ba'ath Party#Requested move 16 October 2020
327:Sorry, but I don't think it works any more, see
808:? Looks like it's stuck in some sort of loop. –
1059:I now see you filtered the contributions; it
950:page history) would have been stopped by the
417:Talk:George Papadopoulos (junk bot edit dump)
526:Invalid selector list at line 2 character 1.
524:Invalid selector list at line 1 character 1.
1275:Thanks for the explanation. I did realise (
954:, before bot version 7.57 was installed. –
901:THIS EDIT that converted it to a multi-move
201:RMCD bot is having some kind of episode at
537:– I need to familiarize myself with that.
388:. This has led to RMCD bot, well.... see
1034:- which article are you're thinking of?
413:George Papadopoulos (junk bot edit dump)
981:as seen on the bottom of this talk page
577:User talk:SDZeroBot/G13 soon/styles.css
14:
220:Thanks. Users always ignore rules per
44:Do not edit the contents of this page.
384:and another that affects the page at
25:
23:
946:The edit-warring (now seen in the
627:Talk:Ba'ath Party (disambiguation)
494:Talk:Ba'ath Party (disambiguation)
24:
1369:
1258:
951:
777:
498:Template talk:G13 soon/styles.css
425:
241:just the latest revision is fine.
1337:
920:
442:
346:
315:
276:
189:
29:
733:...but you missed a couple, so
286:"Twin Towers friendly-fire war"
930:flagged as a malformed request
889:removed it from the multi-move
879:21:58, 29 September 2021 (UTC)
828:12:50, 29 September 2021 (UTC)
816:12:09, 29 September 2021 (UTC)
500:. Not sure what's causing it.
415:and 198 junk bot edits to the
406:15:58, 23 September 2020 (UTC)
329:Special:Contributions/RMCD_bot
13:
1:
1359:23:11, 18 February 2024 (UTC)
1330:23:11, 18 February 2024 (UTC)
964:00:07, 20 February 2024 (UTC)
794:23:54, 19 February 2024 (UTC)
623:Ba'ath Party (disambiguation)
608:23:43, 19 February 2024 (UTC)
490:Ba'ath Party (disambiguation)
478:23:09, 19 February 2024 (UTC)
364:14:20, 14 December 2023 (UTC)
341:14:07, 14 December 2023 (UTC)
298:13:42, 18 February 2024 (UTC)
179:15:45, 16 November 2021 (UTC)
89:Suggestion originally posted
1349:for these types of edits. –
1289:20:06, 21 October 2021 (UTC)
1271:19:27, 21 October 2021 (UTC)
1246:12:02, 20 October 2021 (UTC)
1207:06:13, 14 October 2021 (UTC)
1172:00:44, 14 October 2021 (UTC)
1153:23:45, 13 October 2021 (UTC)
1132:23:41, 13 October 2021 (UTC)
1091:16:56, 13 October 2021 (UTC)
1073:16:54, 13 October 2021 (UTC)
1048:16:51, 13 October 2021 (UTC)
1023:16:48, 13 October 2021 (UTC)
1001:16:40, 13 October 2021 (UTC)
771:17:57, 21 October 2021 (UTC)
635:a single-page RM was started
589:15:32, 20 October 2021 (UTC)
567:15:01, 20 October 2021 (UTC)
550:14:54, 21 October 2020 (UTC)
510:20:32, 19 October 2020 (UTC)
484:Bot edit warring with itself
460:18:42, 15 October 2021 (UTC)
438:19:45, 13 January 2021 (UTC)
272:02:38, 8 December 2023 (UTC)
215:17:48, 6 December 2023 (UTC)
146:19:11, 21 October 2021 (UTC)
7:
942:17:42, 3 October 2021 (UTC)
916:15:04, 3 October 2021 (UTC)
696:History of the Ba'ath Party
670:a multi-move RM was started
10:
1374:
747:At 21:00, 19 October 2020
740:At 10:48, 16 October 2020
737:at 09:07, 16 October 2020
668:At 08:38, 16 October 2020
649:At 22:19, 15 October 2020
633:At 10:26, 15 October 2020
421:issues reported previously
386:Talk:Georgios Papadopoulos
380:. A user started an RM at
313:
187:
88:
1178:the discussions I started
893:that removal was reverted
710:at 08:52, 16 October 2020
704:at 08:53, 16 October 2020
698:at 08:53, 16 October 2020
692:at 08:53, 16 October 2020
651:the nominator was advised
125:21:31, 12 June 2020 (UTC)
535:Knowledge:TemplateStyles
382:Talk:George Papadopoulos
109:13:49, 10 May 2020 (UTC)
891:while in-progress but
742:the single-page RM was
450:by bot version 7.60 –
42:of past discussions.
1193:discussion. Thanks,
735:the bot reverted you
702:Arab Ba'ath Movement
1191:edit filter request
800:Dozens of bot edits
371:George Papadopoulos
18:User talk:RMCD bot
1120:rather than shrug
322:User talk:wbm1058
196:User talk:wbm1058
107:
82:
81:
54:
53:
48:current talk page
1365:
1341:
1223:
1187:
1142:
1058:
1033:
1012:
924:
870:
840:This is because
839:
646:
555:Bot version 7.41
527:
446:
350:
333:NmWTfs85lXusaybq
319:
318:
306:What happens to
280:
258:
247:
240:
236:
193:
192:
167:
163:
159:
154:mw:API:Revisions
97:
78:
56:
55:
33:
32:
26:
1373:
1372:
1368:
1367:
1366:
1364:
1363:
1362:
1217:
1181:
1136:
1063:the same user.
1052:
1027:
1006:
976:
883:In fairness to
868:
833:
802:
642:
620:
523:
517:
507:
506:it has begun...
486:
374:
325:
324:
316:
312:
284:to prevent the
256:
245:
238:
234:
199:
198:
190:
186:
165:
161:
157:
93:
87:
74:
30:
22:
21:
20:
12:
11:
5:
1371:
1335:
1334:
1333:
1332:
1318:
1307:
1302:
1296:
1295:
1294:
1293:
1292:
1291:
1215:
1214:
1213:
1212:
1211:
1210:
1209:
1100:
1099:
1098:
1097:
1096:
1095:
1094:
1093:
975:
972:
971:
970:
969:
968:
967:
966:
918:
897:WP:TALK#REVISE
801:
798:
797:
796:
759:
758:
757:
756:
745:
731:
722:
721:
720:
719:
718:
712:
711:
705:
699:
693:
681:
680:
679:
666:
665:
664:
647:
619:
616:
615:
614:
613:
612:
611:
610:
552:
538:
531:
528:
525:
521:
516:
515:TemplateStyles
513:
505:
485:
482:
481:
480:
462:
440:
373:
368:
367:
366:
314:
311:
304:
303:
302:
301:
300:
260:
253:
249:
242:
231:
188:
185:
182:
160:function sets
151:
150:
149:
148:
86:
83:
80:
79:
72:
67:
62:
52:
51:
34:
15:
9:
6:
4:
3:
2:
1370:
1361:
1360:
1356:
1352:
1348:
1344:
1340:
1331:
1327:
1323:
1319:
1317:
1313:
1312:
1311:
1308:
1306:
1303:
1301:
1298:
1297:
1290:
1286:
1282:
1278:
1274:
1273:
1272:
1268:
1264:
1260:
1256:
1252:
1249:
1248:
1247:
1243:
1239:
1235:
1231:
1227:
1221:
1216:
1208:
1204:
1200:
1196:
1192:
1185:
1179:
1175:
1174:
1173:
1169:
1165:
1160:
1156:
1155:
1154:
1150:
1146:
1140:
1135:
1134:
1133:
1129:
1125:
1121:
1118:had reverted
1117:
1114:involved. If
1112:
1111:
1106:
1102:
1101:
1092:
1088:
1084:
1080:
1076:
1075:
1074:
1070:
1066:
1062:
1056:
1055:Iggy the Swan
1051:
1050:
1049:
1045:
1041:
1037:
1031:
1026:
1025:
1024:
1020:
1016:
1010:
1009:Iggy the Swan
1005:
1004:
1003:
1002:
998:
994:
990:
986:
982:
965:
961:
957:
953:
949:
945:
944:
943:
939:
935:
931:
927:
923:
919:
917:
913:
909:
905:
902:
898:
894:
890:
886:
882:
881:
880:
876:
872:
865:
861:
857:
853:
850:
847:
843:
837:
832:
831:
830:
829:
826:
823:
818:
817:
814:
811:
807:
795:
791:
787:
783:
779:
775:
774:
773:
772:
768:
764:
754:
750:
746:
743:
739:
738:
736:
732:
729:
726:
723:
716:
715:
714:
713:
709:
706:
703:
700:
697:
694:
691:
688:
687:
685:
682:
678:
674:
673:
671:
667:
662:
659:
658:
656:
652:
648:
645:
640:
636:
632:
631:
630:
628:
624:
609:
605:
601:
596:
592:
591:
590:
586:
582:
578:
574:
570:
569:
568:
564:
560:
556:
553:
551:
547:
543:
539:
536:
532:
529:
522:
519:
518:
512:
511:
508:
503:
499:
495:
491:
479:
475:
471:
467:
463:
461:
457:
453:
449:
445:
441:
439:
435:
431:
427:
426:#Edit warring
422:
418:
414:
410:
409:
408:
407:
403:
399:
395:
391:
387:
383:
379:
372:
365:
361:
357:
353:
349:
345:
344:
343:
342:
338:
334:
330:
323:
309:
299:
295:
291:
287:
283:
279:
275:
274:
273:
269:
265:
261:
254:
250:
243:
232:
229:
228:
223:
219:
218:
217:
216:
212:
208:
204:
197:
181:
180:
176:
172:
155:
147:
143:
139:
135:
131:
130:This incident
128:
127:
126:
122:
118:
113:
112:
111:
110:
105:
101:
92:
77:
73:
71:
68:
66:
63:
61:
58:
57:
49:
45:
41:
40:
35:
28:
27:
19:
1342:
1336:
1276:
1254:
1229:
1109:
1060:
977:
925:
903:
848:
819:
803:
760:
639:Ba'ath Party
621:
618:Ba'ath Party
573:page history
487:
447:
375:
351:
326:
281:
226:
205:. Just FYI.
200:
152:
133:
94:
85:Edit warring
75:
43:
37:
708:Arab Ba'ath
644:Baath Party
320:Moved from
203:Twin Towers
194:Moved from
36:This is an
1228:, the bot
1145:Seasider53
1116:Seasider53
1110:52 minutes
1065:Seasider53
1030:Seasider53
1015:Seasider53
952:v 8.40 fix
595:v 8.41 fix
579:closed. –
502:* Pppery *
466:v 8.41 fix
227:find a way
169:the RM. –
1259:this task
1184:Gricehead
836:Dlthewave
822:dlthewave
810:dlthewave
749:I removed
725:Sahib1609
684:Sahib1609
655:multimove
162:rvlimit=1
76:Archive 4
70:Archive 3
65:Archive 2
60:Archive 1
1281:Struway2
1251:Struway2
1238:Struway2
1203:Contribs
1087:Contribs
1044:Contribs
997:Contribs
985:Struway2
885:Showiecz
856:WP:MULTI
852:contribs
842:Showiecz
637:to move
593:OK, the
464:OK, the
398:Muboshgu
352:Facepalm
308:RMCD bot
207:Station1
184:RMCD bot
1351:wbm1058
1322:wbm1058
1263:wbm1058
1220:Wbm1058
1164:wbm1058
1139:Wbm1058
1124:wbm1058
956:wbm1058
934:wbm1058
908:wbm1058
887:– they
786:wbm1058
763:wbm1058
600:wbm1058
581:wbm1058
559:wbm1058
542:wbm1058
470:wbm1058
452:wbm1058
430:wbm1058
378:wbm1058
356:wbm1058
290:wbm1058
264:wbm1058
248:a page.
239:getpage
235:getpage
171:wbm1058
158:getpage
138:wbm1058
117:wbm1058
39:archive
1347:WP:0RR
895:. Per
871:rose64
782:v 8.41
778:v 8.40
598:RM. –
257:nobots
252:edits.
222:WP:IAR
166:rvend=
134:always
1343:Fixed
1314:Hmm,
1277:after
926:Fixed
904:after
571:This
448:Fixed
282:Fixed
16:<
1355:talk
1326:talk
1285:talk
1267:talk
1255:only
1242:talk
1234:here
1230:does
1226:here
1199:Swan
1195:Iggy
1168:talk
1159:THIS
1149:talk
1128:talk
1083:Swan
1079:Iggy
1069:talk
1040:Swan
1036:Iggy
1019:talk
993:Swan
989:Iggy
960:talk
938:talk
912:talk
875:talk
873:🌹 (
846:talk
790:talk
780:and
776:The
767:talk
717:etc.
675:See
625:and
604:talk
585:talk
563:talk
546:talk
474:talk
456:talk
434:talk
428:. –
402:talk
394:here
392:and
390:here
376:Hi,
360:talk
337:talk
294:talk
268:talk
246:edit
224:and
211:talk
175:talk
142:talk
121:talk
104:talk
100:MSGJ
91:here
1201:) (
1085:) (
1042:) (
995:) (
869:Red
657:."
488:On
1357:)
1328:)
1287:)
1269:)
1244:)
1205:)
1170:)
1151:)
1130:)
1103:I
1089:)
1071:)
1061:is
1046:)
1021:)
999:)
962:)
940:)
914:)
877:)
792:)
769:)
641:→
606:)
587:)
565:)
548:)
492:,
476:)
458:)
436:)
404:)
362:)
339:)
331:.
296:)
270:)
213:)
177:)
144:)
123:)
102:·
1353:(
1324:(
1283:(
1265:(
1240:(
1222::
1218:@
1197:(
1186::
1182:@
1166:(
1147:(
1141::
1137:@
1126:(
1081:(
1067:(
1057::
1053:@
1038:(
1032::
1028:@
1017:(
1011::
1007:@
991:(
958:(
936:(
910:(
849:·
844:(
838::
834:@
825:☎
813:☎
788:(
765:(
602:(
583:(
561:(
544:(
472:(
454:(
432:(
400:(
358:(
335:(
310:?
292:(
266:(
230:.
209:(
173:(
140:(
119:(
106:)
98:(
50:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.