190:, identifies the current and immediate future featured articles, and then generates a list of all templates/images appearing on any of these four pages. The bot then checks each template and image to see whether it is protected (i.e. edit=sysop, move=sysop). If it is not protected, the bot will automatically protect the template/image, and add that item to an internal list. The bot will also check this internal list for items it has protected in the past but which are no longer in high profile locations and restore those items to their pre-existing state. It will not remove protection that had been added by someone else.
335:- every 15 minutes is not good enough. That would give a vandal or an unauthorised (well, obviously it would be unauthorised!) vandal-bot 15 minutes to act first. Suggest changing to a lower but unspecified amount of time so that vandals are not aware of how long they have. Ideally, if possible, make it impossible to add unprotected images and templates to these sensitive areas. Can we also come up with a bot-assisted plan to deal with the template vandalism that was seen on 'today's featured article' for about a week, as that will surely return at some point unless it is dealt with now.
779:
could sneak something in just before midnight and the first bot protection... causing the bot to then protect the vandalized material. However, that would then be visible for an entire day before it went live. There'd still be a need for 'human eyes', but we'd have a full day to catch vandalism before it was widely distributed. After midnight of the day before 'activation' the page would be 'safe' unless an admin vandalized or unprotected it... and even the latter would only last for a few minutes. The 'article of the day' would work the same way
1716:? That feels very much like a waste of time to me, and potentially hazardous as well if made public. The current and tomorrow's main page/featured article collectively contain 53 templates and 31 images. All 53 templates are already protected as are 20 of the 31 images. Of the 11 unprotected images (none on the main page currently, thankfully), 6 are local and 5 reside on commons. Parsing out the relevant bits is somewhere around step 2 in a 10 step process. You are welcome to review the code, as several other people have
954:). These are individually dated and what appears on the main page is automatically changed when the date rolls over. The individual sections (and any images or templates they contain) are supposed to be protected before they appear on the main page and unprotected afterward, but because they change over automatically, they often get neglected. There have also been examples of unprotected images added to ITN, DYK, etc, but because these have to be added by hand, the admin who does so usually gets the protection right.
306:(Misread section) I'm fine with the proposal so long as the article of the day page itself is not protected... the blurb about it on the main page and all templates/images displayed on it can be protected, but the article itself should be open to editing. Note that this might result in a vandal image being added to the page and then protected by this bot... but someone could then still revert to remove the image from the page itself. Also note that
2187:
513:
information (i.e. description and licensing information) from
Commons? If it does, will it recognize when a template used on Commons isn't used here, leading to a red link? (In other words, Commons had a template that we didn't have; I've had to manually substitute the code on Commons, sometimes several times for templates within templates, copy the code here, and then revert myself on Commons.) Thanks!
44:
474:, but ultimately, the ideal behavior is probably to do what admins currently do and upload a copy locally for protection. This will take a bit of time to implement, but certainly seems doable. After it was no longer needed, I could have to bot tag the image for local deletion (I prefer doing that than having the bot actually delete the image, as an extra safeguard against rogue deletion behavior).
1678:
1948:? I'm not sure if the bot is actually copying the code from the template pages or taking the code from the source (I haven't gotten a chance to go through the code you sent me ;-) ), so all I've done is place the templates themselves in the category. Or would a creation of a new category for images not on the Main Page but on the FA itself be more appropriate? Thanks!
366:, what are the mechanisms in place for alerting people as to whether the bot is working or not working. If the bot is approved and successful, people will gradually let the issue drift to the back of their minds and come to rely on the bot. How can we ensure that there is always someone watching the bot (more than one person and not just the person running the bot)?
1513:
and anyone can blank it. If, as is likely, the vandal uses the template in the short interval when it is protected, an admin will be able to unprotect it and delete/fix it. I agree though that this is slightly worrying, as people will focus on the "ProtectionBot protected a vandalised template" bit, and not realise that human oversight is still very much needed.
2010:
stay on the same day will need to be changed, etc.). I had to just manually unprotect the SA for
January 6. Secondly, would you mind adding "BOT:...", like you have done with normal edits, to the protection log summary while the bot is running off of your account? This would make it a lot easier to look at the contributions, etc. Thanks a lot!
822:
would catch this either before to or after the protection, I'm still hesitant with a bot doing this. (Note that vandals also adapt to our tactics; once they figured out what time the bot protects, they could easily do some damage if no one was watching the process.) Perhaps some checks could be implemented here, if possible? Thanks!
1617:- what would happen if a template was removed from the featured article during the course of the day. Would ProtectionBot remember it, and would it still unprotect it at the end of the day, or would unprotection happen sooner, at the next interval? ie. Would all unprotection be queued until the end of the day?
2034:
point, I can add "Bot:", but frankly it's already more than a little inconvenient as a developer/operator to have this running on my own account. I would much prefer to fully set up the seperate account as soon as possible, so that the bot's actions would be cleanly seperated from my own. See for reference
2071:
Well, the second point isn't a large issue, now that the bot is undergoing the RfA now and would run from its own, bot-flagged, account. However, I would still prefer, if at all possible, for the bot to unprotect SAs as soon as they're off the Main Page, similar to how the bot would unprotect images/
1774:
The safety valve is controlled by MediaWiki itself through template syntax, so as long as it's tested once to make sure the math is right and it does kick in after 90 minutes, it should work the same every time. Also, blocking the bot would trigger said safety valve 90 minutes after the block; since
221:
To expand on this, I am proposing that the bot copy the image, image description, and any neccesary templates that exist on
Commons but not locally. When the local copy was no longer needed, the image would be tagged for deletion. Any commons image templates would be left here since presumably they
193:
I have already written code capable of performing most (but not all) of the above functions, but I am coming here to get feedback from the community before carrying this project further. As noted above, this bot would require sysop rights in addition to ordinary bot approval. For an alternative but
1795:
I am not suggesting you can not parse code, just that this request needs to have a signfigant degree of caution used for it, and I am all for other suggestions on how to trial this bot, my trial approval was to continue to move this request forward. The hightened caution is twofold, first it is due
1490:
Non-admins could still remove said template from the featured article. The only case where it might be a problem is if that "newly-added template" was used widely on hundreds of other pages. If that was the case, an admin would be needed urgently to undo protection and fix things for the hundreds of
821:
Though the chances of either an image or template being vandalised and then protected are slim, I've seen it happen before; vandals hit the images/templates scheduled to come up in a few days. Although rare, I've (luckily) caught this before, and although I'm also confident that (hopefully) an admin
350:
they actually reach high profile status. The unpredictable elements (such as a news event causing a new image to appear on In The News) would be caught the next time the bot runs, but ideally should still be protected by the admin who added them. It has been the predictable elements that have been
2107:
takes place. Dragons flight I suggest that you post the RfA as soon as possible so that we can get the flag for this bot.In regard of the approved test that should have concluded by now, if more testing needs to be done before the RfA is over please test on as the trial was just given to work out
2033:
Yeah, I've noticed that some of those selected anniversaries have been protected a really long time as well. My thought on that had been that I would propose a seperate one-time run to clear all the really old protections some time after
ProtectionBot was fully set up and deployed. On your second
1988:
I will be leaving the bot running while I go away for a bit. Since this is the first time it has been left running without myself directly in front of it, I thought I should let others know. It has been operating normally for quite a while now and I don't anticipate any problems, especially since
1512:
The template would only remain protected for as long as it was on the Main Page or the
Featured Article page. At some point (less than half an hour I think) after it is taken off the page, ProtectionBot will unprotect the template again, and the vandal only has an unprotected template to play with,
983:
Yes, it could (though copying the edit page transclusion list to a talk subpage would accomplish the same thing), however given the low likelihood of needing to edit a template on a FA versus the high frequency with which they have been targetted, my preference would be just to the protect them all
778:
No, the bot couldn't tell a vandalized image/template from a non-vandalized one... but should it need to? Think about the way it works. It would protect all 'daily' content on the main page (except 'In the news' and 'Did you know') starting at midnight the day BEFORE it went live. So maybe a vandal
1764:
feature, but I wonder if there is a way to test that as well to make sure the "not editing for 90 minutes" thing does work? Also, is it possible to make clear to admins using the emergency shut-off button that they should follow-up and make sure that protection is dealt with by humans, rather then
1660:
to pick up vandalism, in fact we need to do this more than ever before. If this works, people will get complacent and the inevitable result will be that a vandal slips something in just before protection takes place, the vandalism (possibly not very visible) remains undetected for a whole day, and
967:
2:As for the FA, if the challange is in having a hard time finding tempaltes that are subtranslcuded in the FA that have been vandalized, the bots programing could be used to make a talk page or subtalk page link of all transclusions and subtransclusions that could be searched by
Related Changes,
2009:
Thanks for the updates! Two minor requests: first, could you have your bot unprotect old selected anniveraries as well? The "tradition", per se, has always been to unprotect them when they are off the Main Page so that they can be updated accordingly (new events will be added, holidays that don't
1998:
Today's midnight UTC changeover seems to have gone as expected. The bot failed to unprotect a couple images, but this was caused by missing log entries related to yesterday's bugs, and not any current problem in the bot. During the night it also served to protect and unprotect some changes that
512:
Thanks for clarifying this! A few more questions/comments: would the bot be programmed to delete the image once it is off the Main Page? If there are prior revisions in the image description here (i.e. FA tagging) will the bot restore those revisions? In addition, does the bot also copy the image
1533:
Security through obscurity is not. Release the code for everyone to try to break or just have it add "needs-protection" templates to articles/images and do the commonsuploadingreplacement-tagging. If some smart vandal uploading a buffer overrun can block a user, then it cannot run with a bit. Is
1500:
In the scenario I'm thinking about, a vandal would end up with a protected template. Even if removed from the FA (possibly by the vandal himself), it could be added to other (non protected) templates or pages. Yes these additions could all be reverted, but the simplest fix at the point of origin
746:
For that matter, the bot would also not be able to recognize vandalized images prior to protection. Although (hopefully) people will catch the vandalism prior to protection or, at latest, prior to the image being shown on the Main Page, this contributes to my queasiness about eliminating human
640:
I have to agree with the general sentiment of this comment; I'm always wary of entrusting a task to a bot without continuous human oversight. As pointed out above, there is no mechanism to ensure that admins are alerted if the bot is malfunctioning or stops working, and the results could prove
536:
that marks the image for speedy deletion and includes a reminder to the deleting admin to restore any pre-existing description page content after deleting the local copy. Given the unusual nature of this project, I felt it was prudent not to go handing direct deletion authority to a bot.
2072:
tag images for deletion as soon as the images were off the Main Page. This would avoid having the protected SAs accumulate over time, and would also be a large convenience. Finally, it would leave the SAs open for editing, as they should be, the moment they are off the Main Page. Thanks!
783:
that since that page itself would be unprotected someone could add a vandalized image or template to it... which the bot might then protect. However, the article would still not be protected and any other user could just revert/remove the call to the vandalized image or template. There
1324:
but because of the nature of the work the bot will be doing, I would like to request a documented testing overview of the planned QA. Not a bunch of wonkery or make-work, but a quick list of test cases that
Dragons Flight plans to run to validate that the bot won't start WWIII. -
1933:
The first two errors, being fatal, required me to do some substantial manual cleanup after the bot during this initial run. It has also suggested ways that I can improve the error handling which I intend to do now. Aside from these issues, it appears to be working as designed.
2193:
As the RFA required to give this bot the sysop bit has been withdrawn by the operator, this bot can not function as designed. Due to the large size of this request, I'm closing it as a w/d. Should DF wish to due something else with this bot account, please start a new request. —
1733:
the only way to test is to actually run the bot on the main page. Unless
Xaosflux or any other BAG has an objection I give my support for a 24 hour trial (this will cover todays FA and tomorrow's FA protection, and the unprotection of the current FA once it leaves the main page)
797:
I agree. Unless the vandalism is very subtle or there are no admins looking (unlikely) then this is not really a problem. I just wanted to point out that part of the act of an admin protecting a template from vandalism (which is checking that the template is not
689:
I think the concerns raised by people over an admin-bot were (and continue to be) valid, even though I don't necessarily agree with all of them; I also hope that following discussion here, any attempts to make the bot a sysop will go through the usual channel of
1167:. I'm satisfied that most scenarios have been considered and accounted for, and any more that might come up could be dealt with quickly. Any potential unforeseen issue couldn't possibly be any worse than the problems we've got with the main page now. —
675:
transcluded on to the Main Page because people refuse to give the FA-counting bot the necessary flag. In other words, they're happy to let it edit a template on the Main Page via some clumsy hack, but they won't sysop it so it can do so the normal way –
1979:(edit conflict) I have also discovered that the list of transcluded templates does not respond to action=purge and can at times be several hours out of date. Consequently I implemented a work around for this that forces the template list to update.
579:
Sigh. Have I complained recently about how the existence of
Commons makes life here more difficult? Okay, I've modified the bot code to be able to copy over the Commons image descriptions (including duplicating any unique to Commons image tags).
622:
eyes. Historically, most of the disruption on the main page is caused by sysops making small changes without consensus and often introducing bad markup in the process. Every template and image on the main page should be checked by human eyes after
1626:
It unprotects it after two passes of finding a template it protected is no longer part of a featured article. The requirement for two passes insures that a vandal can't simply get something unprotected by catching the bot at the right moment.
1910:
A problem with dropped wikisession information. I suspect that this was caused by how
Mediawiki handles sessions and a conflict with my trying to use my account at the same time the bot was running. If I am correct, this means that this bot
671:: If by some miracle the community emerges from its haze of ignorance and and actually permits this bot to acquire a sysop flag, then for god's sake use the precedent to get the same thing done with other bots that need it. There's a bloody
483:
I'm not sure I quite understand what you mean by " would ignore images uploaded to Commons" - does that mean they would remain unprotected unless a (human) admin uploads and then protects the images? This would be a serious concern.
1877::P) approval of the plans. In any case, anyone can express their opinion in a BRFA, or their support for a proposal - in fact I went and commented on a few today. Helpful suggestions or just plain support for an idea can help :)
1872:
In the last admin bot BRFA, it was felt that the lack of support shown on the BRFA carried through to the RFA's failure. By showing our support here we are avoiding this ill fate and showing the BAG that there is community (or
145:
Intended to automatically protect templates and images appearing on the main page or today's featured article, and unprotect them when they are no longer in these high profile locations. This bot will require sysop rights.
589:
Maybe leaving away all bot-features relating to images for a start? The images thing starts getting very complicated (just and idea, I'm not opposing anything). Concentrating on the templates first wouldn't be that bad.
1000:, if there's a protected "Stop" page which will immediately halt the bot's operation when an admin edits it. More likely to be needed to please the editors at an RfA and satisfy them that you've ticked all the boxes.
2108:
any kinks before the RfA. If this bot has as much support as the BRfA has the closing B-crat can take into consideration all of the anti-adminbot biasis when they close it since it is a discussion and not a election.
984:
while the topic is front page featured. This would also ensure they get unprotected afterward, whereas right now templates that are protected because of an attack may remain protected for a long time unnecessarily.
273:, we need this. Giving it admin status is no problem as long as it is assured that it will only ever use them for the task described, and as long as it has a giant "nuke me now" button in case it should malfunction.
2141:
status for a period of 2-4 weeks (albeit in PRODUCTION) and that it should NOT have a bot flag. This should give plenty of time for any troubleshooting and tweaking for the functions approved before this point. —
448:
Since the plan is for the bot to also protect images that appear on the main page, how will it deal with those from Commons? The current procedure is to upload a local copy here onto Knowledge (XXG), tag it with
314:
and thus it might be better to check some of those templates directly. Specifically, the other templates are the 'article of the day', 'picture of the day', and 'on this day' sections for the following day and
722:
though note that usually the admin protecting a page looks at the page before protecting it; if this bot protects an already vandalized template it will be harder for regular users to undo that vandalism.
210:
In order to protect images which come from Commons, I have added an ability to upload them to Knowledge (XXG). When the local copy is no longer needed, I would have the bot tag them for speedy deletion.
907:
Unprotected templates and images are ending up on the main page because there are not enough admins to double check them everytime someone makes a change. It can happen when someone changes the image on
1692:
results if it can post the results to a page that is then swiftly deleted admins can review the results. Due to the expected high visibility of this bot lets also leave this discussion transcluded on
351:
greatest sources of vandalism lately, and so that ought to be eliminated. I also plan to add random jitter to the bot execution times, so as to make it more difficult for anyone to race the bot.
459:, and protect that. Protecting just the image description page here does not work because a vandal can simply log onto Commons using a sleeper account and save a new version of the image there.
1661:
then silently switches over on the main page, at which point all hell will break loose. Checking the 'tomorrow' version will also guard against various 'date template' vandalism possibilities.
323:. The 'next update' page often gets updated several times per day and is currently accessible to non-admins and thus might not be appropriate to protect prior to be placed on the Main page. --
788:
be 'vulnerabilities' if this proposal were implemented (including some I haven't mentioned to avoid educating the vandals), but they would be significantly less than those which exist now. --
2232:
1475:- if the bot runs ever 15 minutes, will it also protect templates newly-added to an article while it is on the main page? That could make a vandal template inaccessible to non-admins.
951:
391:
If it is expected to be offline, I would warn people. At present I have no other plans for ways to make sure any unplanned downtime is noticed, but I am open to suggestions.
1304:
933:
1765:
just walking away with a "bot's shut off now, everything should be OK now" shrug of the shoulders. That's the only thing I can think of at the moment. All looks really good!
2157:
Shrug. I'm sure people are going to be watching it very carefully regardless of whether we call that time a trial or not, so I don't see it making much difference to me.
1915:
run on my account at the same time that I am using it, and consequently continuous operation absolutely requires a seperate account. I will be investigating this further.
1042:
Hmm OK - I wasn't sure about the situation with protections being allowed after a block, but after a test it appears not (the protect counts as an edit). I'm happy with
195:
766:
I agree. If the bot cannot recognize vandalized images and templates, then I would rather have non-admins constantly revert those files until another sysop can step in.
2170:
2119:
1016:
I believe the big red block button should be adequate. Software changes have made it so that a blocked admin can neither edit nor perform any admin action other than
1712:
I've already run all the trials I feel are necessary short of full-scale deployment. You really want me to sit around generating lists to show that I know how to
892:
at all? Adding anything to the MP requries sysop rights already, and there is a clear proceedure for doing it. I can't see needing an adminbot to do this. —
1300:. We have better things to do than babysit every %*!@# template that touches the front page or the daily featured article. I cannot emphasize this enough.
928:
is created but not protected. It can also occur when another unprotected template is placed onto one of the main page templates, such as when the unprotected
346:
As described it would be looking at Main Page/Tomorrow and Tomorrow's Featured Article as well as the current ones, so predictable elements will be protected
627:
edit is made. I fear that adding a bot will reduce the amount of redundant checks on these pages and thus cause minor mistakes to stay up even longer. ---
1501:(blanking the vandal template) would not be accessible to non-admins. A little variation in the protection timing would help avoid this sort of exploit.
425:
and as long as you are willing to share the code with other admins via e-mail or other secure method I have no problem with this bot not being approved.
1800:
and getting full support and showing all due dillegence here on RFBOT should alleviate challenges that have occured on RFA during other bot attempts. —
1967:
I was thinking that "Protected by ProtectionBot" and "Uploaded by ProtectionBot" could be made subcats of all protected/uploaded high profiles stuff.
2123:
1688:
if it is possible to run this without admin rights (perhaps generating the lists so we can verify the parsing?) As this type of test will produce
1029:
Well, apart from editing their talk page to request unblocking, but then I guess you haven't programmed it to do that. :-) Just make sure it can't
645:, I don't feel that there is an urgent need for the bot, especially with the (very real and plausible) chances of malfunction or stoppage. Thanks!
1720:, but if we are going to have a trial I would ask that it be a full demonstration that it works, rather than making extra pointless work for me.
1717:
21:
304:
On AN you also mentioned protecting templates and images for the article of the day, but this is not specified above. That should be clarified.
84:
1301:
1945:
1404:
79:
2173:
for this bot ended, with the bot operator withdrawing the bot. As such I don't think this request will be able to continue. Cheers! ——
1266:
316:
236:
1775:
the bot would theoretically have already handled the next day's protection, I think warning within 90 minutes should be plenty. —
114:
99:
1138:
1020:
issuing and removing blocks. Hence blocking the bot (even if it has sysop rights) will stop it from doing anything.
540:
1918:
A formatting issue wherein the bot converted a newline to a space. I haven't yet tracked down why this occured.
533:
94:
2204:
2180:
2161:
2152:
2130:
2112:
2086:
2058:
2046:
2024:
2003:
1993:
1983:
1971:
1962:
1938:
1925:
1888:
1863:
1844:
1810:
1786:
1769:
1755:
1738:
1724:
1706:
1682:
Approved for trial. Please provide a link to the relevant contributions and/or diffs when the trial is complete.
1665:
1640:
1631:
1621:
1609:
1595:
1583:
1563:
1546:
1517:
1507:
1495:
1481:
1467:
1438:
1421:
1409:
1385:
1370:
1350:
1337:
1316:
1292:
1273:
1226:
1199:
1178:
1159:
1147:
1120:
1108:
1096:
1072:
1057:
1037:
1024:
1011:
988:
978:
958:
945:
902:
872:
836:
816:
792:
773:
761:
737:
712:
680:
659:
631:
594:
584:
574:
558:
527:
507:
503:
I now have code prepared to automatically copy images over from Commons so that they can be protected locally.
498:
478:
466:
438:
429:
421:
About time for this to come here, I have full support of this bot and bot operator, you have done great work at
408:
395:
386:
370:
355:
339:
327:
294:
282:
259:
243:
226:
215:
202:
1903:
I have begun running this on my admin account on a manual basis. In doing so I have identified several issue:
1831:
1347:
857:- Someone vandalized a template again tonight with a picture of a bloody vagina. We need something like this.--
811:
732:
89:
1491:
other articles where the template was being used. But high-use templates should already be protected anyway.
698:
requests for admin rights, and would have a wider participation than here, on the bot request page.) Thanks!
1399:
1030:
74:
950:
To expand on what Zzyzx11 said, the biggest culprit recently appears to the be the rotating sections (e.g.
1944:
Thanks for the trial report. A comment: would it be possible for the bot to add the images it protects to
1825:
1559:
1134:
1367:
1156:
789:
324:
320:
1796:
to this requests interaction with our most viewed page; and second is that it will end up requiring an
1210:? We need this, and there isn't any point in !voting. Recent events could have been avoided with it. |
618:- I personally think that the templates and images on the main page need to be watched by more sets of
929:
2078:
2016:
1954:
1575:
1142:
828:
753:
704:
651:
519:
490:
376:
363:
2158:
2127:
2043:
2000:
1990:
1980:
1968:
1935:
1922:
1882:
1730:
1721:
1628:
1539:
1502:
1476:
1382:
1051:
1021:
1005:
985:
955:
805:
726:
581:
555:
547:
504:
475:
453:
435:
405:
392:
352:
278:
256:
240:
223:
212:
199:
125:
2100:
422:
1781:
1761:
1657:
1444:
1434:
1394:
1333:
1173:
865:
401:
307:
252:
187:
55:
2042:. Even a temporary sysop flag would make it easier for me and others to see what it is doing.
1693:
1689:
878:
1861:
1555:
1554:
I support this more eagerly than any other proposal I have ever voted for on Knowledge (XXG).
1312:- I was worried people would get mad about a bot with a sysop flag. Boy do we need this one. -
1286:
1239:
1129:
1069:
942:
770:
571:
463:
383:
2039:
2035:
1874:
1235:
1207:
925:
17:
2109:
1735:
1363:
426:
375:
Carcharoth raises a very crucial issue here. Shadowbot2 has also had a problem as well, see
2104:
1837:
1820:
1797:
1359:
917:
909:
882:
691:
2186:
2073:
2011:
1949:
1766:
1752:
1662:
1637:
1618:
1604:
1580:
1572:
1514:
1492:
1034:
823:
748:
699:
646:
642:
514:
485:
367:
336:
2051:
As a bot running it probably should have had those words on the edit summery. Cheers! ——
921:
2174:
2126:, that also includes a request that it be allowed to continue running during the RFA.
2052:
1879:
1535:
1379:
1313:
1048:
1002:
274:
1907:
A unicode handling bug in one part of the program that crashed it. This is now fixed.
2226:
2195:
2143:
1853:
Xaosflux is a member of the group, and approved a trail run. So what is the problem?
1801:
1776:
1697:
1684:
Well it looks like there is more then enough support to run trials with this bot, so
1592:
1431:
1418:
1326:
1211:
1194:
1188:
1168:
1117:
969:
893:
858:
1854:
1282:
1105:
939:
916:
but forgets to protect it. This problem also can occur when the new daily rotating
767:
628:
591:
568:
460:
380:
291:
1534:
there anything in the code worth keeping secret? Only if there's a mistake in it.
43:
1591:- we need this urgently to stop the template vandalism that hits the main page.
1713:
677:
641:
disastrous. The current system works, and given the new system of checks with
563:
There might be a problem if you do not copy the description from Commons. See
2137:
I'd request that should the RFA get approved, we keep the bot officially in
1089:
1068:
Ultra-super-duper support, in light of today's latest template vandalism. --
889:
434:
Once fully implemented, I would be willing to share the code non-publicly.
311:
183:
802:
vandalized) can't be replicated by a bot, so we still need some oversight.
1921:
The formatting issue should be resolved now (albeit with an ugly hack).
251:
I now have an essentially fully functional code base, and have updated
139:
Python (partially dependant on pywikipedia, but mostly original code)
472:
The code written so far would ignore images uploaded only to Commons
1748:
1744:
913:
539:
It does not copy the description from Commons but rather provides
532:
When the local image is no longer needed, it is programmed to add
1571:. Requested something similar myself...great minds think alike!--
235:
Per suggestion, it would also track images/templates used within
1819:
What the hell? Approval is not a vote, it is a request made of
379:. Because it sends an email, we were able to detect it quickly.
2211:
The above discussion is preserved as an archive of the debate.
1088:
in the past half hour with another really disturbing photo. --
1155:: can't see any drawbacks - certainly worth the experiment. --
694:, which seems to be more appropriate (i.e. it's the place for
1989:
there is little activity on the Main Page this time of day.
1116:. I live in terror of ever seeing one of these photos. o_O --
888:
1:How are unprotected templates and images ending up on the
404:
to provide a limited sort of warning if it stops working.
1358:
in principle. Admin rights should be sought through the
1186:
Stop the unnecessary procedural nonsense and do it now.
952:
Knowledge (XXG):Today's featured article/January 1, 2007
543:
that points at the Commons description page, similar to
937:
564:
109:
104:
69:
2099:
Please note that this bot will only be approved of if
310:
duplicates all but four of the templates used on the
196:
Knowledge (XXG):Bots/Requests_for_approval/Shadowbot2
2217:
Subsequent comments should be made in a new section.
1417:
per... let's see... Can't sleep, clown will eat me.
39:
Subsequent comments should be made in a new section.
2233:
Withdrawn Knowledge (XXG) bot requests for approval
877:First, I'm glad we're dealing with this here on
33:The following discussion is an archived debate.
2197:
2145:
1803:
1699:
971:
895:
1378:. I for one welcome our new robot overlords.
8:
1652:- there is the point that we still need to
2118:As requested, I've shut it down and filed
885:; and I know we've had some issues, but:
1999:where made to the Did you know image.
1279:Support support support support support
153:(e.g. Continuous, daily, one time run)
7:
1946:Category:Protected main page images
255:to give more operational details.
1760:Some serious comments. I like the
400:I've added the function described
222:could be used for future images.
28:
317:Template:Did you know/Next update
237:Template:Did you know/Next update
41:The result of the discussion was
2185:
1676:
1234:. Get this thing going now per
42:
1751:overlords during the test? :-)
1454:
1452:
1450:
1448:
1446:
1261:
1256:
1253:
1250:
1247:
1244:
1241:
859:
131:Automatic or Manually Assisted:
1400:
1391:Super-Über-Mega-Speedy SUPPORT
1302:Can't sleep, clown will eat me
1084:. The main page was just hit
194:less extensive proposal, see:
1:
817:16:26, 31 December 2006 (UTC)
793:10:44, 31 December 2006 (UTC)
774:00:28, 31 December 2006 (UTC)
762:23:48, 30 December 2006 (UTC)
738:23:35, 30 December 2006 (UTC)
713:23:29, 30 December 2006 (UTC)
681:20:23, 30 December 2006 (UTC)
660:23:24, 30 December 2006 (UTC)
632:19:21, 30 December 2006 (UTC)
499:23:18, 30 December 2006 (UTC)
479:18:28, 30 December 2006 (UTC)
467:16:05, 30 December 2006 (UTC)
439:18:31, 30 December 2006 (UTC)
430:15:22, 30 December 2006 (UTC)
396:18:28, 30 December 2006 (UTC)
387:15:53, 30 December 2006 (UTC)
371:15:09, 30 December 2006 (UTC)
356:18:28, 30 December 2006 (UTC)
340:15:04, 30 December 2006 (UTC)
328:13:21, 30 December 2006 (UTC)
295:12:52, 30 December 2006 (UTC)
283:11:59, 30 December 2006 (UTC)
203:11:32, 30 December 2006 (UTC)
2205:04:34, 11 January 2007 (UTC)
2181:02:16, 11 January 2007 (UTC)
1838:
1832:
1826:
1395:
1287:
377:User talk:Shadowbot2#Problem
2162:03:51, 9 January 2007 (UTC)
2153:03:43, 9 January 2007 (UTC)
2131:09:54, 7 January 2007 (UTC)
2113:05:04, 7 January 2007 (UTC)
2087:16:10, 7 January 2007 (UTC)
2059:05:29, 7 January 2007 (UTC)
2047:03:12, 7 January 2007 (UTC)
2025:02:11, 7 January 2007 (UTC)
2004:01:13, 7 January 2007 (UTC)
1994:07:21, 6 January 2007 (UTC)
1984:04:17, 6 January 2007 (UTC)
1972:04:22, 6 January 2007 (UTC)
1963:04:14, 6 January 2007 (UTC)
1939:01:14, 6 January 2007 (UTC)
1926:04:17, 6 January 2007 (UTC)
1889:20:43, 5 January 2007 (UTC)
1864:20:32, 5 January 2007 (UTC)
1845:19:59, 5 January 2007 (UTC)
1811:04:25, 6 January 2007 (UTC)
1787:17:18, 5 January 2007 (UTC)
1770:14:38, 5 January 2007 (UTC)
1756:14:28, 5 January 2007 (UTC)
1739:06:47, 5 January 2007 (UTC)
1725:06:33, 5 January 2007 (UTC)
1707:05:16, 5 January 2007 (UTC)
1666:10:24, 7 January 2007 (UTC)
1641:10:24, 7 January 2007 (UTC)
1632:10:17, 7 January 2007 (UTC)
1622:10:10, 7 January 2007 (UTC)
1610:21:46, 6 January 2007 (UTC)
1596:16:54, 6 January 2007 (UTC)
1584:03:29, 6 January 2007 (UTC)
1564:23:52, 5 January 2007 (UTC)
1547:21:45, 5 January 2007 (UTC)
1518:12:24, 8 January 2007 (UTC)
1508:17:39, 7 January 2007 (UTC)
1496:10:10, 7 January 2007 (UTC)
1482:19:01, 5 January 2007 (UTC)
1468:12:02, 5 January 2007 (UTC)
1439:05:57, 5 January 2007 (UTC)
1422:05:11, 5 January 2007 (UTC)
1410:04:39, 5 January 2007 (UTC)
1405:
1386:04:03, 5 January 2007 (UTC)
1371:03:14, 5 January 2007 (UTC)
1351:03:12, 5 January 2007 (UTC)
1338:02:14, 5 January 2007 (UTC)
1317:01:58, 5 January 2007 (UTC)
1305:01:48, 5 January 2007 (UTC)
1293:01:45, 5 January 2007 (UTC)
1274:01:39, 5 January 2007 (UTC)
1232:Strong speedy super support
1227:01:21, 5 January 2007 (UTC)
1200:01:18, 5 January 2007 (UTC)
1179:01:12, 5 January 2007 (UTC)
1160:01:09, 5 January 2007 (UTC)
1148:01:05, 5 January 2007 (UTC)
1121:01:05, 5 January 2007 (UTC)
1109:01:04, 5 January 2007 (UTC)
1097:01:02, 5 January 2007 (UTC)
1073:01:00, 5 January 2007 (UTC)
1058:00:46, 2 January 2007 (UTC)
1038:22:26, 1 January 2007 (UTC)
1025:22:13, 1 January 2007 (UTC)
1012:19:08, 1 January 2007 (UTC)
989:22:13, 1 January 2007 (UTC)
979:18:40, 1 January 2007 (UTC)
959:22:13, 1 January 2007 (UTC)
946:19:17, 1 January 2007 (UTC)
903:18:41, 1 January 2007 (UTC)
873:04:33, 1 January 2007 (UTC)
866:
837:04:01, 2 January 2007 (UTC)
595:11:50, 3 January 2007 (UTC)
585:01:09, 3 January 2007 (UTC)
575:17:29, 2 January 2007 (UTC)
559:04:10, 2 January 2007 (UTC)
528:03:54, 2 January 2007 (UTC)
508:06:37, 1 January 2007 (UTC)
409:04:14, 2 January 2007 (UTC)
260:00:43, 2 January 2007 (UTC)
244:10:46, 1 January 2007 (UTC)
227:01:09, 3 January 2007 (UTC)
216:06:37, 1 January 2007 (UTC)
2249:
1686:Conditional Trial Approved
1114:Strongest possible support
1080:- We absolutely need this
1393:. Practically essential.
2214:Please do not modify it.
137:Programming Language(s):
36:Please do not modify it.
1821:the bot approvals group
1104:as Cyde. Oh, hell yes.
934:2006-07-28 TFA template
673:user javascript subpage
2191:Withdrawn by operator.
2169:Please note that this
2124:a notice of this at AN
2101:Knowledge (XXG):OFFICE
423:Knowledge (XXG):RFASUM
362:Also, per the comment
168:Already has a bot flag
1747:will be watching our
1694:Knowledge (XXG):RFBOT
879:Knowledge (XXG):RFBOT
321:Template:Did you know
48:Withdrawn by operator
22:Requests for approval
1236:Knowledge (XXG):SNOW
1208:Knowledge (XXG):SNOW
162:Edit rate requested:
18:Knowledge (XXG):Bots
2040:proposal at the end
1899:Comments from Trial
1798:Knowledge (XXG):RFA
1082:as soon as possible
883:Knowledge (XXG):RFA
747:oversight. Thanks!
1887:
1839:Neutrality Project
1658:Main Page/Tomorrow
1056:
1044:the BIG red button
1018:unblocking himself
1010:
308:Main Page/Tomorrow
253:User:ProtectionBot
188:Main Page/Tomorrow
2122:. I have posted
2085:
2023:
1961:
1878:
1718:volunteered to do
1562:
1543:
1330:
1198:
1146:
1047:
1001:
932:was added to the
835:
760:
711:
658:
565:this edit summary
526:
497:
281:
180:Function Details:
158:Every 15 minutes
143:Function Summary:
2240:
2216:
2201:
2189:
2149:
2082:
2076:
2020:
2014:
1958:
1952:
1885:
1859:
1843:
1840:
1834:
1828:
1807:
1784:
1703:
1680:
1679:
1558:
1541:
1464:
1462:
1460:
1458:
1456:
1437:
1407:
1402:
1397:
1328:
1289:
1272:
1259:
1258:
1255:
1252:
1249:
1246:
1243:
1224:
1219:
1216:
1192:
1176:
1132:
1094:
1054:
1033:how to do that.
1008:
975:
930:Template:Pokenum
899:
870:
863:
832:
826:
815:
808:
757:
751:
736:
729:
708:
702:
655:
649:
552:
546:
523:
517:
494:
488:
458:
452:
277:
46:
38:
2248:
2247:
2243:
2242:
2241:
2239:
2238:
2237:
2223:
2222:
2221:
2212:
2200:
2148:
2097:
2080:
2036:this discussion
2018:
1956:
1901:
1883:
1855:
1824:
1806:
1782:
1702:
1677:
1674:
1560:(Упражнение В!)
1430:
1271:
1240:
1220:
1217:
1212:
1174:
1090:
1052:
1006:
974:
898:
830:
806:
803:
755:
727:
724:
706:
653:
550:
544:
521:
492:
456:
450:
267:
120:
59:
34:
26:
25:
24:
12:
11:
5:
2246:
2244:
2236:
2235:
2225:
2224:
2220:
2219:
2198:
2167:
2166:
2165:
2164:
2159:Dragons flight
2146:
2134:
2133:
2128:Dragons flight
2096:
2093:
2092:
2091:
2090:
2089:
2066:
2065:
2064:
2063:
2062:
2061:
2044:Dragons flight
2028:
2027:
2001:Dragons flight
1991:Dragons flight
1981:Dragons flight
1977:
1976:
1975:
1974:
1969:Dragons flight
1936:Dragons flight
1931:
1930:
1929:
1928:
1923:Dragons flight
1916:
1908:
1900:
1897:
1896:
1895:
1894:
1893:
1892:
1891:
1867:
1866:
1848:
1847:
1816:
1815:
1814:
1813:
1804:
1793:
1792:
1791:
1790:
1789:
1758:
1731:Dragons flight
1722:Dragons flight
1700:
1673:
1670:
1669:
1668:
1647:
1646:
1645:
1644:
1643:
1629:Dragons flight
1612:
1598:
1586:
1566:
1549:
1527:
1526:
1525:
1524:
1523:
1522:
1521:
1520:
1485:
1484:
1470:
1441:
1424:
1412:
1388:
1373:
1353:
1340:
1319:
1307:
1298:Speedy support
1295:
1276:
1265:
1229:
1202:
1181:
1162:
1150:
1123:
1111:
1102:Speedy support
1099:
1078:Speedy support
1075:
1066:
1065:
1064:
1063:
1062:
1061:
1060:
1022:Dragons flight
995:
994:
993:
992:
991:
986:Dragons flight
972:
965:
964:
963:
962:
961:
956:Dragons flight
896:
875:
850:
848:
847:
846:
845:
844:
843:
842:
841:
840:
839:
807:brighterorange
776:
741:
740:
728:brighterorange
717:
716:
715:
684:
683:
665:
664:
663:
662:
635:
634:
613:
612:
611:
610:
609:
608:
607:
606:
605:
604:
603:
602:
601:
600:
599:
598:
597:
582:Dragons flight
556:Dragons flight
505:Dragons flight
476:Dragons flight
443:
442:
441:
436:Dragons flight
419:
418:
417:
416:
415:
414:
413:
412:
411:
406:Dragons flight
393:Dragons flight
360:
359:
358:
353:Dragons flight
330:
297:
285:
266:
263:
257:Dragons flight
241:Dragons flight
230:
229:
224:Dragons flight
213:Dragons flight
200:Dragons flight
182:The bot reads
150:Edit period(s)
126:Dragons flight
119:
118:
112:
107:
102:
97:
92:
87:
82:
77:
72:
70:Approved BRFAs
67:
60:
58:
53:
52:
51:
29:
27:
15:
14:
13:
10:
9:
6:
4:
3:
2:
2245:
2234:
2231:
2230:
2228:
2218:
2215:
2209:
2208:
2207:
2206:
2203:
2202:
2192:
2188:
2183:
2182:
2179:
2177:
2172:
2163:
2160:
2156:
2155:
2154:
2151:
2150:
2140:
2136:
2135:
2132:
2129:
2125:
2121:
2117:
2116:
2115:
2114:
2111:
2106:
2102:
2095:End of Trials
2094:
2088:
2083:
2075:
2070:
2069:
2068:
2067:
2060:
2057:
2055:
2050:
2049:
2048:
2045:
2041:
2037:
2032:
2031:
2030:
2029:
2026:
2021:
2013:
2008:
2007:
2006:
2005:
2002:
1996:
1995:
1992:
1986:
1985:
1982:
1973:
1970:
1966:
1965:
1964:
1959:
1951:
1947:
1943:
1942:
1941:
1940:
1937:
1927:
1924:
1920:
1919:
1917:
1914:
1909:
1906:
1905:
1904:
1898:
1890:
1886:
1881:
1876:
1871:
1870:
1869:
1868:
1865:
1862:
1860:
1858:
1852:
1851:
1850:
1849:
1846:
1841:
1835:
1829:
1827:Peter M Dodge
1823:. Cheers, ✎
1822:
1818:
1817:
1812:
1809:
1808:
1799:
1794:
1788:
1785:
1780:
1779:
1773:
1772:
1771:
1768:
1763:
1759:
1757:
1754:
1750:
1746:
1742:
1741:
1740:
1737:
1732:
1729:I agree with
1728:
1727:
1726:
1723:
1719:
1715:
1711:
1710:
1709:
1708:
1705:
1704:
1695:
1691:
1687:
1683:
1671:
1667:
1664:
1659:
1655:
1651:
1648:
1642:
1639:
1635:
1634:
1633:
1630:
1625:
1624:
1623:
1620:
1616:
1613:
1611:
1608:
1607:
1602:
1599:
1597:
1594:
1590:
1587:
1585:
1582:
1579:
1578:
1574:
1570:
1567:
1565:
1561:
1557:
1553:
1550:
1548:
1545:
1537:
1532:
1529:
1528:
1519:
1516:
1511:
1510:
1509:
1506:
1505:
1499:
1498:
1497:
1494:
1489:
1488:
1487:
1486:
1483:
1480:
1479:
1474:
1471:
1469:
1466:
1465:
1442:
1440:
1436:
1433:
1428:
1425:
1423:
1420:
1416:
1413:
1411:
1408:
1403:
1398:
1392:
1389:
1387:
1384:
1381:
1377:
1374:
1372:
1369:
1365:
1361:
1360:usual process
1357:
1354:
1352:
1349:
1345:
1341:
1339:
1335:
1331:
1323:
1320:
1318:
1315:
1311:
1308:
1306:
1303:
1299:
1296:
1294:
1290:
1284:
1280:
1277:
1275:
1270:
1269:
1264:
1260:
1237:
1233:
1230:
1228:
1225:
1223:
1215:
1209:
1206:
1203:
1201:
1196:
1191:
1190:
1185:
1182:
1180:
1177:
1172:
1171:
1166:
1163:
1161:
1158:
1154:
1151:
1149:
1144:
1140:
1136:
1131:
1127:
1124:
1122:
1119:
1115:
1112:
1110:
1107:
1103:
1100:
1098:
1095:
1093:
1087:
1083:
1079:
1076:
1074:
1071:
1067:
1059:
1055:
1050:
1045:
1041:
1040:
1039:
1036:
1032:
1028:
1027:
1026:
1023:
1019:
1015:
1014:
1013:
1009:
1004:
999:
996:
990:
987:
982:
981:
980:
977:
976:
966:
960:
957:
953:
949:
948:
947:
944:
941:
938:
935:
931:
927:
923:
919:
915:
911:
906:
905:
904:
901:
900:
891:
887:
886:
884:
880:
876:
874:
871:
869:
864:
862:
856:
853:
852:
851:
838:
833:
825:
820:
819:
818:
813:
809:
801:
796:
795:
794:
791:
787:
782:
777:
775:
772:
769:
765:
764:
763:
758:
750:
745:
744:
743:
742:
739:
734:
730:
721:
718:
714:
709:
701:
697:
693:
688:
687:
686:
685:
682:
679:
674:
670:
667:
666:
661:
656:
648:
644:
639:
638:
637:
636:
633:
630:
626:
621:
617:
614:
596:
593:
588:
587:
586:
583:
578:
577:
576:
573:
570:
566:
562:
561:
560:
557:
554:
549:
542:
535:
531:
530:
529:
524:
516:
511:
510:
509:
506:
502:
501:
500:
495:
487:
482:
481:
480:
477:
473:
470:
469:
468:
465:
462:
455:
447:
444:
440:
437:
433:
432:
431:
428:
424:
420:
410:
407:
403:
399:
398:
397:
394:
390:
389:
388:
385:
382:
378:
374:
373:
372:
369:
365:
361:
357:
354:
349:
345:
344:
343:
342:
341:
338:
334:
331:
329:
326:
322:
318:
313:
309:
305:
301:
298:
296:
293:
289:
286:
284:
280:
276:
272:
269:
268:
264:
262:
261:
258:
254:
250:
246:
245:
242:
238:
234:
228:
225:
220:
219:
218:
217:
214:
209:
205:
204:
201:
197:
191:
189:
185:
181:
177:
175:
172:
169:
165:
163:
159:
157:
154:
151:
147:
144:
140:
138:
134:
132:
128:
127:
124:
116:
113:
111:
108:
106:
103:
101:
98:
96:
93:
91:
88:
86:
83:
81:
78:
76:
73:
71:
68:
66:
62:
61:
57:
56:ProtectionBot
54:
49:
45:
40:
37:
31:
30:
23:
19:
2213:
2210:
2196:
2190:
2184:
2175:
2168:
2144:
2138:
2103:steps in or
2098:
2053:
1997:
1987:
1978:
1932:
1912:
1902:
1856:
1802:
1777:
1762:safety valve
1698:
1685:
1681:
1675:
1653:
1649:
1614:
1605:
1600:
1588:
1576:
1568:
1556:RyanGerbil10
1551:
1530:
1503:
1477:
1472:
1445:
1426:
1414:
1390:
1375:
1355:
1343:
1321:
1309:
1297:
1278:
1267:
1262:
1231:
1221:
1213:
1204:
1187:
1183:
1169:
1164:
1152:
1130:Royalguard11
1125:
1113:
1101:
1091:
1085:
1081:
1077:
1070:Slowking Man
1043:
1017:
997:
970:
894:
867:
860:
854:
849:
799:
785:
780:
719:
695:
672:
668:
624:
619:
615:
538:
471:
445:
347:
332:
319:in place of
303:
299:
287:
270:
248:
247:
232:
231:
207:
206:
192:
179:
178:
173:
170:
167:
166:
161:
160:
155:
152:
149:
148:
142:
141:
136:
135:
130:
129:
122:
121:
64:
47:
35:
32:
2110:Betacommand
1736:Betacommand
1696:for now. —
427:Betacommand
233:Addendum 2:
2074:Flcelloguy
2012:Flcelloguy
1950:Flcelloguy
1833:Talk to Me
1767:Carcharoth
1753:Carcharoth
1714:parse text
1663:Carcharoth
1638:Carcharoth
1619:Carcharoth
1606:Crazytales
1515:Carcharoth
1493:Carcharoth
1310:Hallelujah
1143:Review Me!
1035:Carcharoth
824:Flcelloguy
749:Flcelloguy
700:Flcelloguy
647:Flcelloguy
643:Shadowbot2
548:c-uploaded
541:a template
515:Flcelloguy
486:Flcelloguy
454:C-uploaded
446:Question:
368:Carcharoth
337:Carcharoth
265:Discussion
133:Automatic
110:rights log
100:page moves
1743:How many
1536:Hipocrite
1504:Gimmetrow
1478:Gimmetrow
1380:Mackensen
1314:Patstuart
1184:Fuck yes.
1092:Cyde Weys
890:Main Page
800:currently
312:Main Page
208:Addendum:
184:Main Page
123:Operator:
105:block log
2227:Category
2199:xaosflux
2147:xaosflux
2038:and the
1805:xaosflux
1778:bbatsell
1701:xaosflux
1636:Thanks.
1593:Moreschi
1552:Support.
1443:Concur.
1419:Melchoir
1344:go ahead
1268:contribs
1170:bbatsell
1118:Masamage
973:xaosflux
897:xaosflux
861:Azer Red
80:contribs
20: |
2120:the RFA
1857:Prodego
1656:at the
1650:Comment
1615:Comment
1601:Support
1589:Support
1569:Support
1473:Comment
1427:Support
1415:Support
1396:Grandma
1376:Support
1356:Support
1329:HAIRBOY
1322:Support
1283:Ryūlóng
1205:Support
1165:Support
1153:Support
1106:Rebecca
998:Support
940:Zzyzx11
881:before
855:Support
768:Zzyzx11
720:Support
669:Comment
629:RockMFR
616:Comment
592:Ligulem
569:Zzyzx11
461:Zzyzx11
381:Zzyzx11
333:Comment
300:Support
292:Ligulem
288:Support
271:support
249:Update:
1913:cannot
1745:humans
1672:Trials
1531:Oppose
1383:(talk)
1342:Fine,
1218:ndonic
968:no? —
943:(Talk)
781:except
771:(Talk)
572:(Talk)
464:(Talk)
384:(Talk)
348:before
2176:Eagle
2139:trial
2081:note?
2054:Eagle
2019:note?
1957:note?
1884:inp23
1875:cabal
1749:robot
1690:beany
1581:oHelp
1447:: -->
1195:Help!
1086:again
1053:inp23
1046:now.
1031:learn
1007:inp23
924:, or
831:note?
786:would
756:note?
707:note?
678:Gurch
654:note?
620:human
534:a tag
522:note?
493:note?
171:(Y/N)
85:count
16:<
1880:Mart
1654:LOOK
1573:Here
1542:Talk
1463:<
1435:khoi
1432:Khoi
1401:ster
1368:talk
1238:. —
1139:Desk
1135:Talk
1049:Mart
1003:Mart
926:POTD
812:talk
733:talk
402:here
364:here
279:(𒁳)
186:and
164:N/A
115:flag
95:logs
75:talk
65:BRFA
2178:101
2171:RFA
2105:RfA
2056:101
1362:.--
1189:Guy
1157:Doc
1126:Yes
918:TFA
914:DYK
912:or
910:ITN
868:Si?
790:CBD
696:all
692:RfA
625:any
325:CBD
275:dab
239:.
198:.
90:SUL
2229::
2079:A
2017:A
1955:A
1836:•
1830:(
1783:¿?
1538:-
1429:.
1406:ka
1366:|
1364:cj
1348:DS
1346:.
1336:)
1291:)
1288:竜龍
1254:ar
1251:ik
1248:Sh
1245:rk
1242:Da
1175:¿?
922:SA
920:,
829:A
804:—
754:A
725:—
705:A
652:A
590:--
567:.
551:}}
545:{{
520:A
491:A
457:}}
451:{{
302:-
290:--
176:N
2084:)
2077:(
2022:)
2015:(
1960:)
1953:(
1842:)
1603:~
1577:T
1544:»
1540:«
1461:t
1459:n
1457:a
1455:i
1453:d
1451:a
1449:R
1334:☎
1332:(
1327:C
1285:(
1281:—
1263:/
1257:i
1222:O
1214:A
1197:)
1193:(
1145:)
1141:·
1137:·
1133:(
1128:-
936:.
834:)
827:(
814:)
810:(
759:)
752:(
735:)
731:(
710:)
703:(
657:)
650:(
553:.
525:)
518:(
496:)
489:(
174::
156::
117:)
63:(
50:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
