Knowledge (XXG) talk:Bots/Requests for approval/Archive 2

2381:

usernames, undoing "expired" page protection etc.) but at the same time, all these things which can be defined as a simple algorithm could be incorporated into Mediawiki and arguably done better than a bot could hope to achieve. (Pagemove rate could be limited, bad usernames could stopped being created, proper expiry could be add to page protection). The admin bot to date being Curps suffered many of the issues people object to in admin bots, it had false positives and was subject to scope creep (it started as a bad username blocking tool for a short term problem when we had a sustained attack of 100's/minute of dodgy usernames being created), and arguably redueced any urgency in dealing with those things being added to mediawiki. Of course the demise of the bot also didn't signal the end of the world, dodgy usernames haven't been a big problem, nor have we had a huge influx of pagemove vandals. For me the way Curps bot came about done was the "right" way, a bot implemented to resolve a short term problem against th users own account (maintaining a strong personal accountability), where it went wrong was that the functionality wasn't absorbed into mediawiki and the bot stopped. --

2457:

of reasons (i) by nature this is quite instance specific so probably best outside of the mainline code (ii) People would just mould theirnonsense around those rules until it got accepted. The latter has a risk of happening with a bot of this nature particularly if it deleted them quickly (though TB2s success perhaps demonstrates the intelligence (or lack thereof) of the average vandal). But early days yet a speedy tagging bot (or a parallel bot tagged speedy) might be interesting to see how well it performed. Alternatively it might be interesting to do something like this just listing up potentials on a page and work out later how many actually got tagged by someone, how many got missed by humans within a given timeframe, how many got tagged by humans but not the bot (perhaps a harder problem to solve, having to work through the delete log and try and work out which were speedies...) and how many shouldn't have been tagged, refine it repeat etc. then we'd have some hard number to demonstrate. --

578:, that is, succinct, with a predefined format that would include the name of the bot and links to the relevant discussion and, perhaps just to make it quicker, a diff to the edit in which an Approvals Group member gave the final endorsement (I always copy those into the "comment" section of the "makebot" tool). We don't need to protect it. We'd have instructions at the top (as we do at WP:CHU), which could include a list with the names of the members of the Approvals Group, explaining (if we decide to do it that way) that only members of the Approvals Group may post there requesting a flag for a bot. So, naturally, if someone else posts, we will deny the request immediately, or remove it from the page. 3432:, as to me personally it would be very useful to have that functionality - it would save me personally lots of menial work, which is what bots are for. I suspect that even if no one else except for me used that bot, it would still 'pay for itself' in time saved, after several months. If anyone else used it, it would be a bonus. But the real reason for my questions here is whether there is some procedural flaw that I am missing, that would preclude this proposed bot from ever being approved here, or whether someone has already built it and I missed it while going over the existing bot list. I am still waiting for an answer to either question. 1023:

longer any reason for it to NOT have a bot flag. Again, the point of the bot flag is not to make bot changes invisible. The point is to make people who don't care about them to have the ability to turn them off. That isn't to stop RC patrol from looking at bot edits to ensure their accuracy. The point is that *any* edits that do not need to be checked by vandalism patrols is good to have filtered out. I don't see why it needs to be checked by more eyes. THe pages that get archived have enough eyes as it is. If a mistake were made, it would be caught quickly, and almost always because of the users of those pages, not because of RC. --

519:

flagged. Since I seem to be sort of the "main" Bureaucrat on the "bot flagging front" for the moment, I'd like to say to the Approvals Group members mainly, but also to all users that may be concerned: please feel absolutely free to ping me directly on my talk page or even e-mail for your bot flagging needs ;) — although if you post only in one of those places, other Bureaucrats will not know about it, and thus won't be able to carry out the request if they come around before I do. But in any case, I'm at your disposal, so that we can get approved bots flagged as soon as possible. Cheers,

1822:(deindent)I wanted to add this note: An acceptable use for downloading 20,000 articles is for some task that is going to be used to improve Knowledge (XXG). It is perhaps not acceptable if the use is for some external use. I suppose it is a judgement call, but if I had to download 30,000 U.S. city articles, say, to fact check them and for other offline processing tasks, then it would be acceptable. But if I was downloading those same articles for another purpose unrelated to improving Knowledge (XXG) articles, then I would expect such a request to be denied. -- 1053:

option to not do so, thus by giving out bot flags we are giving people a facility to sweep under a lot of peoples radar. Bots like this if working properly (and provide the user acts resposibly with the account) I agree there is probably little concern about, the concern is in the opposite circumstance where the bot is malfunctioning or the owner is acting irresponsibly with the bot account. Given the impact of having an additional 2-10 edits show up a day versus the "risk" element, it doesn't appear to me to be a clear cut case either way. --

1118:(ec)As an aside, I was somewhat serious about my agenda. But no so much that I don't want to establish consensus. When the bot flag was first created, its purpose was to hide the rambot. My changes were not trivial in a large number of cases, but the flag was granted anyway. Anyway, I have a particular viewpoint of how the bot flag should be used. Other persons have a *totally* different perspective, perhaps from the newer Knowledge (XXG) era of not trusting anyone (so much for 841:

request, but I'd like to get some thought on what next to do. Should we just approve the bot? What about a bot flag, should it have one? I personally say, yes, that's what the bot flag is for, since all bot edits are additive and there is no compelling reason to not hide the bot edits. Essjay is trusted and it is my understanding that the actions being performed are not controversial, problematic, or overly complex, so thus it should be flagged. --

35: 1122:!). In any case, there is no written policy of when a bot flag should and should not be assigned although some discussion has already occurred, and we will at some point have to come to a consensus on this very issue, which is why I bring it up. I just think it important to keep in mind that the bot flag does not shield the bot from being checked. I myself sometimes do some RC patrol for bot edits. -- 2071:

at least as long as I've been around.) I'm doing it this way because I'd rather hand this work to someone who has done it before, rather than create a bot more or less from scratch & operate it myself for a one-time run. Is there anything I need to state in my request other than who will be running the bot? Do I need to create a special account for the bot to operate under? TIA,

301:

operations as minor to be filterable on RC; many operators like to run multiple tasks under their bot, sometimes these requrie them to be flagged as normal, sometimes not; unless an editor is making a single purpose bot, or a bot that will only ever do flaggable items, no need to flag it. Generally if their edits/min are going to be <3, they don't really need a flag either. —

3227:. This was only a very limited trial - when approved, the bot will add all the talk pages of all those articles (and images) which meet the requirements to a category - this is the reason that I've isolated this project, along with the potential for a huge number of edits (depending on overall quality of course, but could go into tens of thousands (spread out over weeks). 2355:

carefully limited situations - the trick is to provide a framework that allows us to get help in the day to day operation w/o raising more fears. We need to help people see that sysop bots are not a doomsday situation, they can help us keep this place running. Anyways, I've been in discussion w/ a few people re this and there's some progress being made --

2527:. Having automatic welcomes eliminates any personality from welcoming users. It defeats any real purpose of the welcome, and would probably create a lot of needless talk pages. That's not to say that welcoming isn't good, but I would much rather have you welcome users on an individual basis (rather than just pulling the new users feed). 3458:, which solves the problem "at source". If you want a more formal answer from the BAG (as against from here in the peanut gallery), you might consider filing an approval request, but specifying that the trial wouldn't begin at once, assuming it wouldn't be an excessively long period to hold the request 'open' for. 3278:

follow 3RR (or less, for safety), would leave clear edit summaries, etc. Of course once a prototype version is available, I plan to bring it here for approval (it would be run in manual mode until bullet proof), but I would appreciate getting preliminary comments prior to investing any serious effort. Thanks,

3467:

Thanks for the detailed response. Regarding the effort/benefit ratio, I think I can live with that, and the effort is (mostly) one-time, vs. hopefully a long period of benefits. Regarding the linkspam list, I think the issue there is that some linkspam is only posted (persistently) into one article,

2690:

This is fine, and does not need to go through bot requests, its no more of a load then clicking on Random Article 3x a min. If this will start doing high speed pulls/recursive pulls/or continuous operations then send it in as a bot request, and as Tawker mentioned above, running from the tool server

1379:

changes. While I could do all those tedious, repetitive changes with my own account, I decided it would be easier to keep them separately. That way my watchlist doesn't get bogged and my edit history is easier to track. While AWB is by no means an automatic bot (it does not make changes automatically

1197:

You're points are well taken, and I apologize for "drawing you in". I would like to get the opinions of others as well, so a statement from everyone is helpful to try to determine consensus on this issue (if it exists). I'd agree with next to everything that you've said, as it is quite reasonable.

1163:

One argument to this would be of course that we don't filter flag normal editors as bots, because part of RC is also because people may actually be genuinely interested in the changes from a non-vandalism hunting perspective. The nature of the filtering which is all or nothing, whereas I would have a

2714:

I've got a similar read-only question. I have a couple of things in mind, including an anti-linkspam monitor, that could use a real-time feed of recent changes. I'm aware of the IRC channel, and built a parser for that, but I'd also like to get the content of the change. Does somebody already have a

2456:

Sounds reasonable. Of course this could be worked into MW, if you can code a set of rules in a bot that same set of rule could be coded into MW to stop the page being created in the first place. The question would be could it be done better there, on first thoughts I'm not sure it could for a couple

2436:

Editing protected pages, very few things are that urgent they won't wait until protection is removed (it's almost always temporary) or the few problem pages done manually. (This is actually a problem for some of our substing bots dealing with userpages which have since been protected due to abuse by

2316:

Well, first off, you need a pressing need for a bot with sysop privileges. The TawkerbotTorA wasn't one, as the vandalism from Tor proxies, as well as the advice to Chinese users, contradicted the stated need. Also, you need to assert whether something can only be done via an admin bot; if coding an

2254:

is lacking definition of what actions can or should be allowed to be automatically performed by admin accounts. Please note it is WAY to earlier to have a poll or !vote on this yet, but it's certainly time to have an open discussion with the community. Please voice your opinions! Some topics that

1967:

I don't see an need for more members at this time. Perhaps the procedure could be fined tuned. I often want to wait at least a bit for comments by other BAG memembers or outsiders. Also, many bot owners do not respond to the trials after a while, so I am not sure what I can do there, other than wait

1904:

increased the speed of approvals. The next step is to perhaps establish a more stable process for adding new members. Since you (alphachimp) only just barely missed joining the approvals group, perhaps by the time policy is established there will be sufficient evidence to support adding you to the

1727:

If it's going to be a one-time thing, there shouldn't be any problem: it's too small a set for downloading a database dump to be worthwhile. As a point of comparison, OrphanBot downloads between 2000 and 4000 pages a day through the edit interface, and 4800 pages a day through Special:Export, which

957:

is supposed to do). I don't know where this was previously discussed or how it was approved. Perhaps it wasn't approved. In any case, I don't see a problem with it at this point. The issue at hand is what to do since 1) Essjay is inactive while his bot continues to run, 2) the bot runs without a

