Knowledge (XXG)

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

Source 📝

3505:
be blocked for it. Third, if you haven't noticed, Rich is not the only bot operator on Knowledge (XXG). But do you see the things happening to Rich happening to any other operator? Not counting Rich, I can think of only 1 or 2 other bot operators in my entire time on Knowledge (XXG) who have run into serious problems with the community to the extent that the operator got blocked. In each case, the problems go beyond simply "making mistakes." Though in some cases, they didn't even make that many mistakes, they just compounded the ones they did make by acting like an ass when it was brought to their attention. If you really do promptly fix every problem brought to your attention, you have nothing to be concerned about. Rich's issue is that he either doesn't fix the problems when he says he does, or he decides they aren't actually problems. He's being blocked now because he's used up people's good faith.
3416:
a big deal but because I am making in excess of 1000 a day its a problem. The rules of editing don't change between having a BRFA and not having one it just puts more eyes on you and increases scrutiny. Its inevitable that I am going to make a few bad edits and that chance increases exponentially the more edits I do and the more difficult the edit becomes. Having the BRFA request means that, I will have been duly informed of the consequences of my actions so that, when I make a mistake, and that will happen eventually, I get an escelating series of blocks, warnings and the like eventally leading to a situation like the one that Rich is in where I have 2 or 3 editors watching every edit I make and as soon as I make a mistake I get blocked for 48 hours. I apologize if it sounds like I have a bad attitude about this but it really boils down to a lack of
3453:
a better handle on the scope of the project. Even ignoring all the articles tagged by the other 150+ US related projects there are still thousands that aren't tagged at all. Those are the ones I am currently addressing as well as supporting some of the US related projects that have either become defunct, inactive or have minimal activity (such as US counties, District of Columbia and Superfunds). I would be happy to provide the list of other edits but I recommend a separate discussion so that we don't get to confusing here. That list is also very long and I separate things into like groups (Talk page edits, Reference/Citation fixes, other). I find doing them all at once gets very confusing when reviewing differences as you mentioned above. --
4498:@ALL, but especially Cptnono. Anyone can edit, sure. But still we block, protect, abusefilter for edits and spam-blacklist for links, and we use a handful of antivandalism bots (of which I count XLinkBot to be one) to undo the edits which are giving a high number of cases where the edits do more harm than that they help. Anyone can edit, but that does not go for the main page. Whole IP ranges are blocked, pages get long page protections or abusefilters shut down certain types of edits. All of these have an immense impact, they block innocent editors, they disable ANY form of editing to specific pages or specific editors. And yes, practically ALL of these methods have collateral damage, most of which we will 4317:
correct venue to seek its removal. It had nothing to do with not getting nay support. Note that another editor here has supported my proposition so saying it is just me was untrue and does nothing but change the discussion from the bot making edits against consensus to me and whatever reasons I might have. And have I ever been reverted by the bot? No. I have seen it in edit summaries which led me to believe that YouTube was not allowed at all which is why I mentioned that it adds confusion. But if consensus is that it only reverts new users and IPs then we should consider changing the "anyone can edit" mentality of Knowledge (XXG) if we can finally admit that we do not respect the edits made by newcomers.
4539:
recognisable as good links, but unfortunately the majority of them is not as such recognisable. But YouTube has a bar to pass (just like any other link that one adds; and note that XLinkBot tries to detect whether external links are used as references and not revert those). YouTube still has the problem that many useful video's are copyvios (no, I am not saying that most of the videos are copyvios, I am not saying that most of the good videos are copyvios), and that is a pretty grave problem. But there is more, YouTube requires a significant bandwidth, it requires installation of software (which not everyone has, and which is not avaible to anyone), etc. etc.
4560:
not suitable as an external link. Yes, there are many YouTube videos that are good information and are suitable as an external link, but really, the large majority of movies IS NOT. We do not need videos of birthday parties, heavy rain in a small village in China, someone playing with his volleybal, name it (and yes, those are not copyvios .. !). I did a very, very quick check of about 10 reverts, and I did find 2 copyvios being reverted. Others were indirect or just too general to be of significant use. OK, I did not look significantly into them, but if I find 2 copyvios in 10 reverts, then that is certainly .. cause for concern.
3138:
the painstaking process for renaming/moving images for example) In most cases its very obvious what I did and can be identified at a mere glance. Removing these does a couple things. It makes the talk page look less cluttered and easier to read, it again makes it easier to program changes, it takes up less space when saving (if you have 1, 000, 000 pages and they all have 10 versions in history and they all have 20 spaces in the headers, thats a couple GB of space saved when we delete the spaces. Not a huge issue I grant you because GB are cheap in the grand scheme of things but it all adds up and it is a reason I do it.
3282:
combination of edit, over articles you know (at least in this cae I know) you will be routinely editing over and over potentially, or do you get rid of it on the first pass so the next time you have less "clutter" and code needed to make the change. Again I do this more or less up front so that all the follow up code doesn't require the spaces. If now I need to add code to account for the spaces then I am going to need to go back through and make quite a few changes because I do this edit early on in the order to prevent from needing to account for it later a few hundred times. Again its a difference of coding for this
2790:
blank and this is the only thing there. For others such as the assessments it can take several seconds to check the article and then process it but I usually grab the assessment from a project thats already there if its missing for US (I do this using Regex coding). In most cases the high edit rate is do to working on talk pages and it requires very little time to see if there is an error before I move on. I also frequently use 2 instances of AWB at the same time so when the first one is saving I am reviewing the second and I alternate back and forth. If the community want me to request and use a bot for
2989:
edits a day. But I went back and fixed them whenever they come up. They are fairly rare and usually are due to that particular page doing something out of the normal (such as having importancelow instead of importance=low which caused me to add importance=low again for about 10 articles which I fixed and then added some regex code that would watch for the bad parameter values). With that said here is a better description of the edits I am doing to help you decide which route to take, which at this point seems like a BRFA: It is quite long and I can provide the code/regex if requested were applicable.
3501:
anything. You're not really saving any significant amount of space, as it doesn't really add up to much. I think I actually estimated it once, and found that even under an extremely optimistic estimate, removing the spaces saves something like $ 1-10 in disk space costs over the course of a year without considering compression. However, Wikimedia uses a diff-based, compressed storage system for revisions, so making more changes actually increases the disk space used for that edit. If you think it should be changed in the software, file a bug report and convince the developers.
2907:: "In general, processes that are operated at higher speeds, with a high volume of edits, or are more automated, may be more likely to be treated as bots for these purposes". You are obviously making a high volume of edits at a high rate of speed. I'm not sure whether there are actual accuracy concerns being raised here or if it's just "Kumioko should be using a bot flag for this to avoid clogging watchlists and such". Either way, I'm leaning towards asking for a BRFA for this task that could probably be speedily approved at this point, but I'm open to comments. 4109:
99% of other editors don't know that either and to me thats part of the problem here. The issue of using youtube for larger files isn't just one of access but is a software limitation requiring the programmers to do some work on their end from what I understand. Regarding the consensus that doesn't surprise me. Consensus frequently gets formed and then once the action starts and people notice the consensus is revised. Additionally with more and more government agencies using Youtube I can see the exception list getting very large and unwieldy pretty fast. --
3191:
edits by people in the discussions are swamped by useless whitespace-only changes. It's a matter of opinion whether removing the spaces makes them "less cluttered" or "easier to read", as some may find the markup cramped and harder to read without those spaces. You're also right the GB are cheap, and IIRC the way revisions are stored may mean it takes more space for the revision changing it than it would to leave them alone. And none of that really addresses the question of whether there is consensus for this to be done on a large scale.
3331:
these mirror sites do not like the malformed breaks. Thats were the problems lie. It could be argued that we shouldn't care about that but, if we can do a simple edit to fix it while we are there anyway so that the data displays correctly on these other (we'll call them customer sites for lack of a better term) than why shouldn't we. Regarding the vandalism comment I had thought about that a while back and randomly check but have never yet found one that was due to obvious vandalism although admitedly it is possible. --
3540:
doing the assessment changes. Since most editors have little interest in talk pages they seem to be particularly dishevelled. But there are several of us now (Me, Magio, Xeno and a few others as well as several bots) cleaning these up so gradually we are straightening them out. Just let me know what you want me to do. Since this discussion started I haven't done many edits till this gets sorted out and I would like to get back to it. I've only done about 500 edits today and I'm starting to feel like a slacker.:-) --
2256:(2) It appears that the operator took it upon themselves to change the functionality during the trial without explicit approval (which is suboptimal) but they noted the change in functionality prior to final approval. As regards (1), if it becomes evident during the discussion at a central venue that the community does not want visible tags to be placed by the bot, then the bot can start putting hidden categories, listifying the pages needing review, or something of the sort. – 2277:
was turned down with the reasoning that although it would be technically possible, the volunteer new page patrollers should simply work harder; some Wikipedians (well, me actually) felt there could therefore be another way of addressing the problem. This project is in its infancy but although what has been achieved so far is one small step for improving the system of new page patrolling, it's already a huge leap forward towards better quality control.
3420:. If I make a mistake on an edit all someone has to do is tell me and Ill do whatever I can to fix it. I believe my talk page responses will convey that. Contrary to what seems to be the sentiment doing a lot of edits is a good thing and we should be encouraging users to do so not bogging them down in beaurocracy so they slow down. If someone questions my editing accuracy then go through my edits, if you find some mistakes, especially repetetive ones let me know. -- 3676:
or so for a test run and then if the test goes ok it should be approved. I withdrew mine because I simply got tired of waiting and since knowone was screaming for or against it I just decided there must be enough bots and mine wasn't wanted or needed. No hard feelings, its really not a huge issue since I can easily find things to do but at some point I will probably resubmit it and I am trying to learn a little more about how the system works for when I do. --
4568:. One could ask that if one finds a specific rule which has a high error rate, that that specific rule gets removed. If YouTube is really having so much trouble, then that rule could be removed. But it is by no means a reason to shut the whole bot down. Now, pending any statistics on a significant number of reverts for YouTube, I don't think that this calls (yet) for removal of the YouYube rules, let alone for withdrawing the editing rights completely. 685:. It requires scrutiny and care of operator/editor in making sure the new material is accurate. Judging by the above contributions, even manual human editing is not beyond making mistakes. I see no principal difference between using a script and filling fields of a template — the result is the same, if only editorially cumbersome to produce. In my opinion, any almost equal edits more frequently than 5-7 per minute for more than a couple of minutes is 2595:"Basically what happened here is that North created a new article, it wasn't patrolled for 30 days, the bot tagged it, and North had some kind of emotional reaction rooted in his perceived ownership of the article." perfectly summed up Snotty. Which also proves wthout a shadow of a doubt that the the new system is doing exactly the job it was intended to do: getting SPA to pull their socks up and come back and clean up their articles ;) 1089:
feelings” is precisely the attitude that lead to a lack of consensus. I spent a about a week on this decision (and have also loosely followed the progress of this bot since it was proposed orignally), and many hours reading through the comments about this bot. I can safely say that there was reasonable evidence provided for why users thought this bot approval should be denied. Simply claiming there isn’t, as you are doing, can be disruptive per
35: 943: 4283:. His previous statement above, "The operator could have stopped this action if he would have addressed the requests made to stop editing against consensus." is unfounded. The only one making the current request is Cptnono. The only other editor who had complaints concerning XLinkbot never suggested nor backed its shutdown and after the nature of the bot was explained appears to be satisfied well enough. See 2074:) already automatically remove that particular template when articles are patrolled. Making up a new hidden category that gets added to the bottom of the article would be more difficult to maintain, because many patrollers wouldn't even know what it was and would neglect to remove it when patrolling. Kingpin, I think the bot parameter is a good idea, I'll add it to future applications of the template. 5270: 4884:
knowing if someone did something on purpose (giving examples of correct/incorrect use, for instance) I just assumed bots are approved for mainspace unless the operator indicates otherwise; after all we don't have bots dating maintenance citations in Knowledge (XXG):. I do realize there wouldn't be many false positives and I am OK with these edits if they are supervised, but not autonomous. —
1101:
BRfA is a necessary process, and is similar to other consensus-building/judging processes on Knowledge (XXG). It conforms to Knowledge (XXG)’s standards, and operates through consensus like most of Knowledge (XXG). If you have a problem with this (the way in which Knowledge (XXG) is run) then I am glad I judged the BRfA as I did, since it still seems you are unable to work cooperatively. -
3134:
doing many things easier including identifying what projects are there (some names are and where more meaningful than others), fixing problems when programming bots (take a look at the code I linked to above. In the current schema if you want to capture all the projects and their redirects to do a bot change to Wikiproject banners you need to have much much much more code to do things).
2544:
visible tags should not be placed at the top of unpatrolled articles. It's true that the original request for the bot said that it would place the articles into a hidden category. During the bot approval process, the discussion about how the bot would operate evolved and we reasoned it would be more efficient to add them to the existing new article tracking infrastructure provided by
2786:
Columbia project and associated articles to WikiProject United States. I was just converting so there was no need to double check wether they were valid at that time. Also, the user that brought that up inappropriately removed the US/DC tag from articles that clearly fell into the scope of US/DC (there were some exceptions though such as stations in Maryland and Virginia.
4236:
were not performing its work, a new user may very well add 100 or more links before someone notices and takes action. Assuming the links were inappropriate, it becomes difficult for someone like myself to respond once, say, 10 links have been successfully added by a new user because the early success provides an entitlement feeling. If link additions are reverted
3290:(this is one of the 200+ that I use to reorder sections. I only use it here because it makes a good example). Individually its not a big deal but when you have a couple hundred edits and need to do it over and over again, it slows down the time it takes for the program to process the articles and it makes the coding a lot longer and more complicated. -- 3516:. The bot created thousands of articles with factual errors and had a major security flaw that allowed anyone to run it. There was some drama; the articles were deleted and the bot was deflagged/blocked, but the operator was never blocked, and he's currently running other bots without problems. It was an isolated incident, not a pattern of behavior. 4279:
consensus which allows YouTube to be used some of the time, that consensus is on his side despite the fact that things were clearly explained that XLinkbot is only reverting new editors and IPs and all at the discussion agreed. He never protested but instead headed here. I note that he hasn't answered the question I placed to him above which is,
1187: 966: 2874:
significant drawback or errors so I do not want to be the one blamed when it starts drawing criticism. This will significantly slow the tagging process but at the same time will free me to do other project related things so just let me know. I hope this helps to clarify but please let me know if you have any more questions or comments. --
2431:
many steps still to go. It has to start somewhere, or are you just insensitive to the efforts of those who are prepared to give up their time and get such a project underway? IMHO, just throwing negative comments around a workgroup forum is not the best way to encourage those who can and do seek, and implement improvement.
3576:. I have already built in the stop button and I think its set to go for the most part. I would suggest that both be allowed. Manual edit from my main account. Automated from Bob (although there are few on the list I would trust with Automated and I would feel compelled to check a large number of them to make sure they were correct). -- 4535:). Some think that it is good to have as many links as possible about a subject .. but our policies and guidelines, which have been established by many editors, oppose that view. That a link is on topic and links to non-copyvio material is not a reason to link to it (it is also a reason not not to link to it...) 4519:. MySpace is an example - I did a statistics on that link on 30 reverts, and I found 1 which I would not personally have reverted, though I do think it was not particularly helpful even on that one. Another couple were in a 'maybe' mode, but many were not related to the page, many were dead, many were 4883:
I might agree on automatic runs on some namespaces, but not User: for one. Drafts are drafts for a reason, editors may not wish for bots to start treating them as articles. In general, there are no policies/guidelines concerning the use of references in most namespaces, so there is no reliable way of
4559:
However, and that is why XLinkBot exists, if links on a certain domain have a high hitrate of being unsuitable, then that is a reason to revert additions them and notify the adding editor of the problems. Many new editors have no clue that videos on YouTube are sometimes copyright violations, or are
4464:
but there isn't any more that I can do about it than you can do about the YouTube misconception. At the moment, it seems to be well demonstrated that YouTube links added by IPs and the newest of users are all too likely to be unsuitable if not outright linkspam, and in case of false positives the bot
4226:
I have monitored anti-spam pages for a long period and have seen many complaints about XLinkBot. I have investigated some of those complaints from time to time and have never found a "wrong" action by XLinkBot. Of course there will be some actions by XLinkBot that are not correct, but I have not seen
4206:
I think that XLinkBot's messages are adequately informative. It provides suitable links for anyone who wants to read the details. I am concerned that Cptnono might not have read the user notice XLinkBot left, since it explicitly says that the bot might have been a mistake and that s/he could revert
4175:
There are occasional false positives, but when people have actually bothered to go through the bot's history, they usually come back saying that it's 90–95% correct. (Cptnono might want to go through that exercise. I suspect it would be enlightening.) So it saves the community time, by removing so
4108:
Perhaps but if the bot operator is unwilling to discuss it in light of the 3 issues above then there is a problem. Personally I think there are few occassions were Youtube should be used. I do think that it should be allowed though. I didn't know that there was an exception list for the bot and I bet
3999:
Would appreciate it if you did not assume the worse or make unfounded allegations. The EL discussion does not have the authority to shut off a bot and isn't about the bot. It is about if there is a blanket ban on YouTube so it is going perfectly well as far as I can tell. But yes, it is like throwing
3675:
I'm not trying to sound like a smart ass here but why does it take so long for a bot request to be approved? I have seen some linger for months and others fly in and out seemingly without hesitation and there doesn't appear to be much of a trend. It seems like a week or so for discussion another week
3539:
Its no problem, if a BRFA is needed then so be it. I really don't think its necessary but if I am told to use it then I will. I just foresee drama thats all. To answer your question most of the changes are ok but where I usually run into hickups is when I rearrange the templates or occassionally when
3504:
Your concerns about "escelating series of blocks, warnings and the like" are completely ridiculous. For one, you've already been informed of the bot policy, here and in other places, so that point is moot. Second, if you screw up without a bot flag, you're still screwing up, and can still potentially
3415:
I understand what your saying I really do but the truth is I try and follow the rules of editing and although I understand the need to have bots and the like I just think its rather funny that here you have an editor who devotes a lot of time editing. Thats it, if I was making 50 edits it wouldn't be
3330:
Again these changes being useless is subjective. The Wiki software doesn't care what format teh breaks are in and will accept them many different ways. The catch here is that the information in WP including these breaks is no just in WP. There are dozens of mirror sites and even face book and some of
3141:
Although the breaks are one of them I am looking more for things like blockquote, center, big, strike through, bold, and a few others. Im not just looking to make sure they are closed but that the actually have content. If there is an opening and closing for center for instance with nothing inside it
2988:
In the spirit of full disclosure and in fairness to the issue at hand let me clarify a couple things so you can make a better judgement about whether I need a BRFA. I would also like to mention that I have admittedly made a few mistakes along the way which I suppose is natural if your doing 1000 plus
2888:
It's not a matter of you needing to run a completely automated bot, it's a matter of you at present acting like one: you made 4,901 edits yesterday alone and thousands more each day before that. That seems pretty much like a high speed, high volume of edits situation to me. Perhaps a BAG member could
2845:
I am currently concentrating on US related items that do not already have the US banner. I have also been actively monitoring new articles and add it as they appear or within a couple days. I typically do not include articles that have another state or US related project but I have made exceptions to
2543:
Ok, well to sum up, it appears we have one somewhat cantankerous editor who doesn't appreciate our efforts. I think that if North8000 believes this is as big a problem as he/she is making it out to be, then I would encourage North to start a centralized discussion to see if there is a consensus that
2320:
articles, and cannot possibly be setting any bad new precedents. However, while I'm writing this, another 10 pages have joined the list, adding to a total of anything up to 100,000 pages by the end of the year that we are at least now able to know are in need of urgent attention, and where
2276:
I think there is some misunderstanding all round. As up to 300 pages per day are escaping unpatrolled, untagged, (including attack, spam, hoax, and non English pages, etc) into the Knowledge (XXG), a suggestion was made in October at the VP to extend the 30-day backlog period. The request
4935:
I agree that supervised edits should be OK; the bot owner will want to test it on his/her own user space, and other users may want to invoke it to test draft articles. But I am not aware of any space other than article space where citations are required, so who cares if a citation is less-than-ideal
4316:
FFS, BereanHunter. You don't need to paint me as some sort of dick since I believe the the bot should be shut down. So do you have any reason to believe that the bot should continue to operate or is your argument that I am a jerk? I actually stopped following the discussion at EL since it wasn't the
4235:
of work. The advantage of using the bot is that it quickly reverts certain links added by brand-new users, and it puts a very helpful and non-bitey comment on the user's talk, and it specifically advises that the link can be re-added if wanted which will not be reverted by the bot again. If XLinkBot
3452:
Based on your last comment I wanted to clarify that the above list is only what I do on talk pages. I have a complately separate list of edits I make to articles but I haven't been doing them for a month or so because I am trying to get all the articles in the scope if US tagged as such so I can get
3133:
Concencus was garnered when the decision by the community was made to "standardize" the 1300ish WikiProject templates (except 3 (WPUSRoads, MILHIST and another one I don't remember at the moment) to all start with the standard WikiProject) instead of the myriads of things they used to be. This makes
2689:
Thanks, that finally addresses what I brought up initially. And, as an aside, I never had any complaints about your handling of this, except / until you recently wrote "rooted in his perceived ownership of the article" and Kudpunbg repeated it. This is false twice over. But lets move on. Thanks
1665:
OMG. The question is about this, "Not actually changing the output is by default against bot usage..." Now, I am unwatching this page. Please don't not answer my question again, as there is no point. When someone asks a question and the response is defensive non-answerment, there's usually a reason.
1614:
I see nothing at all there that is "putting you in your place"; at worst H3llkn0wz's tone might be read as a little defensive. It seems to me that H3llkn0wz just explained where you were mistaken and gave some more detail as to why he thinks more input should be sought. What specifically do you take
762:
The dilemma above is that it is not clear whether the restriction on semi-automated article creation applies to the "manual" bot-like template substitution this user was doing. The first proposal tries to cut the knot by expanding the restriction to manual large-scale article creation. This comes at
502:
Exactly. This proposal is ridiculous. These articles are manually created. A template which just displays the title of the article is certainly not remotedly "automated". The articles themselves are manual driven. People should be free to create articles were are notable and not have to ask. Silly.
4354:
I think it is good that it only looks at newcomers but I think that the principle of that is not inline with our stated intentions. I do not think the bot would be approved if its sole purpose was to remove YouTube links from newcomers but that is just an assumption. And why is it acceptable for me
4073:
I'm disagreeing with shutting off the bot over a singular issue. The correct course of action for someone who doesn't think that YouTube should be automatically reverted should have been to try to gain consensus to have the singular entry for YouTube removed from XLinkbot's revert list...not try to
4056:
with comments. I think the current method of automatically removing Youtube videos on sight is a bad one since some videos are added to Youtube, for use in Knowledge (XXG), because they exceed the 100MB limit of the Wikimedia servers. If a way can be devised to allow certain videos then the bot can
3943:
All the operator needs to do in my opinion to stay running is not remove links to YouTube. I believe we should err on the side of caution if the bot is editing against consensus since the policy is clear. It is not the bots job to start discussion "just in case" but to preform menial tasks that are
3519:
This has been explained before and you didn't quite seem to get it, but I'll try again. The reason for the lessening of the distinction between fully automatic bots and semi-automatic tools is because the specific tool used to make an edit is not really important. What's important is the content of
3281:
So in the case of this one, if one group says they like the spaces and another group says they don't like the spaces and there is no community concensus which is preferred, and it doesn't hurt anything either way, which way do you go? Do you leave them be and be forced to add extra codeing to every
3190:
It's considered by some (including me) to be "cluttering the diff" because the diff is full of lines showing that you removed that whitespace. It's particularly a problem on active pages where some people may keep up with ongoing conversations by looking at the diff since their last visit; the real
2919:
Fair enough, just let me know what you want me to do. I certainly can't say I never made a mistake but if I did and found out about it I did try and go back and fix it. Regarding the watchlist thing I mark most of the talk page edits as minor per a request a week or so ago so most of them shouldn't
2863:
Precedent has also been established for these types of edits by users with far more edits (and more edits a day, a week and a month) than I who are currently performing these types of edits with their main accounts. It also states that the edit and tool should be noted in the edit summery, which it
2668:
on all pages created by that process. We didn't create the template which gives the "orders", it has been used for other purposes for well over a year. And I dispute the notion that it is "ordering" you to do anything. It is certainly strongly recommending that the article creator doesn't remove
2554:
rather than create a whole new redundant tracking system. As xeno points out, I did mention this during the bot approval process in an attempt to ensure that the change wouldn't be problematic. In any case, if the templates are widely perceived as inappropriate for some reason, there is already a
2430:
North, just decoration? Your own comments are disparaging those users who are right now in the process of doing something about the backlog - please check the timeline by kindly giving a moment to read the preceding threads. You'll se it's in it's first week of operation of the first of
2237:
Well, there seem to me to be two issues: (1) would/does the wider community approve this and (2) was bot approval given for tagging these ariicles? For me the latter question is the more immediate. By the way, when I looked for an example tag transclusion (not bot action) the first example I found
1100:
I fail to see how the slow-nature of BAG has anything to do with this. Threatening to take this to ArbCom isn’t constructive (although you are of course free to do so). In no way am I (or any member of the Bot Approvals Group) attempting to stop members of this project from editing Knowledge (XXG).
1088:
My comment that you need to work with the community is not wrong. It’s perfectly true that when proposing something new, the proposers should work in cooperation, to reach a consensus. Simply denying that there is opposition to the bot, or calling the opposition “unreasonable” or based on “personal
447:
covers specifically lower-speed tools and scripts that can assist users to make decisions but leave the actual decision up to the user (see Assisted editing guidelines below). Any program or tool which does not allow the user to view each edit and give an instruction to make that edit (that is, one
414:
That discussion dealt with "semi-automated or automated" creation of stubs. Though there were confusion about the exact meaning of semi-automation, it is clear that the majority of editors were talking about bot or script edits. There has not yet been a discussion whether article creation by manual
4815:
leading to the approval of the latest version of Citation bot that there was an implicit assumption the edits would be done in article space. Other spaces, such as Knowledge (XXG) space and User space, may have project pages that contain deliberate citation errors as examples of what NOT to do, or
4551:
linking to a large number of YouTube videos. XLinkBot does not disallow editors, it, at first, friendly notifies (not warn!!) them of the common problems with YouTube (or other links), and asks them to reconsider. It will not edit war. Only when editors are persisting in adding numerous youtube
3382:
In response to your comments VM that particular one stems from me updating the code to put the banner on a single line vice multiple lines. I will update it to not do this unless I am doing a more significant edit at the same time. Aside from uneeded minor edits like this (and even those should be
3137:
On the header spaces issue again I only do this as a minor edit but I don't think its cluttering the diff at all. And honestly I never liked that it includes spaces by default and rather thought of it as one of those little flaws in the programming that knowone has ever taken the time to fix (like
3054:
on WPMILHIST is missing or no I delete that empty unneeded parameter. This makes it easier to update in the future, reduces the clutter on the page, is in keeping with the instructions for that WikiProject (they state if the parameter is not needed don't add it) and reduces the amount of space the
1652:
is the policy, particularly the parts "In order for a bot to be approved, its operator should demonstrate that it: performs only tasks for which there is consensus" and "The request will then be open for some time during which the community or members of the Bot Approvals Group may comment or ask
137:
and removing links to nonexistent pages is part of maintaining. However, the bot has been going at quite a high rate (probably because the pages haven't been processed with the new option by other bots yet - it was only added yesterday), so I thought I would stop the bot and check that everyone is
4571:
Cptnono, I find 'the operator has refused to adjust the parameters it uses when dealing with YouTube videos' an incorrect description of what is being said and done (to say the least; you did not ask for adjusted parameters, you just demanded a shutdown without showing errors), and 'Automatically
4432:
is why I don;t like the actions of this bot. The misconception that there is a blanket ban is so prevalent. That of course is not the bot's fault. I do admit that the fact that it is often a useful bot. I also appreciate a comment from a BAG member. However, I would like some comments on if it is
4385:
to override the bot in any individual case. The hypothetical concerns that a newbie will choose one of the tiny fraction of usable YouTube links to add (and then be offended by the bot's polite message) is not convincing enough to outweigh the vast majority of the time that the bot's edit will be
3358:
Mostly in reply to Anomie, my interest here is the accuracy issues (as in the two examples brought up on his talk page that I linked out above) which I think just comes down to needing a clear definition of which categories (or other definition) are being tagged and maybe someone more in-the-know
2799:
guarantee that the bot will not misedit some of the pages due to the nature of the edit being made. Additionally, with the antibot sentiment I mentioned before I have no desire to run my own bot so all you will be doing is A) creating more work for others and B) slowing down my efforts in getting
2789:
To the original issue of my edit rate and needing a bot. The speed of my edit is directly preportional to the amount of manual checking I need to do. For example if I am taging a page for a File, Category or template that related to US I can do it extremely fast because in most cases the page was
2565:
template would just need to be trivially updated to hide the banner when the bot parameter is present. I'm not saying we should do this now, since I (like seemingly everyone else here) disagree with North8000 about the inappropriateness of the banners. Basically what happened here is that North
2462:
Nobody is implying you or your views dumb, they're simply disagreeing, it's not the same thing. I fully understand that your suggestion is made in good faith, and we simply have differing views as to what's the best method for dealing with article issues. It would be nice if you extended the same
2356:
Our readers appreciate being warned about potential issues in an article, and I dare say would like to know if an article has been peer reviewed (since the editor who originally came up with the content is unlikely to be checking for OR, NPOV, etc. And of course it's much more difficult to review
844:
Prop 1 is on the face of it a good idea. However there may be some edits that require a level of scrutiny that is so low that calling it scrutiny might be considered litotic. I'm thinking for example of the monthly maintenance categories, where the manual approach is open all the redlinks, then
563:
and this should definitely be one of them. 10 seconds is a very short time, and even if a template was being copy-pasted that is still, in my opinion, not enough time to do all the appropriate web page opening and checking that manual editing implies. Also, if this really was being done manually,
4538:
YouTube is another case. Yes, there is good info on YouTube, yes, I could, can, and will whitelist links (and every admin can adapt the youtube rule to exclude certain rules, and anyone can request that on the talkpage of the bot, on a talkpage of one of the operators, or come to IRC) which are
2785:
First let me mention that most of the "mistagging" was jsut asking me to calrify a little better, which I have tried to do. Not actually mistagging. The situation with the WMATA stations is a little different, that was a difference of opinion. That came about because I was adding the District of
2597:
For these reasons, experienced editors often scrutinize the editing activities of new editors and SPAs carefully in a discussion to discern whether they appear to be here to build an encyclopedia (perhaps needing help and advice), or alternatively edit for promotion, advocacy or other unsuitable
2570:
of the article. I was alerted to the complaint, and I tried to resolve it as quickly and civilly as possible. I'm sorry that this issue upset you so much, North, but I can't see what more anyone could have done to help you. Again, in my view, a single editor's complaint shouldn't be enough to
2069:
North8000: FYI that template was not created solely for this purpose. It was an existing template which was already being applied to articles regularly for other reasons (e.g. for articles created by the New Article Wizard). Instead of inventing a completely new tag or new category that no one
1900:
was enough for rough consensus and that the task identifying new pages that otherwise fall off the radar is useful. "Top-level" tag did not seem like a problem (at least I am unaware of any agreement that bots aren't allowed to do this). As far as I see it, the bot is not "mindlessly placing top
3069:
In summary, although there are some things here that could be done with a bot, many require watching. In the case of the high speed edits of late, if you were to review them, virtualy none required more than a glance to see what had change before hitting save. Please let me know if you have any
2004:
FYI, I was largely responsible for the initiative that launched the creation of this bot. One needs to understand that this encyclopedia concerns three large groups of people: those who read it, those who contribute the articles, and those who keep it free of crap (there is often some
1096:
The Wikipedians working in the Gastropod’s WikiProject are expected to support this bot, since a large number of them seem to have the objective of creating a page on every single slug/snail (or similar). Since the members of the project are users who agree with this objective, using their wide
1037:
Why this is wrong: Opposing wikipedians provided no reasonably evidence, that anything is wrong with this bot. Their opposing is based on their personal feeling only and not on wikipedia policies. All wikipedians who edit gastropod related articles are supporting this bot and no one of opposing
2794:
I can, the problem here is that many do require review and with the hanti bot zero defect sentiment lately I feel its rather better to do it manually and be able to review them than do them automated and get blocked because my bot did something it wasn't supposed to do. I freely admit and feel
1983:
That was a a part of what was behind my complaint. The first half of my complaint was that robots shouldn't be placing top level tags on articles, not that such was violating any specific rule/agreement regarding that. Further to that I have never seen robots doing that nor being allowed to do
1627:
Yes, defensive and ignoring my request for a link, but shoving the same policy at me, again, without linking. I'm a little overwhelmed lately by how much policy is defensively quoted without links to the actual policy. When I eventually find the policy, it's usually not what is quoted, though.
4278:
on Feb. 12 and he garnered no support for the idea of shutting the bot down. The thread died down on the 13th and without any further input from him there, he switched to this venue several days later with no consensus to back him up. He is attempting to state that because the community has a
3467:
I also forgot to mention that I there is a certain order I do the edits in so if for example you tell me I cannot do the template redirects anymore (which is the first to process) I will have to completely rewrite my code to compensate for the thousands of redirects (multiple times due to the
2315:
was inadvertently used by Snottywong instead of saying 'method', but in prìnciple nothing has changed from the original project. It was a change to a technical issue, such as for example instead of going from A to B via Y, we now go from A to B via Z. This bot is not doing
3500:
It would also allow you to speed up. If you separate the tasks that need review from those that don't, you could run the latter under AWB's fully automatic mode. Thst said, which of the tasks actually requires review of each edit? I agree with Anomie, removing spaces in headers does not help
2873:
In summery of the above I do not believe that bot approval is required for this ongoing task but if concensus determines it is then I will start passing off the tagging to someone with a bot or the desire to run one. I foresee the chances of mistakes are too high as an automated task without
1751:
There were some bots that dealt with longer lists of common fixes, like piping and stuff, that AWB doesn't have a full repository of. I was wanting to compile such a list of non-controversial fixes myself; including if they need human oversight or not. Perhaps on a project page. There's also
5230:
I'm not sure if this request for restriction is really necessary. The request has arisen from only one incorrect edit in the last week as far as I can see. In any case the citation bot must continue to be permitted for the template namespace to support the cite pmid, cite doi templates etc.
4767:
No trick, the page generation is just wrong. It's too bad we didn't made subsequent requests use a slash instead, e.g. "Knowledge (XXG):Bots/Requests for approval/RjwilmsiBot/8", as that could easily be made to work correctly. With the way things are, someone would have to make a hack using
2336:
So, the patrolling process is broken (huge backlog) and this does nothing to help that. My note /advice is to reduce the scope of the patrolling review to serious problems that apply to brand new articles. (notability, advertisements, etc.) Reviewing for other things is very laborious and
4563:
Now, Cptnono. This bot was designed to revert additions of external links by new editors and IPs which were very often (most of the time) problematic (if they were always problematic, it would be blacklisted). If there are particularly grave problems with a certain external link (i.e., a
2998:
If the assessment is missing from a WPUS tag and certain other projects have an assessment I make the WPUS assessment mirror that (For example if WPShips has B WPUS will reflect B). I only do this for about ten of the more common, active and more reliable projects such as (Wisconsin, NRHP,
2516:
Thanks. I did suggest a narrower scope of initial review, but it was a sidebar to the main discussion. My main thought is that if articles with severe initial problems (notability, advertisements) are slipping through due to overloaded patrolers spending a lot of time with general article
1948:
template is perfectly appropriate, because the article is new (31-32 days old in most cases) and the article is unreviewed. The template is not intended to imply that your article is necessarily deficient in any way, just that the article hasn't been independently reviewed by anyone yet.
1482:
On the Norwegian Bokmål Knowledge (XXG) we have a system in place that uses template inclusion for signing up, and which allows inclusion on sub-pages in userspace so those who prefer can get the suggestions posted there (e.g. "/Miscellaneous/Suggestions"). We'll also shortly run the bot
2859:
Regarding the third sentence. Concensus has been established that tracking the articles and items in the scope of US is desired and as further evidence of this, previous to my efforts to WPUS, the mechanism was setup for the tracking of these through the Class assessment structure of the
5036:
does not include a citation template in it's source code. In general, I would be very concerned about changing a citation in Template space for fear that there could be two versions of the citation, one that is generated by the source code on-the-fly, and a different one in the template
4257:
as far as I know, if you re-revert XLinkBot, it won't edit war with you, right? If that's still the case, then I don't see a big deal here. If XLinkBot makes a mistake and the youtube link was indeed not a copyright violation and was an appropriate link, then just revert what it did.
4552:
video's in a short period of time to different pages XLinkBot may issue warnings. XLinkBot does not have a bot-bit, so that recent changes patrollers will see the XLinkBot reverts and may re-revert, and even when XLinkBot gets to a warning level that editors get reported to AIV, it
4505:
The antivandalism bots have complex heuristics to find vandalism, and revert that on sight. However, also there there are mistakes. Those bots sometimes revert edits which are fine and OK. As for the blocks, protects, abusefilters and spam blacklist, there are cases where the bot
4850:
That's a senseless/overkill restriction. There is perhaps a case for a restriction in the User/Wikipedia namespaces (aka, only run in these namespace on request rather than systematically crawl these pages), but there's no reason why the bot should be restricted from running in the
3434:
Actually, a few things do change with a BRFA: it can get you some feedback from people more familiar with doing large numbers of edits; it can get you the bot flag, which helps keep your copious edits from annoying other editors; and it gives the community a little reassurance that
2306:
Nobody cares if they now have an ugly template on them placed by Snotbot - the creators, all SPA, have long since moved on from Knowledge (XXG) leaving us to clean up their mess, and the content of those pages is a lot uglier than any banner that might be on the top of
1241:
I don't think this is a form of spell-checking, Xeno, but applying a general rule to headers. Problem is, it is too error-prone (seen the examples you gave). May I suggest the latter solution, allow it to do 'standard' headers (there are possibly more, but these are obvious).
4135:(ec)Or the bot can not remove appropriate links against consensus. Since the operator has not coded it to do so it should not be allowed to function. Why is there an assumption that the bot should be used as a safety valve instead of as a harmless method of doing mundane tasks? 2956:
Some points of the above discussion seems to focus on whether these edits are necessary or not. This is not the scope of this talk page. It is human judgement and human decision on how to use their editing tools. The matter in question is the method used, namely, is the user
4202:
carefully adhere to the guidelines. There is no guideline that requires us to accept YouTube links. There's one guideline that says these links aren't absolutely prohibited (it weakly discourages them), but there's a big gap between "not actually prohibited" and "must be
2054:
the tags placed by human editors. This way we we can easily switch between invisible and visible bot-tags, something we can presently do. This is an idea I would have suggested before, but I stopped following that discussion after Snottywong started coding instead of me. -
677:
Given the heated issue, I suggest a simple and direct proposal. If we have not fully established what "semi-automated" stands for, then perhaps we can decide if high speed use of templates falls under semi-automation. Alternate solutions and proposed rewording are welcome.
1047:
Kingpin13 suggest to "forming a consensus before submitting another BRfA". But there existed consensus about task of this bot at Wikiproject Gastropods for over 6 months and earlier. And only one critic have appeared after such time who initiated this Request. The only
4510:
mistaken. Try (as an IP) to cite literally an explicit piece of text on the page of a pornography writer making sure there are a significant number of 'bad' words in the text .. I think the chances are quite big that you will be reverted and will receive a warning.
2155:
Although nobody really addressed either of my 2 points, (and this bot is setting a bad new precedent on both of those,) I do sincerely appreciate that folks took to respond and to try to explain things, and also apologize if my tone anywhere was impolite. Sincerely,
2669:
the tag (for obvious reasons, since the article's creator is not an unbiased reviewer), but it is not preventing you the creator from doing anything, or threatening the creator with punishment if they remove the tag. Therefore, I think your criticism is unfounded.
4601:
Just another annoyance with the youtube link reversion: I changed an existing link to a removed youtube video into a working video, also on youtube. xlinkbot reverted my edit, so we've still got a youtube link, but it just doesn't work. This does not feel like a
2019:
All these aspects should be borne in mind before criticising the work of others just because they affect one user's contribution(s). Any reader or editor is more than welcome to consider joining one of the many projects that help to maintain quality.
1855:
It looks like the robot is mindlessly placing top level tags on all articles that have a backlog in patrolling. IMHO no robot should be placing top level tags on articles. Worse than that it "giving orders" based on non-existent policies. Thanks. Sincerely,
2517:
improvement type review, then it might be good to narrow their scope to the point where every new article gets at least a quick review for serious problems. Especially since the editors already know that a brand new article needs a lot of work. Sincerely,
5252:
I want a quick approval from another BAG member for this, but it's not really worth a full BRfA. I've talked on IRC about this. So just requesting that SDPatrolBot can report troublesome users to AIV, instead of just edit warring with them over the tag. -
5164:. In this particular case, the documentation does not contain any example of what a finished citation would look like, but if it did, a change in the documentation page by the bot would make it contradict the citations that would be built by the template. 4433:
appropriate to assume that additions of links from newcomers is bad. Although stats might show it to be true, the idea seems against the project's principle's. If the bot is allowed to continue to make such edits, I will be sure to add it to the essay
1680:
Mass changes that don't affect the content of a page and don't have a compelling reason otherwise are usually not done. It's a waste of resources, and it clutters up watchlists. The bot policy mentions cosmetic changes, it's along those same lines.
1478:
handles its regular users, and am wondering if it will require to file a BRFA or not. Currently users can get regular suggestions by signing up on a list, and then we process the list about once a month and post suggestions to their user talk page.
4816:
pages that compare and contrast various citation styles, or draft articles where unexpected changes would not be appreciated. But, in fact, the bot is editing Knowledge (XXG) space. I request the approval be revisited and limited to article space.
4514:
XLinkBot works similarly, there are links which have a huge hitrate on being 'bad' - most of the links XLinkBot is reverting are plain spam, but there are also many of the others which are, really, hardly ever helpful and have special mention in
1987:
The second half of my complaint was that the robot's tag is "giving orders" implying non-existent policy. Implying that primary author on an article can't remove a top level tag invented and worded by one person and placed by a robot. Sincerely,
4240:, the user works out that pursuing their aim of adding links will not be productive. Also, many new users can add links more quickly than another editor can remove them (because you are supposed to individually check each link in each article). 1709:
Hey BotOps, I was wondering if anybody knew a place where there was a full list of cosmetic changes to be done to an article. The types of changes that do not merit their own bot task, but should be done if an edit is being done anyway. I know
1084:
The number of Wikipedians who opposed/supported is not as relevant as you seem to presume. The BRfA was evaluated based on the strength of the arguments presented, rather than the number of users who felt personally that the bot should run or
587:"The majority of user scripts are intended to merely improve, enhance, or personalize the existing MediaWiki interface, or to simplify access to commonly used functions for editors. Scripts of this kind do not normally require BAG approval." 4380:
member: There is no reason to stop the bot at this time, as there is no evidence that the bot's heuristics are having excessive false positives, the messages left for newbies by the bot are extremely civil, and it is exceedingly easy for
1398:
is a relatively simple task but has been awaiting approval for almost a month. It's holding up template development so it'd be nice if I could run it over the weekend. Would a member of the team be able to evaluate it, please? Thanks,
3785:
correctly because the page is neither a redirect nor a disabiguation page. I can add the ability to deal with hatnote disambiguation (it's not hard, but it will cause a massive increase in data transfer), but it won't be 100% perfect:
3572:. I only submitted the list of edits I do on talk pages for now but once this clears I will submit the list of article space changes separately. If you want me to do this as a bot account rather than my main account I have one setup as 2293:
These pages are unpatrolled because they are in such a poor condition, many patrollers lack the experience to know what to do with them. They often lack all identifying marks such as cats, tags, stubs, talk page templates,
1811:
is approved to delink images that have been OKed by admins and approved users and prepare them for a batch deletion. As part of the process, I'd like to have the bot move the talk pages associated with the file to the new name; e.g.,
1815:(note that file talk pages for commons content are not deletable as G8). It's something I'm currently doing by hand. Would this be something I would need to get approval for, or would it fit broadly enough into the current task? 1278:
A list of exclusions would probably be too tedious to compile. So the other option of making a list of common accepted corrections is preferred. I don't oppose these small changes, as long as they are almost never controversial.
3962:. That's like throwing the baby out with the bathwater. You don't have consensus going your way in the EL discussion so you decide to...forum shop over here? That's what it looks like. The merits of XLinkbot so heavily outweigh 4451:
I for one hate the misconception that there is a blanket ban on "primary" sources, or that there is some sort of real difference in the way we can use a "primary" versus a "secondary" source besides meeting the requirements of
3909:
There is no blanket ban on linking to YouTube videos. Automatically removing these links has proved problematic. For bots to be approved, the operator must demonstrate several things. Of these, the following are problematic:
2852:
The first "Bot-like editing" in fact states "Note that merely editing quickly, particularly for a short time, is not by itself disruptive." So to this I ask, is my editing disruptive and if it is how (so that I may adjust my
1097:
support as a “consensus” is incorrect, as it is a bias sample. You also seem to have the mistaken idea that the only users’ who opinions matter are those who are interested in writing content about the said slugs and snails.
3439:
has looked at the task at some point. Also, "a lot of edits" is not necessarily a good thing, and while WikiProject tagging isn't bad and can help organize some things, it's really not on the list of edits we need more of.
3047:. This list was accrued based on a list from Rich F, Magioloditis and myself but consolidated into one list for us all to use. I continue to refine it as new templates are created, deleted, changed etc. or as I am notified. 2477:
So, what do you call "Uhh, so what you're saying is if we ignore the problem, maybe it will go away?"....(mis)restating my position in a way this is obviously ludicrous?" That was the ONLY thing that I was responding to.
1929:
template on the top of any pages which have existed for more than 30 days and haven't been marked as patrolled by a new page patroller. The only pages that are modified are unpatrolled articles which no longer appear on
749:
edits (i.e. high-speed or large-scale edits that make errors an attentive human would not) are liable to be judged on the same terms as an automated or semi-automated bot, even if the methods actually used are ostensibly
314:
I agree this should go through BRFA. It's obvious that these are semi-automated, and the use of subst:PAGENAME to fill in the "official name" and the name in the lead is inappropriate for those that are (disambiguated)
2961:) paying due attention during his work? Can anyone point out any problems so it can be judged if the user is indeed committing mistakes or his oversight of edits is sufficient. See, for example, where another user has 1560:
just sitting and not linked from anywhere and I'm not sure if it's a serious request or not. It was created by the bot account itself which has been indef-blocked for its username and no bot owner has been identified.
3703:) to properly deal with renamed images. Since it's been a year since ImageRemovalBot last ran and two years since FairuseBot last ran, can I simply start them up again, or is there some procedure I should follow? -- 2969:'s. So this definitely falls under near-bot-like. The question is really if the user is making mistakes due to the speed of editing that a closer look would not make and whether the community can live with these. — 478:" Cut-and-pasting a boilerplate template is semi-automation as far as I'm concerned - especially when you don't even correct the official name to remove disambiguators which do not form part of the official name. – 3240:
No if you take a look at the link I proveded above you will see at the bottom that I also standardize some other templates but again only if I am doing something else more significant and for the same reasons. If
2867:
As a side not this emphasizes the point I tried to make prior that the rules about running bots and the hrole of BAG/BRFA needs to be clarified. As written the rules are simply to vague and leave to much room for
2846:
this on occassion based on the importance of the article or as it pertained to the US as a whole. This includes Articles, templates, categories, files, etc. There is an end in sight but it will be a couple months.
2571:
force an approved bot to change its behavior. I don't see any point in continuing this discussion any further, but please do let me know if a more centralized discussion on the topic becomes necessary. Thanks.
1038:
wikipedians edit gastropod related articles. There is a community of gastropod-related editors and there are only 4 wikipedians who does not edit such articles and who disagree with this bot without any reason.
2638:
If you want to continue to evade those questions, that's no big deal. I was ready to leave this thread a long time ago. But invention of false things about me constitutes personal attacks. Please stop that.
1631:
I am not, however, interested at this point, and I shall unwatch this page. Apparently it is also resident evil to change one's mind about posting a comment, so I was stuck leaving this up without withdrawing
4830:
I would have thought a bot editing templates designed for mainspace would only edit the mainspace. So I do agree it shouldn't edit other namespaces without prior discussion due to inevitable false positives.
4543:
has a number of points which are 'ticked' by YouTube. And do note, some of the YouTube video's are plain spam, they are added by the 'owners' of the channels to get the traffic with which they make money.
4351:
But if consensus is that it only reverts new users and IPs then we should consider changing the "anyone can edit" mentality of Knowledge (XXG) if we can finally admit that we do not respect the edits made by
4607:
So according to the standard, this bot violates it. However, if community consensus is that violating the written standard is worth it then so be it. But don;t pretend it is editing within the alloted rules.
3817:(and potentially others)? Currently these 2 sections must be manually updated but I would like to make these 2 section of Portal:United States as user friendly and maintenance free as possible. Any ideas? -- 3790:
lists over a hundred different ways of creating a disambiguation hatnote, there are probably unlisted ways, and there's always the possibility of freeform wikitext, which the bot will never handle properly.
3251:
is accidentally placed below the wikiprojects (you might be surprised how often) I (and now AWB) move it to the top above the WikiProjects. So for things like this its easier to program something like this:
1963:
Out of curiosity, why does this need a tag (and a rather large one at that)? This isn't really useful information to a reader. It seems like the same thing could be accomplished with something less visible.
4908:
P.S. Per clarification, I was referring to automated edits. I am perfectly fine with user initiated per-page edits. After all it is then the user responsibility to verify that what they are doing is fine.
3939:(It does not. In fact, this bot caused a misunderstanding of our policy when I was a new user since I assumed YouTube videos were not allowed under any circumstance. Certainly a disclaimer would be needed) 1064:
and all talkpages of this WikiProject). Solve it as soon as possible, please, prior it will appear at Arbitration Committee and especially before gastropods-related editors disappear from Knowledge (XXG).
3591:
How long does it usually take to get approval or disapproval? I would like to start working again ad since I have self imposed not editing until this matter is resolved I would like to get rolling again.
2286:
They enter a page called Special:New Pages where they are highlighted in yellow until the 'mark this page as patrolled' button gets pressed, or an edit is made that auotmatically marks the page as
4748: 2279:
First and foremost, at this stage, no new page patrollers are even supposed to be working on the pages tagged by Snotbot, and they probably won't be for a while to come. To explain clearly:
2856:
To the second "Assisted editing guidelines" I have been granted permissions to use AWB which is a "tool". This in part covers the approval mentioned by the first and second sentences of this section.
3781:
I'm reasonably familiar with the general issue of "obviously incorrect disambiguation", as one of my goals with FairuseBot was to deal properly with them. The bot can't handle the specific case of
4355:
to bring up reasoning based on precedent while Berean Hunter only brings up reasoning based on assumed motivation? So we do not need to "continue the discussion" but it was not me who derailed it.
344: 3130:
is used to combine multiple projects into a group for a variety of reasons. Basically though they reduce the amount of space they take up on the talk page when you have more than 3 or 4 banners.
251: 2849:
I previously asked if I needed to request a bot for the creation of talk pages because the rules state creating pages needs one and I was told no. That talk pages are not included in this rule.
3509: 2101:← I think the most important question is: are the new page patrollers giving these tags priority when they are patrolling? i.e. ensure they've all been removed before moving on to the regular 1377:
If you intend to continue with the request, feel free to re-open it. I waited 6 days for an answer before closing it, after your comment that seemed to say that you didn't intend to continue.
133:
option which also removes interwikis to different namespaces, and other things that should generally be checked by humans. I didn't think this would be an issue, since the bot was approved to
2014:
They warn the readers that what they are reading may not be entirely accurate, and in the worst case scenario may even be a blatant advert, a hoax or a personal attack page.
4231:) that any examples of bad edits by XLinkBot have been provided. The amount of damage caused by people adding inappropriate links should not be underestimated, and XLinkBot saves editors a 1628:
However, a link, sometimes, would be nice; for a policy administrator, I consider it necessary. But, those in the know on wikipedia seem often defensive when a link to policy is requested.
1225:. Should approval for this line-item of the linked BRFA be revoked? (or restricted to a well-defined set like ==External Links== → ==External links==, ==See Also== → ==See also==, etc?) – 4564:
significant number are plain copyvios) then we, IMHO, should accept a bit higher error rate, others which are less grave should have a low error rate. XLinkBot reverts on specific rules
4000:
the baby out with the bathwater. The operator could have stopped this action if he would have addressed the requests made to stop editing against consensus. So it isn't my fault, is it?
3902:'s editing rights. Although thew bot might do some fine work, the operator has refused to adjust the parameters it uses when dealing with YouTube videos. The recent request was made at 1195: 3633:
I thought about it a little bit and since my stopping from editing was a self imposed thing I am going to resume but at a much slower pace. Please let me know if this is a problem. --
98: 90: 1093:. Because you are unwilling to listen to the concerns, or address them, you are not working in cooperation, thus you can not compromise, thus the request was closed as no consensus. 4812: 3513: 319:). Notwithstanding the editor's dubious assertion that they are "completely manual", cutting and pasting a boilerplate template is still "semi-automated" as far as I'm concerned. – 85: 73: 68: 63: 2297:
These pages are far too many to be manually patrolled by the experienced editors and admins who nevertheless occasionally have a stab at the bottom of the 'unpatrolled' list.
454:
are personalized scripts (typically, but not exclusively, written in JavaScript) that may automate processes, or may merely improve and enhance the existing MediaWiki interface."
1357: 3194:
So you do uselessly change BRs to add or remove that slash? As for paired tags with no content, do you also look at the article history to see if it's the result of vandalism?
2820:
I at least am not talking about bot per se, just a request for approval for doing what you've been doing to ensure that there are clear definitions of what's being done. See
2756:
Given that just looking through his latest 50 contribs I see that his edit rate was up to 11 tags in a minute at one point and apparently mistagging some recently (see e.g.,
2214:
As an FYI, this is not the first bot to be approved to place tags at the top of articles. If you don't think that the wider community (i.e. outside of those who commented at
4331:
If you want to continue the discussion, please respond to the points raised above. In general, there is no perfect solution to any problem, and some pragmatism is required.
2627:
Why don't you read what I actually said instead of imagining the above baloney? What happened at the article itself was too minor to worry about. I brought up two issues:
2446:
Again, I was responding to your sarcasm which implied that what I said was dumb, that was my only topic and intent in the last post. Sorry to anyone if that was not clear.
2133:, but most established new page patrollers aren't reading that page very often. Eventually, people will probably start to take notice and work on clearing these articles. 912: 2842:
using a bot in this instance. Other than the volume I am not doing anything that should require approval. For further clarification I provide the following explainations:
2391:
places where there are likely to be problems to prevent editors from wasting energy searching for problems rather than fixing them.. I fail to see the problem with that. -
1594:
It's obvious from my post that I don't really know what is going on with the bot, but I thought I would try commenting and learning. Big mistake. I've been put in my place.
352: 5160:
you see that it consists of a bunch of logic that builds a template, and it is unlikely a bot would recognize it as a citation. It also has a separate documentation page,
4176:
many bad links. It certainly doesn't cost us more to revert XLinkBot's occasional false positive than it costs us to revert the anons' frequent inappropriate additions.
2283:
New Pages are tagged as new on creation (but only the ones made by the wizzard get the ugly banner) and get a 'mark this page as patrolled' button put on them.
605:. I believe that in this context commonly used functions is intended as warning/welcoming users, protecting pages, and other basic tasks. Certainly not page creation. - 4599:
So no, not anyone can edit. New users are deemed problematic so their edits are reverted. Just admit it. Unfortunately, we have an IP on the bot's talk page who said: "
1808: 1129: 673:
Manual high-speed mass article creation/modification using a single manual technique (such as, pasting boilerplate templates) should be treated as semi-automated edits.
4572:
removing these links has proved problematic' is yet to be proven (that there are good YouTube links does not mean that the majority that is added is actually not). --
2357:
one's own work), and those editors who are keen to review work need some way to find articles which need to be reviewed, or their eagerness and talents are wasted.. -
4074:
shut the bot off. I didn't see such any such consensus formed after the discussion at the EL noticeboard. There should have been more effort there. This effort looks
2962: 1557: 4428:
Comments from BAG is great. I am pretty sure there is no longer any chance that the bot will be turned off even though I disagree with part of its function.. Ugh...
2008:
They add that article to an appropriate hidden category that is watched by editors who are interested in improving articles that have been improperly created.
5037:
documentation. The bot could create contradictions between what actually appears in the articles where the template is transcluded, vs. the template documentation.
5276:
Clarified details. Multiple (4+) tag removal by author results in AIV report instead of spamming warning user talk templates. Trusted operator, uncontroversial. —
3569: 1874: 2555:
very easy way to hide the templates. With the exception of the first few days of bot activity, the bot includes a "bot=yes" parameter on all templates. So, the
1035:"because the supporters are the ones proposing this, they need to work in cooperation with the community, to reach a proposal which suits everybody (reasonably)." 377:
do you really want to argue that use of a template is "semi-automated", that might well drag in every prod and tag. is there a ruling that approval is required?
3050:
I deleted some uncommon and uneeded fields from several WikiProject templates if they are not being used (i.e. = blanks) or if certain ones =no. For example if
1653:
questions. The decision to approve a request should take into account the requirements above, relevant policies and guidelines, and discussion of the request."
4556:
needs a human editor to review if the editor should be .. sanctioned. XLinkBot hardly EVER gets to that level, and I don't think that it ever has on YouTube.
3966:
that this request has a snowball's chance in hell of succeeding. You do not have consensus in your favor...this looks like a bad attempt at strong-arm tactics.
3647:
Is there any chance someone could take a look at my bot request please? Is there anything else I need to do or any other concerns that need to be addressed? --
845:"ctrl tab, shift alt S" until your fingers fall off. It's still useful to go back at the end and make sure al the red-links turned blue, but that's about it. 392: 290: 2290:
Special:New Pages stays live for 30 days, after which, all still unpatrolled new pages are allowed to sneak into the Knowledge (XXG) through the back door.
1342:
Just be aware that my PHP code is crying itself to sleep because it believes it lacks purpose. It wants only to perform the action for which it was created.
1831:
I don't think this fits under the current task directly, as this is a completely different action. If you fill a BRFA, it can be resolved fairly quickly. —
1757: 202: 21: 3274:
so I would have to have that string of talk header redirect combinations at least 6 times if I didn't standardize it once up front before doing the others.
4791: 4386:
entirely appropriate. That said, however, I do encourage the operator to look into the possibility of whitelisting those YouTube channels that are run by
2634:
the robot's tag is "giving orders" implying non-existent policy. Implying that primary author on an article can't remove a top level tag placed by a robot
745:
Human editors are expected to pay attention to the edits they make, and ensure that they don't sacrifice quality in the pursuit of speed or quantity. Bot-
228:
says that they were created manually and the user has authorization to create these stubs. I see no link to any bot approval. Does bot policy apply here?
1753: 915:
has been open for more than a month now. The last BAG edit was on 8/30. Can someone from the BAG team please look at the consensus and provide a result?
3741:
for automated removal of images under 10c where a rationale exists but the article link is "obviously" incorrectly disambiguated, e.g. the FUR links to
3035:
I move blp=yes from the bottom of the wikiproject banner shell to the top directly before |1 if it appears at the bottom of the banner (Done with Regex)
2463:
courtesy towards me, and not presume that I'm being sarcastic when I'm not being: my suggestions too are made in good faith and are entirely serious. -
4851:
Template/Project/Portal/Help/etc... namespaces (especially in the template namespace), or disallowed to run in the User/Wikipedia namespaces entirely.
4018:
additions of YT links? ...or you are seeing new users and IPs being reverted by the bot? I'm under the impression that the bot is only reverting those.
415:
template copying (which is, assuming good faith, what User:Starzynka is doing) is in par with semi-automation. Perhaps this is the time to have one? —
3722:, although if it doesn't already you might want to consider having it log somewhere which images it removes from which articles in case of undeletion. 1635:
WP:BRFA doesn't get many comments on bots to begin with. I think being defensive and ignoring input or questions is not a good way to get comments. --
3093:
Is there consensus anywhere for this cluttering of the diffs by taking spaces out of section headers? Particularly since the "Post a comment" button
3787: 1824: 1061: 3520:
the edit, and when the edits are made in large quantities and at high speeds, the communication skills and responsiveness of the editor/operator.
3383:
rare) the error rate should be low but admitedly, wether donen manually or by bot it still won't be 100% and by bot will likely be much higher. --
2046:
or similar parameter to the templates. Even if the parameter doesn't do anything presently, it then allows changes to be made at a later dates to
4744: 2566:
created a new article, it wasn't patrolled for 30 days, the bot tagged it, and North had some kind of emotional reaction rooted in his perceived
1486:
Do these kind of changes require me to file a BRFA for an added task to SuggestBot? Also, let me know if there's anything I've missed. Cheers,
298: 1760:. I'm sure there's more. I wonder if a list can be made and then approved by BAG as a list of changes that don't need approval or discussion. — 4769: 4547:
This however does still not totally disallow linking to YouTube. If a YouTube video significantly adds to a page then sure, why not. And we
2995:
Add WPUS if missing to US related articles and usually were there is no other US related project present (this is done particially with regex)
1666:
Namely, the answerer was defensive already. It might be easier and less defensive all around to provide links when first asked. Thank you. --
476:"high-speed semi-automated processes may effectively be considered bots in some cases, even if performed by an account used by a human editor 4162:
There seems to be some confusion. Kumioko, can you tell me just how many FedFlix folks you have who are (1) adding good links from YouTube
2795:
compelled to state in advance that if I am required to use a bot I will not be able to for many of the changes due to the manual nature and
3615:
Ugh, ok thanks. I guess thatll give me time to build the project Page for theh Library of Congress project and start updiating the data on
3468:
programming of some of the changes) to all the projects rather than just program for WikiProject Foo (+ the 3 projects mentioned above). --
1215:) was approved to (among other things) "Correct caps in headers" but this seems to be a form of typo-fixing or spell-checking contrary to 3606:
Minimum a week. We like to get community feedback, you see, but very rarely do. The silence is hence useful as a measure of consensus. -
4975: 1779: 303:
I suggest this task still get approval, or at least get discussed with relevant WikiProjects, even if it is not completely automated. -
5094:
and one "manual" citation (which I'll fix in a second). As for "template documentation", I can't even fathom how it could be an issue.
2123:
The bot has only been running for a few days, I'm sure most new page patrollers are not even aware of what it's doing yet. I've added
3262:{{\s*(Talk+header|TalkHeader|Talk+page|Talk+page+header|Talkpage|Talkpage+header|Talkpageheader|User+talk+header|Usertalkheader)\s*()" 3258:{{\s*(Talk+header|TalkHeader|Talk+page|Talk+page+header|Talkpage|Talkpage+header|Talkpageheader|User+talk+header|Usertalkheader)\s*()" 1160:
Particularly, in view of the earlier problems with Anybot, it would be desirable to first handle the issue raised a few hours ago at
3018:
Article history related items, Skip to talk, Talk header and a few others go above (Done with Regex, some built into AWB now though)
4594:—that a human editor may check if the video violates anyones copyrights. Because, for instance, in that incident above, it did not. 3931:
There is no blanket ban on linking to YouTube or other user-submitted video sites, as long as the links abide by the guidelines...
3749:. If the bot cannot avoid such cases, it shouldn't be run at this time; if it can, please post how it does so for a quick review. 1483:
automatically there, greatly reducing the cost of maintenance and making sure users actually get these recommendations regularly.
4709: 2741: 774:
and elsewhere that effectively did this, with the resolution that the offender must be more careful to not make stupid mistakes.
4275: 4228: 3891: 441:(short for "robots") are generally programs or scripts that make automated edits without the necessity of human decision-making. 343:
the user to stop creating the articles and get an approval. I think this issue must be taken back to ANI if the user disagrees.
3401:
under the "Assisted editing guidelines" part of the policy. This has never been about requesting you to program a bot. Period.
3164: 3124: 3826: 2690:
are due to everyone trying to make Knowledge (XXG) better, even when I don't agree with some of the particulars. Sincerely,
5196: 5104: 4988: 4861: 4483:@WhatamIdoing: But is it possible to go from v=1234567890 to the channel via YouTube's API, or some other reasonable method? 4166:(2) haven't ever made ten edits? XLinkBot doesn't 'see' edits made by users who have made more than ten edits (ever), so it 1212: 518:
It's as close enough to automated as makes no odds because you don't even bother to fix the obvious manual of style errors. –
3417: 3026:
I remove some deprecated parameters from Wikiproject banners (like nested) (Some Regex & some standard find and replace)
1044:
There was no one logical or reasonable opposing reason mentioned neither in the closing comment nor in the whole discussion.
301:. While no specific definition of "large-scale" was decided, a suggestion of "anything more than 25 or 50" was not opposed." 4743:
If I type "Knowledge (XXG):Bots/Requests for approval/RjwilmsiBot 8" (as my next task would be) into the box at the top of
661:
Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
4648:
Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
2721: 1720: 3813:
Is there a bot or would it be possible to create one, for On This Day and DYK's to be updated automatically by a bot for
3009: 1501:
Since the actual task is almost identical and only the sign-up method is changing, I don't think it will be a problem. -
568:(bracket in lead sentence) would not occur (manual editing implies checking of all content, so the fact that he pasted a 4584:
This bot should not remove YouTube videos, as it did here. If anything, it should set something like a flag—maybe using
3746: 881: 635: 4747:
the logic to derive bot name etc. on the created page always seems to generate a red link for me, that then has to be
2559: 2548: 1942: 1923: 1090: 603:"improve, enhance, or personalize the existing MediaWiki interface, or to simplify access to commonly used functions" 138:
okay with it before proceeding. If not, then I will be happy to discuss it and, if needed, go through re-approval. -
1599:
I would hope that part of the process would be community members can learn about it. There is no reason for this. --
4792:
Knowledge (XXG) talk:Categories for discussion#Possible solution for the attribution problem with category renames?
2764:) which indicates they're apparently not paying attention to each edit I'm inclined to agree that this falls under 126: 42: 5289: 5262: 5241: 5209: 5173: 5117: 5046: 5001: 4945: 4922: 4897: 4874: 4844: 4825: 4801: 4779: 4761: 4730: 4714: 4682: 4636: 4616: 4576: 4490: 4476: 4446: 4423: 4400: 4364: 4340: 4326: 4311: 4267: 4249: 4216: 4144: 4118: 4103: 4066: 4042: 4009: 3990: 3953: 3859: 3845: 3800: 3770: 3756: 3712: 3685: 3656: 3642: 3628: 3610: 3601: 3585: 3549: 3534: 3477: 3462: 3447: 3429: 3410: 3392: 3376: 3340: 3299: 3205: 3151: 3113: 3079: 2982: 2929: 2914: 2898: 2883: 2833: 2809: 2777: 2750: 2701: 2683: 2650: 2613: 2580: 2528: 2511: 2489: 2472: 2457: 2440: 2416: 2400: 2382: 2366: 2348: 2330: 2266: 2251: 2232: 2203: 2167: 2142: 2115: 2083: 2070:
would know about, we decided it was better to use the existing infrastructure. Also, some patrolling tools (like
2064: 2029: 1999: 1978: 1958: 1914: 1891: 1867: 1844: 1791: 1773: 1746: 1727: 1690: 1675: 1660: 1644: 1622: 1608: 1583: 1570: 1543: 1525: 1507: 1495: 1461: 1439: 1416: 1384: 1371: 1351: 1337: 1313: 1292: 1265: 1246: 1235: 1173: 1154: 1110: 1074: 1003: 982: 958: 935: 900: 872: 855: 826: 808: 797: 781: 731: 719: 702: 611: 596: 578: 528: 512: 488: 470: 428: 401: 386: 371: 329: 309: 270: 244: 174: 163: 144: 5078: 5030: 4968: 3397:
I'm not sure how else to say this: the discussion started because your rate and quantity of manual tagging means
867: 850: 755: 188: 2498:
check for those errors which are easy to spot, and should ignore other errors. However, since that's apparently
391:
If by "ruling" you mean "discussion showing consensus of the community" then yes, this was discussed and agreed
4596:" Is the first thing at the discussion from another editor. A request to adjust it was made and it was refused. 1820: 1347: 1333: 3264:
several times because different edits are doing different things. I have 6 different code groups just to move
709:
While it seems a bit like instruction creep, I suppose the clarification is needed to prevent wikilawyering. –
4621:
This is not the place for continued complaints regarding how the community treats YouTube links. Take it to
4304: 4096: 4035: 3983: 2502:
what you meant, let's not get hung up on it, I've struck my comment and apologise for any offence caused. -
5161: 3044: 2821: 584: 434: 4502:
know since the editor is blocked from doing the specific edit, but which certainly harms Knowledge (XXG).
4419: 4212: 3406: 3372: 2894: 2829: 2773: 1787: 1742: 1566: 4532: 4434: 4180: 4078:. As to the size limitations, I agree with you and would favor allowing established users to upload : --> 3838: 3568:
It seems clear that the sentiment is that I submit this as a bot request so I have done so. The link is:
2676: 2573: 2135: 2076: 1951: 285:
may effectively be considered bots in some cases, even if performed by an account used by a human editor"
51: 17: 3782: 3742: 3573: 3142:
I delete it (and usually check the result in my contributions to make sure it doesn't scew something. --
2405:
I was just responding to your semi-sarcasm, (i.e. my point wasn't dumb) not arguing the point further.
2183: 5154: 3734: 3514:
Knowledge (XXG) talk:Bots/Requests for approval/Archive 4#Request for deflagging and blocking of Anybot
3100:
What is the "broken or irregular HTML formatting" you fix? I hope not pointless edits like "<br: -->
2661:
Your humble opinion is duly noted. There is no precedent for barring bots from placing top-level tags.
2215: 1897: 1878: 1734: 1444:
The trial's now complete so if anyone gets the chance to give it the nod, that'd be great. Thanks (-:
4798: 4705: 3814: 3719: 3696: 3616: 3268: 3245: 3070:
comments or questions. If you have any suggestions for further improvements I will take those too. --
3043:
Fix redirects for Talk page templates according to logic I wrote using a combination of C# and regex
2736: 1255:
That would be fine, but whatever rules Rich is using now aren't appropriate for unattended editing. –
864: 847: 4622: 1303:
It appears this was human error rather than a poorly programmed regex, so I'll mark this resolved. –
129:. This new option removes interwiki links to nonexistent pages, and is a bit more cautious than the 5285: 5258: 4918: 4893: 4840: 4079:
100MB files (such an allowance might mean pre-approval of the upload so as not to waste resources).
3181: 3102:" or vice versa. Some things aren't even worth a minor edit while doing something else to the page. 2978: 2697: 2646: 2524: 2507: 2485: 2468: 2453: 2412: 2396: 2378: 2362: 2344: 2239: 2163: 2060: 1995: 1910: 1863: 1840: 1816: 1769: 1671: 1640: 1604: 1521: 1343: 1329: 1288: 1106: 978: 954: 822: 698: 593: 508: 467: 448:
which can edit without the operator looking at and approving the change) is considered to be a bot.
424: 383: 340: 225: 159: 5204: 5112: 4996: 4869: 2904: 2765: 2665: 1649: 1216: 556: 276: 5232: 5192: 5100: 5088: 4984: 4857: 4752: 4676: 4336: 4290: 4284: 4245: 4082: 4021: 3969: 3937:
uses informative messages, appropriately worded, in any edit summaries or messages left for users
3903: 3796: 3708: 3525: 3260:
so I standardize the format first before I perform the other logic. Remember I would have to say
2951: 1969: 1455: 1433: 1410: 1206: 1169: 1148: 550: 4170:
reverts these. If you wanted, you could spend all day doing nothing but adding YouTube links.
4075: 4406:
I don't think that whitelisting channels is possible. The typical link only seems to give you
4662: 4612: 4442: 4415: 4393:
I'll leave this discussion open for the moment in case any other BAG members want to comment.
4360: 4322: 4208: 4140: 4114: 4062: 4005: 3949: 3855: 3822: 3681: 3652: 3638: 3624: 3597: 3581: 3545: 3473: 3458: 3425: 3402: 3388: 3368: 3336: 3295: 3147: 3075: 3064:
I fix some broken or irregular HTML formatting (some Regex & some manual find and replace)
2925: 2890: 2879: 2825: 2805: 2769: 2761: 2757: 2715: 2609: 2436: 2326: 2247: 2199: 2025: 1783: 1738: 1725: 1562: 1539: 1491: 1161: 996: 928: 893: 364: 263: 237: 5200: 5108: 4992: 4865: 4540: 4466: 4457: 3833: 3021:
If comments appear before Wikiproject banners I move the banners above them (Done with Regex)
2725: 2371:
No, I was giving a suggestion for fixing the problem vs. just decorating it. :-) Sincerely,
1395: 764: 213: 5169: 5042: 4941: 4821: 4776: 4727: 4689: 4633: 4588: 4487: 4473: 4397: 3753: 3444: 3202: 3110: 2911: 2102: 1935: 1931: 1657: 1619: 1580: 1381: 1070: 778: 728: 569: 458: 197: 4626: 4528: 4377: 4179:
Certainly there's no consensus to delete every single YouTube link—if we wanted that, we'd
3923:(there is no consensus to remove all YouTube links so the bot is editing against consensus) 2601: 2567: 2219: 2130: 1711: 1364: 987:
Thanks Kingpin. It was a long discussion, appreciate you taking time to go thorugh it all.
771: 4795: 4701: 3837: 3726: 3700: 2731: 2675: 2572: 2387:
Well it's not possible for the bot to fix the problems, but it can direct other's efforts
2134: 2075: 1950: 1534:
Thanks for the responses! I'm happy to hear that a new application isn't needed. Cheers,
1475: 1368: 4720: 4524: 4516: 4387: 3762: 3730: 3177:
So you're just bypassing redirects to WikiProject banners, and not other banners such as
2218:) would approve of this task, I suggest you initiate a discussion at some central venue ( 2071: 4523:
superfluous. And for MySpace the problem of copyvio is pretyy minimal. We do not have
4274:
Correct. This proposal was opened by someone who last participated in the discussion at
1363:
Rhetorical question apparently not aimed at bot operator closes case without reply from
1124:
I'm not sure of the process involved in requesting a bot flag for the recently-approved
5278: 5254: 4911: 4886: 4833: 4658: 4263: 3765: 3607: 2971: 2503: 2464: 2392: 2358: 2264: 2230: 2113: 2056: 1903: 1889: 1833: 1762: 1686: 1667: 1636: 1600: 1514: 1512:
Agree that changes to non-mainspace for your task can be made without any new BRFAs. —
1311: 1281: 1263: 1233: 1102: 974: 950: 815: 795: 717: 691: 646: 588: 561:"high-speed semi-automated processes may effectively be considered bots in some cases"' 526: 504: 486: 462: 417: 378: 327: 221: 152: 4453: 2728:. Shouldn't he be doing so with a bot flag, given the volume and rate of his editing? 1901:
level tags" as it has clearly defined unambiguous rules when to place the said tag. —
1896:
The bot was approved after more than a week with no objections on the assumption that
942: 5188: 5181: 5096: 4980: 4853: 4672: 4666: 4573: 4332: 4241: 3899: 3792: 3704: 3522: 2300:
At last, with Snotbot, we now have a way of getting these pages traced, and tracked.
1966: 1714:
has an impressive library of general fixes, is there a place where those are listed?
1451: 1445: 1429: 1423: 1406: 1400: 1243: 1202: 1165: 1144: 1138: 3367:. Nothing that's a big deal except for in the context of the sheer number of edits. 2182:
What am I misunderstanding? The request and approval was to place a hidden category,
2005:
overlap). Maintenance templates on articles also serve three distinct purposes:
767:
instead of having to argue over the method used to make apparently automated edits.
4608: 4438: 4356: 4318: 4136: 4110: 4058: 4001: 3945: 3851: 3818: 3677: 3648: 3634: 3620: 3593: 3577: 3541: 3508:
For a good example of how one can massively screw up and still walk away fine, see
3469: 3454: 3421: 3384: 3332: 3291: 3143: 3071: 3005:
I Move WPBiography to top billing of WikiProjects if living = yes (Done with Regex)
3002:
I remove duplicate blp=yes parameters from the WPBiography banner (Done with Regex)
2966: 2958: 2921: 2875: 2801: 2724:) is running thousands of edits a day on average using AWB to tag pages as part of 2711: 2605: 2432: 2322: 2243: 2195: 2021: 1715: 1535: 1502: 1487: 1125: 1058:
THERE IS GENERAL CONCENSUS, THAT Bot Approvals Group DAMAGES WikiProject Gastropods
990: 922: 887: 803: 606: 573: 396: 358: 304: 257: 231: 169: 139: 4437:
that the community has come to a consensus that the bot does more good than harm.
3917:(the bot creates additional work for others when it removes links inappropriately) 770:
I don't have specific examples, but I do recall seeing a few cases in the past at
4187:. XLinkBot removes only links added by IPs and brand-new accounts, which have a 1934:. The bot should never tag articles which are still displayed in the backlog at 192: 5165: 5038: 4937: 4817: 4773: 4724: 4630: 4484: 4470: 4394: 3750: 3441: 3199: 3107: 3061:
I fix some broken bracket syntax (some Regex & some manual find and replace)
2908: 1654: 1616: 1577: 1378: 1066: 775: 725: 636:
Knowledge (XXG) talk:Bot policy#Clarification regarding high-speed human editing
118: 110: 50:
If you wish to start a new discussion or revive an old one, please do so on the
4739:
Problem filing request for additional task, default links generated incorrect?
3229:
Thats because sometimes the template is broken and says WikiProjectBannerShell
3090:
Is there consensus anywhere for this "fixing" of talk page template redirects?
2354:
Uhh, so what you're saying is if we ignore the problem, maybe it will go away?
802:
Sounds reasonable. The above proposal is also good, but a bit too specific. -
457:
there is no assisted editing, or scripts here, rather manual cut and paste of
2303:
What happens to them next is anybody's guess, but we're working on that too.
4259: 2257: 2223: 2106: 1882: 1682: 1304: 1256: 1226: 1219:. In particular, this has caused problems for suchlike "==Prime Minister==" 788: 710: 639: 519: 479: 320: 4460:
actually says anything true enough to be in policy instead of in an essay,
4287:
for the preceding thread prior to the one at the External links talk page.
3040:
I perform the following edits only if I am making a more significant edit
3718:
Asking here is procedure enough, IMO. I see no problem with reactivating
2838:
I am familiar with both and both actually state in some way that I don't
1164:. I have not looked at the merits of the issue, but it needs a response. 919:
is a summary of the discussion from the Gastropod project team. Thanks.
4723:, as the bureaucrats are the only ones who can actually give the flag. 1328:
in between approval periods? Perhaps there's a need to expand the BAG.
2762:
User talk:Kumioko#Please stop DC-tagging WMATA stations for time being
2494:
That's the impression I got from you suggesting that reviewers should
787:
Yep, I prefer this to the above which seems altogether too specific. –
4414:—but not something that tells you which channel each video is from. 1022:
Support provided by 15 wikipedians (14 wikipedians and User:Ganeshk).
4786:
Possible solution for the attribution problem with category renames?
1180:
Probably erroneous approval for a form of spell-checking (SmackBot)
3929:(please see the above concern. We have [[WP:Youtube which states " 168:
Bot started again since there were no objections in over a day. -
4276:
Knowledge (XXG) talk:External links#Blanket ban on Youtube links?
3892:
Knowledge (XXG) talk:External links#Blanket ban on Youtube links?
3015:
Image/map/diagram requested goes below banners. (Done with Regex)
2999:
WPBiography, WPMILHIST and WPLAW). This is also donen with regex.
2185:
The bot is also putting boilerplate at the top of articles, e.g.
224:
look like they were created using a bot (most probably AWB). The
3761:
The Dab issue should be solved fairly soon, see my thread on an
2824:, and less importantly the section "Bot-like editing" above it. 2194:
but was that discussed as part of the approval? Please clarify.
3058:
I delete the spaces before and after == in the section headings
4936:
in, say, a template, when the citation isn't required at all?
2222:, perhaps) and see if the community shares your trepidation. – 29: 3510:
Knowledge (XXG):Articles for deletion/Anybot's algae articles
3029:
I replace WikiProjectBannerShell1 to WikiProjectBannerShell|1
2631:(IMHO) robots shouldn't be placing top level tags on articles 1025:
Partly support (for generic articles only) by one wikipedian.
763:
it from the other direction, and basically says we can apply
689:
with semi-automation, though not "semi-automation" per se. —
2011:
They warn the authors that the articles require attention.
3012:. (Mostly done with regex but some manual find and replace 1196:
Knowledge (XXG):Bots/Requests for approval/SmackBot Task XI
150:
Seems like a reasonable improvement to the current task. —
3008:
I move some Templates around if out of place according to
1474:
In the near future I'll be working on some changes to how
4964:
Because several templates do make use of citations, like
4794:, where I brought up a possible solution to the problem. 4462:(if you want details on any of that, ask at my talk page) 2889:
comment since they presumably deal with this more often?
4527:
for nothing, and it is based on our core policies (e.g.
3170:
is. But you talked about changing WikiProjectBannerShell
1879:
Knowledge (XXG) talk:NPP#Back of the unpatrolled backlog
555:
The edits were almost all made in under 10 seconds. The
191:
if the project received wide support before continuing.
4657:
I (and others) would be grateful if someone could flag
4429: 4192: 3735:
WT:NFC#Do we need to change how to handle #10c removals
3731:
WP:AN#Trying to defuse a problem with NFCC#10c removals
3364: 3360: 2192: 2189: 2186: 2125: 1813: 1595: 1223: 1220: 1062:
Knowledge (XXG) talk:WikiProject Gastropods#Ganeshbot 5
916: 880:
RF, the discussion on the policy change has been moved
565: 348: 316: 217: 2822:
Knowledge (XXG):Bot policy#Assisted editing guidelines
1938:. If it is doing that, then please let me know. The 601:
I don't see how mass creation of articles falls under
433:
i note no discussion of "semi-automated", i take from
5178:
And that affects, what? 20 templates documentations?
4281:
Has the bot reverted any of his additions of YouTube?
3927:
carefully adheres to relevant policies and guidelines
724:
Ditto. This is ridiculous, but apparently necessary.
3882:
Subsequent comments should be made in a new section.
3055:
the page takes for each consecutive historical save.
2782:
Thanks for letting me know about the discussion VW.
838:
Subsequent comments should be made in a new section.
4183:the domain—but that's irrelevant, because XLinkBot 3359:about AWB has some tips to avoid double-edits like 1558:
Knowledge (XXG):Bots/Requests for approval/YouMeBot
4582:Wow, back to me again instead of the issue, huh? " 3570:Knowledge (XXG):Bots/Requests for approval/Kumioko 3284:==(*)External links*==(.*?)==*References*==(.*?)== 2992:I perform the following actions as primary edits: 1898:Wikipedia_talk:NPP#Back_of_the_unpatrolled_backlog 1875:Knowledge (XXG):Bots/Requests for approval/Snotbot 1132:). I'd be grateful if someone could help me out. 4688:Someone please flag this bot!! It's clogging the 1919:I am the operator of the bot. The bot places an 1754:Knowledge (XXG):WikiProject Check Knowledge (XXG) 1033:This sentence from closing is completelly wrong: 832:The above discussion is preserved as an archive. 583:i saw your comment above; i'm afraid i disagree. 3921:performs only tasks for which there is consensus 3097:these spaces, this seems particularly pointless. 2311:Consensus has not changed, the use of the word 1470:Need BRFA application for functionality changes? 187:As some know I am developing a bot platform and 4229:WT:External links#Blanket ban on Youtube links? 3032:Standard AWB built in talk page related changes 1758:Knowledge (XXG):WikiProject Fix common mistakes 632: 4347:And have I ever been reverted by the bot? No. 2238:had been hanging around for over six months ( 2191:. Snotty has said that the consensus changed 1013:I would like to dispute Kingpin13's closing: 8: 4227:one. I cannot see (in this discussion or at 3288:==External links==(.*?)==References==(.*?)== 2903:You ignored the most relevant sentence from 2800:WikiProject United States up and running. -- 2758:User talk:Kumioko#WikiProject United States? 2604:). Can we shut down disruptive criticism? 2242:) so hopes for timely action may be pious. 4745:Knowledge (XXG):Bots/Requests for approval 1040:So who needs to works with in cooperation? 862:Prop 2 um.. what does "wiki" mean again? 299:Knowledge (XXG):Bots/Requests for approval 4349:Was there another question I missed? and 3118:No problem. Answered in the order asked: 4191:high rate of misusing these links, like 3788:Template:Hatnote templates documentation 113:removing interwikis to nonexistent pages 1130:WP:Bots/Requests for approval/Taxobot 2 1019:How many people joined the discussion: 585:Knowledge (XXG):Bot_policy#User_scripts 4807:Restrict Citation bot to article space 3809:Bot needed to populate DYK's and OTD's 3226:Again commented in the order received 3051: 2043: 2039: 2035: 1881:; the bot is approved for this task. – 48:Do not edit the contents of this page. 4719:You might have better luck asking at 2905:WP:BOTPOL#Assisted editing guidelines 2656:In response to your two issues above: 135:"create and maintain interwiki links" 7: 4790:Feel free to join the discussion at 3876:The following discussion is closed. 3671:Is there something I am missing here 1590:Stupid comments by community members 655:The following discussion is closed. 5186:is perfectly appropriate for this. 4976:Category:Science citation templates 4692:log for newly-created templates... 3850:OOps, I think your right thanks. -- 2664:The same "orders" are given by the 1780:User:Magioladitis/AWB and CHECKWIKI 1615:offense to in H3llkn0wz's message? 4469:and refuses to edit war about it. 3745:but the image is actually used on 3233:instead of WikiProjectBannerShell| 3087:What is "WikiProjectBannerShell1"? 1081:Hi Snek01, thanks for your points. 1056:, who are unable to work swiftly. 351:similar stubs. They are under the 297:creation task must be approved at 28: 4772:to detect and remove the suffix. 4285:User talk:XLinkBot#Youtube videos 4172:As for the specific four issues: 3904:User talk:XLinkBot#Youtube videos 3737:? It seems there is no consensus 3399:you already are acting like a bot 355:that these do not need approval. 339:Thanks for the responses. I have 5268: 5248:Very small change to SDPatrolBot 4644:The discussion above is closed. 3010:Knowledge (XXG):Talk page layout 1825:_need_permission_for_task?": --> 1222:and "==World Series of Poker==" 1185: 1050:PROBLEM is Requests for approval 964: 941: 117:Hey everyone. I've been running 33: 4751:. Am I missing a trick? Thanks 2050:the tags placed by the bot, or 1705:Centralized List of Minor Fixes 648:16:34, 23 September 2010 (UTC) 293:that any large-scale automated 2920:show up on most watchlists. -- 1396:Knowledge (XXG):BRFA#Taxobot_5 936:21:42, 26 September 2010 (UTC) 827:20:06, 22 September 2010 (UTC) 809:19:52, 22 September 2010 (UTC) 798:19:50, 22 September 2010 (UTC) 782:19:46, 22 September 2010 (UTC) 732:19:09, 22 September 2010 (UTC) 720:17:19, 22 September 2010 (UTC) 703:17:18, 22 September 2010 (UTC) 612:17:01, 22 September 2010 (UTC) 597:16:58, 22 September 2010 (UTC) 579:16:57, 22 September 2010 (UTC) 529:17:33, 23 September 2010 (UTC) 513:17:31, 23 September 2010 (UTC) 489:16:55, 22 September 2010 (UTC) 471:16:39, 22 September 2010 (UTC) 429:16:37, 22 September 2010 (UTC) 402:16:18, 22 September 2010 (UTC) 387:16:15, 22 September 2010 (UTC) 372:16:09, 22 September 2010 (UTC) 330:15:43, 22 September 2010 (UTC) 310:15:39, 22 September 2010 (UTC) 271:15:30, 22 September 2010 (UTC) 245:15:20, 22 September 2010 (UTC) 203:12:06, 23 September 2010 (UTC) 175:05:15, 16 September 2010 (UTC) 164:16:46, 14 September 2010 (UTC) 145:16:35, 14 September 2010 (UTC) 1: 4683:18:26, 28 February 2011 (UTC) 4577:11:42, 22 February 2011 (UTC) 4491:01:53, 22 February 2011 (UTC) 4477:01:53, 22 February 2011 (UTC) 4447:01:34, 22 February 2011 (UTC) 4424:01:17, 22 February 2011 (UTC) 4401:00:27, 22 February 2011 (UTC) 4365:22:15, 21 February 2011 (UTC) 4341:22:02, 21 February 2011 (UTC) 4327:20:22, 21 February 2011 (UTC) 4312:03:41, 19 February 2011 (UTC) 4268:02:26, 19 February 2011 (UTC) 4250:01:27, 19 February 2011 (UTC) 4217:05:32, 18 February 2011 (UTC) 4145:03:14, 18 February 2011 (UTC) 4119:03:07, 18 February 2011 (UTC) 4104:02:53, 18 February 2011 (UTC) 4067:01:52, 18 February 2011 (UTC) 4043:03:23, 18 February 2011 (UTC) 4010:03:14, 18 February 2011 (UTC) 3991:00:52, 18 February 2011 (UTC) 3954:23:26, 17 February 2011 (UTC) 3695:I've updated two of my bots ( 3643:18:32, 25 December 2010 (UTC) 3629:15:43, 24 December 2010 (UTC) 3611:15:39, 24 December 2010 (UTC) 3602:15:22, 24 December 2010 (UTC) 3586:14:58, 23 December 2010 (UTC) 3550:22:19, 22 December 2010 (UTC) 3535:22:04, 22 December 2010 (UTC) 3478:21:17, 22 December 2010 (UTC) 3463:21:13, 22 December 2010 (UTC) 3448:20:48, 22 December 2010 (UTC) 3430:20:37, 22 December 2010 (UTC) 3411:20:14, 22 December 2010 (UTC) 3393:19:50, 22 December 2010 (UTC) 3377:19:06, 22 December 2010 (UTC) 3341:22:54, 22 December 2010 (UTC) 3300:22:54, 22 December 2010 (UTC) 3206:22:02, 22 December 2010 (UTC) 3152:21:03, 22 December 2010 (UTC) 3114:20:39, 22 December 2010 (UTC) 3080:19:41, 22 December 2010 (UTC) 2983:19:00, 22 December 2010 (UTC) 2930:18:54, 22 December 2010 (UTC) 2915:18:41, 22 December 2010 (UTC) 2899:18:35, 22 December 2010 (UTC) 2884:18:22, 22 December 2010 (UTC) 2834:17:37, 22 December 2010 (UTC) 2810:17:09, 22 December 2010 (UTC) 2778:16:44, 22 December 2010 (UTC) 2751:05:34, 22 December 2010 (UTC) 1691:21:53, 29 December 2010 (UTC) 1676:21:45, 29 December 2010 (UTC) 1661:20:56, 29 December 2010 (UTC) 1645:19:42, 29 December 2010 (UTC) 1623:19:24, 29 December 2010 (UTC) 1609:18:28, 29 December 2010 (UTC) 1584:02:49, 23 December 2010 (UTC) 1571:22:13, 22 December 2010 (UTC) 1544:19:38, 23 December 2010 (UTC) 1526:17:11, 22 December 2010 (UTC) 1508:16:17, 22 December 2010 (UTC) 1496:13:33, 22 December 2010 (UTC) 1462:21:42, 27 November 2010 (UTC) 1440:19:05, 26 November 2010 (UTC) 1417:18:51, 26 November 2010 (UTC) 1385:05:14, 20 November 2010 (UTC) 1372:22:52, 19 November 2010 (UTC) 1352:02:51, 14 November 2010 (UTC) 1338:07:48, 11 November 2010 (UTC) 1324:Is it normal to have to wait 4465:is extremely careful not to 4014:Has the bot reverted any of 3898:I propose the revocation of 3860:19:33, 20 January 2011 (UTC) 3846:19:20, 20 January 2011 (UTC) 3827:16:43, 19 January 2011 (UTC) 3801:21:22, 19 January 2011 (UTC) 3771:18:11, 19 January 2011 (UTC) 3757:18:09, 19 January 2011 (UTC) 3747:2001: A Space Odyssey (film) 3713:07:48, 19 January 2011 (UTC) 3686:04:10, 2 February 2011 (UTC) 3657:14:49, 24 January 2011 (UTC) 2702:15:37, 24 January 2011 (UTC) 2684:15:27, 24 January 2011 (UTC) 2651:14:39, 24 January 2011 (UTC) 2614:14:02, 24 January 2011 (UTC) 2581:03:45, 24 January 2011 (UTC) 2529:15:25, 24 January 2011 (UTC) 2512:23:46, 23 January 2011 (UTC) 2490:23:23, 23 January 2011 (UTC) 2473:20:51, 23 January 2011 (UTC) 2458:20:39, 23 January 2011 (UTC) 2441:19:12, 23 January 2011 (UTC) 2417:18:47, 23 January 2011 (UTC) 2401:19:18, 22 January 2011 (UTC) 2383:19:17, 22 January 2011 (UTC) 2367:19:13, 22 January 2011 (UTC) 2349:18:40, 22 January 2011 (UTC) 2331:17:04, 21 January 2011 (UTC) 2267:16:23, 21 January 2011 (UTC) 2252:16:20, 21 January 2011 (UTC) 2233:16:06, 21 January 2011 (UTC) 2204:15:55, 21 January 2011 (UTC) 2168:00:50, 21 January 2011 (UTC) 2143:16:44, 20 January 2011 (UTC) 2116:14:49, 20 January 2011 (UTC) 2084:14:44, 20 January 2011 (UTC) 2065:08:08, 20 January 2011 (UTC) 2030:07:57, 20 January 2011 (UTC) 2000:04:41, 20 January 2011 (UTC) 1979:21:03, 19 January 2011 (UTC) 1959:19:17, 19 January 2011 (UTC) 1915:18:41, 19 January 2011 (UTC) 1892:18:25, 19 January 2011 (UTC) 1868:01:27, 19 January 2011 (UTC) 1845:10:41, 11 January 2011 (UTC) 1826:03:09, 11 January 2011 (UTC) 1314:18:25, 25 October 2010 (UTC) 1293:16:49, 25 October 2010 (UTC) 1266:14:49, 25 October 2010 (UTC) 1247:14:43, 25 October 2010 (UTC) 1236:14:35, 25 October 2010 (UTC) 1174:06:30, 24 October 2010 (UTC) 1155:05:29, 24 October 2010 (UTC) 1111:21:34, 15 October 2010 (UTC) 1075:19:29, 15 October 2010 (UTC) 1004:11:56, 14 October 2010 (UTC) 983:08:29, 14 October 2010 (UTC) 959:07:38, 14 October 2010 (UTC) 901:19:43, 24 October 2010 (UTC) 873:19:34, 24 October 2010 (UTC) 856:19:31, 24 October 2010 (UTC) 4663:User_talk:Taxobot#Taxobot_7 3964:anything to do with Youtube 3832:I think you're looking for 2034:The bot should be adding a 1792:16:35, 2 January 2011 (UTC) 1774:16:33, 2 January 2011 (UTC) 1747:16:13, 2 January 2011 (UTC) 1728:16:02, 2 January 2011 (UTC) 1028:Opposed were 4 wikipedians. 5306: 4731:13:49, 13 March 2011 (UTC) 4715:08:16, 13 March 2011 (UTC) 3729:, have you been following 1851:Can you shut down Snotbot? 1183: 754:We could use the shortcut 435:Knowledge (XXG):Bot policy 4637:12:06, 3 March 2011 (UTC) 4617:08:40, 3 March 2011 (UTC) 3808: 3254:"{{\s*(Talk+header)\s*()" 1803:need permission for task? 295:or semi-automated article 18:Knowledge (XXG) talk:Bots 5290:11:10, 30 May 2011 (UTC) 5263:11:06, 30 May 2011 (UTC) 5242:00:58, 21 May 2011 (UTC) 5210:04:23, 21 May 2011 (UTC) 5174:20:29, 20 May 2011 (UTC) 5118:19:21, 20 May 2011 (UTC) 5047:19:08, 20 May 2011 (UTC) 5002:18:44, 20 May 2011 (UTC) 4946:18:41, 20 May 2011 (UTC) 4923:18:33, 20 May 2011 (UTC) 4898:18:23, 20 May 2011 (UTC) 4875:18:00, 20 May 2011 (UTC) 4845:16:02, 20 May 2011 (UTC) 4826:14:12, 20 May 2011 (UTC) 4802:10:08, 15 May 2011 (UTC) 4780:10:50, 12 May 2011 (UTC) 4770:evil string manipulation 4762:17:59, 11 May 2011 (UTC) 4646:Please do not modify it. 4376:Here's my position as a 4057:be allowed to resume. -- 3879:Please do not modify it. 1217:WP:BOTPOL#Spell-checking 835:Please do not modify it. 813:Well-phrased, support.— 658:Please do not modify it. 283:semi-automated processes 4661:as a bot account. See 1756:and smaller ones, like 5026:As far as I can tell, 3237:with a pipe in between 3165:WikiProjectBannerShell 3125:WikiProjectBannerShell 2560:New unreviewed article 2549:New unreviewed article 1943:New unreviewed article 1924:New unreviewed article 650: 5162:Template:Cite pmc/doc 4811:I believe during the 3783:2001: A Space Odyssey 3743:2001: A Space Odyssey 3564:Bot request submitted 911:Hello BAG team, this 572:is not an excuse). - 46:of past discussions. 22:Requests for approval 5184:|deny=Citation bot}} 4412:&feature=channel 3890:Related discussion: 3815:Portal:United States 3720:User:ImageRemovalBot 3697:User:ImageRemovalBot 3691:Reactivating my bots 3617:Portal:United States 345:User:Александр Мотин 252:related ANI incident 4410:, and occasionally 3944:of obvious benefit. 1054:Bot Approvals Group 289:"The community has 4408:watch?v=1234567890 3101:" → "<br /: --> 2126:this brief mention 1422:Super, thank you! 5288: 4921: 4896: 4843: 4713: 4700:comment added by 4680: 4185:is not doing that 3740: 3084:A few questions: 2981: 2955: 1913: 1843: 1772: 1524: 1459: 1437: 1414: 1291: 1162:User talk:Taxobot 1152: 1091:WP:IDIDNTHEARTHAT 825: 759: 701: 554: 427: 162: 104: 103: 58: 57: 52:current talk page 5297: 5281: 5277: 5272: 5271: 5239: 5208: 5185: 5159: 5153: 5116: 5093: 5087: 5083: 5079:Infobox hydrogen 5077: 5035: 5031:Infobox hydrogen 5029: 5000: 4973: 4969:Infobox hydrogen 4967: 4914: 4910: 4889: 4885: 4873: 4836: 4832: 4759: 4699: 4693: 4690:Special:NewPages 4670: 4653:Bot flag request 4593: 4587: 4467:bite the newbies 4463: 4413: 4409: 4388:reliable sources 4310: 4301: 4102: 4093: 4041: 4032: 3989: 3980: 3881: 3843: 3842: 3738: 3533: 3273: 3267: 3250: 3244: 3186: 3180: 3169: 3163: 3160:Oh, I know what 3129: 3123: 3053: 2974: 2970: 2965:for a task like 2949: 2749: 2746: 2739: 2734: 2695: 2681: 2680: 2674:Anything else? 2644: 2578: 2577: 2564: 2558: 2553: 2547: 2522: 2483: 2451: 2410: 2376: 2342: 2262: 2228: 2161: 2140: 2139: 2128: 2111: 2103:special:Newpages 2081: 2080: 2045: 2041: 2037: 1993: 1977: 1956: 1955: 1947: 1941: 1936:Special:Newpages 1932:Special:Newpages 1928: 1922: 1906: 1902: 1887: 1861: 1836: 1832: 1765: 1761: 1723: 1718: 1517: 1513: 1505: 1449: 1427: 1404: 1309: 1284: 1280: 1261: 1231: 1189: 1188: 1142: 1117:Bot flag request 1002: 999: 993: 972: 968: 967: 945: 934: 931: 925: 899: 896: 890: 837: 818: 814: 806: 793: 753: 715: 694: 690: 660: 644: 609: 591: 576: 548: 524: 484: 465: 459:Help:Magic words 445:Assisted editing 420: 416: 399: 381: 370: 367: 361: 325: 307: 269: 266: 260: 243: 240: 234: 172: 155: 151: 142: 82: 60: 59: 37: 36: 30: 5305: 5304: 5300: 5299: 5298: 5296: 5295: 5294: 5279: 5269: 5250: 5233: 5187: 5179: 5157: 5151: 5150:If you look at 5095: 5091: 5085: 5081: 5075: 5033: 5027: 4979: 4971: 4965: 4912: 4887: 4852: 4834: 4809: 4788: 4753: 4741: 4695: 4655: 4650: 4649: 4591: 4585: 4461: 4411: 4407: 4345:I already did: 4291: 4289: 4083: 4081: 4022: 4020: 3970: 3968: 3886: 3877: 3870: 3840: 3811: 3768: 3727:User:FairuseBot 3701:User:FairuseBot 3693: 3673: 3566: 3521: 3271: 3265: 3248: 3242: 3184: 3178: 3167: 3161: 3127: 3121: 2972: 2745: 2742: 2737: 2732: 2729: 2709: 2691: 2678: 2640: 2575: 2562: 2556: 2551: 2545: 2518: 2479: 2447: 2406: 2372: 2338: 2258: 2224: 2157: 2137: 2124: 2107: 2078: 1989: 1965: 1953: 1945: 1939: 1926: 1920: 1904: 1883: 1857: 1853: 1834: 1805: 1763: 1721: 1716: 1707: 1592: 1554: 1515: 1503: 1472: 1393: 1361: 1322: 1305: 1282: 1257: 1227: 1192: 1191: 1186: 1182: 1119: 997: 991: 988: 965: 963: 929: 923: 920: 909: 894: 888: 885: 842: 833: 816: 804: 789: 742: 711: 692: 670: 656: 651: 640: 607: 589: 574: 520: 480: 463: 418: 397: 379: 365: 359: 356: 321: 305: 264: 258: 255: 238: 232: 229: 210: 200: 185: 170: 153: 140: 115: 78: 34: 26: 25: 24: 12: 11: 5: 5303: 5301: 5293: 5292: 5249: 5246: 5245: 5244: 5228: 5227: 5226: 5225: 5224: 5223: 5222: 5221: 5220: 5219: 5218: 5217: 5216: 5215: 5214: 5213: 5212: 5133: 5132: 5131: 5130: 5129: 5128: 5127: 5126: 5125: 5124: 5123: 5122: 5121: 5120: 5060: 5059: 5058: 5057: 5056: 5055: 5054: 5053: 5052: 5051: 5050: 5049: 5013: 5012: 5011: 5010: 5009: 5008: 5007: 5006: 5005: 5004: 4953: 4952: 4951: 4950: 4949: 4948: 4928: 4927: 4926: 4925: 4903: 4902: 4901: 4900: 4878: 4877: 4808: 4805: 4787: 4784: 4783: 4782: 4740: 4737: 4736: 4735: 4734: 4733: 4659:User:Taxobot 7 4654: 4651: 4643: 4642: 4641: 4640: 4639: 4605: 4597: 4496: 4495: 4494: 4493: 4481: 4480: 4479: 4374: 4373: 4372: 4371: 4370: 4369: 4368: 4367: 4288: 4271: 4270: 4252: 4221: 4220: 4219: 4207:the removal. 4204: 4196: 4177: 4171: 4156: 4155: 4154: 4153: 4152: 4151: 4150: 4149: 4148: 4147: 4124: 4123: 4122: 4121: 4080: 4070: 4069: 4050: 4049: 4048: 4047: 4046: 4045: 4019: 3994: 3993: 3967: 3941: 3940: 3934: 3924: 3918: 3896: 3895: 3885: 3884: 3872: 3871: 3869: 3866: 3865: 3864: 3863: 3862: 3810: 3807: 3806: 3805: 3804: 3803: 3776: 3775: 3774: 3773: 3767: 3723: 3692: 3689: 3672: 3669: 3668: 3667: 3666: 3665: 3664: 3663: 3662: 3661: 3660: 3659: 3565: 3562: 3561: 3560: 3559: 3558: 3557: 3556: 3555: 3554: 3553: 3552: 3517: 3506: 3502: 3491: 3490: 3489: 3488: 3487: 3486: 3485: 3484: 3483: 3482: 3481: 3480: 3356: 3355: 3354: 3353: 3352: 3351: 3350: 3349: 3348: 3347: 3346: 3345: 3344: 3343: 3315: 3314: 3313: 3312: 3311: 3310: 3309: 3308: 3307: 3306: 3305: 3304: 3303: 3302: 3276: 3275: 3238: 3215: 3214: 3213: 3212: 3211: 3210: 3209: 3208: 3197: 3196: 3195: 3192: 3188: 3175: 3155: 3154: 3139: 3135: 3131: 3105: 3104: 3103: 3098: 3091: 3088: 3067: 3066: 3065: 3062: 3059: 3056: 3052:|portal3-link= 3048: 3038: 3037: 3036: 3033: 3030: 3027: 3024: 3023: 3022: 3019: 3016: 3006: 3003: 3000: 2996: 2990: 2947: 2946: 2945: 2944: 2943: 2942: 2941: 2940: 2939: 2938: 2937: 2936: 2935: 2934: 2933: 2932: 2901: 2871: 2870: 2869: 2865: 2861: 2857: 2854: 2850: 2847: 2813: 2812: 2787: 2743: 2708: 2705: 2687: 2686: 2671: 2670: 2666:Article Wizard 2662: 2658: 2657: 2636: 2635: 2632: 2625: 2624: 2623: 2622: 2621: 2620: 2619: 2618: 2617: 2616: 2584: 2583: 2540: 2539: 2538: 2537: 2536: 2535: 2534: 2533: 2532: 2531: 2428: 2427: 2426: 2425: 2424: 2423: 2422: 2421: 2420: 2419: 2316:anything to 2309: 2308: 2304: 2301: 2298: 2295: 2291: 2288: 2284: 2278: 2274: 2273: 2272: 2271: 2270: 2269: 2211: 2210: 2209: 2208: 2207: 2206: 2175: 2174: 2173: 2172: 2171: 2170: 2148: 2147: 2146: 2145: 2099: 2098: 2097: 2096: 2095: 2094: 2093: 2092: 2091: 2090: 2089: 2088: 2087: 2086: 2017: 2016: 2015: 2012: 2009: 1985: 1894: 1852: 1849: 1848: 1847: 1817:Magog the Ogre 1804: 1802:OgreBot -: --> 1800: 1799: 1798: 1797: 1796: 1795: 1794: 1706: 1703: 1702: 1701: 1700: 1699: 1698: 1697: 1696: 1695: 1694: 1693: 1633: 1629: 1591: 1588: 1587: 1586: 1576:Easily fixed. 1553: 1550: 1549: 1548: 1547: 1546: 1529: 1528: 1510: 1471: 1468: 1467: 1466: 1465: 1464: 1392: 1389: 1388: 1387: 1360: 1355: 1344:Magog the Ogre 1330:Magog the Ogre 1321: 1320:Waiting period 1318: 1317: 1316: 1300: 1299: 1298: 1297: 1296: 1295: 1271: 1270: 1269: 1268: 1250: 1249: 1199: 1198: 1184: 1181: 1178: 1177: 1176: 1118: 1115: 1114: 1113: 1098: 1094: 1086: 1082: 1078: 1077: 1045: 1042: 1031: 1030: 1029: 1026: 1023: 1017: 1011: 1010: 1009: 1008: 1007: 1006: 908: 905: 904: 903: 876: 859: 841: 840: 829: 811: 800: 756:WP:Turing test 752: 741: 738: 737: 736: 735: 734: 706: 705: 669: 666: 665: 664: 663: 631: 630: 629: 628: 627: 626: 625: 624: 623: 622: 621: 620: 619: 618: 617: 616: 615: 614: 564:mistakes like 534: 532: 531: 500: 499: 498: 497: 496: 495: 494: 493: 492: 491: 455: 449: 442: 437:Definitions: " 407: 406: 405: 404: 337: 336: 335: 334: 333: 332: 226:user talk page 222:User:Starzynka 209: 206: 198: 184: 181: 180: 179: 178: 177: 114: 108: 106: 102: 101: 96: 93: 88: 83: 76: 71: 66: 56: 55: 38: 27: 15: 14: 13: 10: 9: 6: 4: 3: 2: 5302: 5291: 5287: 5283: 5275: 5267: 5266: 5265: 5264: 5260: 5256: 5247: 5243: 5240: 5238: 5237: 5229: 5211: 5206: 5202: 5198: 5194: 5190: 5183: 5177: 5176: 5175: 5171: 5167: 5163: 5156: 5149: 5148: 5147: 5146: 5145: 5144: 5143: 5142: 5141: 5140: 5139: 5138: 5137: 5136: 5135: 5134: 5119: 5114: 5110: 5106: 5102: 5098: 5090: 5080: 5074: 5073: 5072: 5071: 5070: 5069: 5068: 5067: 5066: 5065: 5064: 5063: 5062: 5061: 5048: 5044: 5040: 5032: 5025: 5024: 5023: 5022: 5021: 5020: 5019: 5018: 5017: 5016: 5015: 5014: 5003: 4998: 4994: 4990: 4986: 4982: 4977: 4970: 4963: 4962: 4961: 4960: 4959: 4958: 4957: 4956: 4955: 4954: 4947: 4943: 4939: 4934: 4933: 4932: 4931: 4930: 4929: 4924: 4920: 4916: 4907: 4906: 4905: 4904: 4899: 4895: 4891: 4882: 4881: 4880: 4879: 4876: 4871: 4867: 4863: 4859: 4855: 4849: 4848: 4847: 4846: 4842: 4838: 4828: 4827: 4823: 4819: 4814: 4806: 4804: 4803: 4800: 4797: 4793: 4785: 4781: 4778: 4775: 4771: 4766: 4765: 4764: 4763: 4760: 4758: 4757: 4750: 4746: 4738: 4732: 4729: 4726: 4722: 4718: 4717: 4716: 4711: 4707: 4703: 4698: 4691: 4687: 4686: 4685: 4684: 4681: 4678: 4674: 4668: 4664: 4660: 4652: 4647: 4638: 4635: 4632: 4628: 4624: 4620: 4619: 4618: 4614: 4610: 4606: 4603: 4598: 4595: 4590: 4581: 4580: 4579: 4578: 4575: 4574:Dirk Beetstra 4569: 4567: 4561: 4557: 4555: 4550: 4545: 4542: 4536: 4534: 4530: 4526: 4522: 4518: 4512: 4509: 4503: 4501: 4492: 4489: 4486: 4482: 4478: 4475: 4472: 4468: 4459: 4455: 4450: 4449: 4448: 4444: 4440: 4436: 4431: 4427: 4426: 4425: 4421: 4417: 4405: 4404: 4403: 4402: 4399: 4396: 4391: 4389: 4384: 4379: 4366: 4362: 4358: 4353: 4348: 4344: 4343: 4342: 4338: 4334: 4330: 4329: 4328: 4324: 4320: 4315: 4314: 4313: 4308: 4307: 4302: 4300: 4297: 4294: 4286: 4282: 4277: 4273: 4272: 4269: 4265: 4261: 4256: 4253: 4251: 4247: 4243: 4239: 4234: 4230: 4225: 4222: 4218: 4214: 4210: 4205: 4201: 4197: 4194: 4190: 4186: 4182: 4178: 4174: 4173: 4169: 4165: 4161: 4160:Strong oppose 4158: 4157: 4146: 4142: 4138: 4134: 4133: 4132: 4131: 4130: 4129: 4128: 4127: 4126: 4125: 4120: 4116: 4112: 4107: 4106: 4105: 4100: 4099: 4094: 4092: 4089: 4086: 4077: 4072: 4071: 4068: 4064: 4060: 4055: 4052: 4051: 4044: 4039: 4038: 4033: 4031: 4028: 4025: 4017: 4013: 4012: 4011: 4007: 4003: 3998: 3997: 3996: 3995: 3992: 3987: 3986: 3981: 3979: 3976: 3973: 3965: 3961: 3960:Strong Oppose 3958: 3957: 3956: 3955: 3951: 3947: 3938: 3935: 3932: 3928: 3925: 3922: 3919: 3916: 3913: 3912: 3911: 3907: 3905: 3901: 3900:User:XLinkBot 3894: 3893: 3888: 3887: 3883: 3880: 3874: 3873: 3867: 3861: 3857: 3853: 3849: 3848: 3847: 3844: 3835: 3831: 3830: 3829: 3828: 3824: 3820: 3816: 3802: 3798: 3794: 3789: 3784: 3780: 3779: 3778: 3777: 3772: 3769: 3764: 3760: 3759: 3758: 3755: 3752: 3748: 3744: 3736: 3732: 3728: 3724: 3721: 3717: 3716: 3715: 3714: 3710: 3706: 3702: 3698: 3690: 3688: 3687: 3683: 3679: 3670: 3658: 3654: 3650: 3646: 3645: 3644: 3640: 3636: 3632: 3631: 3630: 3626: 3622: 3618: 3614: 3613: 3612: 3609: 3605: 3604: 3603: 3599: 3595: 3590: 3589: 3588: 3587: 3583: 3579: 3575: 3571: 3563: 3551: 3547: 3543: 3538: 3537: 3536: 3532: 3531: 3529: 3524: 3518: 3515: 3511: 3507: 3503: 3499: 3498: 3497: 3496: 3495: 3494: 3493: 3492: 3479: 3475: 3471: 3466: 3465: 3464: 3460: 3456: 3451: 3450: 3449: 3446: 3443: 3438: 3433: 3432: 3431: 3427: 3423: 3419: 3414: 3413: 3412: 3408: 3404: 3400: 3396: 3395: 3394: 3390: 3386: 3381: 3380: 3379: 3378: 3374: 3370: 3366: 3362: 3342: 3338: 3334: 3329: 3328: 3327: 3326: 3325: 3324: 3323: 3322: 3321: 3320: 3319: 3318: 3317: 3316: 3301: 3297: 3293: 3289: 3285: 3280: 3279: 3278: 3277: 3270: 3263: 3259: 3255: 3247: 3239: 3236: 3232: 3228: 3227: 3225: 3224: 3223: 3222: 3221: 3220: 3219: 3218: 3217: 3216: 3207: 3204: 3201: 3198: 3193: 3189: 3183: 3176: 3173: 3166: 3159: 3158: 3157: 3156: 3153: 3149: 3145: 3140: 3136: 3132: 3126: 3120: 3119: 3117: 3116: 3115: 3112: 3109: 3106: 3099: 3096: 3092: 3089: 3086: 3085: 3083: 3082: 3081: 3077: 3073: 3068: 3063: 3060: 3057: 3049: 3046: 3042: 3041: 3039: 3034: 3031: 3028: 3025: 3020: 3017: 3014: 3013: 3011: 3007: 3004: 3001: 2997: 2994: 2993: 2991: 2987: 2986: 2985: 2984: 2980: 2976: 2968: 2964: 2963:filled a BRFA 2960: 2953: 2952:edit conflict 2931: 2927: 2923: 2918: 2917: 2916: 2913: 2910: 2906: 2902: 2900: 2896: 2892: 2887: 2886: 2885: 2881: 2877: 2872: 2866: 2862: 2858: 2855: 2851: 2848: 2844: 2843: 2841: 2837: 2836: 2835: 2831: 2827: 2823: 2819: 2818: 2817: 2816: 2815: 2814: 2811: 2807: 2803: 2798: 2793: 2788: 2784: 2783: 2781: 2780: 2779: 2775: 2771: 2767: 2763: 2759: 2755: 2754: 2753: 2752: 2748: 2747: 2740: 2735: 2727: 2723: 2720: 2717: 2713: 2706: 2704: 2703: 2699: 2694: 2685: 2682: 2673: 2672: 2667: 2663: 2660: 2659: 2655: 2654: 2653: 2652: 2648: 2643: 2633: 2630: 2629: 2628: 2615: 2611: 2607: 2603: 2599: 2594: 2593: 2592: 2591: 2590: 2589: 2588: 2587: 2586: 2585: 2582: 2579: 2569: 2561: 2550: 2542: 2541: 2530: 2526: 2521: 2515: 2514: 2513: 2509: 2505: 2501: 2497: 2493: 2492: 2491: 2487: 2482: 2476: 2475: 2474: 2470: 2466: 2461: 2460: 2459: 2455: 2450: 2445: 2444: 2443: 2442: 2438: 2434: 2418: 2414: 2409: 2404: 2403: 2402: 2398: 2394: 2390: 2386: 2385: 2384: 2380: 2375: 2370: 2369: 2368: 2364: 2360: 2355: 2352: 2351: 2350: 2346: 2341: 2335: 2334: 2333: 2332: 2328: 2324: 2319: 2314: 2305: 2302: 2299: 2296: 2292: 2289: 2285: 2282: 2281: 2280: 2268: 2265: 2263: 2261: 2255: 2254: 2253: 2249: 2245: 2241: 2240:Mack McCarter 2236: 2235: 2234: 2231: 2229: 2227: 2221: 2217: 2213: 2212: 2205: 2201: 2197: 2193: 2190: 2187: 2184: 2181: 2180: 2179: 2178: 2177: 2176: 2169: 2165: 2160: 2154: 2153: 2152: 2151: 2150: 2149: 2144: 2141: 2132: 2127: 2122: 2121: 2120: 2119: 2118: 2117: 2114: 2112: 2110: 2104: 2085: 2082: 2073: 2068: 2067: 2066: 2062: 2058: 2053: 2049: 2033: 2032: 2031: 2027: 2023: 2018: 2013: 2010: 2007: 2006: 2003: 2002: 2001: 1997: 1992: 1986: 1982: 1981: 1980: 1976: 1975: 1973: 1968: 1962: 1961: 1960: 1957: 1944: 1937: 1933: 1925: 1918: 1917: 1916: 1912: 1908: 1899: 1895: 1893: 1890: 1888: 1886: 1880: 1876: 1872: 1871: 1870: 1869: 1865: 1860: 1850: 1846: 1842: 1838: 1830: 1829: 1828: 1827: 1822: 1818: 1814: 1810: 1801: 1793: 1789: 1785: 1781: 1777: 1776: 1775: 1771: 1767: 1759: 1755: 1750: 1749: 1748: 1744: 1740: 1736: 1732: 1731: 1730: 1729: 1726: 1724: 1719: 1713: 1704: 1692: 1688: 1684: 1679: 1678: 1677: 1673: 1669: 1664: 1663: 1662: 1659: 1656: 1651: 1648: 1647: 1646: 1642: 1638: 1634: 1630: 1626: 1625: 1624: 1621: 1618: 1613: 1612: 1611: 1610: 1606: 1602: 1597: 1596: 1589: 1585: 1582: 1579: 1575: 1574: 1573: 1572: 1568: 1564: 1559: 1552:Orphaned BRFA 1551: 1545: 1541: 1537: 1533: 1532: 1531: 1530: 1527: 1523: 1519: 1511: 1509: 1506: 1500: 1499: 1498: 1497: 1493: 1489: 1484: 1480: 1477: 1469: 1463: 1460: 1457: 1453: 1447: 1443: 1442: 1441: 1438: 1435: 1431: 1425: 1421: 1420: 1419: 1418: 1415: 1412: 1408: 1402: 1397: 1390: 1386: 1383: 1380: 1376: 1375: 1374: 1373: 1370: 1366: 1359: 1356: 1354: 1353: 1349: 1345: 1340: 1339: 1335: 1331: 1327: 1319: 1315: 1312: 1310: 1308: 1302: 1301: 1294: 1290: 1286: 1277: 1276: 1275: 1274: 1273: 1272: 1267: 1264: 1262: 1260: 1254: 1253: 1252: 1251: 1248: 1245: 1244:Dirk Beetstra 1240: 1239: 1238: 1237: 1234: 1232: 1230: 1224: 1221: 1218: 1214: 1211: 1208: 1204: 1197: 1194: 1193: 1179: 1175: 1171: 1167: 1163: 1159: 1158: 1157: 1156: 1153: 1150: 1146: 1140: 1136: 1133: 1131: 1127: 1122: 1116: 1112: 1108: 1104: 1099: 1095: 1092: 1087: 1083: 1080: 1079: 1076: 1072: 1068: 1063: 1060:(confer with 1059: 1055: 1051: 1046: 1043: 1041: 1036: 1032: 1027: 1024: 1021: 1020: 1018: 1016: 1015: 1014: 1005: 1000: 994: 986: 985: 984: 980: 976: 971: 962: 961: 960: 956: 952: 948: 944: 940: 939: 938: 937: 932: 926: 918: 914: 906: 902: 897: 891: 883: 879: 878: 877: 874: 870: 869: 866: 860: 857: 853: 852: 849: 839: 836: 830: 828: 824: 820: 812: 810: 807: 801: 799: 796: 794: 792: 786: 785: 784: 783: 780: 777: 773: 768: 766: 760: 757: 751: 746: 739: 733: 730: 727: 723: 722: 721: 718: 716: 714: 708: 707: 704: 700: 696: 688: 684: 681: 680: 679: 675: 674: 667: 662: 659: 653: 652: 649: 647: 645: 643: 637: 613: 610: 604: 600: 599: 598: 595: 592: 586: 582: 581: 580: 577: 571: 567: 562: 558: 552: 551:edit conflict 547: 546: 545: 544: 543: 542: 541: 540: 539: 538: 537: 536: 535: 530: 527: 525: 523: 517: 516: 515: 514: 510: 506: 490: 487: 485: 483: 477: 474: 473: 472: 469: 466: 460: 456: 453: 450: 446: 443: 440: 436: 432: 431: 430: 426: 422: 413: 412: 411: 410: 409: 408: 403: 400: 394: 390: 389: 388: 385: 382: 376: 375: 374: 373: 368: 362: 354: 350: 346: 342: 331: 328: 326: 324: 318: 313: 312: 311: 308: 302: 300: 296: 292: 286: 284: 278: 274: 273: 272: 267: 261: 253: 249: 248: 247: 246: 241: 235: 227: 223: 219: 218:contributions 215: 207: 205: 204: 201: 196: 195: 190: 189:I like to see 182: 176: 173: 167: 166: 165: 161: 157: 149: 148: 147: 146: 143: 136: 132: 128: 124: 121:with the new 120: 112: 109: 107: 100: 97: 94: 92: 89: 87: 84: 81: 77: 75: 72: 70: 67: 65: 62: 61: 53: 49: 45: 44: 39: 32: 31: 23: 19: 5273: 5251: 5235: 5234: 4974:or those in 4829: 4810: 4789: 4755: 4754: 4742: 4696: 4694:— Preceding 4669: 4656: 4645: 4600: 4583: 4570: 4565: 4562: 4558: 4553: 4548: 4546: 4537: 4533:WP:COPYRIGHT 4520: 4513: 4507: 4504: 4499: 4497: 4435:WP:VIDEOLINK 4416:WhatamIdoing 4392: 4382: 4375: 4350: 4346: 4305: 4298: 4295: 4292: 4280: 4254: 4237: 4232: 4223: 4209:WhatamIdoing 4199: 4188: 4184: 4181:WP:BLACKLIST 4167: 4163: 4159: 4097: 4090: 4087: 4084: 4053: 4036: 4029: 4026: 4023: 4015: 3984: 3977: 3974: 3971: 3963: 3959: 3942: 3936: 3930: 3926: 3920: 3914: 3908: 3897: 3889: 3878: 3875: 3812: 3694: 3674: 3567: 3527: 3526: 3436: 3403:VernoWhitney 3398: 3369:VernoWhitney 3363:followed by 3357: 3287: 3283: 3261: 3257: 3253: 3234: 3230: 3171: 3094: 2948: 2891:VernoWhitney 2839: 2826:VernoWhitney 2796: 2791: 2770:VernoWhitney 2730: 2718: 2710: 2692: 2688: 2641: 2637: 2626: 2596: 2519: 2499: 2495: 2480: 2448: 2429: 2407: 2388: 2373: 2353: 2339: 2321:they are. -- 2317: 2312: 2310: 2275: 2259: 2225: 2158: 2108: 2100: 2051: 2047: 2044:|bot=Snotbot 1990: 1971: 1970: 1884: 1858: 1854: 1806: 1784:Magioladitis 1739:Magioladitis 1733:Do you mean 1708: 1598: 1593: 1563:VernoWhitney 1555: 1485: 1481: 1473: 1448: 1426: 1403: 1394: 1362: 1341: 1325: 1323: 1306: 1258: 1228: 1209: 1200: 1141: 1137: 1134: 1126:User:Taxobot 1123: 1120: 1057: 1053: 1049: 1039: 1034: 1012: 969: 946: 910: 863: 861: 846: 843: 834: 831: 790: 769: 761: 748: 744: 743: 712: 686: 682: 676: 672: 671: 657: 654: 641: 633: 602: 560: 533: 521: 501: 481: 475: 451: 444: 438: 338: 322: 294: 288: 282: 281:"high-speed 280: 211: 193: 186: 183:Bot platform 134: 130: 127:interwiki.py 122: 116: 105: 79: 47: 41: 4665:. Thanks, 3915:is harmless 3269:Talk header 3246:Talk header 2853:practices)? 2337:premature. 2188:leading to 2040:|source=bot 1735:WP:GENFIXES 1556:So there's 1367:. Regards, 913:bot request 907:Ganeshbot 5 40:This is an 4813:discussion 4799:Od Mishehu 4702:Cymru.lass 4456:, or that 4352:newcomers. 3763:WP:AN#Idea 3739:(anymore?) 3725:Regarding 3256:than this 3182:talkheader 2868:confusion. 1807:Currently 1476:SuggestBot 1369:SunCreator 868:Farmbrough 851:Farmbrough 740:Proposal 2 570:magic word 559:says that 557:bot policy 353:impression 277:bot policy 250:Here is a 125:option of 99:Archive 15 91:Archive 10 5274:Approved. 5089:cite book 4796:עוד מישהו 4749:corrected 4198:XLinkBot 3608:Jarry1250 2766:WP:BOTPOL 2693:North8000 2642:North8000 2568:ownership 2520:North8000 2481:North8000 2449:North8000 2408:North8000 2374:North8000 2340:North8000 2313:consensus 2287:patrolled 2159:North8000 2105:patrol? – 1991:North8000 1859:North8000 1668:Kleopatra 1650:WP:BOTPOL 1637:Kleopatra 1601:Kleopatra 1391:Taxobot 5 1201:In 2006, 634:Moved to 590:Accotink2 505:Starzynka 464:Accotink2 380:Accotink2 347:has been 86:Archive 9 80:Archive 8 74:Archive 7 69:Archive 6 64:Archive 5 5236:Rjwilmsi 5197:contribs 5189:Headbomb 5155:Cite pmc 5105:contribs 5097:Headbomb 5084:has two 4989:contribs 4981:Headbomb 4862:contribs 4854:Headbomb 4756:Rjwilmsi 4710:contribs 4673:Smith609 4566:per link 4333:Johnuniq 4255:Question 4242:Johnuniq 3868:XLinkBot 3793:Carnildo 3705:Carnildo 3286:or this 3095:includes 2860:project. 2722:contribs 2598:agendas. 2036:|bot=yes 1778:I wrote 1452:Smith609 1430:Smith609 1407:Smith609 1213:contribs 1203:SmackBot 1190:Resolved 1166:Johnuniq 1145:Smith609 947:Doing... 668:Proposal 349:creating 275:Per the 216:, these 208:Town bot 123:-cleanup 20:‎ | 5255:Kingpin 5201:physics 5109:physics 4993:physics 4866:physics 4609:Cptnono 4589:Youtube 4541:WP:ELNO 4521:totally 4458:WP:PSTS 4439:Cptnono 4357:Cptnono 4319:Cptnono 4296:ean–Hun 4238:quickly 4137:Cptnono 4111:Kumioko 4088:ean–Hun 4059:Kumioko 4054:Support 4027:ean–Hun 4002:Cptnono 3975:ean–Hun 3946:Cptnono 3852:Kumioko 3834:WP:BOTR 3819:Kumioko 3678:Kumioko 3649:Kumioko 3635:Kumioko 3621:Kumioko 3594:Kumioko 3578:Kumioko 3542:Kumioko 3470:Kumioko 3455:Kumioko 3437:someone 3422:Kumioko 3385:Kumioko 3333:Kumioko 3292:Kumioko 3144:Kumioko 3072:Kumioko 2967:Kumioko 2959:Kumioko 2922:Kumioko 2876:Kumioko 2840:require 2802:Kumioko 2726:WP:WPUS 2712:Kumioko 2606:Kudpung 2600:(from 2504:Kingpin 2465:Kingpin 2433:Kudpung 2393:Kingpin 2389:towards 2359:Kingpin 2323:Kudpung 2244:Thincat 2196:Thincat 2072:twinkle 2057:Kingpin 2022:Kudpung 1809:OgreBot 1536:Nettrom 1504:EdoDodo 1488:Nettrom 1135:Thanks 1103:Kingpin 992:Ganeshk 975:Kingpin 951:Kingpin 924:Ganeshk 889:Ganeshk 805:EdoDodo 765:WP:DUCK 750:manual. 683:Support 608:EdoDodo 575:EdoDodo 452:Scripts 398:EdoDodo 360:Ganeshk 306:EdoDodo 291:decided 259:Ganeshk 233:Ganeshk 214:WP:DUCK 171:EdoDodo 141:EdoDodo 43:archive 5166:Jc3s5h 5039:Jc3s5h 4938:Jc3s5h 4818:Jc3s5h 4774:Anomie 4725:Anomie 4697:signed 4667:Martin 4631:Anomie 4627:WP:VPP 4529:WP:NOT 4485:Anomie 4471:Anomie 4395:Anomie 4383:anyone 4224:Oppose 4203:kept". 4076:pointy 3839:Snotty 3751:Anomie 3442:Anomie 3200:Anomie 3108:Anomie 2909:Anomie 2797:cannot 2733:Imzadi 2677:Snotty 2602:WP:SPA 2574:Snotty 2307:therm. 2220:WP:VPP 2216:WT:NPP 2136:Snotty 2131:WP:NPP 2077:Snotty 1952:Snotty 1712:WP:AWB 1655:Anomie 1617:Anomie 1578:Anomie 1446:Martin 1424:Martin 1401:Martin 1379:Anomie 1365:WP:BAG 1358:Review 1139:Martin 1067:Snek01 776:Anomie 772:WP:ANI 726:Anomie 687:in par 131:-force 119:EdoBot 111:EdoBot 5282:KNOWZ 5205:books 5113:books 4997:books 4915:KNOWZ 4890:KNOWZ 4870:books 4837:KNOWZ 4721:WP:BN 4623:WT:EL 4554:still 4525:WP:EL 4517:WP:EL 4500:never 4299:ter—► 4293:⋙–Ber 4168:never 4091:ter—► 4085:⋙–Ber 4030:ter—► 4024:⋙–Ber 3978:ter—► 3972:⋙–Ber 2975:KNOWZ 2864:does. 2707:Query 1984:that. 1907:KNOWZ 1837:KNOWZ 1782:. -- 1766:KNOWZ 1737:? -- 1518:KNOWZ 1326:weeks 1285:KNOWZ 819:KNOWZ 695:KNOWZ 421:KNOWZ 341:asked 194:d'oh! 156:KNOWZ 16:< 5286:TALK 5280:HELL 5259:talk 5193:talk 5182:Bots 5170:talk 5101:talk 5043:talk 4985:talk 4942:talk 4919:TALK 4913:HELL 4894:TALK 4888:HELL 4858:talk 4841:TALK 4835:HELL 4822:talk 4706:talk 4677:Talk 4613:talk 4454:WP:N 4443:talk 4430:this 4420:talk 4361:talk 4337:talk 4323:talk 4264:talk 4260:Gigs 4246:talk 4213:talk 4200:does 4193:this 4189:very 4141:talk 4115:talk 4063:talk 4016:your 4006:talk 3950:talk 3856:talk 3841:Wong 3823:talk 3797:talk 3733:and 3709:talk 3699:and 3682:talk 3653:talk 3639:talk 3625:talk 3619:. -- 3598:talk 3582:talk 3546:talk 3512:and 3474:talk 3459:talk 3426:talk 3407:talk 3389:talk 3373:talk 3365:this 3361:this 3337:talk 3296:talk 3148:talk 3076:talk 3045:here 2979:TALK 2973:HELL 2926:talk 2895:talk 2880:talk 2830:talk 2806:talk 2792:some 2774:talk 2760:and 2738:1979 2716:talk 2698:talk 2679:Wong 2647:talk 2610:talk 2576:Wong 2525:talk 2508:talk 2496:only 2486:talk 2469:talk 2454:talk 2437:talk 2413:talk 2397:talk 2379:talk 2363:talk 2345:talk 2327:talk 2318:your 2294:etc. 2260:xeno 2248:talk 2226:xeno 2200:talk 2164:talk 2138:Wong 2109:xeno 2079:Wong 2061:talk 2052:only 2048:only 2026:talk 1996:talk 1954:Wong 1911:TALK 1905:HELL 1885:xeno 1873:See 1864:talk 1841:TALK 1835:HELL 1821:talk 1788:talk 1770:TALK 1764:HELL 1743:talk 1722:1357 1687:talk 1683:Gigs 1672:talk 1641:talk 1605:talk 1567:talk 1540:talk 1522:TALK 1516:HELL 1492:talk 1456:Talk 1434:Talk 1411:Talk 1348:talk 1334:talk 1307:xeno 1289:TALK 1283:HELL 1259:xeno 1229:xeno 1207:talk 1170:talk 1149:Talk 1121:Hi, 1107:talk 1085:not. 1071:talk 1052:and 998:talk 979:talk 970:Done 955:talk 930:talk 917:Here 895:talk 882:here 865:Rich 848:Rich 823:TALK 817:HELL 791:xeno 747:like 713:xeno 699:TALK 693:HELL 642:xeno 594:talk 566:this 522:xeno 509:talk 482:xeno 468:talk 439:Bots 425:TALK 419:HELL 395:. - 393:here 384:talk 366:talk 323:xeno 317:e.g. 287:and 265:talk 239:talk 212:Per 199:talk 160:TALK 154:HELL 4625:or 4602:win 4549:are 4378:BAG 4306:(⊕) 4233:lot 4164:and 4098:(⊕) 4037:(⊕) 3985:(⊕) 3906:. 3836:. 3766:ΔT 3574:Bob 3530:man 3523:Mr. 3418:AGF 2500:not 2129:at 1974:man 1967:Mr. 1717:Tim 1632:it. 638:. – 220:by 5261:) 5203:/ 5199:/ 5195:/ 5180:{{ 5172:) 5158:}} 5152:{{ 5111:/ 5107:/ 5103:/ 5092:}} 5086:{{ 5082:}} 5076:{{ 5045:) 5034:}} 5028:{{ 4995:/ 4991:/ 4987:/ 4978:. 4972:}} 4966:{{ 4944:) 4909:— 4868:/ 4864:/ 4860:/ 4831:— 4824:) 4712:) 4708:• 4675:– 4629:. 4615:) 4592:}} 4586:{{ 4531:, 4508:is 4445:) 4422:) 4390:. 4363:) 4339:) 4325:) 4266:) 4248:) 4215:) 4143:) 4117:) 4065:) 4008:) 3952:) 3933:") 3858:) 3825:) 3799:) 3791:-- 3711:) 3684:) 3655:) 3641:) 3627:) 3600:) 3592:-- 3584:) 3548:) 3528:Z- 3476:) 3461:) 3428:) 3409:) 3391:) 3375:) 3339:) 3298:) 3272:}} 3266:{{ 3249:}} 3243:{{ 3185:}} 3179:{{ 3168:}} 3162:{{ 3150:) 3128:}} 3122:{{ 3078:) 2928:) 2897:) 2882:) 2832:) 2808:) 2776:) 2768:. 2700:) 2649:) 2612:) 2563:}} 2557:{{ 2552:}} 2546:{{ 2527:) 2510:) 2488:) 2471:) 2456:) 2439:) 2415:) 2399:) 2381:) 2365:) 2347:) 2329:) 2250:) 2202:) 2166:) 2063:) 2038:, 2028:) 1998:) 1972:Z- 1946:}} 1940:{{ 1927:}} 1921:{{ 1877:/ 1866:) 1823:) 1790:) 1745:) 1689:) 1674:) 1643:) 1607:) 1569:) 1542:) 1494:) 1454:– 1432:– 1409:– 1350:) 1336:) 1279:— 1242:-- 1172:) 1147:– 1109:) 1073:) 1065:-- 989:— 981:) 973:- 957:) 949:- 921:— 886:— 884:. 871:, 854:, 758:;) 511:) 461:. 357:— 279:: 256:— 254:. 230:— 95:→ 5284:▎ 5257:( 5207:} 5191:{ 5168:( 5115:} 5099:{ 5041:( 4999:} 4983:{ 4940:( 4917:▎ 4892:▎ 4872:} 4856:{ 4839:▎ 4820:( 4777:⚔ 4728:⚔ 4704:( 4679:) 4671:( 4634:⚔ 4611:( 4604:" 4488:⚔ 4474:⚔ 4441:( 4418:( 4398:⚔ 4359:( 4335:( 4321:( 4309:) 4303:( 4262:( 4244:( 4211:( 4195:. 4139:( 4113:( 4101:) 4095:( 4061:( 4040:) 4034:( 4004:( 3988:) 3982:( 3948:( 3854:( 3821:( 3795:( 3754:⚔ 3707:( 3680:( 3651:( 3637:( 3623:( 3596:( 3580:( 3544:( 3472:( 3457:( 3445:⚔ 3424:( 3405:( 3387:( 3371:( 3335:( 3294:( 3235:1 3231:1 3203:⚔ 3187:? 3174:. 3172:1 3146:( 3111:⚔ 3074:( 2977:▎ 2957:( 2954:) 2950:( 2924:( 2912:⚔ 2893:( 2878:( 2828:( 2804:( 2772:( 2744:→ 2719:· 2714:( 2696:( 2645:( 2608:( 2523:( 2506:( 2484:( 2467:( 2452:( 2435:( 2411:( 2395:( 2377:( 2361:( 2343:( 2325:( 2246:( 2198:( 2162:( 2059:( 2042:, 2024:( 1994:( 1909:▎ 1862:( 1839:▎ 1819:( 1786:( 1768:▎ 1741:( 1685:( 1670:( 1658:⚔ 1639:( 1620:⚔ 1603:( 1581:⚔ 1565:( 1538:( 1520:▎ 1490:( 1458:) 1450:( 1436:) 1428:( 1413:) 1405:( 1382:⚔ 1346:( 1332:( 1287:▎ 1210:· 1205:( 1168:( 1151:) 1143:( 1128:( 1105:( 1069:( 1001:) 995:( 977:( 953:( 933:) 927:( 898:) 892:( 875:. 858:. 821:▎ 779:⚔ 729:⚔ 697:▎ 553:) 549:( 507:( 423:▎ 369:) 363:( 315:( 268:) 262:( 242:) 236:( 158:▎ 54:.

Index

Knowledge (XXG) talk:Bots
Requests for approval
archive
current talk page
Archive 5
Archive 6
Archive 7
Archive 8
Archive 9
Archive 10
Archive 15
EdoBot
EdoBot
interwiki.py
EdoDodo
16:35, 14 September 2010 (UTC)
HELLKNOWZ
TALK
16:46, 14 September 2010 (UTC)
EdoDodo
05:15, 16 September 2010 (UTC)
I like to see
d'oh!
talk
12:06, 23 September 2010 (UTC)
WP:DUCK
contributions
User:Starzynka
user talk page
Ganeshk

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