515:

Hi all. About the delay in flagging approved bots: for most of the Bureacrat-related duties, there's a little delay. Even in RfA, which is the more "critical" of everything Bureaucrats do, there can be some delay. That's a side effect of the fact that the Bureaucrat group is supposed to be a small

334:

We could probably do away with the log. The bot flagging log coveres a good deal of them. The rest, and the flagged ones to, should be easily quered by looking at the arthives since they just use the bot's name anyway, its not like its hard to find. Also, we should enourage people to link to them on

3363:

for vandal and linkspam protection. My plan is to implement it in perl. Do you, or does anyone else, see a problem with that concept? I know I myself need it as a user, but I don't want to invest the effort in it if it's already done somewhere, or if it violates some fundamental bot rule and has no

3158:

four requests for extra tasks on MartinBotII to make, all relating to wikiprojects. To avoid spamming the BRFA page, should I put the the three really simple tasks (which don't edit the mainspace) in one request, and the other (which, at most, involves putting article talk pages in categories, and

2629:

Hello, I was wondering, do I need approval for a bot that reads wikipedia(not excessivly, around 3 requests per minute) but does not write/change? I am thinking of a script that find potentially bad edits, but in such a way that automatic changes would be bad as it is not accurate, and simply gives

2070:

I want to get permission to run a bot to add about 1300 articles I'm writing. The situation is fairly straightforward but there's one small hitch: the bot will be run by another Wikipedian on my behalf. (BTW, I believe he's trustworthy, seeing how he's been a positive contributor to the project for

1086:

Essjay is a bureaucrat, so obviously we have *no* concern about acting irresponsibly. If that were the case, the bot flag would be the least of anyone's concern. If it was a different user I'd perhaps feel differently. Since bot edits are additive and the pages edited are high profile pages with

452:

If a bot is performing such complex tasks, then it may make sense to run it without a flag, provided that it isn't performing large number of edits frequently. But my opinion is to avoid running WITHOUT a flag as much as possible. Someone can still look at bot edits in RC if they want to, but the

300:

work. If flags aren't involved, we don't need to get crats involved, so the Requests bot flags may be useful. I've updated the approved section of this request page to say approved for oepratiosn, incstead of approved for flag, as not all of them will need to be flagged. Most bots can flag their

3222:

and does the same sort of thing as MathBot, except that all features aren't yet implemented. The main difference is that, in its tables, it only lists articles which have been rated by a wikiprject and achieve a score based on calculations done by the bot based on the rating and importance of the

2451:

An idea was discussed a bit in the -admins channel re dealing with vandalism new pages (aka G1, the super super obvious stuff) - essentially if it fit a modified set of criteria for Tawkerbot2 and eventually (after running it in add to a speedy delete list for a while... and approval) an automatic

2331:

Assistance scripts seem absolutely OK for me. For instance, VoA's script includes a rollback all tool, a delete all page creations tool and a block all AOL button. Those are controlled by humans, they just speed up a few very tedious processes. I'd encourage development of this type of admin tool.

2081:

GFDL is the biggest thing to worry about here, if 1300 new articles are created, they will be licensed under the account that creates them, a new bot account may be approriate, with it giving attribution to you, the bot owner. If your helper is simply facilitating the technology of running "your"

1741:

This is an interesting question and response. I have thought about downloading a subset of Knowledge (XXG) (probably in the few times 10000 page range) for my own private uses with refreshes to my local copy every few months. I have had in mind working from the database dumps, but Special:Export

316:

Even if it is less than 3 per minute, they should still have a flag. These types of things are additive: One or two bots isn't a problem, but add them all together and it passed the threshold. It is work that doesn't need to show up in RC normally, minor or not. Vandals can use "minor edit" as

3277:

The sites that are 'guarded' would normally be a very small number (like someone's small watch list) and each could have its own custom set of 'typical' vandal strings/regexps, and/or its own set of blacklisted external link sites. All reversions would include Talk page message to the user, would

2578:

Perhaps, following on for Xaosflux's idea, we could do a bot wo find users who have x edits and who haven't been welcomed, and either give them an information message, or add them to a list of un welcomed users, for humans to welcome. The problem I see with this is finding out whither a user has

2547:

As already said really it'd take away the personal touch. (MediaWiki could easily set up and initial talk page with and initial message on account creation). It also suffers as we get with some users who scatter gun welcomes by going through the new user welcome log, things such as users who have

1803:

I agree. The robots.txt instructions should be followed no matter what. I can't think of any case where it would be acceptable to violate this. So long as the access is reads (as in the case of downloading) and not writes and limited to a one time action, I don't have a problem. The fact that

1773:

Yes, I expect this to be a one-time thing, and no, I don't plan to be uploading them again. I had figured by the percentages that it wouldn't be a massive chunk, proportionally speaking, but I didn't know if in absolute terms it would still pose an overload. (I can also distribute the downloads

840:

is running. It seems like this bot never made it through the process and does not have a bot flag. Granted it only runs 2 - 10 edits per day, but this is a unique situation with a bot approvals group member apparently approving their own bot. At minimum we should do something about the expired

1159:

is also not a call to shut your eyes and hope, we aren't insulting anybody or suggesting bad faith by presenting their bot edits without the bot flag, the same way we aren't with their regular edits. I'm not assuming anyone/everyone will turn rogue otherwise I'd suggest that we never bot flagged

1022:

when it was approved, and I see that you, Essjay, and Xaosflux all were in agreement about it having no flag. Still, at this point the changes made by the bot can be considered trivial and/or low-risk, as it has been making these changes for months now without incident, AFAIK. IMO, there is no

681:

From my perspective I don't see how anything more is needed than this page. Now that there is an active approvals group we all know to watch this page. Since bots are linked in the approvals section when approved (with the needed link to the approval etc), all we have to do it watchlist this one

580:

In fact, this page should have two sections: one, and by far the busier one, would be to grant flags to approved bots; the other would be one to request removal of the flags from bots that have either lost endorsement or whose opperator simply decide to "debot" (this one may not be restricted to

1202:

are quite good. If I might nitpick some more, in the case of Essjay, archiving pages is to me almost on the order of interwiki links. They are being archived because no one cares about the discussion anymore. If people were still interesting in seeing those changes on RC, they'd have taken a

1052:

I don't intend to argue the point beyond this, because ultimately it makes little or no difference to me, and the owner of the bot was of course more than capable of flaging the bot. I disagree slightly with your view on this in that many people will ignore bot flagged edits regardless of their

3453:

Per-article customisation is an interesting idea, and could in theory capture persistent vandalism on a particular article that it's not practical or "safe" to revert in general. I think VoA may well be correct, though, that doing it this way could involve a lot of work, for relatively little

2380:

All of those in generality require some level of intelligence and discretion, there isn't a simple algorithm to determine when those actions should be taken. There are of course instances where a subset can be defined within the scope of a bot. (e.g. blocking page move vandals, blocking dodgy

2354:

What we need is a framework for approving such tasks that need to run under unique accounts. Currently any sort of proposal to run an automated tool "legally" on a seperate account gets a huge share of "admin bots are scary" type !votes. Bots w/ elevated access can help us out if we provide

518:

For my part, I've got all of the bot-related forums on my watchlist, but because of the high traffic, I'm seldom lucky enough to see an "approved" edit when I access my watchlist. I know it's a little more work, but posting to our Noticeboard is indeed the quickest way to get an approved bot

101:

Its been over a week since the last post to it, I have beta-tested it and it works, and all the complaints have been resolved, but as of the moment nothing seems to be happening with regards to approving it or even giving me information about anything I have to change to get it approved. —

1958:. The actual approval itself is a normally simple process of determining consensus and appropriateness and then making it official. The bulk of discussion can be performed by *anyone*. We have more need for community input in general than we do for additional approval group members. -- 3468:

and I am not sure if it would instantly qualify for the global blacklist, although it may eventually. Regarding the application in a 'hold mode', I think I'll take a chance on the 'peanut gallery', enough to whip up a basic prototype, which I can then submit for approval. Thanks again,

2466:

And a downside. New page patrol is more than just tagging speedies, it's also tagging stubs, cleanup etc. etc. So even if the bot tagged them chances are someone would/shuld still look at them anyway, though longer term that might be an argument to let it go straight for the delete...

2680:

Thanks for the info. In answer to Xaosflux's question it would be ran once, produce a few urls to questionable diffs, then stop. Once I have manually delt with the diffs I may run it again if needed. So I guess what I am saying is that it will not be on wikipedia more than I am.

240:

Just remember that this page is open to community input, so we like to wait a few days for that and also just to be a bit sure. I'd rather not just approve anything that seems good shortly after the request. On the other hand, we should not get tied up for a week+ for each

273:. These two pages basically do the same thing. I'm going to merge these pages together, and we'll have to sort it out later. It is just too much hassle to update TWO pages AND the archive AND the requests for approval page. I'm just going to slim down the process. -- 2760:

I don't know, but I seem to recall Brion somewhere said that a sequence of very close load requests can cause further requests not to be served. However, robots.txt contains a delay of 1 sec for crawlers, so probably he was referring to a delay of this order. Probably

1941:, we really do care about community input. Bot approvals oftentimes run faster if they include links to other project pages where the bot was requested and/or a few supporters to come in on the proposal. Yes some bot requests are speedy, but that is not the rule. — 992:

I've sorted out the pages. The point in the bot flag is to not clog up recent changes with minor(ish) edits, the nature of this bot doesn't tally with that rationale, low edit count bots tend not to be flagged so they do have the transparency of appearing in RC.

2509:

This wouldn't be that hard to code, but the real question is it really usefull. Giving every new user the same generic message may take away from the welcoming aspect. Perhaps if only done to new suers after x edits who have not already been welcomed...? —

1751:

Off the cuff, 20000 articles is substantial, but not determetial. How often would this be downloaded, and how quickly? Also once downloaded, what do you plan on doing with it? UPLOADING changed to 20000 pages rapidly would certainly be an issue. —

3454:

benefit, but I don't think that's a basis on which the bot would fail to be approved on (wherein the principle is basically, prevention of bots doing harm). Also bear in mind that for linkspam that should be blacklisted in the general caes, there's

1909:

and not just by approval group members. Feel free to add your thoughts, comments, and ideas. As for me, I don't think I really understood how time consuming approving bots can be. Good thing we don't have to rely on 1 or 2 members anymore. --

1164:

fair guess that the majority of people aren't interested in seeing (say) interwiki links being added/removed, I'm not so sure I cam say the same of every bot task. Part of the equation also has to be if the edits "logically" fit as bot edits. --

2715:

richer feed? If not, I'm like to build and publish one. For that, should I get approval before I start development? In load it would be no worse than some of the vandal-fighting tools, but at one fetch per edit, it's still not small. Thanks,

2452:

speedy. The rough thought had a pretty warm reception on -admins - It might be something worth exploring (I talk msg'd xaosflux and how I post here :) (I can't see how we could integrate it into MW atm) -- Tawker 00:42, 17 October 2006 (UTC)

2437:

the blocked user, which I guess will never be deprotected, though again there is a question of is it really that important? many of those pages will never be viewed again, certainly not often enough to concern ourselves about server load)

2148:

Yeah, I know about the election: I voted in it. I'll wait if you are in the process of designing a new procedure, otherwise we could just do it informally, or have another election. I'm in no rush, just wanted to help out if possible.

3489:). A day later, I added a section for possible tasks to do (e.g. template substitution) if there were no redirects to fix, but never got a response either way. I'm a bit confused on whether it should run these tasks or not, however. 1295:

Your bot will soon be granted the bot flag and then you will be free to operate your bot as requested. So long as the task doesn't change, you won't need to bother with this approval page again. As soon as the page is approved

2209:

Hi - I've been running a "short trail" of AMABot (which seems to have become a bit of a bigger trail, after some starting problems (caused by lightning)), and after a few days of continuous operation I posted some diffs to the

1832:

Thank you for the note; I am certainly in accord with those sentiments. (Having had to maintain servers myself, I fully sympathise with the desire to avoid overloading them!) My plan stemmed from an idea I proposed to

1203:

vested interest in the discussion. I can't imagine why anyone would want to know from RC whether talk pages have been archived. A watchlist entry would be a *much* better alternative than trying to find it in RC! --

1523:

it wouldn't work. Not quite sure if you make another bot page for a new function or just add the new request to the approval page. Though using {{SUBPAGENAME}} is very useful so the user only has to type the bot name

534:

about them. Perhaps we could have a SHORT page that lists bots that need flags, linking to their page where we already approved their operation AND flagging, once flagged, a crat could just mark it on the page? —

405:

Sounds reasonable RM, we (the BAG) should come up with a good standard threshold for flag/no flag (other then obvious reasons for no flag). I think we could go overboard with flagging though if we're too loose. —

2037:

Looks like we've had our share of time managing the interwiki links transcluded on here versions on here, is anyone familiar enough with the interwiki py framework to know if there is an 'ignore this page' tag? —

2750:

Ah, thanks. That may be close enough. I had always assumed the Recentchanges RSS had the same info as the page, so I hadn't looked at it. Do I need any bot-ish blessing to hit that page very frequently? Thanks,

2828:

Sounds fine. When the bot request was approved initially we wanted to be useful while not getting in the way, but if those users who are most involved in the process want otherwise, that's fine. I'll update

179:

Yeah, I'm balancing trying to get the hang of the approval group responsibilities on a weekend when I'd like to do a few other things. But at least the whole process is now *faster* than it was before. --

2434:

doesn't work for en wiki, though again if there was a need for that many that a bot would be required, I guess there would have to be the question about shouldn't MediaWiki do it better in the first place.

1863:

My new bot request has not been acted on for over 2 days, despite the new approvals group members. Any chance of taking a look? (I'll reiterate my offer to help with bot approvals if need be...) Thanks.

1881:

Well you normally should get comments within the first day, but we like to wait a bit for some bots before approving, either per questions, trials, or community input. Though there is sometimes a delay.

2343:

Anything done by an assistance script should be treated as if it had been done the slow way. That means you'd better be sure your script isn't going to screw up and block Jimbo for seventeen years. --

424:

is too much paperwork how about not using it altogether instead of merging it to some place? (tag it inactive and leave it there for historical purposes) Just like the old archives in the BRFA page. --

1786:

suggests a throttle rate of 1 per second. If you're willing to spend 20000 seconds downloading, I wouldn't think it would be a problem. (20000 seconds is 5.5555555555556 hours, according to #expr). --

2012:

I think tha existance of the BAG has discouraged comment from non-BAG users. Basically we trust the BAG folk, so don't comment, BAg are waiting for comments to provide an indication of consensus...

265:

Ironically, after all the attention my recent RfB brought (so that I could set bot flags), the recent approved bots were not quickly set. Perhaps some of this is a problem with the two pages:

899: 1919:

A whole two days doesn't seem that long to me, I haven't looked at the request, but in general I can't imagine anything being that urgent, people wait longer for page moves at times... --

2667:- it's much better suited for read only access. If it's vandal detecting patterns feel free to gimmie a shout over them, if they make sense we can throw em in an autoreverto bot :) -- 2810:), so that unlisted copyright violations are listed together with the others rather than on a separate page. The people dealing with this backlog appear to prefer the bot doing this. 2484:

I would like to know if i can get somebody else's bot or request my own bot to give welcome messages to newcomers. I don't know any programming language as well. Is this possible.--

85: 80: 75: 63: 296:

I think the pages are a mess, I don't like the Log page at all. All approved bots are already in the archives here, and the operators summarize them on the Bots page. Too much

3122: 2243: 2168:

Same goes for me. I've shied away from this page a bit since the "election" (I'm not going to lie, it was a bit discouraging), but I'd be willing to help out in any way needed.

1536:

I've done some more tweaks to the template, and I'll probably make a few more later. At the moment, I added support to the template for alternate functions. The code below...

796: 3638:

I have blocked Betacommand for 1 week for operating an unapproved deletion bot. If I am somehow wildly mistaken and this behavior was properly authorized please correct me.

3191:

Do the same as task 2 on MartinBotII (approved), but for other Wikiprojects (per requests), using exactly the same system, just different message, recipient and opt-out pages

1928:

My general feeling is that waiting is never a great thing. But that said, being a monday with Knowledge (XXG) under heavy load, the bot wasn't/shouldn't operated anyway. --

623:

Yes! I had completely forgotten about that proposal. So we just need to rekindle it, maybe "revamp it" a bit. In fact, I suggest we move the discussion to its talk page.

3025: 505:. It wasn't being used by bureaucrats anyway and it was just extra documentation. We may come up with an alternative at a later point, but for now it's just overhead. -- 2939:

I like the idea. Bot requests is very formal. Discussions are very specific to new proposals. A notice board could be a informal place to discuss all kinds of things. --

1406:

change manually, you don't technically need a bot flag (but having an account named "bot" isn't such a good idea in that case). If you're using the auto-save feature you

1272: 320:

I've held off on merging the pages for now, as we can probably have a fun discussion about it. I'm going to just be bold and try a few things though, see what happens :)

317:

well, so the bot flag helps in all vandalism patrol. But yes, there are a few cases where not having a bot flag is great, but that is probably the exception to the rule.

3615: 3486: 3078: 2247: 433:

My standard would be "does this bot really need to be watched?" such as an antivandal bot or some other bot that deals with varying, almost human-level, complex tasks.

376:

That'd be a great idea, especially with the new template/transclusion system on the page. I'd like to see a link to each individual request and approval for each bot.

1555: 162::p Seriously though, there is a lot of backlog, but we jsut got several new approvers, we are working on clearing the backlog, as well as streamlining the process. — 2637:

based useragents. I could easily spoof a common set of headers, but I want to know if passive, gentle(slow) automatic reading of wikipedia needs special permsision.

1087:

lots of users checking the history, I think a bot flag makes sense here, but because of the low number of edits, I also do not feel like it *has* to be that way. --

2830: 2135:(See Archive2 above), and have not really come up with a policy/proceedure for adding more members (We need it though) Guess it's time to reopen talks on that. — 3544: 3195: 2211: 1687:

I read in the policy that "bots that download substantial portions of the page database are prohibited". Out of curiosity, would roughly 20,000 articles — the

3258:

Is there a centralized place for someone to propose (not to request) a bot that doesn't yet exist, to get the equivalent of a pre-implementation design review?

3288:

This seems similar to my second bot, which goes after shared IPs and suspicious new users (likely socks) to a watchlist, along with link spam revert ability.

2650:

How often would this be run, e.g. only when you are browsing, all day everyday, or someone in between? For the most part, this is pretty much acceptable. —

1954:

This is an excellent point. Obviously in the case of alphachimp, he couldn't very well comment on his own bot, but *anyone* can participate in the approval

21: 3223:

article. For the tests thus far, all those articles which have achieved the minimum score on the wikiprjects which were tested were put into sub-pages of

2548:

never edited, users who were rapidly blocked as vandalism only accounts and users with wildly inappropriate usernames who all have welcome messages... --

953:(ec)It appears as if the request above was for *additional* functionality, to do user pages in addition to project talk pages (which is apparently what 3218:

These are the non-mainspace (talk) edtting tasks, which are fairly simple. All have been fully tested, as shown by the diffs. The other task is for

1520: 3351:

I read the external 'specs' available at your bot page. If it supports specific tools for EL enforcement (by specifiying blacklisted linked sites

2911:

Yes, of course, we can have links to there from the top of the noticeboard. But there may be discussions that don't really fit on any talk page.--

1297: 750: 1478: 2111:

and pywikipedia. I have been following this page quite a lot and have a pretty good idea about what is and what is not acceptable for a bot. —

1458: 958:

bot flag, and 3) the request above appears to be what EssjayBot III is designed to do, but not approved for, so maybe we should approve it. --

1906: 3060: 2979: 2192:

I also would be willing to help when you are ready, just message me. I have skills with webbots, and and understanding of wikipedia policy.

3389:

My bot only gets 20-80 edits/day usually (now its at a low point). If it only watched single pages it would probably be of very little use.

1615: 1473: 2793: 1410:

need a bot flag. Also, if you're doing a lot of edits at speed a bot flag would be a good idea so that you don't flood recent changes. --

1281: 1155:

is certainly not an issue here, as the owner of the bot is in a fairly trusted position, checkuser, boardvote, oversight etc. That said

3570:

TaeBot, TheJoshBot, Huzzlet the bot all didn't have any discussions for weeks, are they going to expire or stay on the list longer? --

3159:

which runs similarly to MathBot) in another? Or all four together? I'm not sure what the norm is for this - any input appreciated.

2579:

been welcomed if they have deleted the message from their page - perhaps we'ed need to look for empty talk pages. Just a few ideas -

1248: 1230:

I am not sure how the approval works, and I can't find any description on what you want me to do after I have done a trial run for my

802: 226: 131: 3590: 1508: 197:

now? It seems to have been flipping back and forth lately, but now not only a guideline, but policy?! This is getting insane! —

746: 1242: 1018:

Well, since I've just recently been pushing my agenda on the usage of bot flags, that's why I brought it up ;-) I looked at the

485:

Yes, that's pretty much what I was trying to say. Faster, larger bots need flags. Slower, complex bots shouldn't have them. --

2297:

members should be a requirement here, as well as the support and approval of the community to ammend the Bot Policy. Thanks! —

1804:

permission was sought suggests good will. I wouldn't consider this to be precedent so that *anyone* could do this, however. --

466:

If the tasks are too complex, regardless of edit amount, it should not be flagged. If its that risky it needs to be slowed down.

1493: 1621: 1561: 1384:

has pointed out to me that perhaps I would have to be approved by this body first, before I use that account. Is it needed?

933: 502: 421: 270: 2807: 2493: 742: 715:

Cross-listing this discussion is probably counter-productive. So if you would, please see my answer to your question on

599: 284: 266: 3558: 2572: 2425: 1797: 863: 3037: 2414:

is an admin action too (I'm not sure about enwiki), and I can imagine mass transwikis taking place quite easily too. --

581:

Approvals Group members, since bot opperators may wish to relinquish their bots' flag themselves). Just a few ideas.

2815: 2770: 2738: 2407: 1717: 1260: 3261:

On the assumption that this is the place (for now), my idea is to write a bot (in perl) that can revert in two modes:

3254:

I have not used or written a WP bot before (except simple read-only for analysis) and I have a couple of questions:

2603: 1488: 875: 42: 3661: 3651: 3628: 3601: 3584: 3574: 3537: 3518: 3507: 3495: 3472: 3462: 3436: 3403: 3368: 3334: 3311: 3302: 3282: 3241: 3183: 3173: 3143: 3133: 3108: 3095: 3085: 3048: 3007: 2996: 2973: 2954: 2926: 2917: 2906: 2883: 2872: 2864:) Many bot operators are off-wiki, and rely on interwiki talk page links to their operators on other projects. — 2854: 2837: 2822: 2777: 2755: 2745: 2719: 2699: 2685: 2671: 2658: 2644: 2614: 2597: 2552: 2542: 2533: 2518: 2503: 2471: 2461: 2443: 2385: 2359: 2347: 2338: 2326: 2305: 2232: 2196: 2183: 2174: 2163: 2143: 2125: 2090: 2075: 2056: 2046: 1995: 1982: 1962: 1949: 1932: 1923: 1914: 1895: 1875: 1852: 1826: 1808: 1778: 1760: 1746: 1732: 1720: 1707: 1676: 1530: 1442: 1414: 1396: 1361: 1304: 1289: 1207: 1168: 1126: 1091: 1057: 1027: 997: 977: 962: 940: 921: 845: 778: 757: 723: 686: 656: 627: 606: 585: 565: 552: 543: 523: 509: 489: 480: 461: 447: 428: 414: 387: 371: 358: 349: 329: 309: 291: 277: 255: 234: 184: 170: 153: 139: 2017: 893: 881: 2889: 1483: 3232: 3164: 2765:

is one of the best people to ask, since he's running an anti-vandalism bot (which I presume uses these feeds).

2586: 2221: 1987:

I've taken to moving pinging the operators talk on them, and moving to expired if no response in a few days. —

869: 528:

Thanks! It's good to see the some 'crats are interested in keeping up with these pages, I also got a note from

3198:

list of articles by editting sub-pages of that, based on which article talk pages contain the project banner (

1468: 2640:

Sorry if a document already explains the answer, I have read so many and I know I have missed a few. Thanks!

3626: 3091:

Probably a f*ckup. The bot was approved. Would a friendly bureacrat please flag it? Muchos gracias (sic). --

1285: 887: 749:. I reallize there is a merge proposal for the latter two, but what's the need for more than even one page? 3594: 2406:

The last in particular doesn't seem wildly inappropriate for a bot; I can certainly imagine a bot updating

363:

Certainly agree, perhaps a bot requirement should be a link to it's approval somewhere on its user page? —

3391: 3322: 3290: 3224: 2396: 1970: 1883: 1430: 1351: 1254: 468: 435: 337: 243: 221: 126: 2321: 51: 17: 3359:

then I can't find that either. Those are the 2 main missions I see for my proposed bots - customization

548:

Presuming all group members are admins (which they ought to be), best make it a fully protected page? --

2103:

Hi guys: I was curious, does anyone object to me being on the Bot Approvals group? I've been running

917:

Looks like a screw up the tasks page is actually talking about EssjayBot III, II was approved IIRC. --

741:

De-indent. No, no, that's not what I was referring to. What I mean is the discussion about this page,

2528: 2410:(although I don't think we have a need for such a bot at the moment). On some other Wikimedia wikis, 2333: 2179:

Personally, I'm in favour of an existing BAG member approves you're in.... that makes sense to me --

2169: 2014: 1841: 1700: 1236: 2439:

And as you say, I can't think of a situation requiring automation for editing media wiki messages.--

2317:

extension is feasible, then go for that instead. IMO, sysopbots should be the absolute last resort.

1713:

Does 20,000 out of 1,395,974 (~1.4%) seem like a "substantial" portion to you? It doesn't to me. --

189:

Thanks for the info. I just felt like nothing was happening, but now its nice to know why ;). And

3648: 3237: 3169: 3033: 2752: 2716: 1900:

We could clearly use more members to the approvals group, although the addition of new members has

1743: 1341: 1329: 3205:

Produce a list of all wikiproject pages for the WikiProject Directory, displaying them in a table

2524: 516:

one, for security reasons. Currently, with Essjay inactive, we are a little more busy than usual.

3619: 3131: 3046: 3029: 2870: 2697: 2656: 2612: 2516: 2303: 2141: 2088: 2044: 1993: 1947: 1758: 1393: 1277: 954: 774:

Bot flag is assigned quickly and without much fuss. Much smarter way of doing things IMHO :) --

541: 412: 369: 307: 168: 1848:

respectively; I hope, but cannot guarantee, that it will redound to Knowledge (XXG)'s benefit.

159: 2364:

A good start would be to define what admin tasks a bot can sensibly do. Admin buttons are for:

973:

On second thought, we shouldn't approve EssjayBot III since it doesn't appear to be tested. --

283:

There are some bots who are approved but do not require a flag, thus not suitable to be put at

3003: 2991: 2968: 2947: 2913: 2901: 2879: 2850: 2801: 2557:

I have nearly all of the user-talk messages stored in my user scripts for rapid use, except {{

2489: 2158: 2120: 1845: 1696: 1526: 791: 198: 150: 103: 3081:) but appearently not yet being flagged nor is it in any of the archives. What's going on? -- 2861: 2251: 3581: 3555: 3504: 2569: 2558: 2422: 2053: 1794: 1452:

Just to inform everyone that I updated the template for bot requests with a new template -

1381: 1358: 1319: 857: 562: 355: 2704: 2294: 2108: 2097: 1938: 1376: 1271:, but I was approved to do a trial run which I have now completed, and added a note on the 1156: 1152: 1119: 575: 574:

Nichalp had mentioned a new forum as well. I like the idea. Something along the lines of

190: 146: 3657:

Just an update for everyone's information: there was no bot involved in this incident. --

2811: 2766: 2734: 1865: 1834: 1714: 1231: 1160:

anyone and I wouldn't by default exclude bot edits in the IRC bot I run for several wikis.

377: 3642: 716: 649: 3571: 3317: 3229: 3161: 3082: 3067: 2591: 2581: 2431: 2411: 2226: 2216: 652:

until we finish up the backlog and have a chance to work more closely on that page. --

425: 288: 3455: 3219: 3180: 3140: 3126: 3092: 3041: 2923: 2865: 2692: 2682: 2651: 2641: 2607: 2549: 2511: 2468: 2458: 2440: 2382: 2344: 2298: 2193: 2136: 2083: 2039: 1988: 1942: 1920: 1753: 1729: 1695:

coverage — count as a "substantial portion"? Background to my question can be found

1610: 1550: 1411: 1390: 1372: 1165: 1054: 994: 918: 682:

page. I'd much prefer that to another redundant page unless I'm missing something. -

549: 536: 407: 364: 302: 163: 3658: 3534: 3514: 3491: 3469: 3433: 3365: 3308: 3279: 2984: 2961: 2940: 2894: 2834: 2797: 2539: 2485: 2151: 2113: 2104: 2072: 1959: 1929: 1911: 1849: 1838: 1823: 1805: 1775: 1704: 1673: 1337:

code along with the cat for the discussion I thought that might be better than the

1301: 1204: 1123: 1088: 1024: 974: 959: 937: 905: 842: 720: 653: 603: 529: 506: 486: 458: 326: 274: 181: 3036:

is already indef blocked, and does not hold a bot flag, I've removed its entry on

2498: 2538:

I'll second this. It is an interesting idea, but not really a practical one. --

3598: 3552: 3548: 3355:) then I can't find it. If it supports custom regexps for vandal edit detection 2877:

Just be a general place for bot owners to discuss current bots/jobs/ideas etc.--

2762: 2668: 2566: 2562: 2419: 2415: 2356: 2318: 2180: 1791: 1787: 1692: 1426: 852: 775: 754: 683: 50:

If you wish to start a new discussion or revive an old one, please do so on the

2922:

If you want it, be bold and create it. You don't need anyone's permission :) --

3105: 2819: 2774: 2742: 2664: 2022: 624: 582: 520: 3597:), we have been waiting patiently for approval so the conversion can be made. 2214:. I'm not sure what happens next/what I need to do - any help appreciated. 2082:

bot, it should be ok, though you will be responsible for anything it does. —

3459: 1728:

doesn't seem to be having a major impact on Knowledge (XXG)'s operations. --

1541:*{{botlinks|Zorglbot|2}} ''In trial period as of 07-Sep-2006'' (''Task 2'') 3032:

may no longer operate bot accounts, nor use their user account as a bot.

3268:

Vandal mode: by looking for specific strings and regular expressions; and

2731:

http://en.wikipedia.org/search/?title=Special:Recentchanges&feed=atom

1742:

might be more practical if traffic on this scale doesn't bother people.

1539:*{{botlinks|Zorglbot}} ''In trial period as of 07-Sep-2006'' (''Task 1'') 3271:

Linkspam mode: by looking for links to web sites that are on a blacklist

2959:

You're right, I changed my mind. A noticeboard would be a good thing. —

2796:

and an explicit request on my talk page, I have changed the behavior of

2727:

http://en.wikipedia.org/search/?title=Special:Recentchanges&feed=rss

2633:

I only ask this as it seems wikipedia refuses clients with unknown, or

1688: 2630:

me(a human with an account in good standing) a list of urls to diffs.

1519:

I was going to use {{SUBPAGENAME}} but if users created pages such as

2892:

to discuss ideas for bots, and this page to talk about other stuff. —

1672:

Hopefully this should solve the current problems with the system. --

3307:

Do you have a link to its specs that I can read? Is it Open Source?

2561:}} and similar; IMO the personal aspect of welcomes is important. -- 2267:

The potential for approval of single-purpose robotic admin accounts

936:), perhaps you could shed some light on why it has no bot flag? -- 904:

has been inactive for quite some time now with no explanation... —

3533:

please add someone who knows how to, the ] to the list - thanks --

3001:

Added first discussion, someone beat me to creating {{botnav}}.--

851:

I am tempted to agree with you on this one, but it must be noted

2634: 2025: 1774:

over time to reduce the stress.) Thanks for the information.

1516:

at the top. Thought it might be very convenient for all users.

2264:

The running of an automated process by existing admin accoutns

1521:

Knowledge (XXG):Bots/Requests for approval/AP.BOT 2nd function

29: 3364:

chance for approval here. Any comments would be appreciated.

2261:

The running of an assitance script by existing admin accounts

2250:

have involved this topic, it's become pretty clear that the

1783: 1198:

I apologize for invoking AGF inappropriately. Your points

3618:. May I request somebody in BAG to have a look. Thanks -- 3125:

to help determine approvals for this request. Thanks, —

1335:

for achiving the discussion it has the <noinclude: -->

3123:

Knowledge (XXG):Bots/Requests for approval/MartinBotII 3

1300:

will be updated to indicate the bot flag assignment. --

3589:

What is the approval for the TheJoshBot stalled on? At

3210: 3206: 3199: 3074: 2730: 2726: 1651: 1643: 1635: 1627: 1591: 1583: 1575: 1567: 1503: 1498: 1463: 1266: 1019: 832: 824: 816: 808: 3026:

Knowledge (XXG):Requests for arbitration/Marudubshinki

1905:

group. The discussion can be taken up at any time on

1428:

to help automate the approvals process for AG members.

561:

Please crap the full protected page (Im not an Admin)

3061:

Knowledge (XXG):Bot owners' noticeboard#Inactive Bots

771:

Find a B'Crat on IRC (lots of very nice people there)

97:

Can someone please deal with my request for approval?

3079:

Knowledge (XXG):Bots/Requests for approval/PlangeBot

2401:

Editing fully-protected pages and interface messages

2052:

talk to cyde he has basicly written the pywiki bot.

2860:

Would this be to centralize editor comments, etc? (

2833:to ensure that this is remembered historically. -- 2280:

The running of automated processes by such accoutns

3545:Knowledge (XXG):Bots/Requests for approval/Header 3196:Knowledge (XXG):WikiProject Trains/Recent changes 2067:It's a little odd no one has asked this before. 2277:The running of assitance scrips by such accoutns 1371:Hello all. I've recently created a bot account ( 3503:go ahead but make sure you update pywikipedia. 2523:The idea has been rejected many times over at 1937:While the approval of bots does come from the 3543:Done; the correct page to add the link to is 3485:Back in June, I requested a flag for my bot ( 8: 3077:that the said bot was approved a while ago ( 2888:I don't think we really need that. We have 2107:for a while, and have large experience with 1380:and all of them have to be approved first), 1226:Elissonbot waiting for response after trials 747:Knowledge (XXG):Approved Bots Awaiting Flags 335:the bot's userpage to make this even easier. 158:Only if you want to see the official polixy 3209:and making a seperate list of new projects 3614:I have posted the trial results of my bot 3428:As I noted above, the issue for me is not 751:Knowledge (XXG):Bots/Requests for approval 2848:Don't we need a bot owners noticeboard?-- 1907:Knowledge (XXG) talk:Bots/Approvals group 2980:Knowledge (XXG):Bot owners' noticeboard 2794:Knowledge (XXG) talk:Copyright problems 719:and post a response there instead. -- 48:Do not edit the contents of this page. 3117:Additional BAG member input requested 1683:How large a portion is "substantial"? 7: 932:Since you approved EsjayBot II (See 753:serves every need I can think of. - 743:Knowledge (XXG):Requested bot flags 600:Knowledge (XXG):Requested bot flags 285:Knowledge (XXG):Requested bot flags 267:Knowledge (XXG):Requested bot flags 1784:http://en.wikipedia.org/robots.txt 1275:three days ago. What to do now? – 501:I've made historical/inactive the 28: 3591:Template:Infobox Australian Place 2982:. Let's get it up and running! — 1661:In trial period as of 07-Sep-2006 1600:In trial period as of 07-Sep-2006 422:Knowledge (XXG):Bots/Approval log 271:Knowledge (XXG):Bots/Approval log 2390:You missed a few admin actions: 33: 3250:Request for proposed bot review 3038:Knowledge (XXG):Registered bots 2663:Personally I'd run this on the 2393:History review of deleted pages 2293:Buy-in from a supermajority of 1703:, for the morbidly curious. -- 2604:Knowledge (XXG):Lonely newbies 2274:Accountabilty of such accounts 1996:01:43, 27 September 2006 (UTC) 1983:22:56, 26 September 2006 (UTC) 1963:17:51, 26 September 2006 (UTC) 1950:12:17, 26 September 2006 (UTC) 1933:11:53, 26 September 2006 (UTC) 1924:06:20, 26 September 2006 (UTC) 1915:03:40, 26 September 2006 (UTC) 1896:03:09, 26 September 2006 (UTC) 1876:01:24, 26 September 2006 (UTC) 1853:18:11, 22 September 2006 (UTC) 1827:16:47, 22 September 2006 (UTC) 1809:16:29, 22 September 2006 (UTC) 1779:01:22, 22 September 2006 (UTC) 1761:01:09, 22 September 2006 (UTC) 1747:00:23, 22 September 2006 (UTC) 1733:00:12, 22 September 2006 (UTC) 1721:22:56, 21 September 2006 (UTC) 1708:21:38, 21 September 2006 (UTC) 1677:16:44, 22 September 2006 (UTC) 1531:16:53, 20 September 2006 (UTC) 1443:03:06, 17 September 2006 (UTC) 1415:22:05, 16 September 2006 (UTC) 1397:22:02, 16 September 2006 (UTC) 1362:13:38, 15 September 2006 (UTC) 1305:00:53, 15 September 2006 (UTC) 1290:18:14, 14 September 2006 (UTC) 1208:21:16, 13 September 2006 (UTC) 1169:21:03, 13 September 2006 (UTC) 1127:20:43, 13 September 2006 (UTC) 1092:20:47, 13 September 2006 (UTC) 1058:20:42, 13 September 2006 (UTC) 1028:20:32, 13 September 2006 (UTC) 998:20:25, 13 September 2006 (UTC) 978:20:18, 13 September 2006 (UTC) 963:20:17, 13 September 2006 (UTC) 941:20:21, 13 September 2006 (UTC) 922:20:16, 13 September 2006 (UTC) 846:19:33, 13 September 2006 (UTC) 779:20:53, 12 September 2006 (UTC) 763:Tawker's steps to bot flagging 758:14:13, 15 September 2006 (UTC) 724:12:44, 15 September 2006 (UTC) 687:02:26, 15 September 2006 (UTC) 657:14:29, 12 September 2006 (UTC) 628:14:13, 12 September 2006 (UTC) 607:13:33, 12 September 2006 (UTC) 586:13:19, 12 September 2006 (UTC) 566:12:49, 12 September 2006 (UTC) 553:10:07, 12 September 2006 (UTC) 544:02:09, 12 September 2006 (UTC) 524:00:34, 12 September 2006 (UTC) 510:17:26, 11 September 2006 (UTC) 490:03:50, 11 September 2006 (UTC) 481:03:43, 11 September 2006 (UTC) 462:03:31, 11 September 2006 (UTC) 448:03:03, 11 September 2006 (UTC) 429:03:00, 11 September 2006 (UTC) 415:02:53, 11 September 2006 (UTC) 388:04:09, 11 September 2006 (UTC) 372:04:05, 11 September 2006 (UTC) 359:03:16, 11 September 2006 (UTC) 350:03:03, 11 September 2006 (UTC) 330:02:48, 11 September 2006 (UTC) 310:02:36, 11 September 2006 (UTC) 292:02:19, 11 September 2006 (UTC) 278:02:16, 11 September 2006 (UTC) 256:15:50, 12 September 2006 (UTC) 235:23:37, 11 September 2006 (UTC) 185:22:53, 10 September 2006 (UTC) 171:22:15, 10 September 2006 (UTC) 154:22:09, 10 September 2006 (UTC) 140:22:05, 10 September 2006 (UTC) 1: 3662:14:58, 28 November 2006 (UTC) 3652:08:49, 28 November 2006 (UTC) 3629:14:53, 17 November 2006 (UTC) 3602:15:39, 16 November 2006 (UTC) 3585:17:10, 13 November 2006 (UTC) 3575:16:45, 13 November 2006 (UTC) 3538:16:11, 13 November 2006 (UTC) 3529:InterWikiLink for arabic page 3519:17:13, 13 November 2006 (UTC) 3508:16:37, 13 November 2006 (UTC) 3496:00:30, 13 November 2006 (UTC) 3473:02:21, 11 November 2006 (UTC) 3463:01:53, 11 November 2006 (UTC) 2602:Or non-existant talk pages. 1357:that we are currently using. 598:Perhaps you are reffering to 3643:WP:AN#Massive Image Deletion 3437:23:49, 9 November 2006 (UTC) 3404:23:21, 9 November 2006 (UTC) 3369:21:37, 9 November 2006 (UTC) 3335:18:43, 9 November 2006 (UTC) 3312:17:49, 9 November 2006 (UTC) 3303:17:14, 9 November 2006 (UTC) 3283:17:11, 9 November 2006 (UTC) 3242:14:49, 4 November 2006 (UTC) 3184:14:34, 4 November 2006 (UTC) 3174:14:29, 4 November 2006 (UTC) 3144:13:26, 4 November 2006 (UTC) 3134:17:43, 2 November 2006 (UTC) 3109:17:44, 30 October 2006 (UTC) 3096:12:04, 30 October 2006 (UTC) 3086:01:15, 29 October 2006 (UTC) 3049:02:15, 22 October 2006 (UTC) 3008:18:42, 22 October 2006 (UTC) 2997:17:54, 22 October 2006 (UTC) 2974:17:47, 22 October 2006 (UTC) 2955:18:23, 21 October 2006 (UTC) 2927:15:43, 22 October 2006 (UTC) 2918:15:24, 22 October 2006 (UTC) 2907:18:02, 21 October 2006 (UTC) 2890:Knowledge (XXG):Bot requests 2884:17:45, 21 October 2006 (UTC) 2873:17:35, 21 October 2006 (UTC) 2855:17:25, 21 October 2006 (UTC) 2838:16:34, 20 October 2006 (UTC) 2823:09:37, 20 October 2006 (UTC) 2778:16:03, 20 October 2006 (UTC) 2756:15:20, 20 October 2006 (UTC) 2746:09:32, 20 October 2006 (UTC) 2720:19:38, 19 October 2006 (UTC) 2700:17:19, 18 October 2006 (UTC) 2686:16:11, 18 October 2006 (UTC) 2672:02:25, 18 October 2006 (UTC) 2659:02:23, 18 October 2006 (UTC) 2645:00:45, 18 October 2006 (UTC) 2615:04:04, 18 October 2006 (UTC) 2598:18:22, 17 October 2006 (UTC) 2553:06:21, 17 October 2006 (UTC) 2543:00:42, 17 October 2006 (UTC) 2534:23:48, 16 October 2006 (UTC) 2519:23:44, 16 October 2006 (UTC) 2504:22:00, 16 October 2006 (UTC) 2472:20:13, 17 October 2006 (UTC) 2462:20:07, 17 October 2006 (UTC) 2444:17:53, 17 October 2006 (UTC) 2386:08:12, 13 October 2006 (UTC) 2360:05:10, 13 October 2006 (UTC) 2348:05:41, 13 October 2006 (UTC) 2339:03:45, 13 October 2006 (UTC) 2327:01:34, 13 October 2006 (UTC) 2306:01:31, 13 October 2006 (UTC) 2197:20:08, 19 October 2006 (UTC) 2184:03:44, 13 October 2006 (UTC) 2175:03:43, 13 October 2006 (UTC) 3512:Had done anyway, thanks :) 2408:MediaWiki:Recentchangestext 2233:20:19, 8 October 2006 (UTC) 2164:19:38, 8 October 2006 (UTC) 2144:19:03, 8 October 2006 (UTC) 2126:02:41, 8 October 2006 (UTC) 2091:03:24, 5 October 2006 (UTC) 2076:20:34, 4 October 2006 (UTC) 2057:13:17, 2 October 2006 (UTC) 2047:02:31, 2 October 2006 (UTC) 1546:...produces the following: 1151:Arrgh, you've drawn me in. 3678: 1790:15:54, 22 September 2006 ( 648:We'll continue posting to 453:point is that with a flag 3551:16:24, 13 November 2006 ( 3188:I'll outline them below: 2691:may be an option then. — 2255:should be addressed are: 145:See the official policy: 18:Knowledge (XXG) talk:Bots 3634:Betacommand Deletion Bot 2565:13:14, 17 October 2006 ( 2418:13:24, 17 October 2006 ( 2205:AMABot awaiting response 1273:Elissonbot approval page 911:19:57, 13 September 2006 3580:we will move them soon 2844:Bot owners noticeboard? 2373:Protecting/Unprotecting 2131:We just went though an 3179:What are the tasks? -- 3024:Please note that per ( 2788:Bot change of function 2397:Special:Unwatchedpages 2063:An uncovered situation 789:I noticed today that 46:of past discussions. 22:Requests for approval 3075:brought to my notice 2978:I've created one at 1402:If you're approving 2705:Bot Approvals Group 2370:Deleting/Undeleting 2367:Blocking/Unblocking 1859:Bot Approval Status 1336:</noinclude: --> 3566:Expiring requests? 3240: 3172: 2596: 2231: 955:User:EssjayBot III 455:they have a choice 3228: 3160: 3150:Multiple Requests 2988: 2965: 2898: 2792:Per consensus on 2580: 2215: 2155: 2117: 1311:Archive Templates 91: 90: 58: 57: 52:current talk page 3669: 3624: 3456:m:spam blacklist 3400: 3397: 3394: 3331: 3328: 3325: 3299: 3296: 3293: 3235: 3167: 3129: 3044: 3006: 2995: 2986: 2972: 2963: 2953: 2950: 2943: 2916: 2905: 2896: 2882: 2868: 2853: 2695: 2654: 2610: 2594: 2589: 2584: 2514: 2501: 2324: 2301: 2229: 2224: 2219: 2162: 2153: 2139: 2124: 2115: 2086: 2042: 1991: 1979: 1976: 1973: 1945: 1892: 1889: 1886: 1873: 1868: 1756: 1659: 1657: 1654: 1646: 1638: 1630: 1598: 1597: 1594: 1586: 1578: 1570: 1529: 1439: 1436: 1433: 1425:I wrote a script 1388: 1356: 1350: 1346: 1340: 1334: 1328: 1324: 1318: 1288: 1280: 1270: 908: 903: 839: 838: 835: 827: 819: 811: 539: 532: 477: 474: 471: 444: 441: 438: 410: 385: 380: 367: 346: 343: 340: 305: 252: 249: 246: 233: 218: 217: 214: 211: 208: 205: 202: 166: 138: 123: 122: 119: 116: 113: 110: 107: 72: 60: 59: 37: 36: 30: 3677: 3676: 3672: 3671: 3670: 3668: 3667: 3666: 3636: 3620: 3612: 3568: 3531: 3483: 3398: 3395: 3392: 3329: 3326: 3323: 3297: 3294: 3291: 3252: 3233: 3165: 3152: 3127: 3119: 3071: 3056: 3042: 3022: 3020:Bot restiction. 3002: 2983: 2960: 2948: 2945: 2941: 2912: 2893: 2878: 2866: 2849: 2846: 2790: 2725:Have you tried 2693: 2652: 2627: 2608: 2592: 2587: 2582: 2512: 2497: 2482: 2322: 2313: 2299: 2240: 2227: 2222: 2217: 2207: 2150: 2137: 2112: 2101: 2084: 2065: 2040: 2035: 2033:Interwiki links 1989: 1977: 1974: 1971: 1943: 1890: 1887: 1884: 1869: 1866: 1861: 1754: 1685: 1652: 1644: 1636: 1628: 1613: 1609: 1592: 1584: 1576: 1568: 1553: 1549: 1525: 1514: 1450: 1448:Template update 1437: 1434: 1431: 1423: 1386: 1369: 1354: 1348: 1344: 1338: 1332: 1326: 1322: 1316: 1315:I have created 1313: 1284: 1276: 1234: 1228: 912: 906: 855: 833: 825: 817: 809: 794: 790: 787: 537: 530: 475: 472: 469: 442: 439: 436: 408: 381: 378: 365: 344: 341: 338: 303: 263: 250: 247: 244: 231: 220: 215: 212: 209: 206: 203: 200: 199: 164: 136: 125: 120: 117: 114: 111: 108: 105: 104: 99: 68: 34: 26: 25: 24: 12: 11: 5: 3675: 3673: 3665: 3664: 3649:Dragons flight 3635: 3632: 3611: 3608: 3607: 3606: 3605: 3604: 3567: 3564: 3563: 3562: 3530: 3527: 3526: 3525: 3524: 3523: 3522: 3521: 3482: 3479: 3478: 3477: 3476: 3475: 3450: 3449: 3448: 3447: 3446: 3445: 3444: 3443: 3442: 3441: 3440: 3439: 3415: 3414: 3413: 3412: 3411: 3410: 3409: 3408: 3407: 3406: 3378: 3377: 3376: 3375: 3374: 3373: 3372: 3371: 3342: 3341: 3340: 3339: 3338: 3337: 3318:User:VoABot II 3275: 3274: 3273: 3272: 3269: 3263: 3262: 3259: 3251: 3248: 3247: 3246: 3245: 3244: 3216: 3215: 3214: 3203: 3192: 3151: 3148: 3147: 3146: 3118: 3115: 3114: 3113: 3112: 3111: 3099: 3098: 3070: 3068:User:PlangeBot 3065: 3055: 3052: 3021: 3018: 3017: 3016: 3015: 3014: 3013: 3012: 3011: 3010: 2937: 2936: 2935: 2934: 2933: 2932: 2931: 2930: 2929: 2845: 2842: 2841: 2840: 2789: 2786: 2785: 2784: 2783: 2782: 2781: 2780: 2753:William Pietri 2717:William Pietri 2712: 2711: 2710: 2709: 2677: 2676: 2675: 2674: 2626: 2623: 2622: 2621: 2620: 2619: 2618: 2617: 2576: 2555: 2545: 2536: 2481: 2478: 2477: 2476: 2475: 2474: 2449: 2448: 2447: 2446: 2438: 2435: 2432:Special:Import 2412:Special:Import 2404: 2403: 2402: 2399: 2394: 2388: 2377: 2376: 2375: 2374: 2371: 2368: 2362: 2352: 2351: 2350: 2329: 2312: 2309: 2291: 2290: 2289: 2288: 2284: 2283: 2282: 2281: 2278: 2275: 2269: 2268: 2265: 2262: 2239: 2236: 2206: 2203: 2202: 2201: 2200: 2199: 2190: 2189: 2188: 2187: 2186: 2100: 2095: 2094: 2093: 2064: 2061: 2060: 2059: 2034: 2031: 2030: 2029: 2010: 2009: 2008: 2007: 2006: 2005: 2004: 2003: 2002: 2001: 2000: 1999: 1998: 1965: 1860: 1857: 1856: 1855: 1820: 1819: 1818: 1817: 1816: 1815: 1814: 1813: 1812: 1811: 1766: 1765: 1764: 1763: 1749: 1744:Dragons flight 1736: 1735: 1724: 1723: 1684: 1681: 1680: 1679: 1670: 1669: 1668: 1607: 1544: 1543: 1542: 1540: 1513: 1512: 1506: 1501: 1496: 1491: 1486: 1481: 1476: 1471: 1466: 1464:Approved BRFAs 1461: 1454: 1449: 1446: 1422: 1419: 1418: 1417: 1368: 1365: 1312: 1309: 1308: 1307: 1227: 1224: 1223: 1222: 1221: 1220: 1219: 1218: 1217: 1216: 1215: 1214: 1213: 1212: 1211: 1210: 1182: 1181: 1180: 1179: 1178: 1177: 1176: 1175: 1174: 1173: 1172: 1171: 1161: 1138: 1137: 1136: 1135: 1134: 1133: 1132: 1131: 1130: 1129: 1107: 1106: 1105: 1104: 1103: 1102: 1101: 1100: 1099: 1098: 1097: 1096: 1095: 1094: 1071: 1070: 1069: 1068: 1067: 1066: 1065: 1064: 1063: 1062: 1061: 1060: 1039: 1038: 1037: 1036: 1035: 1034: 1033: 1032: 1031: 1030: 1007: 1006: 1005: 1004: 1003: 1002: 1001: 1000: 983: 982: 981: 980: 968: 967: 966: 965: 948: 947: 946: 945: 944: 943: 925: 924: 914: 913: 910: 786: 783: 782: 781: 772: 769: 739: 738: 737: 736: 735: 734: 733: 732: 731: 730: 729: 728: 727: 726: 700: 699: 698: 697: 696: 695: 694: 693: 692: 691: 690: 689: 668: 667: 666: 665: 664: 663: 662: 661: 660: 659: 637: 636: 635: 634: 633: 632: 631: 630: 614: 613: 612: 611: 610: 609: 591: 590: 589: 588: 579: 569: 568: 559: 558: 557: 556: 555: 517: 499: 498: 497: 496: 495: 494: 493: 492: 431: 403: 402: 401: 400: 399: 398: 397: 396: 395: 394: 393: 392: 391: 390: 323: 322: 321: 318: 262: 261:Bot Flag Pages 259: 238: 237: 227: 187: 176: 175: 174: 173: 132: 98: 95: 93: 89: 88: 83: 78: 73: 66: 56: 55: 38: 27: 15: 14: 13: 10: 9: 6: 4: 3: 2: 3674: 3663: 3660: 3656: 3655: 3654: 3653: 3650: 3646: 3644: 3639: 3633: 3631: 3630: 3627: 3625: 3623: 3617: 3610:Trial results 3609: 3603: 3600: 3596: 3595:WP:AUSTPLACES 3592: 3588: 3587: 3586: 3583: 3579: 3578: 3577: 3576: 3573: 3565: 3560: 3557: 3554: 3550: 3546: 3542: 3541: 3540: 3539: 3536: 3528: 3520: 3517: 3516: 3511: 3510: 3509: 3506: 3502: 3501: 3500: 3499: 3498: 3497: 3494: 3493: 3488: 3480: 3474: 3471: 3466: 3465: 3464: 3461: 3457: 3452: 3451: 3438: 3435: 3431: 3427: 3426: 3425: 3424: 3423: 3422: 3421: 3420: 3419: 3418: 3417: 3416: 3405: 3402: 3401: 3388: 3387: 3386: 3385: 3384: 3383: 3382: 3381: 3380: 3379: 3370: 3367: 3362: 3358: 3354: 3350: 3349: 3348: 3347: 3346: 3345: 3344: 3343: 3336: 3333: 3332: 3319: 3315: 3314: 3313: 3310: 3306: 3305: 3304: 3301: 3300: 3287: 3286: 3285: 3284: 3281: 3270: 3267: 3266: 3265: 3264: 3260: 3257: 3256: 3255: 3249: 3243: 3239: 3236: 3231: 3226: 3221: 3217: 3212: 3208: 3204: 3201: 3197: 3193: 3190: 3189: 3187: 3186: 3185: 3182: 3178: 3177: 3176: 3175: 3171: 3168: 3163: 3157: 3149: 3145: 3142: 3139:And again. -- 3138: 3137: 3136: 3135: 3132: 3130: 3124: 3116: 3110: 3107: 3103: 3102: 3101: 3100: 3097: 3094: 3090: 3089: 3088: 3087: 3084: 3080: 3076: 3069: 3066: 3064: 3063: 3062: 3054:Inactive Bots 3053: 3051: 3050: 3047: 3045: 3039: 3035: 3034:User:Bot-maru 3031: 3030:Marudubshinki 3027: 3019: 3009: 3005: 3000: 2999: 2998: 2993: 2989: 2981: 2977: 2976: 2975: 2970: 2966: 2958: 2957: 2956: 2951: 2944: 2938: 2928: 2925: 2921: 2920: 2919: 2915: 2910: 2909: 2908: 2903: 2899: 2891: 2887: 2886: 2885: 2881: 2876: 2875: 2874: 2871: 2869: 2863: 2859: 2858: 2857: 2856: 2852: 2843: 2839: 2836: 2832: 2827: 2826: 2825: 2824: 2821: 2817: 2813: 2809: 2806: 2803: 2799: 2795: 2787: 2779: 2776: 2772: 2768: 2764: 2759: 2758: 2757: 2754: 2749: 2748: 2747: 2744: 2740: 2736: 2732: 2728: 2724: 2723: 2722: 2721: 2718: 2708: 2706: 2701: 2698: 2696: 2689: 2688: 2687: 2684: 2679: 2678: 2673: 2670: 2666: 2662: 2661: 2660: 2657: 2655: 2649: 2648: 2647: 2646: 2643: 2638: 2636: 2631: 2625:Read only bot 2624: 2616: 2613: 2611: 2605: 2601: 2600: 2599: 2595: 2590: 2585: 2577: 2574: 2571: 2568: 2564: 2560: 2556: 2554: 2551: 2546: 2544: 2541: 2537: 2535: 2532: 2531: 2526: 2522: 2521: 2520: 2517: 2515: 2508: 2507: 2506: 2505: 2500: 2495: 2491: 2487: 2479: 2473: 2470: 2465: 2464: 2463: 2460: 2455: 2454: 2453: 2445: 2442: 2433: 2430: 2429: 2427: 2424: 2421: 2417: 2413: 2409: 2405: 2400: 2398: 2395: 2392: 2391: 2389: 2387: 2384: 2379: 2378: 2372: 2369: 2366: 2365: 2363: 2361: 2358: 2353: 2349: 2346: 2342: 2341: 2340: 2337: 2336: 2330: 2328: 2325: 2320: 2315: 2314: 2310: 2308: 2307: 2304: 2302: 2296: 2287:Anything else 2286: 2285: 2279: 2276: 2273: 2272: 2271: 2270: 2266: 2263: 2260: 2259: 2258: 2257: 2256: 2253: 2249: 2245: 2237: 2235: 2234: 2230: 2225: 2220: 2213: 2204: 2198: 2195: 2191: 2185: 2182: 2178: 2177: 2176: 2173: 2172: 2167: 2166: 2165: 2160: 2156: 2147: 2146: 2145: 2142: 2140: 2134: 2130: 2129: 2128: 2127: 2122: 2118: 2110: 2106: 2099: 2096: 2092: 2089: 2087: 2080: 2079: 2078: 2077: 2074: 2068: 2062: 2058: 2055: 2051: 2050: 2049: 2048: 2045: 2043: 2032: 2027: 2024: 2020: 2019: 2016: 2011: 1997: 1994: 1992: 1986: 1985: 1984: 1981: 1980: 1966: 1964: 1961: 1957: 1953: 1952: 1951: 1948: 1946: 1940: 1936: 1935: 1934: 1931: 1927: 1926: 1925: 1922: 1918: 1917: 1916: 1913: 1908: 1903: 1899: 1898: 1897: 1894: 1893: 1880: 1879: 1878: 1877: 1874: 1872: 1858: 1854: 1851: 1847: 1843: 1840: 1836: 1831: 1830: 1829: 1828: 1825: 1810: 1807: 1802: 1801: 1799: 1796: 1793: 1789: 1785: 1782: 1781: 1780: 1777: 1772: 1771: 1770: 1769: 1768: 1767: 1762: 1759: 1757: 1750: 1748: 1745: 1740: 1739: 1738: 1737: 1734: 1731: 1726: 1725: 1722: 1719: 1716: 1712: 1711: 1710: 1709: 1706: 1702: 1698: 1694: 1690: 1682: 1678: 1675: 1671: 1666: 1662: 1655: 1650: 1647: 1642: 1639: 1634: 1631: 1626: 1623: 1620: 1617: 1612: 1608: 1605: 1601: 1595: 1590: 1587: 1582: 1579: 1574: 1571: 1566: 1563: 1560: 1557: 1552: 1548: 1547: 1545: 1538: 1537: 1535: 1534: 1533: 1532: 1528: 1522: 1517: 1510: 1507: 1505: 1502: 1500: 1497: 1495: 1492: 1490: 1487: 1485: 1482: 1480: 1477: 1475: 1472: 1470: 1467: 1465: 1462: 1460: 1456: 1455: 1453: 1447: 1445: 1444: 1441: 1440: 1427: 1421:Helper script 1420: 1416: 1413: 1409: 1405: 1401: 1400: 1399: 1398: 1395: 1392: 1389: 1383: 1382:User:Sciurinæ 1378: 1374: 1373:User:Halibott 1366: 1364: 1363: 1360: 1353: 1352:Debate bottom 1343: 1331: 1321: 1310: 1306: 1303: 1299: 1294: 1293: 1292: 1291: 1287: 1283: 1279: 1274: 1268: 1265: 1262: 1259: 1256: 1253: 1250: 1247: 1244: 1241: 1238: 1233: 1225: 1209: 1206: 1201: 1196: 1195: 1194: 1193: 1192: 1191: 1190: 1189: 1188: 1187: 1186: 1185: 1184: 1183: 1170: 1167: 1162: 1158: 1154: 1150: 1149: 1148: 1147: 1146: 1145: 1144: 1143: 1142: 1141: 1140: 1139: 1128: 1125: 1121: 1117: 1116: 1115: 1114: 1113: 1112: 1111: 1110: 1109: 1108: 1093: 1090: 1085: 1084: 1083: 1082: 1081: 1080: 1079: 1078: 1077: 1076: 1075: 1074: 1073: 1072: 1059: 1056: 1051: 1050: 1049: 1048: 1047: 1046: 1045: 1044: 1043: 1042: 1041: 1040: 1029: 1026: 1021: 1017: 1016: 1015: 1014: 1013: 1012: 1011: 1010: 1009: 1008: 999: 996: 991: 990: 989: 988: 987: 986: 985: 984: 979: 976: 972: 971: 970: 969: 964: 961: 956: 952: 951: 950: 949: 942: 939: 935: 931: 930: 929: 928: 927: 926: 923: 920: 916: 915: 909: 901: 898: 895: 892: 889: 886: 883: 880: 877: 874: 871: 868: 865: 862: 859: 854: 850: 849: 848: 847: 844: 836: 831: 828: 823: 820: 815: 812: 807: 804: 801: 798: 793: 784: 780: 777: 773: 770: 767: 766: 765: 764: 760: 759: 756: 752: 748: 744: 725: 722: 718: 714: 713: 712: 711: 710: 709: 708: 707: 706: 705: 704: 703: 702: 701: 688: 685: 680: 679: 678: 677: 676: 675: 674: 673: 672: 671: 670: 669: 658: 655: 651: 647: 646: 645: 644: 643: 642: 641: 640: 639: 638: 629: 626: 622: 621: 620: 619: 618: 617: 616: 615: 608: 605: 601: 597: 596: 595: 594: 593: 592: 587: 584: 577: 573: 572: 571: 570: 567: 564: 560: 554: 551: 547: 546: 545: 542: 540: 533: 527: 526: 525: 522: 514: 513: 512: 511: 508: 504: 491: 488: 484: 483: 482: 479: 478: 465: 464: 463: 460: 456: 451: 450: 449: 446: 445: 432: 430: 427: 423: 419: 418: 417: 416: 413: 411: 389: 386: 384: 375: 374: 373: 370: 368: 362: 361: 360: 357: 353: 352: 351: 348: 347: 333: 332: 331: 328: 324: 319: 315: 314: 313: 312: 311: 308: 306: 299: 295: 294: 293: 290: 286: 282: 281: 280: 279: 276: 272: 268: 260: 258: 257: 254: 253: 236: 232: 230: 225: 222: 219: 196: 192: 188: 186: 183: 178: 177: 172: 169: 167: 161: 157: 156: 155: 152: 148: 144: 143: 142: 141: 137: 135: 130: 127: 124: 96: 94: 87: 84: 82: 79: 77: 74: 71: 67: 65: 62: 61: 53: 49: 45: 44: 39: 32: 31: 23: 19: 3647: 3640: 3637: 3621: 3613: 3569: 3532: 3513: 3490: 3484: 3429: 3390: 3360: 3356: 3352: 3321: 3289: 3276: 3253: 3156:around three 3155: 3153: 3120: 3072: 3058: 3057: 3023: 2847: 2831:your request 2804: 2791: 2713: 2702: 2665:m:Toolserver 2639: 2632: 2628: 2529: 2483: 2450: 2334: 2292: 2242:As a recent 2241: 2212:request page 2208: 2170: 2132: 2102: 2069: 2066: 2036: 2013: 1969: 1955: 1901: 1882: 1870: 1862: 1821: 1686: 1664: 1660: 1648: 1640: 1632: 1624: 1618: 1603: 1599: 1588: 1580: 1572: 1564: 1558: 1518: 1515: 1451: 1429: 1424: 1407: 1403: 1385: 1370: 1367:AWB accounts 1314: 1263: 1257: 1251: 1245: 1239: 1229: 1199: 934:Approval log 896: 890: 884: 878: 872: 866: 860: 829: 821: 813: 805: 799: 792:EssjayBot II 788: 785:EssjayBot II 762: 761: 740: 503:Approval log 500: 467: 454: 434: 404: 382: 336: 297: 264: 242: 239: 228: 223: 194: 133: 128: 100: 92: 69: 47: 41: 3582:Betacommand 3505:Betacommand 3361:per article 3357:per article 3353:per article 3194:Update the 3121:Please see 2480:Bot Request 2054:Betacommand 2023:17 October 1968:a bit more. 1693:mathematics 1653:user rights 1629:actions log 1593:user rights 1569:actions log 1359:Betacommand 876:protections 834:user rights 810:actions log 768:Approve bot 563:Betacommand 356:Betacommand 40:This is an 2530:Alphachimp 2335:Alphachimp 2311:Discussion 2252:Bot Policy 2238:Admin Bots 2171:Alphachimp 2018:Farmbrough 1835:Byrgenwulf 1718:(contribs) 1504:rights log 1494:page moves 1342:Debate top 1330:Bot Bottom 1261:page moves 1232:Elissonbot 1200:in general 888:page moves 3572:WinHunter 3225:this page 3083:WinHunter 3059:Moved to 2820:Sempronio 2775:Sempronio 2743:Sempronio 2733:already? 2525:WP:BOTREQ 1658:(Task: 2) 1637:block log 1577:block log 1499:block log 1375:) for my 1298:this page 1267:block log 882:deletions 818:block log 426:WinHunter 289:WinHunter 86:Archive 5 81:Archive 4 76:Archive 3 70:Archive 2 64:Archive 1 3181:kingboyk 3141:kingboyk 3128:xaosflux 3093:kingboyk 3043:xaosflux 2924:kingboyk 2867:xaosflux 2808:contribs 2694:xaosflux 2683:HighInBC 2653:xaosflux 2642:HighInBC 2609:xaosflux 2513:xaosflux 2494:contribs 2345:Carnildo 2300:xaosflux 2194:HighInBC 2138:xaosflux 2133:election 2085:xaosflux 2041:xaosflux 2021:, 13:34 1990:xaosflux 1944:xaosflux 1755:xaosflux 1730:Carnildo 1645:flag log 1622:contribs 1611:Zorglbot 1585:flag log 1562:contribs 1551:Zorglbot 1474:contribs 1412:kingboyk 1243:contribs 864:contribs 826:flag log 803:contribs 550:kingboyk 538:xaosflux 531:=Nichalp 409:xaosflux 366:xaosflux 354:I agree 304:xaosflux 241:request. 229:contribs 165:xaosflux 160:WP:BLOCK 134:contribs 20:‎ | 3593:(under 3535:Mandavi 3481:Scepbot 3470:Crum375 3434:Crum375 3366:Crum375 3309:Crum375 3280:Crum375 3238:rtinp23 3220:WP V1.0 3170:rtinp23 3154:I have 3104:Done. 3073:It was 2942:Ganeshk 2862:WP:BOWN 2798:DumbBOT 2606:? :) — 2593:rtinp23 2559:welcome 2486:Ageo020 2244:request 2228:rtinp23 2105:MetsBot 2073:llywrch 1956:process 1850:Anville 1839:Hillman 1776:Anville 1705:Anville 1689:physics 1524:once.-- 1320:Bot Top 1278:Elisson 1020:history 907:FireFox 43:archive 3599:SauliH 3549:ais523 2763:Tawker 2669:Tawker 2563:ais523 2416:ais523 2357:Tawker 2295:WP:BAG 2181:Tawker 2028:(GMT). 1902:vastly 1788:ais523 1665:Task 2 1604:Task 1 1391:Halibu 1377:WP:AWB 894:rights 870:blocks 853:Essjay 776:Tawker 755:Taxman 684:Taxman 576:WP:CHU 195:policy 191:WP:IAR 151:bogdan 149:. ;-) 147:WP:IAR 3641:See: 3393:Voice 3324:Voice 3292:Voice 3106:Redux 3040:. — 3004:Andeh 2914:Andeh 2880:Andeh 2851:Andeh 2812:Tizio 2767:Tizio 2735:Tizio 2499:count 1972:Voice 1885:Voice 1871:Chimp 1867:alpha 1715:Gwern 1527:Andeh 1479:count 1432:Voice 1404:every 1249:count 650:WP:BN 625:Redux 602:? -- 583:Redux 521:Redux 470:Voice 457:. -- 437:Voice 383:Chimp 379:alpha 339:Voice 298:paper 245:Voice 16:< 3622:Lost 3616:here 3547:. -- 3515:Will 3492:Will 3487:here 3460:Alai 3430:need 3396:-of- 3327:-of- 3316:See 3295:-of- 3211:diff 3207:diff 3200:diff 2992:talk 2985:Mets 2969:talk 2962:Mets 2949:talk 2902:talk 2895:Mets 2816:Caio 2802:talk 2771:Caio 2739:Caio 2635:perl 2490:talk 2319:Tito 2246:and 2159:talk 2152:Mets 2121:talk 2114:Mets 2026:2006 2015:Rich 1975:-of- 1888:-of- 1846:here 1844:and 1842:here 1837:and 1701:here 1699:and 1697:here 1691:and 1616:BRFA 1556:BRFA 1509:flag 1489:logs 1469:talk 1459:BRFA 1435:-of- 1347:and 1325:and 1286:Talk 1255:logs 1237:talk 858:talk 797:BRFA 745:and 473:-of- 440:-of- 342:-of- 287:. -- 269:and 248:-of- 3399:All 3330:All 3298:All 2987:501 2964:501 2897:501 2729:or 2550:pgk 2469:pgk 2459:pgk 2441:pgk 2383:pgk 2248:RFA 2154:501 2116:501 2109:AWB 2098:BAG 1978:All 1939:BAG 1921:pgk 1891:All 1484:SUL 1438:All 1166:pgk 1157:AGF 1153:AGF 1120:AGF 1055:pgk 995:pgk 919:pgk 900:RfA 476:All 443:All 420:If 345:All 325:-- 251:All 193:is 3659:RM 3645:. 3028:) 2835:RM 2818:, 2814:, 2773:, 2769:, 2741:, 2737:, 2707:). 2540:RM 2502:) 2496:• 2492:• 2467:-- 2428:) 2323:xd 1960:RM 1930:RM 1912:RM 1824:RM 1806:RM 1800:) 1674:RM 1408:do 1394:tt 1387:// 1355:}} 1349:{{ 1345:}} 1339:{{ 1333:}} 1327:{{ 1323:}} 1317:{{ 1302:RM 1205:RM 1124:RM 1089:RM 1025:RM 993:-- 975:RM 960:RM 938:RM 843:RM 721:RM 717:BN 654:RM 604:RM 507:RM 487:RM 459:RM 327:RM 275:RM 213:ar 210:ik 207:Sh 204:rk 201:Da 182:RM 118:ar 115:ik 112:Sh 109:rk 106:Da 3561:) 3559:C 3556:T 3553:U 3320:. 3234:a 3230:M 3213:. 3202:) 3166:a 3162:M 2994:) 2990:( 2971:) 2967:( 2952:) 2946:( 2904:) 2900:( 2805:· 2800:( 2703:( 2588:a 2583:M 2575:) 2573:C 2570:T 2567:U 2488:( 2426:C 2423:T 2420:U 2223:a 2218:M 2161:) 2157:( 2149:— 2123:) 2119:( 1798:C 1795:T 1792:U 1667:) 1663:( 1656:) 1649:· 1641:· 1633:· 1625:· 1619:· 1614:( 1606:) 1602:( 1596:) 1589:· 1581:· 1573:· 1565:· 1559:· 1554:( 1511:) 1457:( 1282:• 1269:) 1264:· 1258:· 1252:· 1246:· 1240:· 1235:( 902:) 897:· 891:· 885:· 879:· 873:· 867:· 861:· 856:( 837:) 830:· 822:· 814:· 806:· 800:· 795:( 224:/ 216:i 129:/ 121:i 54:.

Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.

Knowledge (XXG)

talk:Bots/Requests for approval/Archive 2 - Knowledge (XXG)

Index