Wikipedia:Administrators' noticeboard/Betacommand/Archive 3

A modest suggestion
I've been reading these threads for a while now because, frankly, it's fascinating to observe on the level of how we interact online, a topic that's interested me even since I first went online some 20 odd years ago. As a relative non-combatant, who's only commented a couple of times, I'd like to suggest that there are a number of people who might consider retiring from the discussion for a while, because they've become somewhat too invested in their positions and have (I think) lost perspective on the problem. If they were to do so for, say 48 hours, it might be possible for cooler heads to thrash through some of the concerns to see if there aren't practical things that can be done. For instance, it seems to me to be somewhat impractical to expect a totally new bot and operator to get up to speed quickly enough to get the job done by the deadline your require, and it's now irrelevant how consistent or inconsistent the past runs of the bot have been. However, there have been other suggestions, such as improving the bot's interface with the users to provide better information on what they should so, that seem to me are quite possible to implement in the time remaining. (I know that when I first saw a BetacommandBot notice on an article I was monitoring, I didn't have a clue what I should do about the problem, where I should go for help, or what was expected of me. I simply didn't involve myself much with image uploads - and I imagine there are many users who are in a similar position.) So that's my suggestion, for what it's worth, that the primary combatants take a break for a while and sit things out, come back in a couple of days and see if anything's improved. It would take some of the weight off the discussion and allow it to breathe a little. Ed Fitzgerald (unfutz)  (talk / cont)  18:27, 26 February 2008 (UTC)
 * Sounds very throw-sand-in-the-sandbox-and-jimmy-through-the-first-punch-not-me! but, if MickMacNee stops the relentless assault for 48 hours, so will I. --Hammersoft (talk) 18:32, 26 February 2008 (UTC)
 * It's discussion, not assault, this is the exact problem you have here. MickMacNee (talk) 18:35, 26 February 2008 (UTC)
 * Ah. Right. Me having a mental breakdown (according to you) is "discussion". My offer stands. You stop your assault for 48 hours, I stop. Deal? --Hammersoft (talk) 18:36, 26 February 2008 (UTC)
 * Mick: You've succesfully raised this issue and got this discussion going. Don't you think it would be worthwhile to see where it will lead if personal animosities are put aside? Since Hammersoft has agreed to a stand down, what harm is there if you take a break as well? Ed Fitzgerald (unfutz)  (talk / cont)  18:38, 26 February 2008 (UTC)
 * Asking for breaks just seems as another attempt to shut the discussion down without giving any valid reasons why, on the principle that if no-one is here, no consensus will be reached. I am here for anyone who has the will to talk reasonably about this subject, and not run to the accusations when they're recieve nothing more than they have given previously (where have I seen that argument used before?), or receive points they cannot answer, nor accuse me of personal attacks and spreading mis-information. Seriously, what correcting information has actually been forthcoming from betacommand in here at all today, or where do we find the correct information? At the end of the day, his complete silence is what will kill this issue off once and for all, a fact he is no doubt fully aware of, as the time-limits will pass and images will be deleted, anyone who wants to save them just seems to have to accept that they will be taking on an impossible job, or have to take on the project of writing another bot, as discussion of this bot seems to be completely unnacceptable. MickMacNee (talk) 18:50, 26 February 2008 (UTC)
 * Mick: I'm not suggesting that everyone leave and the discussion shut down, just a handful of people who are, at this point at least, generating a lot of heat without shedding much light on the problem at hand. It's certainly understandable that the discussion has come to this place, these are contentious issues that people feel strongly about, but I hope you would agree that the bottom-line purpose here should be to improve the current situation, and that thhis would probably be a little easier to do if the discussion cooled down a little. I think a 48-hour break for some folks would be useful in helping to do that. Ed Fitzgerald (unfutz)  (talk / cont)  18:55, 26 February 2008 (UTC)
 * It's difficult when HS effectively calls us children in his response to this, and then accuses Mick of a "relentless assault" in the same post. Some are trying to work toward improvement. Others are bent at defending at all costs. It's as simple as that. Bellwether B  C  18:46, 26 February 2008 (UTC)
 * If I made a personal insult against anyone, give me the diff and I'll apologize for it right here, right now. Do it. --Hammersoft (talk) 18:50, 26 February 2008 (UTC)
 * "...those who absolutely despise our non-free content policies...", "Yawn", and others. The first is a blatant violation of AGF, and the second is just insulting. Bellwether B  C  19:01, 26 February 2008 (UTC)
 * If you construe "yawn" as a personal attack on you, please forgive me as it was not my intent. It is a statement on the constant, repetitive calls for the bot to be blocked, not on the person(s) bringing the calls. As for "those who...despise", I stand by that. There are a number of people who do despise our policies on fair use. It's not a personal attack, and I did not identify any one person. If you have any other concerns regarding perceived personal attacks, please bring them to my attention and I will address them. Thank you, --Hammersoft (talk) 20:37, 26 February 2008 (UTC)
 * Folks, if you would indulge me, I think it might be worthwhile to try to keep this particular thread focused on my specific suggestion, without re-hashing anything that's gone down before. Perhaps my idea is untenable, but I do think it's worth at least some focused consideration while we're all in the neighborhood. Ed Fitzgerald (unfutz)  (talk / cont)  19:05, 26 February 2008 (UTC)
 * Certainly there's been an excess of ardor on both sides, and I suspect that things have been said that will be regretted later, but that's really no reason to not do something that has the chance of helping to move the discussion forward, instead of continuing to paddle in circles, as it appears is the case right now. Ed Fitzgerald (unfutz)  (talk / cont)  18:49, 26 February 2008 (UTC)


 * Well, you have your response from MickMacNee. Thanks for the effort Ed. Truly, sincerely appreciated. --Hammersoft (talk) 18:52, 26 February 2008 (UTC)
 * Don't give up on the idea just yet, if you would - let's see what develops. It's hard sometimes to stop on a dime! Ed Fitzgerald (unfutz)  (talk / cont)  18:57, 26 February 2008 (UTC)


 * Mick: If you're concerned that my suggestion is a subterfuge to derail or shut down the discussion while you're taking a break, please accept my assurances that it's not. I really have no particular agenda here - which is not to say I don't have opinions, but simply that I'm not focused on getting any specific result, just on allowing the conversation to proceed in a constructive way.  I'll be happy to chat with you here or on my talk page via e-mail if you'd like to be reassured of my intentions. Ed Fitzgerald (unfutz)  (talk / cont)  19:11, 26 February 2008 (UTC)


 * There frankly aren't enough people in here who are interested in bringing it to a conclusion, even if that was 'no consensus', as is now seen in the repetition of some proposals that I originally proposed on a now buried page at DRV, where history is being rewritten as we speak claiming that that page is an unnecessary duplicate, when in actual fact it pre-dated this page, and is a mere sub-section of it. There is no way of bringing the NFCC10c bot issue to an end without the inevitable Rfc on betacommand in my view, either that or like I say, he does what he wants to do and waits it out with the occassional outburst, and everyone accepts his bot operation for NFCC10c is off limits for discussion, and editors have to accept that to save images they have to wade through the completely random categories that contain 10 images or 10,000 depending what he's doing in real life, or just not be bothered about image losses at all. MickMacNee (talk) 19:28, 26 February 2008 (UTC)
 * Is it possible, do you think, to summarize your primary concerns aside from question of Betacommond's behavior? I ask because, assuming you were to agree to my suggestion and take a bit of a break from the discussion, it would be good to have a concise statement of what you perceive to be the problem at hand.  Perhaps you are right and the underlying issues can't be separated from how the bot is currently operated, but if you're wrong, and some changes can be made, it would be helpful to know where your thinking is at. Ed Fitzgerald (unfutz)  (talk / cont)  19:36, 26 February 2008 (UTC)


 * The bot tagging methodology as it is currently coded is totally indiscriminate and unhelpful, and the bots position in the whole saving images process is being innacurately represented due to lack of central discussion of its operation or planned use, or a proper statement of function, and to an extent its closed source nature. The code does not incorporate any finnesse to help the people who want to fix the images, especially in the initial case that raised this issue, an 11,000 tagging run in one day (that's images tagged mind, every single one needing the subsequent attention of a human to fix). There is no attempt to meaningfully sub-categorise images as per likely cause of non-comliance, i.e. newbie mistake, or previously compliant images, or images whose usage has changed, or as high risk cases of absentee uploaders, all of which are bot-detectable. This post has the disclaimer about lack of any meaningfull central discussion meaning opinons have to be formed from experience, archives or random recollections from observers. MickMacNee (talk) 19:59, 26 February 2008 (UTC)
 * Mick, thank you for that. As I said, I'm running out the door at the moment, but I'll be back shortly and will see if I properly understand your focus. Ed Fitzgerald (unfutz)  (talk / cont)  20:04, 26 February 2008 (UTC)
 * Hammersoft, if you'd also like to synopsize your views into, say, a half-dozen or so bullet points, that too would be helpful. Ed Fitzgerald (unfutz)  (talk / cont)  19:38, 26 February 2008 (UTC)
 * And if you would both pardon me if I sounded condescending there -- that wasn't my purpose. I've never done any kind of mediation before, so I'm sorta grasping for what to do. (IRL I'm much more of a yell-at-them-until-they-do-it person, so this is new for me.)  I'm just interested in having you both tell me what your major concerns are so they can be referenced by the participants if you folks decide to accept my suggestion and take a break. Ed Fitzgerald (unfutz)  (talk / cont)  19:46, 26 February 2008 (UTC)
 * Folks, I have to leave momentarily to pick up my kid from school, but I'll be back in about a half hour. Thanks very much for considering my suggestion. Ed Fitzgerald (unfutz)  (talk / cont)  19:59, 26 February 2008 (UTC)
 * Ed... no matter how heated things get on Wikipedia nothing is more important than your family or real life. Just saying... so we maintain a healthy perspective on this. EconomicsGuy (talk) 20:08, 26 February 2008 (UTC)
 * Ed, here's my response to Mick's points:
 * Mick point 1: Bot is "totally indiscriminate and unhelpful".
 * A:Hard to respond to as there is no specific complaint.
 * Mick point 2: "bots position in the whole saving images process is being inaccurately represented due to lack of central discussion of its operation or planned use"
 * A: The bot's position is clear; if the image doesn't name the article(s) where the image appears, it fails 10c. Not sure what else to make of this point.
 * Mick point 3: Bot has no "proper statement of function".
 * A:See big red letters much earlier on this page written by Betacommand regarding what the bot does with relation to 10c.
 * Mick point 4: "The code does not incorporate any finesse to help the people who want to fix the images".
 * A:The bot leaves a message for anyone who uploads or edits an image, with a description of what is wrong and where to get help to fix the problem. I recognize that WP:FURG isn't bedtime reading, but it is our standing guide on how to do this. If MickMacNee has suggestions on improving that guideline, he should propose them. Shortcomings of the guideline are not the bot's fault, and the bot is linking to the best resource out there for this.
 * Mick point 5: "11,000 tagging run" (being bad)
 * A:The bot has dealt with a huge number of images, number in the hundreds of thousands. The issue of scale is not a problem of the bot's. It's a function of how much traffic we get on the site, and there's little we can do about it. Either we tag the images or we don't. 11k isn't a figure we should be running away from just because it's large. This is not the bot's fault, but the fault of either (a) the uploaders failing to work within policy and/or (b) a failure of the project to make it easier for people to upload fair use imagery (not sure that would be a good idea, given our mission to produce a free encyclopedia).
 * Mick point 6: "There is no attempt to meaningfully sub-categorise images as per likely cause of non-compliance"
 * A:If Mick wants, we can create dated categories noting fair use images tagged by the bot as missing on 10c, but it's not going to change the volume of tagged images. The issue of scale remains, and is not a fault of the bot's. As someone else noted, if the bot tags for 10c, it's frequently the case that the image has other serious problems. Thus, categories such as Category:Disputed non-free images as of 26 February 2008 are proper categorization. I'm open to suggestions on better categorization from MickMacNee.
 * Mick point 7: "i.e. newbie mistake, or previously compliant images, or images whose usage has changed, or as high risk cases of absentee uploaders, all of which are bot-detectable."
 * A: The bot doesn't discriminate based on newbie uploads or absentee uploaders because there is no provision in policy for there to be a special case for such images. We don't make special cases for newbies to get around policy, or for absent users either. If there was a special case in policy, ok, but there isn't. Again, this isn't the bot's fault. Go change the policy to permit liberal acceptance of fair use outside of our normal acceptability policy for new users and for absent users. Then the bot can do something about it. Until such time, this special case scenario is non-compliant with policy. As for images whose usage has change, that's impossible. The bot can only go with what status the image is currently in. If it was used in article A and was compliant but is now in article B only, it's non-compliant. The bot can't detect if it WAS used in article A, nor can it determine if it's usage in article B is acceptable or not, only if it complies with 10c. If the image description page doesn't mention article B, it's not compliant. That's been policy for 3.5 years.
 * There you have it. --Hammersoft (talk) 20:55, 26 February 2008 (UTC)


 * I've started taking longer and longer "breaks" recently. Very few have been at the suggestion of another user, so I doubt I'll "take a break" from the discussion at your suggestion either, Ed. I agree with EconGuy, though, that family and RL are first, so by all means, take care of your family before working on a resolution of these problems. God knows they'll still be here when you return! :) Bellwether B  C  20:28, 26 February 2008 (UTC)
 * I absolutely agree with both of you - but, boy, it's hard sometimes to tear yourself away, isn't it? In any case, my son and I are home, snacks have been prepared and all is right in the world. (Well...) Ed Fitzgerald (unfutz)  (talk / cont)  20:45, 26 February 2008 (UTC)


 * So, if I'm understanding Mick's post correctly, he's got three major areas of concern: -tagging is indiscriminate and unhelpful -control of the bot's use is lax and not centralized -categorization of non-compliant images is not specific enough Hammersoft has responded to Mick's concerns with specificity above, but if I can for a moemnt broadly generalize his point of view (and please correct me if I'm misrepresenting you): -the deadline has to be met -therefore images have to be tagged -and BetaCommandBot is the best (only?) tool available that can do the task in the time alloted. If this summary is a good approximation of the two viewpoints, it doesn't appear to me that they are necessarily irreconcilable - but then, the last programming I did was over 30 years ago in FORTRAN.... Ed Fitzgerald (unfutz)  (talk / cont)  21:10, 26 February 2008 (UTC)

Proposal: Release the code, or shut off the bot
There is no excuse in a free encyclopedia to have a secretive, closed-code bot causing deletion of multiple perfectly valid images that have been a part of the project for many years. I have much less of a problem with this bot if Betacommand would do two things: (1) Open up his code to community scrutiny. Failure to do so demonstrates a clear distrust of the community that is completely incompatible with this type of project. (2) Stop with the incivility toward complaints. Some are from new users, who simply don't understand the sub-section of a sub-section that BCB is using to tag for deletion. Some are from more established users overwhelmed by the massive talkpage spam geerated by the tagging of older images that they'd uploaded long before.

If these two conditions are met, I think the drama generated by BCBot's tagging would be minimized exponentially. Bellwether B  C  00:40, 26 February 2008 (UTC)
 * Another call to block. Yawn. --Hammersoft (talk) 00:59, 26 February 2008 (UTC)
 * If you have nothing to contribute, don't. I've seen your equally incivil comments on BC's talkpage. You're part of the problem, not the solution. Bellwether B  C  01:05, 26 February 2008 (UTC)
 * And for the record, I'm calling for the release of the code, and a change in BC's (and his supporters, such as your) demeanor. Bellwether B  C  01:07, 26 February 2008 (UTC)
 * And for the record, I find this umpteenth call to block the bot to be tedious, repetitive, and unlikely to yield anything positive. I'm sorry you disagree with my tone, but I'm calling a spade a spade and find no reason to not call it that. --Hammersoft (talk) 13:37, 26 February 2008 (UTC)
 * Your tone is "on the record" in many places, defending BCBot--no matter the issue, no matter the problems--often in BITE-y ways. Bellwether B  C  15:07, 26 February 2008 (UTC)
 * Factually incorrect, as I have specifically voiced disagreement with some of Betacommand's actions before. --Hammersoft (talk) 16:07, 26 February 2008 (UTC)


 * Please step away from the corpse. Seriously, you want code that can run at 35000 edits an hour opened up to all and sundry? Anyone who would be confident enough with such code to modify it should be able to write their own version of BCBot and have it approved. Black Kite 01:10, 26 February 2008 (UTC)
 * It's not a "dead horse." There are many people who feel that on a free project, code for such active bots should be open to criticism and improvement. Such secrecy, combined with the incivility present in the communications of BC and his supporters, does not improve this project. Bellwether B  C  01:14, 26 February 2008 (UTC)
 * Whilst BC is occasionally incivil, that aimed towards BC is many times worse. Try reading the archives of his talk pages sometime, or try enforcing WP:NFCC on articles. You'll soon get the idea. Seriously. Black Kite 01:16, 26 February 2008 (UTC)
 * I've heard this claim many times, but to date the evidence has been pretty thin. Can we have some diffs where BetaCommand receives abuse over and above that which is normal for an administrator doing CSD patrol?  I know he no longer has the bit, but the parrallel is obvious. - 152.91.9.144 (talk) 01:23, 26 February 2008 (UTC)
 * I still don't get the "The bot can do lots and lots of edits a minute and therefore shouldn't be made open source" argument. As I've found out above, normal editors can't make that many edits anyways, whether they program a bot to do it or not, and it's highly unlikely that an admin would suddenly start running the bot (without any kind of approval) once the source code would be out in the open. So.. I honestly don't see the harm if the code that can run at 35000 edits an hour is opened up to all and sundry. --Conti|✉ 02:18, 26 February 2008 (UTC)
 * Conti, I contacted some MediaWiki devs shortly after that was posted. there is no edit throttle on users. βcommand 02:21, 26 February 2008 (UTC)
 * Hmm, I stand corrected, then. Maybe the devs should think about that, tho, an editing limit for non-bots sounds quite reasonable to me. Anyhow, I still think it should be rather easy to program a bot that would do lots of edits, so if someone with enough malice would be around, he would've already programmed and used that bot. I doubt someone will suddenly turn up and use that bot to do any harm if the source code would be released. I therefore still don't really see this as a reason not to reveal the code to the community. --Conti|✉ 02:28, 26 February 2008 (UTC)
 * Look, the editing rate in a bot is a number in the code. There's no super-secret trick to making a bot edit 35,000 times per minute. Anyone can take a bot with open source code, like any of the Pywikipedia bots, and crank up its editing rate if they want. Then they'll get blocked. There is nothing magic about BCB's ability to edit quickly, so that is a pointless argument for why its code should be hidden.  r speer  / ɹəəds ɹ  06:23, 26 February 2008 (UTC)


 * For the love of all things: This is getting ridiculous. - Rjd0060 (talk) 01:13, 26 February 2008 (UTC)
 * Per WP:BOT he must inform us what framework/language he is using. Since the bot was approved as a Pywikipedia bot he either a) must answer my question above or b) request approval again. In addition to that, it is not possible for non-admins or non-bots to run it at that speed yet Betacommand now shows that he doesn't even trust OTRS let alone the admins. And we are suppopsed to respect the wishes of a user who acts like this? No thank you. He wasn't desysopped for nothing and he needs to either listen or leave. EconomicsGuy (talk) 01:19, 26 February 2008 (UTC)
 * I don't think that is your choice; to decide who has to leave because you deem them "not listening". He is listening, as obvious from his edits to this page.  It is no secret what the bot does, as it is approved for every function it serves. - Rjd0060 (talk) 01:42, 26 February 2008 (UTC)
 * Also, since this has been brought up a couple times, out of context. BC did not jab OTRS or any admins. What he said was that he doesn't trust OTRS to decide who is trustworthy to receive the code for the bot. His failure to trust all admins is completely legitimate. An example of why that distrust is justified was given by him: Archtransit. The community makes mistakes. BC wants to avoid this mistake from being made.  Lara  ❤  Love  02:53, 26 February 2008 (UTC)


 * He doesn't even need to release the code, just inform other editors in a sensibly located place, what it actually does, beyond the innacurate and mis-leading statement 'the bot enforces policy'. MickMacNee (talk) 01:22, 26 February 2008 (UTC)
 * let me restate myself for the 100th time  ALL BETACOMMANDBOT LOOKS FOR IS THE NAME OF THE ARTICLE OR A REDIRECT TO THAT PAGE. THAT IS REQUIRED BY WP:NFCC IT DOESNT NEED TO BE A WIKI LINK JUST THE NAME OF THE ARTICLE. IT DOES NOT NEED A TEMPLATE STYLE RATIONALE, IT DOES NOT NEED THE ARTICLE= PARAMETER ALL IT NEEDS IS TO MEET ONE BASIC PART OF OUR NON-FREE POLICY   βcommand 02:31, 26 February 2008 (UTC)
 * Betacommand basically just doesn't get it, he cleary thinks the above a sensible reply to the request; well, take this as yet another attack if you want, I know you will, but the above reply is just another example of what he thinks is being helpful or informative, blowing his stack on a talk page that will be archived and never seen again in a few weeks time, helping no-one who has to deal with his bot, or any third party who wants to save the mass-deletions his bot threatens. The sentence isn't even all that informative for the unninitiated who have not been following this whole sorry teeth-pulling epic, which is the real hoot, red bolded text or not. MickMacNee (talk) 12:49, 26 February 2008 (UTC)
 * MickMacNee, you asked what BCBot checks for, I used simple English to explain that. If you cannot understand English well Ill be happy to translate it into what ever language you do speak. If English is your native language, that means that you have not even bothered to read our non-free media policy. I am not sure how else I can say it any simpler. I made it big and red in hope that you might actualy read it, guess not, yet another example of where you ignore what I say, and attacking me. βcommand 15:17, 26 February 2008 (UTC)
 * What does providing the policy link have anything to do with giving a sensible reply to a request to state what the bot does? Unless you are saying everyone can deduce what it does from the policy, which is plainly not the case because the bot cannot read English as you point out, and hence cannot assess whether there is a separate fair-use rationale for each use of the item, presented in clear, plain language, and is relevant to each use, because as we all now by now bar some die-hards, for NFCC10c enforcement, the bot is just a link checker when all is said and done, barely even relevant to the spirit of the 10c statement. And again, you seem to think posting replies here is what I and others want, it is not, as stated repeatedly all over the place and in the original discussion page now obscured (although any communication is gladly received at this rate). What happens when this page gets archived and someone again asks here how the bot "enforces the policy" as is often stated, or someone reaches the bot page with the same issues I and others have had? Do you just carry on ignoring them, blowing your stack once in a while, because you can't see the basic logic in heading off enquiries at source? Seriously, why do you think it is not necessary to provide a stable link from the bot page to a toned down and informative, contextualised version of the red text above, with the quite important extra explanation of why the image description auto-page link(s) is/are not sufficient. — Preceding unsigned comment added by MickMacNee (talk • contribs) 03:23, 27 February 2008
 * A fair-use case for using non-free media must identify the article in which it is to appear. It follows that using the presence of the name of the article as a proxy for compliance is a useful automation step.  I suspect that this is more difficult for some people to understand than for others, and perhaps some rewording of the BetacommandBot FAQ might be in order. --Anticipation of a New Lover's Arrival, The 03:30, 27 February 2008 (UTC)
 * It is difficult to understand when there is a rationale stated in clear plain language "for the film Foo", but it's tagged because it is actually supposed to be for the article Foo (film), I have corrected two of those just today, dating from 2006. But that is by the by, the point being stated by me in the last sentence is the fact that there is a reason why the often quoted defence on BCBtalk and the copydesk that presence of the article links at the bottom of the image description page are not sufficient to meet NFCC10c and the usage needs to be stated in effect twice on the same page; the reason behind this was finally explained by betacomand somewhere, but like I say, as it was just a talk page reply it is now not easily findable again, and I had never seen it explained before, nor posted as alluded to above in a better place since. MickMacNee (talk) 04:02, 27 February 2008 (UTC)
 * Actually I did notice that you edited Image:House of Wax poster.JPG and Image:Hostage poster.JPG, but they don't seem to have any fair-use justifications at all, for any article, so I tagged them appropriately. Without the bot's work, these instances of inappropriately used non-free material would not have been spotted.  I don't think your edits, though well intended, helped. --Anticipation of a New Lover's Arrival, The 04:26, 27 February 2008 (UTC)
 * Actually you are both wrong. The correct approach is to upload a smaller size version and add a proper fur template with appropriate parameters. Both the size issue and lack of a proper fur template can be detected by a script. The size issue can be automatically fixed and fur templates inserted by an assisted script at fairly high speed. The only reason I'm not simply doing this myself is that the last guy who automated this had 5000 edits indiscriminately reverted. This isn't rocket science, we know what the problems are (size, decorative use and missing fur) and we know how to fix them. For images used in articles with standard infoboxes this can be done at high speed. For other images we can do this semi-automated at fairly high speed. All that is holding this back is the unwillingness to allow anyone else to do automated edits on image pages. I notice that one prominent member of BAG has a "Death to fair use" message on his user page. How are we suppopsed to work constructively on this when this is the attitude we are being met with? Folks, this a collaboration - not a one-man or one-group show. Let's work together. EconomicsGuy (talk) 07:27, 27 February 2008 (UTC)
 * I happen to be human and I could write a fair use case for an image of whose provenance I was aware, where I could convince myself that such a case could be argued (I know this because I've done it).  What you seem to be doing is confusing the planting of a template on an image page with the writing of a fair use justification.  The former could be done by a computer, but as talented a programmer as I know many of my fellow Wikipedians to be, I don't think any of them would be capable of writing a computer program, to run at reasonable speed in Wiki conditions, and synthesize fair use justifications for random images uploaded by wikipedians.  To take Image:House of Wax poster.JPG, how does this fit into the Foundation's policy?  We have a "minimal" exception, "to illustrate historically significant events, to include identifying protected works such as logos, or to complement (within narrow limits) articles about copyrighted contemporary works." How does this poster complement the work, and is it of such importance that it merits use?  Where, for instance, was this poster used?  Did its imagery become an important part of the distribution or illustrate the theme?  Who holds the copyright in the original picture?  How was the current copy obtained, and does it contain any intermediate transformative material? Who designed the poster again?  We cannot yet write programs to do this, at least not at reasonable speed, in wiki conditions. --Anticipation of a New Lover's Arrival, The 07:45, 27 February 2008 (UTC)
 * The copyright holder is obviously the studio - this can all be retrieved from the infobox on the page where it is used. I'm talking about semi-automated fixing of these. As for the template vs a rationale issue we do have fur templates that we prefer people use with appropriate parameters. Betacommandbot does not do any work related to the rationales. Itt merely looks for a back link. For all we know there are thousands of non-compliant images out there even after BetacommandBot is done. If you want to clean this up a fair speed you need to allow the use of automated tools to help with the trivial bits such as resizing, back links and retrival of relevant fur parameters from infoboxes. How many fair use rationales do you know of that don't simply use those already in the fur template? Look at Image:Talk_Show.jpg. How do you want such rationales individualized to each image? The rationale is the same for all of them and the info easily retrieved. EconomicsGuy (talk) 07:57, 27 February 2008 (UTC)
 * It may be possible for a human to deduce that the studio holds all copyrights in a poster (and usually he'd be right--but not always, see Dalek, for instance, for an example of a famous property whose image is not owned either by the programme maker or the distributor). A computer cannot make or defend such a deduction.  It is not even capable of checking that the image in question is at all related to the work it is supposed to illustrate.  Semi-automatic work won't do.  If we're going to use somebody else's work, we're going to have to do some work of our own. --Anticipation of a New Lover's Arrival, The 08:14, 27 February 2008 (UTC)
 * Why is it debates on Wikipedia always end up involving Doctor Who ;). More seriously though, suppose I write a plugin for AWB. You are presented with the page where the image is used and asked to confirm some simple facts retrieved from the infobox, alternatively correct the info. In addition to this the size is checked. This is easy to do. Like I said, semi-automated but still at fairly high speed in most cases. Sure, we aren't getting bot-like speeds but if enough people participate this would make the process more efficient. EconomicsGuy (talk) 08:25, 27 February 2008 (UTC)
 * Perhaps you would be interested in FurMe. It is a javascript implementation that does practically exactly what you are saying with the exception of image size checking (I would actually think that you could get a bot approved that reduced the size of images that were tagged with a certain template, which could be added by FurMe, so that could probably be automated). - AWeenieMan (talk) 16:45, 27 February 2008 (UTC)
 * Actually that looks like something we could get a fair number of additional folks to use. We really should give that a try, I'll check it out later tonight! EconomicsGuy (talk) 16:59, 27 February 2008 (UTC)
 * There's cognitive dissonance here: You won't release the super-skerit code, but that's all it does? Further, I think it's fairly clear that that's a hopelessly reductionist explanation.  you could almost as easily have said "It edits wikipedia." - 152.91.9.144 (talk) 03:15, 26 February 2008 (UTC)
 * without getting into complex programming speak that 90% of the people here will not understand, its what the bot does for dummies. also do not edit my comments. βcommand 03:42, 26 February 2008 (UTC)
 * Oh please enlighten us. What super super sekrit algorithm is used to analyze the very few words on the image description pages? Why can't you just admit that your bot is a simple script and nothing more than that? Why does it mean so much to you that everyone has to think you are some sort of programming genius for having written a freakin' Mediawiki bot? This secrecy and belief that you have some sort of super special powers is ridiculous. We are grown-ups here, not kids. At least describe in pseudo-code what your bot really does and per WP:BOT what framework/language you are using. That is not too much to ask if you want people to trust you given your history with scripts prior to losing your bit. EconomicsGuy (talk) 10:02, 26 February 2008 (UTC)
 * It's becoming increasingly clear that this is a pride thing. He feels like he's smarter than the rest of us, and the we couldn't possibly understand (or even be trusted with) the truth about his bot's code. I have been distinctly reminded of a certain Col. Jessep in the responses of BC and his supporters. YOU CAN'T HANDLE THE TRUTH!!!! Bellwether B  C  15:17, 26 February 2008 (UTC)
 * Yet another personal attack ^^ βcommand 15:22, 26 February 2008 (UTC)
 * You have a very liberal definition of what constitutes a "personal attack" toward you, while you maintain a near-constant state of incivility toward anyone who dares question your actions in regards to your bot. The above was my observation of how you and your supporters have behaved in response to simple requests for your bot to be open-source on a free project. Nothing more, nothing less. Bellwether B  C  15:49, 26 February 2008 (UTC)
 * Three times in one week oppose - They say that once you do something ten times it becomes a habit. We're on our way.  Lara  ❤  Love  02:58, 26 February 2008 (UTC)
 * Sorry, what exactly is it that you're opposing? (1) Open up his code? So far the only objection is that it's too fast for "normal" users. (2) Stop with the incivility?  You're for more incivility? Or are you objecting to the straw man argument raised by Hammersoft, what this is another threat to block.  In the same spirit of my asking several of the members of the "other camp" to step back, can I ask that you, LaraLove, take these pages off of your watchlist for a while?  I personally am not finding your input helpful.  It's growing increasingly repetative.  For example, in the above comment you've "voted" without providing much to go on. - 152.91.9.144 (talk) 03:15, 26 February 2008 (UTC)
 * Oh, let me clarify. This specific oppose is to the specific proposal of this specific thread. And yes, you can ask that I take these pages off my watchlist, but no, I'm not going to. I'm only repetitive because I'm responding to the same things over and over and over again. If people would read more comments on the page than their own, they wouldn't have to keep asking the same questions and I and BC and others wouldn't have to keep making the same, repetitive comments. I didn't elaborate on my oppose because I just opposed a similar proposal a few inches up, which followed another similar proposal from like two days ago, maybe... and I think there was one a day or so before that... and one last week. Maybe I'm wrong... but it's something like that.  Lara  ❤  Love  03:36, 26 February 2008 (UTC)


 * Comment If you want to have a policy that all bots are open source, then are ways for you to do that. Arbitarily deciding that one bot needs to be open source because you don't like it (or whatever) despite being unable to explicitly explain what the problem is however is not acceptable Nil Einne (talk) 10:29, 26 February 2008 (UTC)
 * The bot shouldn't be open source because it's disliked by people, it should be open source because, hopefully, this would reduce the drama by quite a bit.
 * People would stop asking what the bot does. And if they would, we could simply show them the code or tell them exactly what they want to know.
 * Wikipedians could improve the bot in many ways. (Hey, that's almost like this weird wiki thing, isn't it?)
 * The bot could, finally, be split up, so if one part messes up, we wouldn't have to block all other functions as well.
 * If the bot owner one day decides not to work on Wikipedia anymore, we wouldn't have to create a whole new bot for all these tasks.
 * Well, and it's kinda ironic that a bot that removes lots of non-free content is itself not free. But that's a minor point, of course. On the other hand, I see no reason whatsoever not to publish the code of the bot. --Conti|✉ 13:17, 26 February 2008 (UTC)


 * Quite simply, BetaCommand is under no obligation to release his code. He's already stated that he's not going to make it open source and he's not releasing it to anyone he doesn't explicitly trust. Calls to block the bot have failed repeatedly, several times in the past few days, so it's really a pointless issue to even discuss. By all means, please continue, as it's your right. I'm just pointing out how much of a complete waste of time it is to keep making the same requests over and over again.  Lara  ❤  Love  14:55, 26 February 2008 (UTC)
 * I, for one, am not trying to say "Release the code or be blocked!". Instead, "Releasing the code would be a really peachy thing to do, and there's really no reason not to, even though you are of course completely free not to do so anyways. Releasing the code would solve quite a number of problems, tho." is what I had in mind. --Conti|✉ 16:05, 26 February 2008 (UTC)
 * As a programmer, I can see why he is loathe to release his code to the public. I do, however, have faith in Betacommand's programming ability - I think it's other things that cause a lot of ire - for the very reason that it has tagged thousands of images correctly.  x42bn6 Talk Mess  16:31, 26 February 2008 (UTC)
 * I don't really see why he wouldn't want to release his code. But that's probably because I am not a programmer. Could you explain what reasons there might be not to release your own code to the public? --Conti|✉ 16:37, 26 February 2008 (UTC)
 * Somewhere in one of these huge discussions, Betacommand said that the last time he wrote useful code and released its source, somebody modified it to be disruptive code. I guess I can understand why he's not tremendously eager to do that again (especially nowadays, when so many people seem to be scrutinizing his every move).  For an exhaustive treatment of such issues, see here.    Xeriphas1994 (talk) 15:18, 27 February 2008 (UTC)
 * Not only that - imagine writing a book and then releasing it to the public domain. He may be using similar code in his other projects and he may not want the ideas copied.  Put short, it's his code and it may well be in his own interests not to release the code.  I don't feel he needs to release any algorithms or pseudocode either - personally, I think the bot does work that is quite easy to understand - go through a list of images, do some rule checking, and do stuff, then move on.  x42bn6 Talk Mess  21:47, 28 February 2008 (UTC)
 * That's the usual argument to keep code to yourself, yes. But this is Wikipedia. Wikipedians are supposed to support free content, right? --Conti|✉ 22:27, 28 February 2008 (UTC)
 * Free mainspace content, of course, but certain parts of the MediaWiki code are closed source for the same reasons. AFAICT the community's apprehension about "sorcerer's apprentice" bugs has created a sort of don't-ask-don't-tell attitude among many non-coding editors, especially w/r/t admin functions.  (This should obviously be taken with a mole of salt, since I've been reading the archived debates by subject area, not chronologically.)
 * This may be getting somewhat off topic because, even if a strong community mandate arose that all bots be open source, existing bots would probably be grandfathered for a while.   Xeriphas1994 (talk) 03:22, 29 February 2008 (UTC)
 * Thanks for the link, Xeriphas. I even !voted on that RFA, actually. I can see how the code of ProtectionBot might be used to vandalize, but I don't quite see that possible danger in BetacommandBot. I mean, I can kinda see Betacommand's point, but I still think the benefits greatly outweigh the possible drawbacks. --Conti|✉ 22:27, 28 February 2008 (UTC)
 * Conti, for those who need to need to see the code its open to them. Due to the nature of the language that I program, I dont have excitable(.exe) files My end user files are pure source code. I write my programs to get the job done I dont have safety features that a lot of other people build into their code. For those that I trust getting viewing access to my code is not an issue, (lar just got a copy). AGF does apply to wikipedia, however it does not apply to programming. My philosophic view is never assume any thing, verify facts, and prove your theorem before making a judgment. Until you prove your theorem of you being trustworthy, I dont trust you with the tools. (similar to being an admin) βcommand 02:24, 29 February 2008 (UTC)
 * Thanks for letting Lar see the code, Betacommand. I hope we have you with us for a good, long time, but it's good to know that if ever you were unable to continue devoting so much of your time to this excellent, valuable and necessary work, it would be possible for a suitably knowledgeable coder to continue maintaining and running the bot. --Anticipation of a New Lover's Arrival, The 14:04, 29 February 2008 (UTC)
 * Just want to second what Tony just said. Also, I did actually manage to get a bot to edit at extremely high speed on a test server. *Cough*multithreading*cough*. There's nothing wrong with having a bot that gets the job done with the simplest possible code so just want to apologize to Betacommand, especially per Tony's very well-worded comments on my talk page. That said, what is the general mood about getting the remaining images checked for other non-compliance issues like images not being sufficiently low resolution? EconomicsGuy (talk) 14:24, 29 February 2008 (UTC)


 * Personally, I would have no problem with a bot going through and fixing obvious cases of non-free use images that are of high resolution (album covers sounds like a good place to start to me). A few things to keep in mind though: 1) image size may not be the only factor to consider, as a higher resolution jpeg with high compression settings might not really need to be resized, for example; 2) I am sure there are cases where people give good rationales for having higher resolution images (perhaps they are discussing in specific one detail of the image); and 3) what is the maximum allowable resolution of a non-free image (or what should the standard be). Some non-free use templates set this mark at 300px x 300px (and completely ignore any other factors), but I never found a compelling consensus for this number.


 * I would think that having images tagged by human as being too large and fixed by bot would probably go over best. Perhaps you could get your bot to produce a list of images it would want to alter for review by humans. Or semi-automate it to review changes. Or perhaps there is a way to have the bot be smart enough to ignore high resolution images that are high rsolution for a reason.


 * I guess my question would be, how automated would you want your bot to be? - AWeenieMan (talk) 19:18, 29 February 2008 (UTC)
 * about the most a bot can do reliably without much error is list images over a certain dimension. other than that the risk of error becomes too great. βcommand 19:36, 29 February 2008 (UTC)

On image size, I would say that we discuss what is reasonable for most purposes. At nominal compression, JFIF (JPEG) files of around 20kb maximum combine fast download and optimal caching with good display characteristics. I've obtained excellent results from files as small as 3kb. Free images may be much larger, it doesn't matter because the Mediawiki software chooses a suitable conversion for the download context. But it may sometimes happen that a larger non-free image is justified (I can't think of such a circumstance off-hand, but there might be such). This is a matter for the image upload guidelines. --Anticipation of a New Lover's Arrival, The 19:39, 29 February 2008 (UTC)


 * First of all the bot I wrote should not be editing Wikipedia as I wrote it from scratch only to see how fast I could edit on a test wiki on a spare machine (yes I have no life - this is what I do for laughs). Far too unsafe for Wikipedia editing. Pywikipedia seems like the way to go (far safer) and I could have that working fairly soon. Is this issue covered by the deadline? In response to Betacommand I would think that the resizing was the most reliable task for the bot as the tagging would need to be done at least semi-automated to catch false positives as AWeenieMan describes. I'm open to ideas or a non-negotiable no before I spend too much time on the code. EconomicsGuy (talk) 19:51, 29 February 2008 (UTC)

Entirely serious question
Since BetaCommand felt free to write, and is allowed to run, a bot that flagged images for deletion under "NFCC 10 c"... would I be allowed to write and run a bot to revert its flaggings, under "Assume Good Faith"? Both are policy... I would definitely like some serious replies to this, thanks! --75.5.176.16 (talk) 07:11, 26 February 2008 (UTC)
 * you would need to file Bot Request for Approval and any such bot would not be approved. βcommand 15:27, 26 February 2008 (UTC)
 * But it would be my goal to improve and have a better-maintained Wikipedia to have such a bot, and the "Ignore all rules" policy seems to DIRECTLY support me, and in fact to go ahead with the bot despite a lack of approval. --75.5.176.16 (talk) 02:38, 27 February 2008 (UTC)
 * The problem with invoking "ignore all rules" to justify such actions is that we have about 1000 admins, one of whom might just "ignore all rules" and block you. Ignore all rules is not a tool to be trifled with. --Anticipation of a New Lover's Arrival, The 02:53, 27 February 2008 (UTC)
 * I wouldn't recommend that you try this. --Anticipation of a New Lover's Arrival, The 07:16, 26 February 2008 (UTC)
 * Well, a bit of an addition: If revertings would be 'too extreme', what about removing the deletion-flaggings and replacing them with user-or-article talk page notifications? Assuming good faith, a notification of some sort whould be a much more friendly and useful solution to images without a rationale.  I don't see the use in the rampant deletion of images via a time-delay that users may not have time to respond to, or even understand.  --75.5.176.16 (talk) 07:11, 26 February 2008 (UTC)
 * The procedure for speedying was, I seem to recall, agreed months ago. If you now have a proposal for changing it, it wouldn't be a specific Betacommand matter but a matter of policy, so you should discuss your proposal there. --Anticipation of a New Lover's Arrival, The 07:25, 26 February 2008 (UTC)
 * I'm not too familiar with the back-end of Wikipedia (yet)... would you be able to point me to a proper area to ask about such a policy question/proposal? Thanks --75.5.176.16 (talk) 07:31, 26 February 2008 (UTC)
 * I believe the procedure is outlined in Non-free_content and the deletion criteria at Criteria_for_speedy_deletion. If you want to change the former I think you would therefore discuss your proposal on Wikipedia talk:Non-free content. --Anticipation of a New Lover's Arrival, The 07:43, 26 February 2008 (UTC)
 * Thank you. --75.5.176.16 (talk) 02:30, 27 February 2008 (UTC)


 * You don't seem to understand 'assume good faith'. No one is saying that the people who uploaded the images are trying to harm wikipedia. They are probably trying to improve wikipedia. I.E. No one is assuming that these images weren't uploaded in good faith. However they have also in most cases failed to comply with NFCC policy which we consider serious enough that it needs to be fixed ASAP or the images deleted. Nil Einne (talk) 10:06, 26 February 2008 (UTC)

Entirely serious answer: You are unregistered and have four edits, the first of which for a very odd comment on Beta's talk page and the other three to this page. So I'm going to go with the wild guess of "no" on this one. Now, from that odd comment and your comments here, it's obvious you're not a new user, so what account do you normally edit under?  Lara  ❤  Love  14:35, 26 February 2008 (UTC)
 * I have no account, mainly because of crap like BCB. Finally got annoyed by it enough to (maybe) pursue something.  Also, why did you focus on my registration or lack thereof?  Does that make my opinions or questions less valid?  --75.5.176.16 (talk) 02:30, 27 February 2008 (UTC)

And another serious answer; policies don't work in conflict with each other. They work in harmony. Using one policy to undermine another policy isn't going to be supported. They work together, not apart. --Hammersoft (talk) 20:27, 26 February 2008 (UTC)
 * It seems pretty obvious to me that they do not. (Ref: any discussion on BCB.) --75.5.176.16 (talk) 02:30, 27 February 2008 (UTC)

None of this is helping anything. Why is anybody responding to this? If it's a legit threat, it won't last, and if it's not, you're just fanning the flames. &mdash;Torc.  ( Talk. ) 03:30, 27 February 2008 (UTC)
 * How do you figure this to be a threat? I see something I dislike about Wikipedia and am fed up enough to do something about it.  It might seem hostile to some eyes, and not to others, but it is not a threat, just something I am looking into at the moment. --75.5.176.16 (talk) 02:09, 28 February 2008 (UTC)

Outsider's perspective
I hesitate to dip my toe into such murky waters, but here is an outsider's perspective: My suggestion would be that we assemble a short FAQ that explains why BetacommandBot tags images, and outlines a workflow for fixing them. Betacommand can then link to this page in the bot's messages, and at the top of his talk page. Bovlb (talk) 21:18, 26 February 2008 (UTC)
 * BetacommandBot is performing a valuable service to the community by helping us work towards our non-negotiable deadline.
 * People who work on copyright violations certainly come in for a lot of flack.
 * All Wikipedia editors have a responsibility to remain civil, notwithstanding provocation.
 * Bot operators have a responsibility to be responsive to questions and suggestions about their bot's behaviour.
 * The notice at the top of User talk:Betacommand is definitely uncivil, especially the point about "whine and complain".
 * The message left by BetacommandBot (example) could be more friendly, but I'm not seeing any concrete suggestions here for how to fix it.
 * The periods of 48 hours for new uploads and 7 days for old uploads do seem a little short, and could usefully be lengthened, say to 7 days and 21 days.
 * Image copyright help desk/BCBFaq. --Hammersoft (talk) 21:21, 26 February 2008 (UTC)
 * That's excellent, and exactly what I was after. The question remains: Why am I not tripping over links to it everywhere?  Why it it not in the message that BCB leaves?  Why isn't in the box at the top of BC's talk page?  I have added it to Media copyright questions. Bovlb (talk) 01:09, 27 February 2008 (UTC)
 * Image copyright help desk/BCBFaq says to use, but the latter has no documentation or discussion, and a warning that essentially says "Don't use this". Guidance, please?  —johndburger 15:46, 27 February 2008 (UTC)
 * Please see the TfD. It should not be used. The right hand doesn't know what the left hand is doing anymore. Assuming good faith per the sensible editor just below. EconomicsGuy (talk) 16:44, 27 February 2008 (UTC)


 * I would say this was a simple typo. I have changed it to recommend using . - AWeenieMan (talk) 16:52, 27 February 2008 (UTC)
 * Ah, got it, thanks. I added a pointer on the talk page for any future head-scratchers.  —johndburger 16:57, 27 February 2008 (UTC)

I have asked the user to make his talk page notice more friendly, and to link to the FAQ, but from his response he does not seem inclined to do either. Bovlb (talk) 07:05, 1 March 2008 (UTC)
 * We shouldn't be surprised by this at all. Bellwether B  C  03:47, 3 March 2008 (UTC)

Moving forward

 * Looking at the conversation in above - MickMacNee's concerns, Hammersoft's response, and my summary - I have a few questions which I hope someone can answer, not only about the desireability of doing these things, but also the practicality of doing so (which I presume willl have to be answered by Betacommand):


 * If suggestions can be generated for improving the interface with the user, i.e. the messages left by the bot, can these be easily implemented? If so, what specific changes would be suggested to be made to help the typical user be less confused about what they need to do?


 * If some consensus can be reached about a better categorization scheme which would increase the chances of images not being lost at the deadline, can this be implemented?


 * If it is important that the bot run on a more consistent schedule, to minimize its impact, is there someone Betacommand would trust to run the bot at those times that Betacommand is not available, under Betacommand's direction, of course?


 * Let's start with those questions, which I hope are not totally naive. Ed Fitzgerald (unfutz)  (talk / cont)  21:25, 26 February 2008 (UTC)


 * Point 1: Maybe I've missed it, but the bot haters haven't come up with suggested changes that I know of that have not already been implemented.
 * Point 2: Probably. But, that has nothing to do with the bot really. It has to do with where Template:Dfu places images, as it is responsible for the categorization, not the bot.
 * Point 3: I can't respond, but past responses from Beta indicate (1) no, and (2) the initial tagging runs are all done, so there's not much point to this, nor is there much point in re-writing the bot from scratch as the work's been done. Now, it's just routine scans for new non-compliant images, and an additional phase that Beta's not coded to remove non-compliant images from articles (I'd guess this would run after the March deadline). --Hammersoft (talk) 21:31, 26 February 2008 (UTC)
 * Hammersoft: Thanks for the response. One caveat, though, since it's possible that everyone's taken a deep breath at this point, it would probably be best to keep things level and avoid using pejoratives whenever possible, so the discussion can continue at a lower decibel level. About point 1, I guess the import of my question was if changes were suggested and agreed to, could they be implemented?  Thanks. Ed Fitzgerald (unfutz)  (talk / cont)  21:40, 26 February 2008 (UTC)
 * Ok, redoing:
 * Point 1: If something was suggested that was reasonable and accurate, probably. Beta's been amenable to such changes before.
 * Point 2: Sure. Anyone can update the template. It's not a bot function. The bot just uses that template.
 * Point 3: Moot point. Work's done, and now routine scans are all that will happen.
 * Better? --Hammersoft (talk) 21:43, 26 February 2008 (UTC)
 * Indeed - thanks. Ed Fitzgerald (unfutz)  (talk / cont)  22:06, 26 February 2008 (UTC)

Good suggestions, I think I touched on a few of them above in My Thoughts. As the deadline is approaching, how about just giving everyone until then to fix them. That is not a viable longterm solution, but as we are within a month of them all being gone, I don't see a problem with that time table. Also, I believe that BCbot should use a different template than a human user would for tagging 10.c violations, as they operate in a fundamentally different way. And finally, yes the scan schedule seems to be a moot point but perhaps we can learn from that in the future. Random89 (talk) 08:24, 27 February 2008 (UTC)


 * I wonder about the notion that the bot's irregular schedule causes any serious "impact". Carcharoth's page on compliance seems to suggest strongly that this and other bots have little or no impact on overall deletion rates.  It's just a small, though necessary, part of the work Wikipedia does that results in image pages being improved to the point of compliance or deleted. --Anticipation of a New Lover's Arrival, The 14:08, 29 February 2008 (UTC)
 * I am not a "bot hater", but in the section above, I made two concrete suggestions: that the bot's talk page be more civil; and that the bot's messages and talk page link to the bot's FAQ. Bovlb (talk) 17:54, 3 March 2008 (UTC)

Categories
I've just blocked because it looks like it's doing an unapproved task. It's approved to do CfD work and remove red linked cats after a discussion. What it's actually doing is removing all red linked cats, even those which have simply never been created. This has included removing them in userspace, where users have specifically wanted them to be red linked. I don't believe there is any consensus to remove all red link cats from all pages, and BrownHairedGirl made a very good point on Betacommands talk page saying that a lot of the cats are red linked because of small typos - this is easier to spot if the cat is red linked on the page rather than completely removed.  Ry an P os tl et hw ai te  18:03, 4 March 2008 (UTC)


 * Is there any reason not to permanently removal whatever approval Beta has to run any bots for any reason? He's unable to respond meaningfully to concerns about bot behavior, and they do seem to come up a lot.  Perhaps he could find a way to help some other, more responsible, bot owner, short of running one himself?  Friday (talk) 18:07, 4 March 2008 (UTC)
 * Ryan Postlethwaite please note that I stopped the bot over 10 minutes ago, shortly after your post to my talkpage. βcommand 18:09, 4 March 2008 (UTC)
 * I do appologise, it was still functioning a few mintues after I posted to your talk, and in the time I went to block, you must have stopped it.  Ry an P os tl et hw ai te  18:11, 4 March 2008 (UTC)
 * you posted at 17:52 the last edit by the bot was 17:56, and your block was 17:58 βcommand 18:13, 4 March 2008 (UTC)
 * Yup, exactly what I said - you must have stopped it in the time I went to block.  Ry an P os tl et hw ai te  18:15, 4 March 2008 (UTC)
 * Ryan I just considered this category house keeping part of the CfD work. Ive been removing redlink cats for a while. prior to this there have not been any issues. What I have seen from prior runs is that pages often get improper categories removed. and ones with typographical errors get fixed. in general a lot of good comes from these runs. βcommand 18:50, 4 March 2008 (UTC)


 * I am somewhat worried over Betacommand's operation of this bot, this is the second time in a month that it has been known to run a unapproved task, remember making a few thousands of null edits in a sub page to prevent deletion on the main page? -  Ca ri bb e a  n ~ H. Q.  18:14, 4 March 2008 (UTC)
 * Indeed, there was a two minute gap between the stop of the bot and the block, which is not an unreasonable amount of time to elapse. Had you stoped your bot before you replied to the concerns on your talkpage and invited discussion about the subject rather than carrying on, it would have never been blocked at all.  &#10154; Hi DrNick ! 18:18, 4 March 2008 (UTC)


 * (ec) It looks more to me as if it were running an approved task in a manner indicative of programmer error (setting which redlinks to remove), not necessarily anything nefarious. I also note that Betacommand had stopped the bot prior to the block - a four minute response time, quite impressive in any context, and certainly not indicative of an unresponsive bot operator. I'm inclined to tag this as Resolved, since it is unclear what further admin action is necessary. I presume the bot has been unblocked? UltraExactZZ Claims~ Evidence 18:22, 4 March 2008 (UTC)
 * Obviously the bot isn't unblocked yet, given there's no assurances that the bot is fixed and won't continue to do this task. I actually don't think this was a bug - Betacommand seemed to think this came under the scope of "CfD" work which it clearly didn't.  Ry an P os tl et hw ai te  18:26, 4 March 2008 (UTC)


 * Not unblocked yet. And the response time wasn't 4 minutes. BHG posted about this at 14:48 (others may have posted earlier), edits resumed at 16:56, block took place at 17:58. In total, BetacommandBot has made over 2000 edits removing categories since 00:32. Why did Betacommand resume using the bot even after BHG had raised her concerns? I'm also concerned that BetacommandBot got approval to do category work in the first place. Category work is tricky and not at all easy to undo if a bot goes wrong. I'm hoping there won't be future problems, but this is the second time I've seen Betacommand get something basic wrong in category work. The first was a (non-bot) attempt to fully populate high-level categories without much discussion that I could see. This failure to distinguish between deleted categories and red-linked categories is another. And I thought Cydebot did this sort of thing anyway (and better as well)? If it had any chance of succeeding, I'd urge WP:BAG to withdraw approval for this bot to carry out any category work until more extensive testing and discussion, and well, some demonstration that Betacommand actually understands how categories work, but getting bot approval withdrawn, even in a specific case like this, is actually rather difficult. Carcharoth (talk) 18:45, 4 March 2008 (UTC)


 * I think BC's attitude towards criticism is unhelpful. There is absolutely no justification for describing the removal of a category that has never had a CfD as "CfD work". None. —Random832 18:18, 4 March 2008 (UTC)
 * I think BC probably did that in good faith, since he was delinking the category, removing the other non existent categories sorta makes sense, database-load wise (I was not aware that red cats were asked for). -- lucasbfr  talk 18:26, 4 March 2008 (UTC)


 * Re blocking a bot for running an unapproved task - just based on the policy, only completely new tasks require explicit approval. In the case of completely new tasks, it requires the approval of a member of BAG. This isn't a completely new task (as you say, BCBot does similar work already) and Betacommand is a member of BAG (currently, with Voice-Of-All, the member with the earliest join date). Blocking him a few minutes after leaving a note is sort of an assumption that he will refuse to discuss it, or change the operation of the bot. Given past experience, this doesn't seem like something that should be assumed. The bot should be unblocked, and input should be sought from another member of BAG. Avruch  T 18:47, 4 March 2008 (UTC)
 * Well, this was a completely new task - he was removing all red linked cats, not ones that have been deleted through CfD like his approval states. There is no consensus to remove all red linked cats, so he shouldn't be performing the task. Other people left notes earlier with no response - I gave him one final opportunity before I blocked soon after myself. He was continuing to use his bot at first dispite my warning. I see no reason to unblock the bot until BC makes it clear he will stop the task.  Ry an P os tl et hw ai te  18:53, 4 March 2008 (UTC)


 * I'm fairly disturbed that BCB seems to come up here on a regular basis. After a lengthy discussion about the last episode on-wiki (tagging thousands of images for deletion), more discussion followed on en-wiki-l and it doesn't really seem that apparent that BC is understanding some of the core issues the community has here. What I see instead is some kind of repeated justification for doing things that were never specifically approved by the community. Does there come a time, when we've had enough, that's the question. Wjhonson (talk) 18:54, 4 March 2008 (UTC)


 * As a positive-action follow-up, I'd like to recommend that any changes to BCB code should go through an approval process by an unaffiliated set of eyes. That is, the code itself should be reviewed, not merely the textual explanation of what it does. Wjhonson (talk) 18:57, 4 March 2008 (UTC)


 * The WikiEn-l discussion is mostly irrelevant to on-wiki issues, IMHO, but even if not it should be stated that the thread was mostly you arguing your point against everyone else who disagreed with you. Not exactly proof of consensus for your position. Avruch  T 19:13, 4 March 2008 (UTC)


 * Then you weren't paying close attention. Many posters agreed that the situation was not acceptable.  And the discussion of wiki related material is never irrelevant.  That's why we have the en-wiki-l list.  I wasn not trying to prove consensus by my remark, only pointing out that there is a significant amount of discord over the actions of this bot. Wjhonson (talk) 23:45, 4 March 2008 (UTC)

I'll post here what I posted on BetacommandBot's talk page: This bot needs to follow nobots and bots per Template:Bots. I've about had enough of this bot removing things and when I revert, it coming back to do it again. And what about this bot edit where it removed one cat but said in the edit summary it removed another? Betacommand replied to me on BetacommandBot's talk page that he "doesn't have to follow" nobots/bots. Agreed, you don't "have to", but you should. All bots should - it should be a requirement for having a bot. If Category:Rouge admins still existed, I'd put this bot in it and add nobots to its own userpage! - &#10032; ALLSTAR &#10032; echo 19:04, 4 March 2008 (UTC)
 * Funny you should say "If...still existed" and have it show as a blue link. I agree that he should follow the bot/nobot template in userspace in most cases. Avruch <strong style="color:#000;background:#fff;border:0px solid #000"> T 19:15, 4 March 2008 (UTC)
 * Yeah, well, as you noted below, it's since been restored. lol - <font size="+1" color="red">&#10032; <strong style="letter-spacing:1px;font-family:Verdana">ALLSTAR <font size="+1" color="red">&#10032; echo 19:36, 4 March 2008 (UTC)


 * Comment - This campaign has been very damaging to our users' navigation. Many, if not most of the cats removed were simple misspellings of actual cats that do certainly exist. These misspelled cats that were blanked should have been replaced with the properly spelled ones, by hand.

Examples of such poor editing include this edit and this edit.

The editor needs to go back and do that. If s/he does not, I recommend a "forever" block and complete dissolution of this bot, which has shown such disruption so many times in the past. Badagnani (talk) 19:38, 4 March 2008 (UTC)

User:BetacommandBot is removing misspelled (and thus redlinked) categories from thousands of articles, always without taking the few moments it would take to substitute the properly spelled category--thus often leaving the article without a proper category. This is very wrong and needs to be stopped. The redlink will be noticed eventually and experts in the particular subject of the article will substitute the proper cat. But removing the cat entirely without substituting the proper cat hampers navigation for all of our users. Please have this person go back and do this by hand, as should have been done in the first place. Badagnani (talk) 19:35, 4 March 2008 (UTC)

Examples include this edit and this edit. Badagnani (talk) 19:35, 4 March 2008 (UTC)


 * This is already under discussion, see Administrators%27_noticeboard/Incidents. Friday (talk) 19:37, 4 March 2008 (UTC)

I'd like some attention to this. Will the damage be undone? If so, when, and by whom? Badagnani (talk) 19:39, 4 March 2008 (UTC)
 * While it is true that Betacommand could do that, a bot cannot. One only has to see the difficulties related in spell-checking and related words to know that a bot cannot do all things a human finds obvious.  x42bn6 Talk Mess  19:44, 4 March 2008 (UTC)

I (as well as the rest of the community) would like to see some attention to this. I do not care if it will be difficult to do by hand. The bot is operated by a real person, and that real person should edit articles in a thoughtful manner, not "blanking and running." Misspelled/redlinked categories need to be replaced with properly spelled ones. Attention to this would be greatly appreciated, more than excuses for the individual who operated his/her bot in such a damaging way. Will this damage be undone? If so, when, and by whom? Badagnani (talk) 19:49, 4 March 2008 (UTC)


 * Please exclude me specifically from this "the rest of the community" you claim to be speaking for. Thanks! ➨ REDVEЯS dreamt about you last night 19:51, 4 March 2008 (UTC)


 * I would like to go on record as stating that I _agree_ that there are some tasks that nobots does not and should not affect. BC's image tagging task even has two separate components: tagging images ignores nobots, but warning users (at least, IIRC) respects it. Of all the problems that BCBot has had, I don't think this is one of them. —Random832 19:54, 4 March 2008 (UTC)

Will this damage be undone? If so, when, and by whom? Clearly, User:Redvers has not actually examined the edits made by the bot, such as this edit and this edit, as well as a thousand others, which are clearly damaging to our project. Badagnani (talk) 20:12, 4 March 2008 (UTC)


 * Breathtaking, and wrong, assumption. I don't see a problem with losing unprofessional redlinked categories with misspellings in them, and I wish to be excluded specifically from when you are speaking for "the rest of the community". But assumptions beyond that are assumptions. Please refrain from making them. ➨ REDVEЯS dreamt about you last night 20:16, 4 March 2008 (UTC)
 * Agree with Redvers, on the cats, and, "the rest of the community" doesn't include me either. Please, speak for yourself. SQL <sup style="font-size: 5pt;color:#999">Query me!  20:24, 4 March 2008 (UTC)

Uncivility is un-Wikipedian and should be avoided. Please avoid it. Regarding the bot's edits, the damage needs to be undone. A "professional" bot operator would have used the bot to identify redlinked (misspelled) categories, and replaced them with properly spelled ones. What the bot actually did was highly damaging and the damage needs to be undone. Please do not attempt to hinder this, for whatever reason you are doing so. Badagnani (talk) 20:20, 4 March 2008 (UTC)
 * WP:SOFIXIT. <strong style="color:#000;background:#fff;border:0px solid #000">Avruch <strong style="color:#000;background:#fff;border:0px solid #000"> T 20:38, 4 March 2008 (UTC)

Will this damage be undone? If so, when, and by whom? I am very familiar with bot misbehavior, which nearly always goes along with admin inattention, with the end product always being the user noticing the damage (rather than the one who did the damage, who always claims they were "just doing their job" and "it would be too hard" to fix it) being the one asked to undo it. It's time to break this cycle. Let's have some attention to this. Badagnani (talk) 20:41, 4 March 2008 (UTC)


 * Since simply not agreeing with you is "uncivil", it's hard to reply. Nevertheless: sofixit ➨ REDVEЯS dreamt about you last night 21:25, 4 March 2008 (UTC)

I provided diffs showing that the bot's behavior was improper and damaging to our project. I'm quite familiar with the policy of asking editors who notice bot damage to undo such massive damage (in this case amounting to literally thousands of blanked categories, for which the spelling should simply have been fixed. Such a request is wrong and it is time to break this cycle. Let's have some attention to this. Will this damage be undone? If so, when, and by whom? Badagnani (talk) 21:28, 4 March 2008 (UTC)


 * Badagnani, I see no incivility towards you here. Also, just as a piece of advice re: interacting in this forum: repeating the same questions, concerns, or information in reply to several different comments generally casts a less-than-ideal light on your ideas...in short, it makes you look argumentative, which I'm sure is not your intention. Just a thought. Gladys J Cortez 21:29, 4 March 2008 (UTC)


 * Comment - I am also very familiar with comments on the comments made by editors pointing out bot damage rather than actually seeing to it that such damage is repaired, and the bot operator censured. Let's break this cycle. I didn't see that you addressed my actual comment. Badagnani (talk) 21:33, 4 March 2008 (UTC)


 * Will this damage be undone? It's not damage, per se. If so, when, and by whom? As soon as you like, by you. I can only put this so many ways: if you want to add redlinked and misspelled categories to articles, then you should do so yourself. There is unlikely to be a queue forming to do it for you. sofixit ➨ REDVEЯS dreamt about you last night 21:36, 4 March 2008 (UTC)


 * Comment - I'm very familiar with the editor noticing bot damage (who usually does not have a bot at his/her disposal--and is just a highly productive contributor to our project) being the one asked to repair bot damage, often numbering thousands of damaged pages. I have provided diffs and the pages certainly are damaged, if the properly spelled cat was not substituted, as they should have been. It's time to break this cycle. Attention to this damage, and repair thereof, is needed. Badagnani (talk) 21:39, 4 March 2008 (UTC)


 * sofixit ➨ REDVEЯS dreamt about you last night 21:47, 4 March 2008 (UTC)


 * Comment - I think I see what the problem is--the three editors above who seem to be defending the bot operator don't seem to have actually examined the diffs, which are typical of many hundreds of the thousands of articles damaged by the bot (in that slightly misspelled cats were blanked rather than repaired). In this edit, the redlinked/misspelled cat "Beijing Cuisine" was blanked, and in this edit the redlinked/misspelled cat "Botswana people" was blanked. In both cases, one letter would have fixed it. The articles were left without cats and, without the redlinked cat to alert editors in each subject area that the cats needed to be fixed, now they're simply not there, hampering navigation for all our users. This was an improper use of a bot and needs to be fixed. Simply defending the bot operator (perhaps because the other editors are also bot editors and strongly wish that such a precedent not be set, that bot operators who make mistakes actually have to go back and fix their own mistakes, by hand, as the rest of WP editors do), and asking the non-bot-operating editor who noticed the damage to do to, serves to support such damaging actions in the future, with no accountability for such widespread and huge damage to our project. This is a cycle that needs to be broken. Let's see to it that this fixed--and that we don't shift the onus from the actual editor who caused the damage in the first place (in this case, an editor who has achieved widespread notoriety for such damage). Badagnani (talk) 21:50, 4 March 2008 (UTC)
 * That's the second time you've made the breathtaking assumption that I'm commenting without reviewing the evidence, and the second time you've been startlingly wrong. As you say: "one letter would have fixed it" - go on then: fix it. Nobody is going to re-add misspelled, redlinked categories to articles. A bot cannot add them with the correct spelling - bots cannot spell. If this is as big a problem as you believe it to be, you are going to have to fix it. sofixit ➨ REDVEЯS dreamt about you last night 21:57, 4 March 2008 (UTC)

This bot is worse than Britney Spears or Michael Jackson about always being in the public eye. - Philippe &#124; Talk 22:00, 4 March 2008 (UTC)


 * Comment - A bot may be used to identify improperly spelled categories, then the correct ones may be located and added. This is now impossible, as the cats were blanked entirely. This was improper. The fact that this damage was done to thousands of articles makes it improper to ask the editor noticing the damage to repair it, rather than the bot operator who did the damage--and also encourages the bot operator to keep doing such damage in the future. I'm very familiar with the onus being placed on the editor noticing the damage, shifted away from the actual bot operator who did the damage. This is a cycle that needs to be broken. Let's have some attention to this and the damage corrected. See Ryan Postlethwaite's first comment above, which says "BrownHairedGirl made a very good point on Betacommands talk page saying that a lot of the cats are red linked because of small typos - this is easier to spot if the cat is red linked on the page rather than completely removed." Badagnani (talk) 22:04, 4 March 2008 (UTC)
 * It is unlikely that any bot or program can guarantee a correct decision especially regarding spell-checking. It is difficult enough for a bot to realise that "Micheal Jackson albums" [sic] is really "Michael Jackson albums" or that "Michael Jackson Albums" is "Michael Jackson albums".  To me there is no real issue with redlinked categories being removed although HTML commenting would possibly be better but I do not feel there is any lasting damage especially as one has the history tab.  x42bn6 Talk Mess  22:11, 4 March 2008 (UTC)


 * (ec)Then write a bot or request someone with bot-making experience makes you one. Nobody is going to re-add misspelled, redlinked categories to articles so they can be fixed later. We are better off without them. If you want, go through the bot's contribs and make any changes you want yourself. But there will be no wholesale return of misspelled, redlinked categories, there is no way a bot can add categories with the correct spelling, and there is no point continually arguing for these things or playing the martyr on this noticeboard. ➨ REDVEЯS dreamt about you last night 22:12, 4 March 2008 (UTC)

Arbitrary section break

 * Comment - The damage is extensive and makes navigation impossible for thousands of articles. Please read the first comments in this thread, and also the comments at Betacommand's page for more background on this issue. The two diffs presented above show that this massive blanking has damaged thousands of articles, by leaving them with no cats. A bot may certainly be used to identify redlinked cats, then the properly spelled cats can be put in. It simply takes care. In this case, from Betacommand's responses, s/he simply didn't care to take care. Supporting his/her actions is improper in light of this massive damage, and encourages future damaging campaigns of this nature on his/her behalf. We must be reasonable, and asking the editor who noticed the damage, who does not operate a bot (as has happened many times in the past) is improper. It is time to break this cycle, and to finally ask that the bot operator who perpetrated this damage to our project correct him/herself. Badagnani (talk) 22:18, 4 March 2008 (UTC)
 * Redlinked categories mean that navigation is impossible in the first place. Redlinked categories are no more damaging than having no such redlink category on an article.  BetacommandBot acted in good faith although it would have possibly been better to think of other solutions but I still do not see the point of continuously attacking Betacommand.  x42bn6 Talk Mess  22:22, 4 March 2008 (UTC)


 * (ec)There's no communicating with you, is there? This is the third time you've made the breathtaking assumption I've not looked at the evidence before commenting, and the third time you've been wrong. ➨ REDVEЯS dreamt about you last night 22:22, 4 March 2008 (UTC)


 * I don't understand how the removal of a redlinked category makes navigation impossible. Badgnani, could you explain what you mean by that?  - Philippe &#124; Talk 22:26, 4 March 2008 (UTC)


 * Comment - Please see the diffs I provided above. The blanking of the misspelled/redlinked "Botswana people" rather than replacing it with the correct "Botswanan people" (as a thoughtful, reasonable editor would have done) means that this individual cannot be found in such a manner. There are thousands more unrepaired articles of this sort. When will this damage be fixed? Badagnani (talk) 22:32, 4 March 2008 (UTC)


 * Time to set up Administrators' noticeboard/Betacommandbot and get the constant argumentation off the noticeboards. Guy (Help!) 22:28, 4 March 2008 (UTC)


 * How about WP:AN/B? Its nicely bluelinked already, and full of delicious arguments. <strong style="color:#000;background:#fff;border:0px solid #000">Avruch <strong style="color:#000;background:#fff;border:0px solid #000"> T 22:31, 4 March 2008 (UTC)


 * There appears to be a record playing here, on continuous repeat... But I can't recall the album name. Any ideas? <strong style="color:#000;background:#fff;border:0px solid #000">Avruch <strong style="color:#000;background:#fff;border:0px solid #000"> T 22:30, 4 March 2008 (UTC)
 * What about this one?. Or even just the the disam page would suffice...  <font color="#21421E" face="comic sans ms">Keeper   |  <font color="#CC7722" face="Papyrus">76   |  <font color="#ff0000"> Disclaimer  22:37, 4 March 2008 (UTC)


 * Comment - Asking that damage caused to our project by a bot be corrected is not an "attack." A bot certainly can be used to identify redlinked cats and replace them with the correctly spelled ones, although it would take care to do so. Let's see to it that this damage is corrected. Covering for the mistaken bot operator (likely by other bot editors who fear a precedent being set, that bot errors will have to be repaired by the bot editors themselves) and insisting that s/he not repair such damage is illogical and equally damaging to our project, in that it encourages future damaging campaigns of this nature. The diffs provided show that thousands of articles are still without cats, whereas the redlinked cats would eventually have alerted editors active in those particular subject areas. There are many ways to proceed in correcting redlinked cats, and this was not the proper way to have proceeded, as witnessed by the earliest comments in this thread, and blocking. When will this damage be repaired? Badagnani (talk) 22:30, 4 March 2008 (UTC)


 * Can you point to a precedent for requiring affirmatively that an individual make or unmake a particular action? We have prohibitions, but affirmative requirements I think are some what in contradiction with the "volunteer" aspect of Wikipedia. <strong style="color:#000;background:#fff;border:0px solid #000">Avruch <strong style="color:#000;background:#fff;border:0px solid #000"> T 22:33, 4 March 2008 (UTC)


 * I can. The bot policy is very clear about this: "The contributions of a bot account remain the responsibility of its operator. In particular, the bot operator is responsible for the repair of any damage caused by a bot which operates incorrectly." Those who show themselves unwilling to accept this responsibility should not operate bots; this entire issue could have been avoided if the operator had sought consensus for the change before making it.   &#10154; Hi DrNick ! 22:49, 4 March 2008 (UTC)


 * That is a very good point (the bot policy note). <strong style="color:#000;background:#fff;border:0px solid #000">Avruch <strong style="color:#000;background:#fff;border:0px solid #000"> T 23:40, 4 March 2008 (UTC)


 * Comment - Your comment above (i.e., Avruch's comment about the record) makes it difficult to respond to you, as it appears to demonstrate a lack of seriousness regarding this issue. Badagnani (talk) 22:35, 4 March 2008 (UTC)


 * Look, it's a non-starter to demand Betacommand himself go back and fix all of the broken categories his bot removed. It's not like things were fine until his bot came along; things were broken, and his bot came along and broke it in a different way. However, I'd also like to ask people to re-consider the underlying suggestion we would be better off with no category than with a misspelled category.  Please consider the message, not how annoying the messenger is.  I'd like to suggest one of these two options:
 * (a) Preferred option (IMHO): Could someone with AWB or script or bot skills revert all the edits BetacommandBot made on this red-category run, so (as some point out) the red category is back on the page, hopefully catching the eye of interested editors who will fix the spelling when they see it? Also, I assume Betacommand got this list of empty categories from somewhere; if you point out to category-challenged people like me where that list is, I might find it interesting to go thru and change the spelling from that end too.
 * (b) Alternate option: Could someone with AWB or script or bot skills make a list of all the edits BetacommandBot made on this red-category run, and stick them on a page somewhere (User:Barneca/BCBot's redcat run if necesary, or better yet some appropriate wikiproject's space) as a click-able list? Then, those who want to can look through them, and relatively easily fix the misspelling.
 * Option (a) is better IMHO. I'm just afraid that the antagonistic approach some people have taken to BetacommandBot have pissed enough bot-people off that no one would be willing to do it.  But either way, we'd have a list to work off of, and could stop arguing and start fixing.  However, it seems clear to me that in the future, this isn't the greatest task for a bot to take on; I think the pre-bot broken situation was better than the post-bot broken situation.


 * Finally, there's a certain amount of Boy Who Cried Wolf syndrome here. So many people scream about BetacommandBot so often for so many incorrect reasons, that many bot-type people automatically tune out what might be a legitimate request. --barneca (talk) 22:36, 4 March 2008 (UTC)


 * Comment - This is unhelpful and unreasonable. The damage needs to be repaired. Leaving an article about a Botswanan person with no cat--to one article, let alone thousands--then moving on to other tasks, is simply unreasonable and unacceptable. Badagnani (talk) 22:39, 4 March 2008 (UTC)
 * Jesus Christ, Badagnani, it looks to me like I'm the closest thing you've got to an ally in this argument, and I'm "unhelpful and unreasonable"? Saying the same thing 1000 times doesn't help your case, it hurts it.  Read my lips: I 100% guarantee Betacommand is not going to be forced at gunpoint to replace the broken links with unbroken links.  Due to your behavior here, I think the odds are pretty similar that no one is even going to undo his bot's edits.  If you keep it up, no one is going to do anything.  Please. --barneca (talk) 22:47, 4 March 2008 (UTC)
 * So far, and not to badger you but, your position here has found no support - and for good reason. If you think that the problem of having the non-categories of articles removed is big deal, you are able to fix it. There is no precedent or principle that would allow us to mandate Betacommand take a set of actions (particularly if its laborious, and yes I know he would only be reverting his own activity). So, since no one else is going to do it right away, and we can't make BC do it... Feel free, eh? <strong style="color:#000;background:#fff;border:0px solid #000">Avruch <strong style="color:#000;background:#fff;border:0px solid #000"> T 22:45, 4 March 2008 (UTC)
 * Badagnani, the English language means that basic spelling corrections are unlikely to be always correct - incorrect category selections, in my opinion, do more damage than redlinked categories. Take Category:Iraq, for example.  Say an article was categorised as Category:Ira.  Should this article be categorised under Category:Iraq or Category:Iran?  A bot cannot be carefully written to categorise articles without a lot of work - until today, not even Microsoft Word has spell-checking to the extent that the word you intended is always the one on top of its suggestions.  Also, take Category:Guantanamo detainees known to have participated in their seconnd ARB hearing which is a redlink but has an article categorised under it.  It has a spelling error yet even if this was corrected, it would be put into a redlinked category.  There are some things humans must do because bots cannot do everything.  There may come a time when a perfect bot is able to guarantee spellings are always correct but today's world does not allow for that.  x42bn6 Talk Mess  23:00, 4 March 2008 (UTC)


 * Comment - We must always be reasonable in everything we do at WP. Such arguments, propping up the massive damage conducted by this bot operator, insisting that s/he not repair it, and ignoring the lack of navigation caused by this blanking of cats, does a disservice to our users, and shows contempt for the proper care of our content. I've encountered it many times before--in fact, every time a bot has similarly damaged our project. The other bot operators come out to defend the improper actions of the bot, insist that the editor noting the damage (who is usually simply a highly productive contributor without access to a bot) be the one to correct it, and fail to show any concern for our users or the data we should be maintaining with great care and reasonableness--presumably because they are other bot operators who fear a precedent being set (that is, that a bot operator conducting a similarly misguided, damaging, and unapproved campaign be asked to repair such damage after it is discovered). Rather than spend many dozens of paragraphs to insist the improperly behaving bot editor not do such work, it would be best to actually see to it that this massive damage be promptly repaired, as would be the most reasonable course of action. Badagnani (talk) 22:58, 4 March 2008 (UTC)
 * "and ignoring the lack of navigation caused by this blanking of cats" - If there are redlinked categories, how is this any better for navigation purposes? If there is damage then the onus is on the operator to fix it; however, I still do not see the damage caused by cleaning up purposes.  BetacommandBot, as I have said above, cannot think like a human and therefore cannot choose at its own free will (or, rather, lack of it) what is correct and what is not.  I think you are arguing that if there were redlinked categories then it would be easier to spot and fix.  Yet there are cases where if there is a redlinked category then it should be removed (i.e. Category:Wikipedians who believe that a;sfjdoiausdof8iausf is a correct word because THEY SAY SO).  But if a legitimate category is removed, then someone will inevitably categorise it properly, just as inevitably, a user will fix a spelling mistake for a category, or a user will remove superfluous words to make a category correct, or a user will remove an incorrect category.  For a bot, I believe it will only ever be able to remove redlinked categories and to me there is no damage - but if you feel there is, you have a list of contributions and you have a history tab - and this is fixable.  x42bn6 Talk Mess  23:08, 4 March 2008 (UTC)
 * Hi x42bn6, I agree with almost everything you're saying about BCBot's inability to figure out what the cat "should" have been; when it evolves to the point that it can do that, I'd also like it to make me a nice cup of tea. However, I agree with just one of Badagnani's points: I think a misspelled category is better than a missing category; a misspelled category will hopefully catch the attention of someone who knows enough about the article to fix it, whereas the fact that there is a missing category, while likely to get fixed sometime, is less likely to be noticed soon.  I think it would be marginally better if BCBot's red category edits were reverted.  And going forward, for the very reasons you mention, I think this kind of removal is not really appropriate for a Bot.  As you say, some things are better done by a human. What do you think of my 2 suggested options i made earlier?  Would either one of those be acceptable? --barneca (talk) 23:19, 4 March 2008 (UTC)
 * I prefer b) although I would not be opposed to a). But until we know something about the "damage" BetacommandBot has done nobody will know which option is best.  That said, it may probably best to do a) because there is no guarantee that a list of 1000+ category checks will be fixed quickly.  Choices, choices...  x42bn6 Talk Mess  23:26, 4 March 2008 (UTC)
 * The question is, where to have this discussion, since it seems to have been hijacked here. --barneca (talk) 23:42, 4 March 2008 (UTC)


 * Comment - Diffs for representative categories (slightly misspelled ones) that have been blanked have been given above. I certainly do not object to the removal of nonsensical cats such as "XESSESSLDFKSJDF Wikipedians" and this is why editors (even those who operate bots) must always act with the utmost care and reasonableness. Badagnani (talk) 23:29, 4 March 2008 (UTC)

Well, I think this part of this discussion has reached the limit of its usefulness, and successfully derailed the rest of the discussion as well. BCBot/BC is not going to be required to change everything back. Period. You might ask him, but good luck. I wouldn't do it if I were him, even though I am actually not a bot operator at all. I'd suggest, Badagnani, that repeating yourself over and over again with little variation is probably not going to convince anyone to your point of view. Again, though, good luck. <strong style="color:#000;background:#fff;border:0px solid #000">Avruch <strong style="color:#000;background:#fff;border:0px solid #000"> T 23:22, 4 March 2008 (UTC)


 * Hi Avruch. OK, but where would you suggest I go to make my comment/suggestion if this thread is no longer useful?  So far, the only response I've got is from Badagnani... I don't think I'm being so shrill that I should be ignored too. --barneca (talk) 23:29, 4 March 2008 (UTC)


 * Sure, somewhere else other than this section (or even, this issue) would probably work. HiDrNick has made a good point above that the bot policy appears to require bot operators to undo damage caused by their bot. Since the bot policy also specifically prohibits bots from correcting spelling errors, BCBot would have no other option than mechanically replacing all the broken cats with new and identical broken cats. <strong style="color:#000;background:#fff;border:0px solid #000">Avruch <strong style="color:#000;background:#fff;border:0px solid #000"> T 23:42, 4 March 2008 (UTC)


 * I agree DrNick's point is a good one, but we haven't reached a consensus that what BCBot did was "damage". It was broken one way, now it's broken the other way.  People with the best interests of the project can disagree on which is worse (as it appears you and I do).  But I don't know how to have this conversation (anywhere) in a calm organized way with all this loud background noise. --barneca (talk) 23:50, 4 March 2008 (UTC)
 * Comment - Assisted spell-checking is acceptable (as is doing it by hand). The bot can be used to simply identify redlinked cats, whose spelling can then be fixed in an assisted manner, or by hand. The claims that bots can't do this or that fail to acknowldge actual solutions that have already existed for years. Badagnani (talk) 23:46, 4 March 2008 (UTC)
 * Agreed. But Betacommand took a slightly blunter approach - not wrong, but possibly not the best solution.  That said, tool-assisted or manually done are unfeasible if Betacommand wishes to do it alone, but it is one of the solutions presented below.  x42bn6 Talk Mess  23:51, 4 March 2008 (UTC)


 * Comment - We must be reasonable in everything we do. Inserting more paragraphs about how such damage is fine, and insisting that a bot operator causing such damage not be asked to repair it, is unreasonable, does a disservice to our users, and our content. Let's see to it that this is fixed, promptly. Badagnani (talk) 23:27, 4 March 2008 (UTC)
 * Comment Is there any chance that you could stop repeating yourself? I think anyone who was listening to begin with has turned off by now. <b style="color:black;">Black Kite</b> 23:31, 4 March 2008 (UTC)


 * Comment - If the problem were fixed after the first (or second, or third) request rather than the repeated (and repetitive) comments insisting that the editor noting the damage be the one to repair it (and repeatedly insisting that the bot operator not repair it, and instead move on to other tasks), repeated requests for such a prompt repair would not have been necessary. I think that's quite clear. Badagnani (talk) 23:34, 4 March 2008 (UTC)
 * Badagnani, you're missing the point. A bot cannot be careful.  It cannot say to itself, "Hold on a second, that looks like an obvious misspelling - I'll run it through my in-built spell-checker and test it against the "obvious" capitalisation errors."  It is not necessarily a spelling error, capitalisation error or anything - it could be an extra word, an extra space, a word that is a synonym to another word in the category, and so on.  A bot cannot be careful.  Please remember that.  x42bn6 Talk Mess  23:43, 4 March 2008 (UTC)


 * Comment - This is incorrect. A bot can identify errors, which can then be corrected in an assisted manner (or by hand). Bots are operated by human beings, who must always edit with great care. This was not done in this case, and this damage needs to be repaired. Badagnani (talk) 23:48, 4 March 2008 (UTC)
 * I agree, but Betacommand cannot possibly do all of it alone - there are several thousand things to fix. But it still does not mean there is damage that he needs to reverse.  If a person builds a house but it turns out there is a better way of building a house, then there is no need to unbuild the house to build it the new way unless the old way is completely wrong.  But Betacommand's method is not wrong - it is, however, heavy-handed and for some cases possibly makes things harder to fix.  x42bn6 Talk Mess  23:56, 4 March 2008 (UTC)


 * Comment - Leaving a page for a Botswanan person with no cat (at all) was an improper action. There are up to several thousand other pages like it now, with no way to know which need to be fixed (even by editors skilled in this subject, who would normally attend to such things). Even a bot set to add a notice regarding such a misspelled cat would have been preferable, as it would have allowed such editors to identify and correct the problem. As Barneca noted, now nobody knows there is a problem, whereas the redlink shows it clearly. It was necessary to insist that this be fixed because there have been many prior instances where the damage was as great or greater--and the insistence that the bot operator not correct the mistake was, despite the very clearly stated bot policy, similarly as great or greater. We must have the utmost care and respect for our data, and users. Badagnani (talk) 00:01, 5 March 2008 (UTC)
 * Comment Yes. You are correct.  You were correct the first time, and you are still correct this time, which I make to be approximately the 22nd time you've posted something similar on this page.  Please stop now, this is starting to verge on the disruptive. <b style="color:black;">Black Kite</b> 00:16, 5 March 2008 (UTC)
 * Badagnani, you're being quite disruptive here. I ask you that you contribute here much more constructively here, so please treat this as a final warning for disruption. I suggest you refrain from editing this page for say, 12 hours. If you continue your disruption, I can formally ban you from this page from 12 hours and if you violate it that ban, I'll block you for 12 hours. How does that sound?  Maxim (talk)  00:20, 5 March 2008 (UTC)


 * Comment - I appreciate the constructive criticism of my postings. Can you outline specific elements of my comments to which you object (so strongly as to block one of the most productive contributors to our project?), so that I may not make them again? Thanks, Badagnani (talk) 00:24, 5 March 2008 (UTC)
 * You're making the same demand over an over again. See your posts on this page at 20:20, 20:41, 21:33, ... 00:01 I hope you get the gist of it. You've posts with the same point around 20 times; that's really disruptive.  Maxim (talk)  00:27, 5 March 2008 (UTC)
 * I even largely agree with the point you're making and even I'd support this block if it was enacted. Saying or making the same point several times under "Comment" sections is close to blatantly disruptive, and when your behaviour itself is derailing the discussion, it actually (and somewhat sadly) ceases to matter whether you have a valid point or not. Orderinchaos 13:37, 6 March 2008 (UTC)

Discussion got swamped
I like to address here how the useful discussion above got swamped by Badagnani and those responding to him. Badagnani had some useful points to make, but overdid it by incessant repetition. Equally though, those incessantly responding to him were feeding that sort of behaviour, and were contributing to the swamping of the discussion. Please, in future, just respond a few times and then refer them to your previous answers and then ignore. Carcharoth (talk) 05:21, 5 March 2008 (UTC)
 * Some specific points. Redvers said "I don't see a problem with losing unprofessional redlinked categories with misspellings in them" - the correct approach is to correct the spelling, if the category is needed. This cannot be done if the category tags are simply removed. I am puzzled as to why Redvers and others cannot see this basic point. I agree with Barneca that in the case of "requested" categories (ie. ones where someone put a category tag down without creating the page) and mis-spelt categories, BetacommandBot has changed the situation from one broken one to another broken one, but with less chance (in fact almost no chance) of being corrected. Bot operators should be prepared to revert their edits or clean them up manually if need be. It is an important part of the process, as it makes them more careful next time. Carcharoth (talk) 05:21, 5 March 2008 (UTC)

Constructive step
If anyone's interested in actually starting to fix things (and note, whether or not BCBot's edits are reverted, a human has to fix these things), My User:Barneca/Sandboxen/Sandbox page has a list of all of BCBot's red category removals. It isn't formatted perfectly, and I don't have the time or inclination to perfect it, but since a decison about reverting the edits, one way or the other, is going to be made in April or May at the earliest, I did what I could now. I'm going to tackle three of them and call it a night. Anyone else? --barneca (talk) 00:35, 5 March 2008 (UTC)


 * I did a few, 50-75 or so - maybe a bit more. I'm not doing the other 1925 though ;-) <strong style="color:#000;background:#fff;border:0px solid #000">Avruch <strong style="color:#000;background:#fff;border:0px solid #000"> T 00:54, 5 March 2008 (UTC)

If you want to find and fix uncategorized articles, have a look at Special:Uncategorizedpages and Category:Uncategorized pages. If you want to find and fix red category links, see Special:Wantedcategories. Bovlb (talk) 01:03, 5 March 2008 (UTC)


 * (e/c with Bovlb) I saw that, thanks Avruch. I see you went the reverting route.  I misunderstood and thought we disagreed on that, so I went the hard way instead.  I'll revert a few myself, but then need to go do real world stuff.
 * From a little research, if all of BCBot's removals are reverted, it appears the place they would show up, and where humans can go to correct misspellings, remove obvious mistakes, recategorize, etc. for nonexistant categories with members is Special:Wantedcategories, which is formatted much better than my sandbox! G'night. --barneca (talk) 01:05, 5 March 2008 (UTC)


 * I disagreed on making Betacommand do it, mostly. I don't think its really necessary to revert them, but if it makes people happy... Its fine with me. If later consensus says the cats should be removed, BCBot can pretty simply do it again. <strong style="color:#000;background:#fff;border:0px solid #000">Avruch <strong style="color:#000;background:#fff;border:0px solid #000"> T 01:07, 5 March 2008 (UTC)


 * To be safe, I'm assuming I'd get lots of people mad at me if I used rollback on this, right? --barneca (talk) 01:12, 5 March 2008 (UTC)
 * p.s. We never disagreed on making BC do it. --barneca (talk) 01:13, 5 March 2008 (UTC)
 * Who knows. I used it. If someone wants to remove it from me for this, oh well. The whole "Only ever use this for vandalism" argument is a pain in the butt. Its a tool, use it when its useful and don't when it isn't. That said, I hardly use it anyway. <strong style="color:#000;background:#fff;border:0px solid #000">Avruch <strong style="color:#000;background:#fff;border:0px solid #000"> T 01:15, 5 March 2008 (UTC)
 * I agree, the distinction seems silly to me (especially when reverting a BOT for pete's sake), but I'd also like to hang on to my adminship for longer than 20 days. I think I'll be unbold --barneca (talk) 01:37, 5 March 2008 (UTC)

What would be useful is running a spell-check over the list of categories, and looking for incorrect capitalisations, and seeing if the corresponding categories exist. Barneca's sandbox is useful, but a bit messy now, so I'll start my own list and analysis. I'll do this off-wiki, but it will be interesting to see how many red-linked categories were correctly or incorrectly removed. Carcharoth (talk) 04:48, 5 March 2008 (UTC)
 * My admittedly small sample showed very roughly 1/4 should just be removed, 1/2 were spelling or capitalization or similar problems, and 1/4 were complicated cases requiring more category experience than I have, usually creating the category, or using what would have been a parent category. FYI most of the "spelling" errors weren't actual spelling errors, they were either capitalization errors, or mistakes like using (as a made up example so I don't have to check spelling) Category:Municipalities in Oregon instead of Category:Cities in Oregon. --barneca (talk) 05:04, 5 March 2008 (UTC)


 * I'm going to see if I can tackle this tomorrow and try to fix some of the deleted categories. It's very disappointing that people are having to clean up for what the bot did.  Enigma  msg! 07:11, 6 March 2008 (UTC)


 * Fairyland, FieldTurf, The Barber, Eleanor Boardman, User:Astronouth7303, New Era University, PAOK F.C, Nakoruru, User:Kmweber,Fred De Luca,Casshern,Tracey,List of candidates in the United States presidential election, 2004,Odawara Station.

It's very time-consuming to edit the sandbox and cross out all the ones I did. Oh well. I don't think anyone will ever be able to completely fix this, unless someone designs a bot to fix what another bot did.

BCBot indefinitely blocked
So, BCBot remains indefinitely blocked. The areas that we might focus on are: Anyone have any opinions on this, rather than the secondary stuff above about reversing all the removals of broken cats? <strong style="color:#000;background:#fff;border:0px solid #000">Avruch <strong style="color:#000;background:#fff;border:0px solid #000"> T 23:26, 4 March 2008 (UTC)
 * Should the bot remain blocked, and for how long?
 * Should a request for approval to BAG have been made, despite Betacommand's status as a member?
 * If yes, and this is a repeat violation of the requirement to have task approval ahead of time, should Betacommand again be removed from the bot approvals group?


 * Comment - Yes. And the bot operator should undo the damage done (i.e., the blanking of slightly misspelled categories). Badagnani (talk) 23:35, 4 March 2008 (UTC)
 * Comment - Status as a member does not mean you can do any code change you wish, anytime you wish, and then run it without notification.Wjhonson (talk) 23:37, 4 March 2008 (UTC)


 * Well, I'm aware that this isn't the only thing BetacommandBot does so it should be unblocked if it wants to do something else, but it should leave this task alone until something has been fixed.
 * It isn't required at present but such a thing would be preferred, to me. Not necessarily to seek approval but to see if there are alternative solutions or overriding criteria, or even if there is an existing task already, amongst other reasons.
 * No opinion. Mistakes can happen.  x42bn6 Talk Mess  23:34, 4 March 2008 (UTC)
 * As I said above, I don't think this kind of knowledge-intensive task is a good thing for a bot to be doing. If BC says he won't have his bot do this particular task anymore until a consensus forms that he should resume what he was doing, unblock; I certainly don't think unblocking should depend on whether the edits are reversed.
 * It doesn't matter if a BAG request should have been made; BC's actions were in good faith, and looking back like that serves no purpose. I do think that a consensus here or at BAG should be acheived before the same task is resumed.
 * It would damage the project to remove BC from BAG, and I can see no upside to it. --barneca (talk) 23:37, 4 March 2008 (UTC)


 * (a) it'll need to be unblocked for the next time it needs to run its core work. (b) it would probably have been a good idea. (c) No. <b style="color:black;">Black Kite</b> 23:47, 4 March 2008 (UTC)

Yes to all three points: a) BetacommandBot should remain blocked until i) Betacommand acknowledges that the task was run without approval, and demonstrates that he he understands the difference between implementing decisions agreed at CfD and simply removing redlinked categories, ii) the bot's approved list of tasks are submitted afresh for approval, so that the list can be checked carefully for any possible ambiguities b) Yes, approval should have been sought. "CFD" clearly refgers to WP:CFD, "Categories for discussion", and these edits are nothing whatsoever to do with WP:CFD. c) Yes, Betacommand should definitely be removed forthwith from the BAG. Quite apart from the serious issue of repeatedly running a bot for an unapproved task, there is a clear conflict-of-interest between Betacommand's presence on the BAG and his status as the owner of the bot which generates the most controversy. I quite accept that some of that controversy is over his legitimate work wrt to images, and that most objections to that work are simply wrong ... but some separation of powers is needed here, and Betacommand's position presents a clear conflict-of-interest. --BrownHairedGirl (talk) • (contribs) 04:32, 5 March 2008 (UTC)

Unblock
As the blocking admin, I think I should clarify what I'd like to see before an unblock. Just a simple statement from BC to say that he will stop removing red linked cats, and should he want to do the same in the future, he will firstly seek consensus that it's what's wanted first, and then get BAG approval. It's not difficult for him to say that and it's my only caveat for unblocking.  Ry an P os tl et hw ai te  23:57, 4 March 2008 (UTC)
 * And I'd just like to see the damn bot follow nobots/bots on userpages. Seriously, how hard is it to implement that in the code? I won't support ever being unblocked unless this is done. It's called "bot with manners", and this one doesn't have any. - <font size="+1" color="red">&#10032; <strong style="letter-spacing:1px;font-family:Verdana">ALLSTAR <font size="+1" color="red">&#10032; echo 01:03, 5 March 2008 (UTC)

As I said this task will not be run without further discussion. βcommand 04:19, 5 March 2008 (UTC)
 * Then I'd agree to the unblock. But the fact that the task ran into difficulty either means that there was not enough oversight at WP:BAG, or it was incorrectly implemented. Which was it? Carcharoth (talk) 05:02, 5 March 2008 (UTC)

Apart from the commitment to stop removing redlinked cats, I want to add one more: that before any unblocking, Betacommand should be removed from the Bot Approvals Group. There is a clear conflict of interest between Betacommand's presence on BAG and BCB's status as a bot which has repeatedly run unapproved tasks. BCB's work in images is important and needed, but it is highly controversial among editors who don't understand why it has to be done, and it is basic good practice that there should be separation of powers between running such a bot and approving it. --BrownHairedGirl (talk) • (contribs) 04:39, 5 March 2008 (UTC)
 * The discussion where Betacommand rejoined WP:BAG can be seen here. There is a bit of history behind WP:BAG, its operation and membership, including the proposed deletion of WP:BAG itself at one point. I recently proposed that people who weren't bot programmers but were knowledgable on policy and guideline issues would be helpful as part of WP:BAG to bring a wider perspective to the table and ensure a stronger voice on non-technical issues. All too often bots are approved without requiring further discussion in specialist areas of Wikipedia (eg. WP:MoS or WP:CfD), or further community discussion. Also, like admin flags, it also hard to get bot flags or specific bot task approvals withdrawn through WP:BAG. One proposed community-drive process is at Requests for comment/User conduct, which is untested so far. Carcharoth (talk) 05:01, 5 March 2008 (UTC)


 * Comment - It's being corrected, at User:Barneca/Sandboxen/Sandbox. Please take a look, and assist if you would like. I note that the human behind the Beta Command bot has not lifted a finger to assist yet, apparently preferring to simply move on to other projects, as bot operators generally do when they make an error (despite WP's very clear bot policy, which states that they must be the ones to make the repair of damage they cause). Regarding my comments, had you contributed to the discussion earlier, I would not have needed to reiterate my request that our bot policy be adhered to, and Betacommand undo his/her damage. Lord knows, it's been so many times that the same thing occured, and no one like you ever contributed with similar comments to the discussion (the bot operator generally either ignoring my request or stating in no uncertain terms that it "wasn't their job" to make the repair, and that it would be "too difficult," and they're not doing it--but they always invited me to undo it, even if it was into the thousands of articles damaged), and, in fact, there are articles that have been without the proper cats for over a year (and still are without cats) because of this. Badagnani (talk) 06:04, 5 March 2008 (UTC)]

I really like BrownHairedGirl's idea of seperation of powers. Perhaps BC would voluntarily step-down from BAG? Either way, I'd agree with this proposed policy. I also very much like nobots on userpages. And can we add no bots on user talk pages as well? I see no point for bots in non-article space at all to tell you the truth. I went to the RfC but I don't see anything there yet. Wjhonson (talk) 06:09, 5 March 2008 (UTC)
 * What do you mean by "separation of powers"? It's not like BC claims he's self-approving his tasks. Gimmetrow 09:30, 5 March 2008 (UTC)


 * Bot has been unblocked by User:Krimpet at 04:31, 5 March 2008, with block log summary "bot has stopped". Carcharoth (talk) 09:41, 5 March 2008 (UTC)
 * That's a real pity. There seems to have been attempt by Krimpet to discus the issue (see [contribs), and no consensus here to unblock. I will ask Krimpet to reinstate the block. --[[User:BrownHairedGirl|BrownHairedGirl]] (talk) • (contribs) 11:31, 5 March 2008 (UTC)
 * I seriously don't see anything wrong with an unblock. BC's said he wont run the task without discussion. Doesn't stop its other tasks from running (e.g. Wikiproject tagging). If the task runs, reblock. Will (talk) 11:55, 5 March 2008 (UTC)
 * Me either. The unblock seems perfectly sound to me. SQL <sup style="font-size: 5pt;color:#999">Query me!  14:42, 5 March 2008 (UTC)
 * I too support the unblock to allow the bot to carry out other tasks, but I am concerned that Betacommand hasn't actively engaged in the discussion here (he has made a total of four edits). There is a direct question from me about whether this was a misunderstanding on his part, or incorrect programming of the bot, that he has not yet answered. Does he not care about the effects his bot has had? Do either of you (SQL and Will) have comments on what MBisanz has said below? The bit about how BCB has less "mission critical" tasks and so that argument against blocking is becoming less relevant? MBisanz points out three recent incidents. Is there any indication that Betacommand learnt anything from any of them? Carcharoth (talk) 16:06, 5 March 2008 (UTC)
 * Carcharoth, as I stated before, this is/was a task that I have done multiple times in the past without issue. I thought category maintance was covered under my CfD work. Prior runs have been un-eventful and very helpful for getting the missing/improper categories addressed. βcommand 16:24, 5 March 2008 (UTC)
 * Thanks for the clarification (good thing i edit conflicted here, erm...). I support the unblock too, since the task stopped. That being said, we should think of a way to fix the red categories in the future, only (very) popular misspellings would appear on wantedcats. -- lucasbfr  talk 16:28, 5 March 2008 (UTC)
 * here is a thought, I can generate a list of red linked cats, (I posted about 1/5 in my sandbox), there are ~26k red cats. Weekly I post them to wiki and users remove/create cats that are needed. once the list has been up for a week any remaining redlinks will be emptied. and start doing this weekly. that way we can get wanted categories created and get rid of the useless red link cats. βcommand 16:43, 5 March 2008 (UTC)
 * We're getting closer to a solution here, except I think many here are very uncomfortable with the last step you propose. Identifying red cats for users is a good move though and I think it could become a maintenance task like faulty ISBN numbers and no-cat articles and such things. Orderinchaos 13:44, 6 March 2008 (UTC)
 * Sorry, Betacommand, I missed that. Let me quote you from above: "'Ive been removing redlink cats for a while. prior to this there have not been any issues. What I have seen from prior runs is that pages often get improper categories removed. and ones with typographical errors get fixed. in general a lot of good comes from these runs.'" Could you clarify how long you have been doing this task for and how many runs you have done on this task? I know your bot does lots of other tasks, but if you use edit summaries consistently, it shouldn't be hard for you to split your contributions log up into dated sections according to which task the bot was carrying out at that time. So, do you have such a list? That way, an analysis can confirm or deny your statement "in general a lot of good comes from these runs". Would you be able to do that before doing any more runs? Carcharoth (talk) 17:26, 5 March 2008 (UTC)
 * As for the proposal: "once the list has been up for a week any remaining redlinks will be emptied" - this sounds like redlinks could be removed that would be useful if corrected, and that is a bad thing. In general though, this is not the right place to propose and get approval for such a proposal. You really, really, need to get the attention of people doing this sort of work and discuss it with them before charging ahead with bot work like this. The discussion here should have shown you that. One further point "the useless red link cats" is not the same as "the red link cats no-one has got around to fixing yet". This is another bot task with wide-ranging effects that needs further discussion in the right venues, and that doesn't mean WP:BAG - that group doesn't have the non-bot knowledge necessary to approve something like this. Carcharoth (talk) 17:26, 5 March 2008 (UTC)
 * Carcharoth, I was just throwing an Idea up, seeing what the responce would be before making further discussions. It has been a few months since going redlink removal, and Im not sure when it was done last. I can confirm my statements about how it improves things. I know Ive been doing this for at least 9 months. βcommand 17:45, 5 March 2008 (UTC)
 * Just to be clear, you realise that removal of redlinked categories and removal of categories deleted at CfD are two different things? And that you have approval for the latter, but not the former? And that you need to get WP:BAG approval before doing the former? Yes, yes, and yes is what I think. Though I'm still not sure that deciding whether to remove category redlinks is something that a bot can help with. In my view, it should only remove redlinks from a list of approved removals, but in most cases the number of removals per category is small enough to do by script or manually. Carcharoth (talk) 18:10, 5 March 2008 (UTC)


 * BAG approval is not entirely on point - its a generally technical review, and requires the approval of only one member - of which Betacommand is one. <strong style="color:#000;background:#fff;border:0px solid #000">Avruch <strong style="color:#000;background:#fff;border:0px solid #000"> T 18:53, 5 March 2008 (UTC)
 * Well, putting aside for a moment the strange appearance of someone approving their own request... (is it not more logical to require a different BAG member to do the approval?) Who approves the non-technical parts of a bot proposal? Carcharoth (talk) 23:15, 5 March 2008 (UTC)
 * To quote WP:B:
 * is harmless
 * is useful
 * does not consume unnecessary resources
 * performs only tasks for which there is consensus
 * adheres to relevant policies and guidelines
 * So I'd say the task's relate policy talkpage would nee to give consensus. A bot reverting vandalism for instance should follow the consensus of the AIV page or a bot signing for users should follow the consensus of the SIG page.  MBisanz  talk 23:28, 5 March 2008 (UTC)
 * Or in this case, consensus at some categorization policy talk page. Carcharoth (talk) 00:07, 6 March 2008 (UTC)


 * Avruch said: "BAG approval is not entirely on point - its a generally technical review, and requires the approval of only one member - of which Betacommand is one."
 * BAG approval is not simply a technical approval. Tasks need to be in accord with wikipedia policy in general (not just WP:BOT), and have consensus. Also, I have never seen BC claim he is approving his own tasks. Gimmetrow 03:42, 6 March 2008 (UTC)

My good faith is stretched very thin
I'm glad that BC has joined in the discussion, but he hasn't allayed my concerns. I don't see sign of an offer by BC to undo the damage, but my main concern is that BC says "I thought category maintance was covered under my CfD work".

I'm sorry, but this is stretching my good faith a very long way. WP:CFD is "Categories for discussion", a process which makes precise decisions about removing, merging or renaming particular categories, and whose outcome is a very specific set of instructions at WP:CFD/W, which are usually implemented very thoroughly by CydeBOT, which creates very clear edit summaries so that there can be no doubt why category links are being removed.

CfD is not "general category maintenance", or removal of redlinks. If I accept BC's statement in good faith, then I find myself rather more worried than if I thought he was being untruthful in his reply ... because I am very worried by the idea of a fast-running bot being operated by someone who can't distinguish between CfD and other things which could be done with categories. This is sort if boundary issue is very important in a bot owner, where I would have thought that the key principle was "if there is any doubt, check" ... and after all the trouble BCB has run into before, I would have thought that BC would be very acutely aware of the importance of seeking clear approval for bot tasks.

I'm also wary of BC's defence that this has been done before. It seems to me to be very unlikely that it was, because this run was spotted very quickly, and while I don't intend to try to scan BCB's hundreds of thousands of edits, a defence that nobody objected last time he ran this unauthorised task is not encouraging.

Something is not at all right here. I can't decide whether BC is a fool or a knave, but I can't see any third possibility and those two both alarm me. --BrownHairedGirl (talk) • (contribs) 17:36, 5 March 2008 (UTC)
 * I honestly think he means well and is project-minded, but is sometimes on a different plane from the rest of us - at times when I've dealt with him he genuinely does not seem to comprehend the concerns. Orderinchaos 13:44, 6 March 2008 (UTC)


 * BrownHairedGirl, <OMIT RANT ABOUT FACTLESS PERSONAL ATTACKS> dont call me a liar without proof. I take great offense to that. <OMIT MORE RANTS>. βcommand 17:54, 5 March 2008 (UTC)
 * Betacommand, please re-read what I wrote. --BrownHairedGirl (talk) • (contribs) 18:01, 5 March 2008 (UTC)


 * I agree with what BHG has said. I've also read through Bots/Requests for approval/BetacommandBot (last edited in July 2007), and I don't see approval there for this task. I know others have said this already, but it is alarming that Betacommand still says that he has done this task before. I think he is still (despite people trying to explain this to him) confusing the removal of genuinely deleted categories with the removal of redlinked categories. I would ask that BetacommandBot not be used for any tasks until Betacommand provides a list of the previous runs done with this task. We need to see how widespread the damage is. Carcharoth (talk) 17:52, 5 March 2008 (UTC)
 * (through EC) I too agree with what BHG has written. I also view BC's angry response accusing BHG of "personal attacks" as symptomatic of what I view as the root problem: a user who is far too thin-skinned to run such a powerful tool that will, from time-to-time raise the ire of other users. That and the fact that BC treats the code like it's a trade secret, refusing to allow the community at large to view and work to improve the bot's functionality. These are my main issues, as I outlined above, in my previous commentary. Bellwether B  C  18:08, 5 March 2008 (UTC)
 * I second that request: if Betacommand has indeed done this before, then let's see the evidence and decide what to make of it. I also agree that BCB should not be used further until this has been reviewed. --BrownHairedGirl (talk) • (contribs) 18:04, 5 March 2008 (UTC)
 * Carcharoth here is a list of that the bot has done. βcommand 18:11, 5 March 2008 (UTC)
 * No. That is a list of all the contributions of a multi-task bot. We are asking for the contributions done under a specific task. How can anyone be expected to find a few thousand edits when they are swamped among other ones. The answer is that the bot operator should make careful records of the start and end of each run under each task, and deposit the records on wiki. So, do you have such records? If not, will you start making such records? Carcharoth (talk) 18:19, 5 March 2008 (UTC)
 * I was reviewing bot policy and noticed this rather interesting clause Bot_policy.
 * "As explained at Wikipedia:Categorization of people, certain types of person categories should not be filled or emptied using a bot. Addition of sensitive categories to articles requires per-article manual review, and should not be carried out simply by generating a list from existing Wikipedia content."
 * So as far as I understand it, Bot are specifically prohibited from emptying categories relating the people, as I believe happened in this matter as a side-effect of de-populating ALL redlinked categories. If BCB is actually approved somewhere to do this, then we need to change the policy to reflect this change in consensus.  Betacommand, were you aware of this part of policy when you coded the redlink run?  MBisanz  talk 23:11, 5 March 2008 (UTC)

No unblock until the damage is repaired
As noted above, WP:BOT says that "The contributions of a bot account remain the responsibility of its operator. In particular, the bot operator is responsible for the repair of any damage caused by a bot which operates incorrectly."

I have yet to see any attempt by Betacommand to undo this damage, or any offer to do so. Quite apart from the other issues raised above, it seems to me to be wrong to unblock the bot until Betacommand has at least started to repair the damage. WP:BOT is not a guideline, it's a policy, and it states quite unambiguously that leaving the tidyup to others is not acceptable. --BrownHairedGirl (talk) • (contribs) 08:27, 5 March 2008 (UTC)
 * The trouble is, as people have pointed out before, that BetacommandBot does a rather large number of tasks. Betacommand has said he is working on separating them out, but progress appears to be slow. I think the best you will get is an agreement (which Betacommand has already given) not to run the bot on this categpory-related task again. I'd like WP:BAG to go further and withdraw approval for the specific task until the bot and/or operator have shown they can do the task properly. As for repairing the damage, it is possible from the contribs to examine the edits manually (there are between 2000 and 2500, so a large but not impossible task). Reverting all edits the bot carried out on this task was one possibility, but now that manual correction has started, this is not really possible anymore. I'll try and help out, as I am interested in a tally of how many of the edits were off-task or inappropriate. Carcharoth (talk) 08:59, 5 March 2008 (UTC)


 * How can he repair the damage when his bot is blocked? If he attemt to do it from his main account, he will be blocked as unauthorized bot. Max S em(Han shot first!) 09:11, 5 March 2008 (UTC)


 * This way. Badagnani (talk) 09:12, 5 March 2008 (UTC)
 * Demanding to fix thousands of automatic edits manually is completely unfunny. Max S em(Han shot first!) 09:22, 5 March 2008 (UTC)
 * That is an interesting opinion. Because, in fact, I was asked no fewer than 6 times today to do this (because Betacommand did not wish to do it, believing it would be too hard). I didn't find it funny either. Nevertheless, we are doing it. I invite you to read the discussion archive and take a look before commenting further about this matter. Badagnani (talk) 09:27, 5 March 2008 (UTC)
 * One solution to the alleged problem was to revert all the edits. That could be done quite fast with rollback. Gimmetrow 09:30, 5 March 2008 (UTC)
 * What do you mean "alleged problem"? There clearly was a problem, one that a bot can't fix, and one that people are now manually fixing. You could say the bot action drew attention to a problem (mis-spelt redlinked category tags), but it tried to brush those mis-spelt category tags under the carpet by removing them from articles. Carcharoth (talk) 09:37, 5 March 2008 (UTC)
 * Noe that it's uncovered, there's no significant difference between manually reviewing Special:Wantedcategories and bot's contibs at User:Barneca/Sandboxen/Sandbox. Max S em(Han shot first!) 09:49, 5 March 2008 (UTC)
 * I don't understand what you are saying here. What has been uncovered? Carcharoth (talk) 09:51, 5 March 2008 (UTC)
 * That BCB was removing redlinked categories blindly. Max S em(Han shot first!) 09:52, 5 March 2008 (UTC)
 * So long as the BCB edit is the last edit, it can be reverted with rollback. Even by hand it's possible to do 50 rollbacks/minute. If these 2500 or so edits are such a problem, one grueling hour would restore everything as it was. Gimmetrow 09:57, 5 March 2008 (UTC)
 * The trouble is that some of the removals were categories that had been deleted after a CfD discussion, though it is unclear whether Betacommand got a list from CfD or whether these were redlinks that had been re-added by others after the normal CfD procedure had removed them. And I still don't see why you are saying "If these [...] edits are such a problem". It is clear there are problems there. It is equally clear that Betacommand is doing nothing to help fix the problems. It is also clear that rollback could fix some of the problems, but would in any case need to be applied with an edit summary (you can do rollback with an edit summary, but you need to set things up properly to do this), something like "rollbacking indiscriminate removal of redlinked categories by BetacommandBot after discussion here - manual checking still required" (with a link to this discussion). As has been said above, this will send most of these category redlinks back to Special:Wantedcategories for manual checking. Carcharoth (talk) 10:52, 5 March 2008 (UTC)

(undent)I think it would still be better to revert any of the bot's removals that are still the last edit to the articles. As I said somewhere above, that way people that are interested in individual articles will help fix redlinks from that direction, while those interested in attacking it from this direction can just go to Special:Wantedcategories, which is much better formatted than the list in my sandbox. If BCBot isn't the last edit, either someone's already reverted, which is good, or someone's already fixed the category, which is good, or someone's made another edit in an unrelated area, which is imperfect, but we can live with imperfection. --barneca (talk) 12:59, 5 March 2008 (UTC)
 * As the guy who created the proposed Bot RFC process, I had realy hoped BCB would not be the first bot subject to it, given the long-running and wide-ranging span of commentary on its actions. Given that this page exists, I think we could sidestep the RFC given that its still only a proposed process and continue this existing discussion.
 * In the last month (?) BCB has now been used three times to do un-approved controversial edits. One was the spamming of MickMacNee's talk page, which is it had been done by a human user through special tools like Twinkle or AWB would have resulted in the automatic revocation of those tools and probably a decent block to boot, without the benefit of such a lenghty review and discussion.  The second was the revision counter run-up at the mainpage.  Bots are given a flag that lets them operate far faster than regular users, because its trusted that they will only perform approved tasks.
 * Now this third incident of the categories removal. Over the last month or so, there has been a slow-running debate over user categories spread over many pages.  I can only assume that BC follows some of the discussion as these boards and would've noticed this as a controversial topic.  And given that there was already a discussion at WT:RFAR about whether or not an arbcom was warrented over this bot's actions, I'd say he should've trended towards adhereing to both the letter and spirit of the BOT policy.
 * In the past I've questioned if blocking BCB was a good idea, given the mission critical tasks it performs. But I now understand that MessedRocker's RFC Bot can be run, albeit inefficiently, as a replacement to BCB.  And the Fairuse image backlog has been dealt with well before the March 23rd deadline.  So I'm withdrawing my prior comment that any definitive action against BCB should take into account mission critical tasks.   MBisanz  talk 14:33, 5 March 2008 (UTC)
 * If there's an available replacement for Betacommandbot, it probably should be used instead, especially if the replacement is open source, the tasks it does are well defined, and the code can be audited by others. Once the functionality is correct, the performance problem can be dealt with later. --John Nagle (talk) 18:59, 5 March 2008 (UTC)


 * Mbisanz, there was a fourth misuse of the BCB: the mass-adding of the WikiProject Interfaith banner to over 3000 articles, discussed late February on WP:AN here. It would seem that whenever someone asks for some automated edits, BetaCommand jumps over himself to help, no questions asked. Not a sign of good judgement. -- llywrch (talk) 00:35, 6 March 2008 (UTC)


 * That wasn't misuse. It was a good-faith attempt to do an approved task, but came across some false positives. Will (talk) 00:39, 6 March 2008 (UTC)

Bot task made redundant
The bot task of clearing those 26,000+ redlinked cats is now being done by humans (with the help of the bots) at User:Random832/WantedCats. Carcharoth (talk) 18:37, 5 March 2008 (UTC)
 * Fairuse image tagging per NFCC 10c appears to be handled by a new bot per Bots/Requests for approval/Non-Free Content Compliance Bot.  MBisanz  talk 23:45, 5 March 2008 (UTC)
 * MBisanz, I am just handing operation of the bot off, I am still the programmer. βcommand 23:46, 5 March 2008 (UTC)
 * Correct, thats why I said "by a new bot" and not "by a new bot op".  MBisanz  talk 23:47, 5 March 2008 (UTC)
 * I'm very excited about Bots/Requests for approval/Non-Free Content Compliance Bot. Hopefully this will result in the best of both world's. Betacommand's bot skills and teams of people to be slightly more organised about actually running the bot. Good luck guys (ST47, Martinp23, and SQL), and I hope it works. I'm just wondering where the name came from? Was it inspired by Non-free content criteria compliance or not? Carcharoth (talk) 00:06, 6 March 2008 (UTC)
 * Yeah, it was. --MZMcBride (talk) 00:39, 6 March 2008 (UTC)
 * I have proposed an ammendment on the approval pageMickMacNee (talk) 00:48, 6 March 2008 (UTC)
 * I was excited that we had a new bot, then I looked into it. Apparently Betacommand is still writing the code and still has absolute authority over what the bot does, but three other people are taking responsibility for it. This means we won't get more sensible messages or reasonable handling of near misses from this bot.  r speer  / ɹəəds ɹ  06:29, 7 March 2008 (UTC)

Well so much for trying to reach a consensus
And what's with all this "not a vote" crap? The way I had it set up is the same way used for VOTING at RfA and RfB. So, wtf?? Nothing but lip service going on on this page anyway. Let's stop talking about it, and do something about it. This page has gotten so big, no one knows what's going on. A consensus discussion was ongoing about unblocking the bot and what has that lead to? Disregard as the bot was unblocked anyway. I mean, seriously here. Get off the duffs and take action. - <font size="+1" color="red">&#10032; <strong style="letter-spacing:1px;font-family:Verdana">ALLSTAR <font size="+1" color="red">&#10032; echo 18:51, 5 March 2008 (UTC)
 * RFC is that way, which is the traditional way of actually geting something done about these sorts of things. I think that many admins are relunctant to take these problems seriously since BCB does most of the NFCC image tagging, which is an extremely important task.  If we create another bot that does the same thing (with open source code that anyone can review and implement, that groups notifications together on user pages and takes other feature requests, etc.) then BCB would been less indespencible.  I'll start working on the problem tonight, and I hope some experienced bot operators will take a look at it as well.  There's nothing technically hard about non-free image tagging, we just need to get cracking on it.  &#10154; Hi DrNick ! 21:00, 5 March 2008 (UTC)
 * User:BetacommandBot/Non-Free Template Useage may be of use. Or ask Betacommand himself for the list of non-free templates he uses to track non-free use. Carcharoth (talk) 23:26, 5 March 2008 (UTC)
 * Actually, scrub that, see Bots/Requests for approval/Non-Free Content Compliance Bot. Hopefully that will help smooth things over, and maybe it will even see some regular schedules being planned for future runs on other operations. Carcharoth (talk) 00:01, 6 March 2008 (UTC)
 * First thing, concensus is very much against role accounts. "Shared with some members of the BAG that BC approves" is not the same thing as open source.  Any sufficently motivated vandal can find scripts to edit Wikipeida in a hurry; making the source availilble is not WP:BEANS, the cat is already out of the bag.  And "as long as the users in question follow my directions" does not bode well for reason.  &#10154; Hi DrNick ! 00:39, 6 March 2008 (UTC)
 * HiDrNick, its not a role account. it is a bot that is operated by trusted users. its just a group of users who all press the same start button. βcommand 00:54, 6 March 2008 (UTC)
 * I have proposed an ammendment on the approval pageMickMacNee (talk) 00:48, 6 March 2008 (UTC)
 * and that amendment will rot in hell. βcommand 00:54, 6 March 2008 (UTC)
 * I'm getting the distinct impression you actually want people to take you on at Rfc rather than try and deal with the bot as a bot without consideration of your people skills. I did have an article project in mind for tomorrow but if you really push me I can set it aside and draw up some evidence. MickMacNee (talk) 01:15, 6 March 2008 (UTC)
 * And you seem to have some sort of vendetta against Betacommand. How would you like if a user was constantly following you around and being a jackass about it?  Maxim (talk)  01:21, 6 March 2008 (UTC)
 * Check your facts, I haven't entered a BC discussion for days, ever since his preferred method of communication on WP, or lack of it, became quite clear, yet it hasn't stopped the regular traffic about him, nor did it not occur before I came along with a good faith attempt at a change of a bot. You will also find when checking that separation of responsibility for NFCC tagging from his bot was one of the first proposals I made in the page that was derailed, stalled at Mfd as an 'attack', and now courtesy blanked because it somehow emotionaly disturbs betacommand to discuss his bot's operation, only for much of its original suggestions to resurface here again without any poking from me. Ever wonder why? This never was about him personally, but he has been determined to move it that way whatever it takes, from day 1. MickMacNee (talk) 01:33, 6 March 2008 (UTC)
 * The only one "being a jackass" in the above conversation is BC. I mean "and that amendment will rot in hell"?!? And you take his side? Wow. Bellwether B  C  01:26, 6 March 2008 (UTC)

Umm, and that amendment will rot in hell ? Nice one Betacommand. Seriously. - <font size="+1" color="red">&#10032; <strong style="letter-spacing:1px;font-family:Verdana">ALLSTAR <font size="+1" color="red">&#10032; echo 05:04, 6 March 2008 (UTC)
 * Not nice but I feel that the amended proposal is not nice either. It seems to suggest that if this bot starts screwing up, either Betacommand loses his BAG status, he ends up releasing his code, or both.  MickMacNee, I do not feel any of these requests are reasonable at all.  One has not even seen this bot in action yet to see if this causes the same amount of ire as BetacommandBot.  I do believe Betacommand is quick to fix problems with his bot in terms of debugging - need we demonise him further?  x42bn6 Talk Mess  05:10, 6 March 2008 (UTC)
 * It is intended to allow code changes agreed by the operators to be implented, otherwise, what is the point in handing over operation, and hence the point of contact for communication about the bot, to these operators. They are then basically just button pushers, just a front for betacommand. In that case what's the differene between this new bot and bcb just creating a separate NFCCbot run by himself? Nothing was said about removing his status, just a recognition that should betacommand stop cooperating with the operators of the new bot, then as the declared code owner, the existance of the separate bot becomes moot. MickMacNee (talk) 12:11, 6 March 2008 (UTC)
 * Hmm, it suggests to me that if the group of ops running it request a change, the change be made or the bot be taken offline. I don't see what's wrong with that?  Is there a situation where this group and BC would differ so much over a change that a showdown like this would even happen, and if so, do we want one person overriding the will of the people trusted to complete this work?  I think the text can be changed such that if the group votes to share the code with somebody whom he refuses to share, he can simply take the bot offline.  The question is whether or not this group will be just a group of yes-men or an actual independent body; if it's the former, it's really not going to fix anything.
 * I also think striking out some of the sections is absolutely warranted given the tone it takes towards editors who have criticized the process; several people here here would freak if "Betacommand and his bot are vilified for the work they do tagging images" was written from the opposite POV: "Unhelpful messages and dismissive behavior have poisoned public opinion of Betacommand and his bot." And "Anti-fair-use people would be shielded from attacks. People will find it much harder to demonize or blame if there's a trusted group of BAG people versus a single individual" is needlessly confrontational and simply invites conflict.    Editors critical of the BCB's operation already face a group of people whenever they comment.  It wouldn't be anything new.  I also don't think it's accurate to categorize them as "anti-fair-use people".  These are simply unnecessary to the proposal and would not change anything if removed. <font color="#4B0082">&mdash;Torc.  <font color="#4F7C4F">( <font color="#4F7C4F">Talk. <font color="#4B0082">) 05:39, 6 March 2008 (UTC)

Block of BetacommandBot reinstated
I have just reinstated the indefinite block on.

The owner, (aka ), remains in breach of an explicit point of WP:BOT policy, viz. "The contributions of a bot account remain the responsibility of its operator. In particular, the bot operator is responsible for the repair of any damage caused by a bot which operates incorrectly." Betacommand has not asisted in any way in undoing the damage caused by the bot's mass removal of red-linked categories, and should not have resumed category-related work before fixing the daamge already caused.

The bot has resumed editing of articles to remove categories, without clearly indicating what it is doing and why. Some of the category removals contain no indication of why the bot is doing this (e.g. ), while others say "per CfD" without indicating which CfD.

The lack of explicit labelling by BetacommandBot of category-related edits is a notable contrast with Cydebot. Cydebot regularly does CfD work, and uses much more useful edit summaries, such as this one which is part of a series clearly labelled "Speedily moving". Where there is a normal, non-speedy CfD, Cydebot uses an edit summary which explicitly links to the discusion, as in this list of edits.

Now that hasd been authorised to do the NFCC work (see WP:BRFA/Non-Free Content Compliance Bot), there is no longer any reason to consider BCbot's work as being so critical that the bot should not be required to comply with policy. Cydebot does the CFD-related work more effectively, so BetacommandBot is not required for that role &mdash; it may be regarded as a useful backup, but it is not essential.

An indefinite block is not. of course, an irrevocable block. A discussion has been underway above on conditions for BCBot's unblocking, and I suggest that discusion should be allowed to continue until a consensus is reached. --BrownHairedGirl (talk) • (contribs) 13:41, 6 March 2008 (UTC)
 * BrownHairedGirl, you have zero ground for blocking. those categories in question where renamed/deleted per valid CfD/U request. I see nowhere in WP:BLOCK that admins are allowed to block for no reason. βcommand 13:50, 6 March 2008 (UTC)
 * (ec x 3)This seems incredibly punitive to me, but, I'm open to hear a better explanation. What are you aiming to prevent, exactly? Also, please, please, please be careful when blocking bots, especially those hosted on the toolserver. Leaving the autoblocker enabled, winds up blocking a lot of unrelated bots. SQL <sup style="font-size: 5pt;color:#999">Query me!  13:58, 6 March 2008 (UTC)
 * Re-read para 2 above: The owner, (aka ), remains in breach of an explicit point of WP:BOT policy, viz. "The contributions of a bot account remain the responsibility of its operator. In particular, the bot operator is responsible for the repair of any damage caused by a bot which operates incorrectly."
 * The bot is being used in breach of a fundamental part of bot policy. --BrownHairedGirl (talk) • (contribs) 13:53, 6 March 2008 (UTC)


 * Bullshit, this this was very standard WP:CFD/WU work. your just pissed that your previous block did not hold water, so you make some un-founded bullshit up to block the bot? βcommand 13:56, 6 March 2008 (UTC)


 * Erm, how is he to repair this damage if the Bot is now blocked? Was it causing any further damage in your opinion? WjBscribe 13:54, 6 March 2008 (UTC)
 * Betacommand, WP:CIVIL please. First, I have not blocked you or bot before. Secondly, the unrepaired damage was nothing to do with WP:CFD/WU. --BrownHairedGirl (talk) • (contribs) 14:02, 6 March 2008 (UTC)
 * As discussed at length in previous threads, the damage could be undone by manual use of rollback, which other editors have been doing. If Betacommand wants to use the bot to revert those edits, thereby saving other users the work of fixing the damage, then I will of course lift the block to allow that to be done. However, so far as I can see, no such offer has been yet made by Betacommand. --BrownHairedGirl (talk) • (contribs) 14:01, 6 March 2008 (UTC)
 * I have spoken with Betacommand and given the Bot rollback for it to accomplish the task. Please unblock the Bot. WjBscribe 14:04, 6 March 2008 (UTC)
 * Thanks for giving BCB rolback powers. I will unblock promptly when Betacommand states clearly requests unblocking (either here on on BcBot's talk) in order to be able to rollback the mass deletion of redlinked categories. --BrownHairedGirl (talk) • (contribs) 14:11, 6 March 2008 (UTC)
 * You have my assurance that the Bot will do this - please unblock the Bot. WjBscribe 14:12, 6 March 2008 (UTC)
 * I appreciate your efforts and naturally assume your good faith, but I don't see why Betacommand himself cannot make an unblock request. If you think that it is in any way unreasonable to ask the Betacommand himself makes the request, pls can you explain why, because it's not obvious to me. --BrownHairedGirl (talk) • (contribs) 14:17, 6 March 2008 (UTC)
 * I've unblocked the Bot myself given Betacommand's agreement. Can I remind you that blocks are preventative? They should be lifted when they are no longer necessary, which this one clearly is no longer given Betacommand is going to remedy the matter. I'm not entirely convinced that the blocking of a Bot with multiple functions because you feel all its operations must wait until a previous matter is corrected is a correct reading of the Bot policy. In any event, I am disappointed both with the technical manner in which you carried out this block and with your reluctance to unblock this Bot when I asked you to do so having taken the time to see your concerns would be addressed. WjBscribe 14:22, 6 March 2008 (UTC)
 * Retrospectively endorsing both BHG's reblock, and WJB's subsequent unblock - both, in the circumstances in which they arose, were fair and reasonable actions. Orderinchaos 21:58, 6 March 2008 (UTC)

I think it's a great pity that has unblocked BetacommandBot without the usual requirement of a public request for unblocking. I do not intend to wheelwar, and will not reimpose the block unless BcBot starts other editing before completing the repair of the damage. However, I still think that an explanation is in order from WJBscribe as to why the unblock was made without a public assurance from that he intended to use the bot to undo the damage.

You are quite right that blocks are preventative. The issue being prevented here was continued use of a bot by a bot-owner who has so far refdused all requests to repair the damage caused by his bot.

As to the method of blocking the bot, that was an error which I immediately set out to remedy, as discussed on my talk: see User talk:BrownHairedGirl. --BrownHairedGirl (talk) • (contribs) 14:31, 6 March 2008 (UTC)


 * I disagree with you, and in fact think that you should have (a) not reblocked the bot, since it wasn't doing anything against policy beyond what it had already been blocked/unblocked for (WP:WHEEL gets people desysopped) and (b) unblocked it yourself, particularly after WjB said your concerns, whatever their merit, would be addressed. Since you failed to do either (a) or (b), WjB is fully justified in unblock the bot himself. <strong style="color:#000;background:#fff;border:0px solid #000">Avruch <strong style="color:#000;background:#fff;border:0px solid #000"> T 16:12, 6 March 2008 (UTC)


 * OK, I'm delighted to see that the bot has begun undoing the damage. However, it should not have taken a further block to trigger this repair, and I would still like to know why Betacommand was not prepared to make his own unblock request. --BrownHairedGirl (talk) • (contribs) 14:36, 6 March 2008 (UTC)
 * Given his profane tirade in response to being blocked, I'd say that he just didn't want to give you the satisfaction of him making his own unblock request. I have to say, I've never seen a less civil user running a bot. Bellwether B  C  14:47, 6 March 2008 (UTC)


 * What "usual requirement of a public request for unblocking"? There are several legitimate ways to get unblocked, without making an on-wiki request. We've got a private mailing list for it (https://lists.wikimedia.org/mailman/listinfo/unblock-en-l), and IRC Channel #wikipedia-en-unblock on freenode, a user may e-mail an administrator (or, contact them, via any other means), or, a user may contact arbcom. Exactly where's it required that all unblock requests be made on-wiki? SQL <sup style="font-size: 5pt;color:#999">Query me!  05:00, 7 March 2008 (UTC)

I should very much hope you do not intend to wheel war - I find it odd that you should need to announce this. I'm afraid "asking nicely" is not a precondition to unblock. It never has been and I hope never will be. As to you other comment, as long as the Bot is repairing damage, I do not think it should be prohibited from performing other tasks. As I see it, you are certainly not entitled to reblock the Bot simply if it also makes other edits it is approved to make before all the edits you feel should be reverted have been. WjBscribe 14:53, 6 March 2008 (UTC)


 * As to "refused all requests to repair the damage", this is patently false. I asked Betacommand to program his Bot to revert the problematic edits. He said he would need rollback to assist with this. I gave the Bot rollback and the edits are now being reverted. WjBscribe 14:57, 6 March 2008 (UTC)


 * Several points here. First, I announced "no wheel-war" for the avoidance of any misunderstanding about my intentions, because I feared that if I didn't, then in the heated climate here my good faith in that respect might not be assumed.  Better, I thought. to clarify upfromt than to try to explain afterwards.
 * Secondly, it is not "patently false" that he had refused all requests to undo the damage until he was blocked; all that happened was that you claimed after the block that BCB had made a private assurance to you that he would revert. If you dispute that, please could you show me the diffs of BCB's offer to repair? The last I saw from BC was his abusive reply above.
 * What is the point of WP:BOT including a repair-all-damage requirement if an uncivil bot-owner simply ignores that policy? Like any other bot, BCB is required to undo its damage.  Despite Betacommand's ever-so-civil description of the block as "un-founded bullshit", it succeeded in preventing BcB from continuing to ignore that policy. I count that as a very effective and appropriate use of a block. --BrownHairedGirl (talk) • (contribs) 15:20, 6 March 2008 (UTC)
 * What I disputed was that it would be appropriate to reblock the Bot if it performed tasks other than reverting those edits before you judged those reversions were complete. Provided those edits are continuing to be undone, I do not think the completion is a pre-requisit to Betacommand performing the other tasks it is approved to do. As long as the reverts are reverted in due course, everyone should be happy - restoring redlinked categories is hardly a time-sensitive task. And he cannot have refused all requests if he agreed to mine, surely that is incontrovertible? WjBscribe 15:27, 6 March 2008 (UTC)
 * Sorry, my point stands. Until blocked, BCB had refused all requests to undo the damage: if you think I am mistaken, please show me the diffs.
 * Given the complete lack of any public statement of intent by BC to undo the damage, and the disgraceful fact that there was not even a private offer to do so until the block was imposed, I had no reason to assume good faith from Bc in this regard, and it would have been perverse to do so. I am not aware if any of BCbot's other tasks being not so time-urgent that they must take priority over the required damage repair, and in the absence of any public assurance of damage removal, there was no reason to assume in good faith that Bc would resume the "un-founded bullshit" damage repair if he stopped.
 * Further, there is a time0semnsitive aspect to the damage repair: rollback can't fix the problem if further edits have been performed on the page. The longer the repair was delayed, the less thorough any repair would be. --BrownHairedGirl (talk) • (contribs) 15:48, 6 March 2008 (UTC)

The new edits were valid UCFD work (located here) that I specifically asked BC to work on, as I didn't think there would be any problem. While the edit summaries could have been more clear, it wouldn't have taken much diligence to figure out that the edits were valid UCFD work. VegaDark (talk) 16:08, 6 March 2008 (UTC)\

Re wheel warring and Brown Haired Girl - announcing that you won't wheel war after having done so is sort of meaningless, wouldn't you think? The bot was blocked for a specific problem, and unblocked based on a consensus demonstrated above (despite your objection there). Without evidence of a reoccurrence or additional violation, you reblocked the bot based on your opinion that it should not have been unblocked initially. This is the definition of wheel warring, and you should both be more careful and more respectful of the opinions of others. <strong style="color:#000;background:#fff;border:0px solid #000">Avruch <strong style="color:#000;background:#fff;border:0px solid #000"> T 16:14, 6 March 2008 (UTC)
 * Nonsense; please re-read my explanation at the start of this thread. I did not "reblock the bot based on your opinion that it should not have been unblocked initially"; I did not think that it should have been unblocked, but I accept that there may have been consensus to unblock, and certainly no consensus to reblock for that offence. I blocked it today for a different reason: because the bot-owner had failed to repair the damage as required by policy WP:BOT. The result of that was that despite the abusive response, Betacommand did undo the damage.
 * If you have any alternative suggestions about how to enforce that aspect of bot policy, then please set them out so that they can be discussed. --BrownHairedGirl (talk) • (contribs) 16:50, 6 March 2008 (UTC)


 * Sorry, its not nonsense. BC isn't reverting his actions because you made the block - he is reverting it because WjB convinced him to in order to appease you. The actions are being reverted in spite of your action, because you refused to unblock the bot. WjB unblocked it over your objection in order for the work you wanted to begin. So what damage were you preventing, and what action did you take that led directly to an outcome you were trying to achieve? How often are users/bots blocked for passive violation of a policy? <strong style="color:#000;background:#fff;border:0px solid #000">Avruch <strong style="color:#000;background:#fff;border:0px solid #000"> T 17:23, 6 March 2008 (UTC)
 * Avruch, I'm really not sure what you are trying to claim, but it is spectacularly silly to claim that damage was undone in spite of me. The action I took of blocking BCbot led directly to the damage being fixed, and it is bizarre to suggest that BC's preference for communicating on IRC (or somewhere other than this page, I'm only guessing that it was IRC) rather than on talk pages somehow breaks that link. If you re-read the discussion above, you will see that I did not object to unblocking to allow the work to be done; I objected to unblocking until Betacommand  confirmed on wikipedia that was his intention, when his abusive response earlier had given every reason to question his good faith. --BrownHairedGirl (talk) • (contribs) 18:01, 6 March 2008 (UTC)


 * Well, I don't think I'm being unclear. I also don't appreciate that you described my first comment as "nonsense" and my second as "spectacularly silly." You clearly don't understand my point, so I won't try making it again. Suffice it to say, I don't think it should have been blocked and I dispute each instance of your reasoning before and after. (See, however, my comment below regarding civility). <strong style="color:#000;background:#fff;border:0px solid #000">Avruch <strong style="color:#000;background:#fff;border:0px solid #000"> T 19:14, 6 March 2008 (UTC)
 * Avruch, it's not complicated. Two days after the redlinked acts were removed, and after numerous requests for them to be reinstated, Betacommand had done nothing to restore them or to offer in any way to undo the edits for which his bot was not authorised, leaving other editors to try to manually rervert 2000 edits. Yet within minutes of his being blocked, he had begun a mass rollback ... and I stand by my comment that it is "spectacularly silly" to claim that the reversion happened in spite of my block. --BrownHairedGirl (talk) • (contribs) 19:39, 6 March 2008 (UTC)

I've been following this from the start, and I have to say that BrownHairedGirl's logic is impeccable here. She was fully justified in blocking, and the toolserver needs to not put all its eggs in one basket. The only reason I can see that Betacommand did not undo the previous damage was because he thought that the damage was being undone by others, slowly, manually. But still, just a little bit more communication from Betacommand, and this could have been avoided. And no, communication on IRC does not count. I don't like seeing on-wiki communication and discussion processes avoided, like the recent case of a bot request that was speedily approved 2-minutes after the page was created. Carcharoth (talk) 17:08, 6 March 2008 (UTC)


 * So, Betacommand didn't undo the damage himself but it was being undone by others. There was some disagreement above whether any damage per se actually occurred. BrownHairedGirl believes that there was damage, and that Betacommand was refusing to do it. She mentioned that BCBot was doing more similar work, which she thought might be a repeat of the same previous problem (according to VegaDark, it wasn't). But according to the statement right above, BCBot was blocked not because she thought it shouldn't have been unblocked, and not because the bot was taking more actions of the type that got it blocked before, but because he wasn't actively participating in the effort to revert the prior actions. I've done a portion of the reverts myself, but as I noted above - this isn't because I agree necessarily that what BCBot did was damaging, but because some folks thought it was and its easier to fix it than argue about it. It seems like if you want to block a bot for not repairing damage, you should be sure everyone agrees that damage was actually done. Furthermore, the bot policy doesn't require the bot to repair the damage, it requires the bot operator to repair the damage. Why, then, did you block the bot instead of Betacommand himself? And what, either way, were you preventing with the block?


 * Now, on to Carcharoth - as far as I'm aware, people aren't often blocked for not being more communicative. I understand and agree that far better communication from Betacommand is warranted and would dramatically improve this and all related problems. I also think that all BCBot functions should be duplicated by other bots, particularly if Betacommand has not made progress doing this himself. Unless you're saying BCBot should be blocked because of the sum of all prior problems, this issue should be and has been evaluated on its own merits. If BCBot wasn't causing any damage, and it had been blocked and unblocked already after discussion about this same incident... Then there is no justification for blocking it again without first seeking consensus to do so. <strong style="color:#000;background:#fff;border:0px solid #000">Avruch <strong style="color:#000;background:#fff;border:0px solid #000"> T 17:19, 6 March 2008 (UTC)
 * There was justification to block, you just refuse to acknowledge it. He was using his bot while refusing to correct the damage that bot had done, forcing normal editors (read: not bots) to slowly undo the damage themselves. This is blockable, and not wheel-warring in the least. Please stop explicitly calling it that, and tacitly implying it with the "without first seeking consensus" nonsense. He was blocked for a different problem than the first issue, which is not wheel-warring, even if he shouldn't have been unblocked in the first place. Bellwether B  C  18:52, 6 March 2008 (UTC)
 * I have defended BetacommandBot in the past. But I am growing more and more concerned that amongst all the false accusations lobbed at the bot, there are also very real concerns about the lack of response to community desires mixed in.


 * When considering a block against a bot it is important to remember it is not a human. You can block for much lesser reasons than one would block a human, specifically to prevent damage and ensure responsibility. I shut down one of my bots because I did not have the time to repair a bug in it. <font color="Red">(1 == 2)<font color="Green">Until  17:28, 6 March 2008 (UTC)


 * I need to address what WJBscribe said above. Betacommand had refused requests to fix what happened, as evidenced by the fact that individual users, including myself, had to begin to revert the edits manually. WJBscribe, your comment was very misleading. If Betacommand had simply agreed to revert the damaging edits (after his bot being granted rollback, which is minor), there wouldn't have been a big problem.  Enigma  msg! 18:05, 6 March 2008 (UTC)
 * WJB is operating in the utmost of good faith, and I strongly commend him for negotiating with Betacommand to get him to follow policy and fix the situation he had created - as a result of this the immediate situation is now resolved - but it concerns me greatly that it took two blocks and all of the above discussion to get BCB to follow policy on this, and this incident and Betacommand's responses have done nothing to convince me that there will not be further violations of this kind (in fact Betacommand has admitted to previous violations as a defence for his current one). Orderinchaos 21:58, 6 March 2008 (UTC)
 * And therein lies the problem. He shouldn't have had to "negotiate with Betacommand to get him to follow policy and fix the situation he had created". Betacommand has practically been nothing but silent on these issues and when he has spoken, it's been nothing but foul-mouthed incivility. Comments like "that proposal will rot in hell" and "unfounded bullshit" aren't productive when people are already pissed that you can't control your bot and refuse to control it. Any other editor would have been blocked for Betacommand's brand of incivility! - <font size="+1" color="red">&#10032; <strong style="letter-spacing:1px;font-family:Verdana">ALLSTAR <font size="+1" color="red">&#10032; echo 22:45, 6 March 2008 (UTC)
 * I agree - and I think it's heading to ArbCom sooner rather than later. Had BC cooperated initially none of this would have been necessary. My only point above was that WJB was making the best of a bad situation which was strictly speaking well outside his control, and his successful efforts to broker a diplomatic deal to resolve the immediate situation (i.e. the one causing grief to about 2,000 editors re categories) deserve commendation rather than criticism or accusations of misleading people. The longer-term problem is for the community to solve. Orderinchaos 00:49, 7 March 2008 (UTC)

Bizarrely today I encountered an edit where this morning a spammer/vandel/noob managed to edit a stub template cat into a spam like red link cat. It beggars belief that bcb could just come along, delete that 'bad cat' from the more than one pages worth of stub articles, and do precisely nothing to fix it, and even expect editors to use his contribs to locate all the lost articles. It just happens that I noticed the odd red colour and investigated, proving red cats do attract attention if left alone. Bearing in mind most were stubs, and therefore likely never to see human eyes again, lost in the orphansphere. MickMacNee (talk) 18:41, 6 March 2008 (UTC)

More verbal abuse from Betacommand
I'd like to know whether any of the IRC crew would like to stand up and publically say that they think that this sort of behavior is appropriate. I'm sure there's some long, involved, complicated rationale that explains how it's OK to call BrownHairedGirl a "dumbass" and a "dick". When will enough be enough? Nandesuka (talk) 17:52, 6 March 2008 (UTC)


 * No, it is not at all appropriate. That language, by itself, could merit a block - particularly because he has been warned many, many times about civility. <strong style="color:#000;background:#fff;border:0px solid #000">Avruch <strong style="color:#000;background:#fff;border:0px solid #000"> T 18:42, 6 March 2008 (UTC)


 * None of this behavior will change until Betacommand himself is blocked for his refusal to communicate civilly with those who disagree with him strongly, his bot is reworked, and the community is allowed to contribute to the improvement of the tools (read: bots) that work with tagging our images, deleting our categories, and so one. Bellwether B  C  18:57, 6 March 2008 (UTC)


 * He then reverted Bellwether's comment without explanation, which is pretty rude. He does it all the time, but it's still rude. I don't really care how much "shit" he takes or whatever excuses some want to make. This kind of behavior is unacceptable.  Enigma  msg! 22:38, 6 March 2008 (UTC)


 * Well, I just put on my Administrator hat, & left a formal warning for incivility on his talk page. For a long time I thought BetaCommand had cleaned up his language & learned how that helps him; I am honestly disappointed that he's back to his old habits. However, I'm leaving it to another Admin to enforce this warning if he is incivil again. My intent is to get him to stop the language, not block him. -- llywrch (talk) 22:56, 6 March 2008 (UTC)


 * "Vandalism". That's awesome. &#10154; Hi DrNick ! 23:05, 6 March 2008 (UTC)


 * Well, I'm not getting into an edit war with him over that. Removing it means he's seen it. -- llywrch (talk) 23:12, 6 March 2008 (UTC)


 * He lacks the temperament to be a constructive contributor here. This has been clear for quite a while now.  I imagine even the most fervent excuse-makers are out of them by now.  I imagine arbcom is the only way forward- I doubt a community ban would fly.  There are always those willing to bend over backward to defend indefensible behavior from longtime contributors.  I hope this is changing, but I'm not sure it's changed sufficiently yet.  Friday (talk) 23:14, 6 March 2008 (UTC)


 * One thing I've observed about Betacommand: he gets tonnes of brickbats, he gets grouchier and grouchier, but the bot just trundles on. It wouldn't be doing that job if we either didn't think it needed to be done or thought we should do it ourselves.  While there are many of us who are capable of constructing and operating a bot of that kind, few of us would have the sheer tenacity to stick at it.  If even Betacommand isn't a constructive contributor, I don't think any of us has a right to the term. --Anticipation of a New Lover's Arrival, The 05:19, 8 March 2008 (UTC)


 * If the bot is useful but the operator is problematic, there sure appears to be an obvious solution. Beta can give his code away, but continue to help out with further development (preferably, helped by a more experienced developer who can solve some of the technical problems he's unable to address.)  Get him out of the business of operating the bot- leave that to someone with better communication abilities, who isn't so sick of being trolled that he sees trolls where there are none.  Problem solved.  Friday (talk) 16:22, 8 March 2008 (UTC)


 * If it were simply a matter of writing code, there'd be dozens of these bots running. It is not difficult to write an automated tool that can handle http transactions at high speed.  There is no horde of skilled communicators waiting to do the job but unable to find a single programmer as talented as Betacommand.  Rather, we have an embarrassingly high geek factor for an encyclopedia project, but few of us are willing to taken on the job. --Anticipation of a New Lover's Arrival, The 00:20, 9 March 2008 (UTC)

Blanking cats

 * Perhaps even worse than the language is that Betacommand still maintains that blanking slightly misspelled cats rather than actually fixing them was, and is a good thing for our project. There appears to be a fundamental lack of understanding of the care we need to have for our data and users; the editor appears to fetishize the automated aspect of WP above all else and see his/her work simply as a task, rather than something to be lovingly and carefully worked with, in order to ensure maximum usefulness for our readers. This would explain why, until now, the editor did not lift a finger to assist in the actual fixing of the many misspelled redcats, which many of us who do not operate bots have been doing by hand over the past few days in an effort to undo his/her bot's damage. Badagnani (talk) 18:05, 6 March 2008 (UTC)


 * I want to clarify that I believe "nonsense" cats (such as "Category:xidsoiueru Wikipedians"), as well as cats deleted by consensus at CFD, should be removed, and a bot is a fine way to do that. But that should be done in a targeted manner, just deleting the ones that have been agreed upon, with records kept as to which ones have been deleted. Deleting slightly misspelled cats was wrong and damaging to our project. The fact that Betacommand still will not acknowledge this distinction is disturbing, as it does not reflect community consensus regarding our goals. Badagnani (talk) 18:15, 6 March 2008 (UTC)

For consideration
I hope it's not too much to ask that Betacommandbot's behavior with regard to Fair Use warnings and the policy Assume good faith be discussed a little bit. I lodged a more detailed complaint at User talk:BetacommandBot, but it was removed without comment (diff). The edit summary said it was "archived", but it was not added to User talk:Betacommand/20080201 or any other archive I've been able to find. --Dystopos (talk) 18:22, 6 March 2008 (UTC)
 * You had a really good point there. I'm sorry your post got "lost" and was not archived despite Betacommand's saying so. I suggest you repost it in case it was an oversight. The point of helping out fellow WP editors in a spirit of cooperation, and putting our data and users first is a really key one. Badagnani (talk) 18:25, 6 March 2008 (UTC)

Please see User talk:Betacommand/20080301. βcommand 18:30, 6 March 2008 (UTC)
 * There it is. Thanks for updating the archives. Do you have a response to my charge that the bot's current behavior is inconsistent with Wikipedia policy, or is the lack of comment your response?--Dystopos (talk) 18:37, 6 March 2008 (UTC)
 * its behavior is exactly within policy. When adding to wikipedia, its the writer/uploader to prove inclusion, not for everyone else to prove exclusion. if you cant follow the image policy why should I be forced to clean up your errors? βcommand 18:41, 6 March 2008 (UTC)
 * "[I]f you cant follow the image policy why should I be forced to clean up your errors?" Yet another uniquely helpful response from BC. When will this end? Bellwether B  C  18:55, 6 March 2008 (UTC)
 * To answer your question, because you are a contributor to Wikipedia, not a branch of the secret police. As a member of the community your first responsibility is to be helpful. That is why "assume good faith" is a policy. Any human editor would be expected to offer help rather than grief when encountering an image used without sufficient rationale. I think we should expect the same from a bot. Perhaps the bot could compile a list of alerts for review rather than slapping warnings around. This is especially aggravating to those of use who uploaded content before the requirement for explicit and discrete fair use rationales was elaborated. You're insisting that we are renegade flaunters flouters of the image use policy, but there was a time when the generic templates were presumed to suffice. --Dystopos (talk) 19:41, 6 March 2008 (UTC)
 * Comment - The term is "flouters," not "flaunters." Badagnani (talk) 19:42, 6 March 2008 (UTC)
 * I could have better explained myself by saying that the presence of a problem does not create a responsibility for someone else, merely an opportunity for improvement. We should work to identify and take advantage of such opportunities without assigning tasks to others, or perceiving that tasks are assigned to us. Accepting responsibility for improving Wikipedia is voluntary. Causing problems is the real issue. Allowing them to go uncorrected is better than causing new ones. --Dystopos (talk) 20:16, 6 March 2008 (UTC)
 * "Allowing them to go uncorrected is better than causing new ones." Err, what? Allowing them to go uncorrected made a massive behemoth of an image cleanup job (that was growing at an alarming rate) that is finally manageable thanks to the tagging work of BCB and other editors. -- Ned Scott 01:38, 7 March 2008 (UTC)
 * If we could remove all the incivility from Wikipedia by uploading a few nonfree images, would the ends justify the means then? I'm saying we should excuse honest oversights more readily than automated assumptions of bad faith -- or at least find more productive (as compared to combative) means of dealing with our "to-do lists" --Dystopos (talk) 04:14, 7 March 2008 (UTC)
 * BC isn't passing judgement in the act of tagging. He might be thinking that, he might not be, but the tagging is all the same. -- Ned Scott 05:11, 7 March 2008 (UTC)

Oh, grow up already!

 * 1) The task the BCBot does is necessary. Some people may dislike what the bot does, but it will be done regardless, because it must be done.  Learn to live with it.
 * 2) The bot performs its task in a technically appropriate manner. There is a great deal of whining about what the bot does (see point 1 above), but it does it correctly.
 * 3) The messages left by the bot might be improved. I've yet to read positive suggestions on the matter, however.  Stop complaining about the prose without telling exactly what is wrong with it and propose a fix.

Betacommand himself is oftentime curt, short and/or rude. It can be explained simply enough, but it's not an excuse. However, I have stunning news for many of the people involved in this: Heaping (often vitriolic) abuse repeatedly on someone rarely helps improve attitude. Astonishing, I know, but since I've been around, Betacommand has been maliciously attacked repeatedly. That word was not chosen randomly. I've seen outright lies, nit picking, cherry picking out of context diffs, calls&mdash; demands&mdash; for blocks and bans, personal attacks, aspersions, accusations of bad faith, of deletionism, of pursuing vendettas, etc., etc., etc. And then people complain that, in response to all this venom, he isn't in good humor.

The only reason for all this conflict is because there are some people who don't agree with points 1-3 above. Work to change the effing policy if that's the case, because BCBot is entirely within it. Not liking the policy BCBot is helping apply is not an excuse to attack the bot&mdash; let alone its handler!

Work to change the policy if you disagree with it. Convince the Foundation to modify its stance. That is your only recourse. Any attacks on any editor or tool that is applying that policy is at best pointy and in bad faith, or at worst personally motivated malice.

I don't suppose I'm going to become very popular by taking such a stance, but I'm tired of seeing hard working contributors to the encyclopedia being attacked over and over because they are working hard for the encyclopedia. &mdash; Coren (talk) 19:09, 6 March 2008 (UTC)
 * "Grow up already"?!? Are you effing kidding?!? Show me where BHG did anything to deserve how he responded to her. Blocking his bot is not an excuse for being a jerk to the blocking admin. The sooner BC's apologize quit making excuses for his incivility, the quicker we'll perhaps be able to actually get him to change those behavior patterns. Bellwether B  C  19:17, 6 March 2008 (UTC)
 * Please see my full response on my talkpage. BHG violated multiple policies, including using admin tools in a content dispute to force her POV. βcommand 19:20, 6 March 2008 (UTC)
 * Betacommand, I despair. You used your bot for an unapproved task, you did not tidy up the damage, and now your are trying to claim that an admin who objects to that is in a content dispute with you? Are you serious, or are you just trying to hasten the path to arbcom? --BrownHairedGirl (talk) • (contribs) 19:31, 6 March 2008 (UTC)
 * Huh? More than half of this page is, by now, not at all about the three points you mentioned above. So saying that this conflict is only happening because of people disagree with these three points doesn't quite make any sense to me. --Conti|✉ 19:25, 6 March 2008 (UTC)


 * Coren, this block had absolutely nothing to do with image tagging work or NFCC. Have you even been paying attention? Are you, in fact, unaware that there are multiple tasks routinely performed under the BetacommandBot account? —Random832 19:50, 6 March 2008 (UTC)


 * Ahem. See also straw man argument.  &#10154; Hi DrNick ! 19:51, 6 March 2008 (UTC)


 * Ahem. If you want to bring it up again, even though this block is for yet another (possibly unauthorized) bot function, point 2 is disputed by almost all people who have checked.  As βcommand is not willing to release the code, we would have to take his word for it, so that ANY error, even one probably caused by a Wikipedia glitch, is strong evidence of a bot error, until proven otherwise.  &mdash; Arthur Rubin  (talk) 20:09, 6 March 2008 (UTC)


 * Um, Coren, you might want to actually read the debate. The block and recent discussion has nothing to do with fair-use work, but to do with work (removing red-linked cats which had not gone through CfD) that BC took on which is against bot policy, is unauthorised, and which has caused tremendous amounts of disruption. The worst part is that this is neither the first nor the last time we have seen this sort of violation, and the defence that the bot is necessary becomes weaker on every occasion that there are blatant violations. Orderinchaos 21:42, 6 March 2008 (UTC)


 * Ignoring the fact that this particular issue has nothing to do with NFCC/fair-use rationales, I will address point #3....Positive suggestions re: improving those messages HAVE been offered; for example, a suggestion was discussed in which the bot would be altered to leave ONE message per run with a LIST of images for a given user, rather than a litany of individual messages for one image each. However, between BC's uncertainty on how this might be accomplished easily, and the sound and fury of others NOT involved in offering real suggestions, the suggestion--like others--was abandoned, lost in the yelling. People have offered suggestions on how to improve the messages; they have not been accepted.Gladys J Cortez 23:32, 6 March 2008 (UTC)
 * Gladys J Cortez the one suggestion that you brought up, is something ive been thinking about/trying to develop. yes it sounds very easy but its not. Lar has seen the code and will agree its not a simple fix. Ive come up with a dozen or two different methods of implementing this, but each one has serious problems and end up not being feasible with the code. βcommand 23:40, 6 March 2008 (UTC)
 * As I've said, I have ZERO programming experience, so about all I can do is toss out ideas. I've also discovered, though, that it's never wise to toss things while standing in a minefield--even if you're lucky enough not to hit a mine, it's rare to find a catcher. :) But since the NFCC/fair-use stuff is mostly done anyway, it's a bit of a moot point--I just wanted to counter point #3 with the example I knew of personally. Gladys J Cortez 00:21, 7 March 2008 (UTC)

Put simply? Everything else is nit picking and hunting for imaginary faults caused by the tagging spree. What glitches various functions of BCBot might have had were minor and would have normally caused no more drama than a quick note on BC's talk page for a quick fix. My point is that the reason why there is drama at all is retribution for the perceived evil of the NFCC tagging, or well-intended people caught up into the mob feeding frenzy fueled by same. &mdash; Coren (talk) 00:04, 7 March 2008 (UTC)
 * There _was_ a note on his talk page, originally. He first tried to justify the edits (by claiming "CfD work" for categories that had never seen CFD), then he was blocked, then he claimed that the block was unjust because he'd actually stopped the task (without having said he would stop it) a minute and a half before the block, then he was asked to do the cleanup, then he refused to do the cleanup, then the bot was blocked again. He has still made no assurance he will not run the unapproved task again in the future. —Random832 00:21, 7 March 2008 (UTC) - P.S. He has, I'm told, since agreed to do the cleanup work, but... Coren, is it your contention that the same behavior and the same attitude, from a bot operator who had never done image tagging and only did category work, would not have earned a block for the bot? —Random832 20:28, 7 March 2008 (UTC)
 * The original comment that opened this section is not helpful at all. How many times does it have to be stated that many of the people who have complaints about the way Betacommand and/or his bot do things have these complaints not because of the policy, but because of the way Beta handles it? Telling everyone to "[effing] grow up" when you have very clearly not read the entire discussion (which has gone on for weeks) is downright rude and not at all helpful. Do you know the various issues that have sprung up around Beta and his bot? Did you know about the null edits to the mainpage? Did you know about Beta using his bot to deliberately vandalize User:MickMacNee's Talk page? Did you know about the religion edits? (arguably not his fault) Did you know about the most recent issue? Did you in fact read the discussion before making a rude comment towards many of the editors involved in this dispute?  Enigma  msg! 06:39, 7 March 2008 (UTC)


 * "What glitches various functions of BCBot might have had were minor and would have normally caused no more drama than a quick note on BC's talk page for a quick fix. My point is that the reason why there is drama at all is retribution for the perceived evil of the NFCC tagging" - This is absolutely incorrect. Minor glitches?  Enigma  msg! 06:45, 7 March 2008 (UTC)

I think this is a good idea; I doubt anyone else does
What do you think of a voluntary 12 hour cooling off period before anyone posts to this page again? The issues will all still be here tomorrow, and lots of people on both sides appear to be seriously pissed off right now, and getting moreso each post. --barneca (talk) 19:47, 6 March 2008 (UTC)
 * Nah, I'm not pissed. Are you pissed? <strong style="color:#000;background:#fff;border:0px solid #000">Avruch <strong style="color:#000;background:#fff;border:0px solid #000"> T 23:15, 6 March 2008 (UTC)
 * Not everybody, just "lots of people". Anyway, looks like it didn't fly. --barneca (talk) 01:06, 7 March 2008 (UTC)
 * I was perfectly calm until I read the above section. Is it too much to ask that people read through the material before making blanket accusations?  Enigma  msg! 06:47, 7 March 2008 (UTC)

A party who has stumbled on this mess
I was wandering around the back corridors of Wikipedia and came across this mess. Just wow. Then I came across this quote from Jimbo and thought it appropriate: "I think we really need to much more strongly insist on a pleasant work environment and ask people quite firmly not to engage in that kind of sniping and confrontational behavior. We also need to be very careful about the general mindset of "Yeah, he's a jerk but he does good work". The problem is when people act like that, they cause a lot of extra headache for a lot of people and drive away good people who don't feel like dealing with it. Those are the unseen consequences that we need to keep in mind. --Jimbo Wales (talk) 22:51 5 February 2008 As someone who has no dog in this fight, I just toss this out as it seems that even BC and BCb's supporters think he's often uncivil. <font face="monospace" color="#004080"> Legotech &middot;(t)&middot;(c) 19:48, 6 March 2008 (UTC)
 * I would agree with that sentiment completely. It seems that over all the dozens of arguments regarding BC/BCB, the best defense his defenders can ever muster (and do so repeatedly) is "The bot is operating within the rules!". Which sounds, to me, like blatant admission of rules lawyering. Clayhalliwell (talk) 20:27, 6 March 2008 (UTC)
 * Civility is a rule. --Dystopos (talk) 20:47, 6 March 2008 (UTC)
 * BCBot's detractors have hardly been the model of civility either. Mr.  Z- man  05:54, 7 March 2008 (UTC)
 * That's bunk. When have we called other users "dumbasses" or ranted and raved like BC has been doing? He gets away with far more incivility than any of his legitimate "detractors" (not the crazy types that write basically nonsense on his page, but people who actually try to engage him) ever do. Bellwether B  C  05:59, 7 March 2008 (UTC)
 * I'd say all involved (BC, his supporters, his detractors, even myself) have probably not been model Wikipedians throughout the last year. Yes we can argue about degrees of civility, but none of us have perfectly clean hands.  MBisanz  talk 06:14, 7 March 2008 (UTC)
 * Whether or not everyone engaging Beta has been civil is not the point. The point is whether Beta has been civil, and if not, what should be done?  Enigma  msg! 06:49, 7 March 2008 (UTC)

Time for an Rfc of Betacommand?
Frankly I've had enough now. Despite trying to keep discussion focused on the bot for about three weeks now, betacommand is determined to turn every single discussion into an attack on him, and thereby invoke IAR in the responses, if responding at all. Tonight he has decided to start involving himself in my edits elsewhere in articles that have nothing to do with him or his bot, as if he is not busy enough, in clear violation of WP:POINT. I have enough evidence, anyone who is likeminded in the opinon it's time for a user based action now, comment below, and we'll see where we go from there. MickMacNee (talk) 23:07, 6 March 2008 (UTC)
 * I'm not defending Betacommand's behaviour, but it's obvious he's under considerable stress pressure, and you attitude and behaviour isn't helping, which is not exactly better than Betacommand's.  Maxim (talk)  23:11, 6 March 2008 (UTC)
 * What is wrong with my attitude? Every objection I have made here and elsewhere is mirrored by others. Line in the sand time, if betacommand can't hack it, he should put away his hobby and find another past-time, his wannabe programmer attitude affects too many people on WP to be continualy let off like a naughty but favourite child in flagrant denial of most core policies, daily. Enough is enough. MickMacNee (talk) 23:16, 6 March 2008 (UTC)
 * (ec)Normally I'd agree with an RfC. But twice now  and  BC has seemed to indicate a preference for an RFAR as the next step.  I'm tied up until later tonight, but may begin drafting one to see if when I try to compose a picture of the situation, an RFAR maeks sense.  MBisanz  talk 23:17, 6 March 2008 (UTC)
 * MickMacNee, you're supposed to be communicating with a fellow human being not an ass, and you don't seem to realise that. You're showing Betacommand no respect nor patience. We're all humans and we all have faults, and me, you and Betacommand all obviously have them.  Maxim (talk)  23:20, 6 March 2008 (UTC)
 * What Maxim said. I'm not sure it's useful to berate anyone, especially not Beta... it's rather a thankless job and we're down to the wire here. ++Lar: t/c 23:22, 6 March 2008 (UTC)
 * Lar, that thankless job for which we are down to the wire (no disagreement on either of those assertions) is, according to most of what I've read here, done or close to done. If that were the ONLY issue, I would share your concern that an RfC/RfAr would be unnecessary "berating"--but there are many, many other issues under consideration here. (Having said that--I don't favor Mick MacNee's handling of the situation, either; dispassionate, evidence-based claims will always get farther than invective and hectoring, and MMN, you might do well to remember that.)Gladys J Cortez 23:41, 6 March 2008 (UTC)
 * Three weeks of patience, accusations and incivility should be too much, but not even content with vandalising my talk page, now he pointily stalks my edits. Would you accept the same? Like I said, he was not the issue, until now. MickMacNee (talk) 23:25, 6 March 2008 (UTC)
 * Any action is fine by me if there is general agreement here. MickMacNee (talk) 23:25, 6 March 2008 (UTC)
 * MickMacNee, your posts here are becoming uncivil and provocative, to the point it's really disruptive. This is becoming kinda damaging, so instead of blocking you outright, I'm banning you for 6 hours from this page. Please feel free to edit here when you contribute constructively.  Maxim (talk)  23:30, 6 March 2008 (UTC)
 * You are blocking me for 6 hours? How is that justified. You have just placed a barnstar on bc's page for 'putting up with all the crap', and you now want to act as an impartial admin? MickMacNee (talk) 00:00, 7 March 2008 (UTC)
 * No, you're banned from posting to this page for six hours. Adios.  Maxim (talk)  00:02, 7 March 2008 (UTC)
 * That block is out of line, seriously. Especially from someone who has just given Betacommand a barnstar for "For all the crap that you've been facing for the past few weeks.". I urge you to reconsider your conflict of interest in regards to this 6-hour block. - <font size="+1" color="red">&#10032; <strong style="letter-spacing:1px;font-family:Verdana">ALLSTAR <font size="+1" color="red">&#10032; echo 00:05, 7 March 2008 (UTC)
 * I don't know if anybody realises but Maxim has just blocked MickMacNee for a week - and not just from this page. Orderinchaos 00:50, 7 March 2008 (UTC)
 * I think a 6 hour voluntary cooldown might not be a bad idea, because you really do seem a bit upset. Whatever point you want to make can wait a bit, can't it? I wouldn't enforce it by block, just by a polite request. Civility BLOCKS never work but civility requests sometimes do. ++Lar: t/c 00:30, 7 March 2008 (UTC)
 * RFCs are for getting community feedback. That is not something we're lacking here.  I don't see what useful thing could be accomplished.  Friday (talk) 23:23, 6 March 2008 (UTC)


 * Undo Mick's block now. There was no reason for it, and it should never have happened. Questioning BC is not a reason for a block. Period. Bellwether B  C  00:54, 7 March 2008 (UTC)
 * It looks like, according to the block log, the block is meant to be unrelated to this page/discussion or the topic ban. There was a warning to MickMacNee about edit warring and that is the reason he was blocked (according to the log). <strong style="color:#000;background:#fff;border:0px solid #000">Avruch <strong style="color:#000;background:#fff;border:0px solid #000"> T 01:00, 7 March 2008 (UTC)


 * He wasn't just blocked for this - he's just come off a block for edit warring and continued to edit war. He's been editing disruptively in other areas.  Ry an P os tl et hw ai te  00:59, 7 March 2008 (UTC)
 * How amazingly coincidental that he was blocked for other disruption by an admin who just happened to be involved in a dispute with him elsewhere. I'm glad I don't really get into much controversial editing (save protecting Barack Obama from POV-pushers) on here. You never know when something "coincidental" might happen to me! :p Bellwether B  C  01:06, 7 March 2008 (UTC)
 * The block, coming from an admin who had just posted a barnstar on Betacommand's page "For all the crap that you've been facing for the past few weeks," should be reversed, and the blocking admin should apologize for it. Badagnani (talk) 01:03, 7 March 2008 (UTC)
 * I agree, it looks bad. Maxim was talking about unilaterally banning MickMacNee from this page (I don't think this would have had universal approval), and the block coming soon after that looks like someone went looking for a reason to block. I don't think Maxim did do that, but it might look that way to some people. Carcharoth (talk) 01:10, 7 March 2008 (UTC)
 * I think Maxim has erred more than violated - he made a decision which was somebody else's to make, and which others may well not have made. The "topic ban" business above I think was a misunderstanding of topic bans, which originate from the community and really have nothing to do with admins - we don't rule, we help. However, the last thing we need in this sorry saga is people who are only peripherally involved "going down with the ship", and in my experience and observation Maxim is a good admin. Orderinchaos 02:21, 7 March 2008 (UTC)
 * No, it doesn't just look bad. It is bad. There's no excuse for blocking someone you're in a dispute with. Ever. If a block is necessary to prevent damage to the project, someone else can do it. --FOo (talk) 07:18, 7 March 2008 (UTC)
 * I think the confusion partially stems from the fact that "Any uninvolved admin may issue topic bans in this area" is a standard remedy we often see in arbcom cases. Browse General sanctions for examples (the term "topic ban" isn't actually used, but there are a lot of instances of the term "ban" that refer to the same thing) —Random832 20:32, 7 March 2008 (UTC)


 * It's just as well I didn't take betacommand's bait and actualy break 3RR on that unrelated article after he just happened to pop by and revert me. MickMacNee (talk) 01:22, 7 March 2008 (UTC)


 * If Betacommand is wikistalking someone, that's a serious problem that shouldn't be handwaved away. That's just not acceptable. —Random832 02:11, 7 March 2008 (UTC)
 * Indeed. That is completely unacceptable in any situation. Orderinchaos 02:21, 7 March 2008 (UTC)
 * No, Betacommand gets picked on by so many of us trolls so often that any thing he does on-wiki is OK. Don't be ridiculous, he's just under stress.   (That is the party line around here, right?)  &#10154; Hi DrNick ! 04:22, 7 March 2008 (UTC)
 * Precisely.  Enigma  msg! 06:53, 7 March 2008 (UTC)

All this crap needs to be shut down. It's just pile-ons of unproductive comments. Ironically inappropriate comments, at that. And it's getting no where.  Lara  ❤  Love  14:43, 7 March 2008 (UTC)


 * Quite. The next step is an RFAr against Betacommand ... and separately, Betacommandbot.  There's quite enough evidence presented here to bring that forward.  &mdash; Arthur Rubin  (talk) 15:22, 7 March 2008 (UTC)
 * Agreed, there's enough here and at the bot approval group to warrant ArbCom getting involved.. inappropriate blocks, consensus circumvention, improper use of sysop powers. —Locke Cole • t • c 15:35, 7 March 2008 (UTC)
 * It will be difficult to keep an arbcom case from spiralling out of control. Personally, I don't think it has quite reached that stage yet. I would urge anyone considering an arbitration case to wait until after the deadline people have been working towards (23 March). Please, just a few more weeks and things may begin to calm down. I've had a productive exchange with Betacommand here and here, and I agree with what BrownHairedGirl has said here. Carcharoth (talk) 16:06, 7 March 2008 (UTC)


 * I disagree. This should go to Arbcom, now-- it's obvious nothing useful will ever come of the matter with regards to WP:ANI as folks just keep going in circles. Jtrainor (talk) 16:49, 7 March 2008 (UTC)
 * Then you will need to focus the issue on behaviour problems, and away from legitimate non-free image work. And preferably not focused on Betacommand, but also on the other editors, those who have failed to contribute to the various discussions but have used incivility and rhetoric instead. Carcharoth (talk) 17:01, 7 March 2008 (UTC)
 * You mean like Betacommand's supporters? The entire point of an RFA case about Betacommand is, you know, for it to be about Betacommand. Everyone would have the chance to get their two cents on the subject in, one way or the other. Pretending Betacommand and his supporters have done nothing reprehensible is a waste of time. Jtrainor (talk) 17:21, 7 March 2008 (UTC)
 * If that's the attitude you would take in an arbitration case, it would spiral out of control very quickly. You have to have some clear boundaries and aims in mind. Carcharoth (talk) 17:32, 7 March 2008 (UTC)
 * Yea, that's where the irony statement in my last comment came from. Those who... oh, what's a CIV/AGF-appropriate word... are displeased with Betacommand and his bot have been less than civil themselves, so I welcome an RFAR which claims only those of us who support Betacommand have spoken with a lack of civility.  Lara  ❤  Love  19:57, 8 March 2008 (UTC)

Did the move problem with Betacommandbot ever get fixed?
There's a long-standing problem with Betacommandbot image tagging that works like this.
 * 1) Editor uploads image, and correctly adds a fair-use statement that points to article A.
 * 2) Someone else moves article A to B, in a way that breaks the link in the fair use statement.  (This tends to happen when disambiguation pages are created.)
 * 3) Betacommandbot tags the image as lacking a fair use statement.
 * 4) The image is deleted by some admin following Betacommandbot's instructions.

So we lose an image from Wikipedia, even though nether the uploading editor nor the moving editor did anything wrong. The uploader of an image is not responsible for keeping track of it forever, and creators of disambiguation pages are not responsible for fixing links outside of article space. So it's the bot's fault.

I've mentioned this previously. It's non trivial to fix, but not impossible. The right answer is for any bot tagging non-free content to go back into the move history of the article to see if the link was valid under some previous name. If a move was involved, or the link has changed to a disambiguation page, then it's inappropriate for a bot to initiate deletion. --John Nagle (talk) 16:48, 7 March 2008 (UTC)


 * Apparently it is not fixed (see here and do a search for "Myst" or "Litton"). You may want to talk to the custodians of the new bot(s) about your solution.


 * Several users have argued (somewhere on this huge page) that your fourth point is not an open and shut case. Some admins look at the image descriptions before deleting them, in case their rationales are easy to fix.  Some do not, because the Foundation's deadline and the sheer size of the task weigh heavily on their minds.    Xeriphas1994 (talk) 19:51, 7 March 2008 (UTC)
 * I believe this is less of a problem than it was a couple of years ago. As I understand it deleted images are now recoverable, so if this happens to you just o to deletion review.  --Anticipation of a New Lover's Arrival, The 05:07, 8 March 2008 (UTC)
 * Yeah, well, I predict that at some point, maybe because deleted images take up a lot of server space (I think), or for more, shall we say, idealistic reasons, there might be calls for the developers to clear the deleted image database table (or whatever the technical term is). I realise that people will still be able to re-upload from the original sources and provide a rationale at that point, but I would hope that those who have used the "but you can ask for undeletion" argument will either oppose such a "clear the deleted images" request, or argue for a period of time to allow people to request undeletion of images. Carcharoth (talk) 10:25, 8 March 2008 (UTC)
 * You surely do have a lot of pessimistic views for the future. Are there discussions on this and your concern of the anti-fair-use crowd pushing to change the NFCC criteria? If not, why are you rallying support for a non-existent situation?  Lara  ❤  Love  21:26, 8 March 2008 (UTC)
 * Yes there have been discussions on this. See the following links:
 * Administrators' noticeboard/Archive127
 * Administrators' noticeboard/Betacommand/Archive_2
 * Wikipedia talk:Criteria for speedy deletion/Archive 28
 * I hope to summarise and restart these discussions sometime over the next few days, and include the issue of what to do with the deleted images. Carcharoth (talk) 02:12, 9 March 2008 (UTC)
 * Actually regularly clearing the deleted images filespace (or whatever it is) would be a very good idea. To catch speedies that went by while someone blinked, you only need to keep a few weeks worth.  And, as you say, you can always go and rip of the source you ripped off before--with the advantage that we can get more accurate sourcing information this time around.  The undeletion  option must never become a permanent back catalog of copyright infringements to dip in whenever we feel like it.  --Anticipation of a New Lover's Arrival, The 21:32, 8 March 2008 (UTC)
 * Agreed that copyright infringements shouldn't be dipped into, but fair use is not copyright infringement. Also, some of these deleted images are public domain, either at the time of uploading (incorrectly labelled as non-free) or after the copyright expired (there are images at the moment that are becoming public domain as we speak, but are still labelled as non-free - remember me telling you that I focus on historical pictures?). Also, I hope you see the problem with telling people on the one hand "we will undelete if needed" (with no indication of how long people have to request undeletion) and then turning round and permanently clearing out the deleted images with no notification that this was going to happen. I would have no problem with a widely advertised discussion, followed by extensive notification in various places, and a grace period of several months. I would oppose a limited discussion with only a few people deciding to suddenly clear all the deleted images. Carcharoth (talk) 02:12, 9 March 2008 (UTC)

A Call for Moderation
Let's lower the temperature a bit, folks. Going the RFAr route at this time would be counterproductive. There are separate issues that cause this counterproductivity:
 * Increased heat without much light. This is to say that tempers are so high right now that there have been things said that folks on both sides probably (or should) regret. Does Betacommand have a problem with chronic incivility? I would say he does. Does bringing an RfAr right now do anything real to solve that problem? Not in my opinion.
 * BetacommandBot is facing a 23 March deadline on some of his important work. Allowing things to cool down until then, reassessing the situation, and then seeing if the problem is such that an RfAr is necessary would seem a better solution, both for the health of the project, and for the tempers of those involved.

Hopefully we can all take a step back and allow users that have a less hostile relationship with BC work with him on the issues that many of us are seeing with regards to his communication style. I think if we do so, everyone would be better served, as would the project at large. Bellwether B  C  20:52, 7 March 2008 (UTC)
 * It seems you are saying "he broke the rules but he's doing important work so ignore that". If that isn't what you mean, perhaps you should restate your position because from reading this mess and his user pages it really seems like the community would be better off without his brand of "help". I'm not saying that no one else is wrong, but at this point I don't think even finishing the project will ever rehabilitate BC's image in the community. <font face="monospace" color="#004080"> Legotech &middot;(t)&middot;(c) 21:12, 7 March 2008 (UTC)
 * If you've followed this discussion at all, you know that you've mischaracterized my position. And while I'd like to see BC "rehabilitate" his image, that's not my main concern. My main concern is for the project, and to see him stop being so incivil, rehabilitated image or not. I don't think an RfAr--at least at this point--would accomplish either of those goals. Bellwether B  C  21:36, 7 March 2008 (UTC)
 * Discussions about Beta and/or his bot often tend to get sidetracked with irrelevancies. Yes, Betacommandbot does useful work.  Yes, people make unfounded and unreasonable complaints about the bot's legitimate actions.  Yes, there are also legitimate complaints to be made.  Betacommand tends to be rude and dismissive in response to legitimate concerns.  Sadly, too many people tend to put themselves into the "he can do no wrong" or "he can do no right" camps.  Both camps are equally wrong, and both camps waste a lot of time.  This issue requires careful adult consideration, not the black-and-white thinking of a child.  Friday (talk) 21:18, 7 March 2008 (UTC)
 * I'd like to clarify a bit: I'm not opposed to the very idea of an RfAr on BC--after 23 March. I think that the issues have become such that if he doesn't change--and soon--arbcom is the next stop. He's even made that clear himself, stating unequivocally that he didn't want an RfC, but preferred to go straight to arbcom. It's just that going into such a hornet's nest with the high temperature that's currently present would not be wise, in my view anyway. Bellwether B  C  21:40, 7 March 2008 (UTC)

My two cents.
A few points I'd like to make about BC et al.

Thanks. Will (talk) 22:50, 7 March 2008 (UTC)
 * BetacommandBot's main job is an approved task. If you have a problem with the task, take it up with the BAG, not on the admin noticeboard.
 * With regards to BCB's edits, it's doing something that it was programmed to do. If it can't find the article name in an image description, it tags per NFCC 10c. If given a list of talk pages to tag, it will tag them. If given a category to empty, it will empty it. Don't take it out on the bot for doing its job. False positives should be expected as nothing is 100% perfect. If it happens, revert it.
 * Bots should really be only blocked for three reasons:
 * The bot is running an unapproved task;
 * The bot is malfunctioning.
 * The maintainer has left Wikipedia (via ban, break, whatever).
 * The main problem with BCB is the civility of its owner. BCB is placed under a tremendous amount of stress due to his bot, and thus it shows in his edits. It doesn't completely absolve him, though: He should stay cool when the editing gets hot.
 * BC has been rather cooperative with requests to fix mistakes in the bot's code.
 * Apart from spamming Mick's talk page, Beta has shown a tremendous amount of good faith. I see no reason to call the religion project tagging malicious, as John Carter made a good-faith request but didn't check over the thousand article long list for false positives.
 * I support ST47's bot. I think it'd be good to split of the tasks and to redistribute the heat.
 * It doesn't take long to fix a rationale - five seconds if it just needs the article name, five minutes at the most if it needs a complete rationale. It's not difficult either.
 * The threads by Mick are slowly becoming annoying. We know you don't like BCB, but there's no reason to make drama on ANI. It's bordering on disruptive. Instead, collaborate with Beta.
 * Will, regarding your comment about the effort required to added FURs-- the main point of contention here is that BCB is tagging images at such a stupendous rate that it's overwhelming both the capacity and the desire of editors to keep up with it. Sure, fixing two or three images is trivial, but when it's dozens or hundreds, the natural HUMAN response is to just throw your hands in the air and give up. For the overwhelming majority of editors, Wikipedia is a hobby, not a job. Make it feel like a job, and you'll lose people. Make it take time away from their real jobs, and you'll lose people. And it's been happening. Everywhere I look in Wikipedia now, I see articles suddenly missing otherwise perfectly legal images because, unlike John Henry, the men couldn't keep up with the machine. Clayhalliwell (talk) 00:49, 8 March 2008 (UTC)
 * I said "five minutes" at the most. I can write a rationale for a fair use image in about one, and for logos it takes around 20 seconds. Say a person does 2 images a minute - if ten people do that for an hour it'd still be a thousand images. Will (talk) 00:54, 8 March 2008 (UTC)
 * The deadline is still the 23rd regardless of whether the images are tagged or not. BCB isn't creating a backlog, it's making it easier to deal with. – <font color="Indigo">Mike .<font color="Indigo">lifeguard  &#124; <font color="Indigo">@en.wb 00:55, 8 March 2008 (UTC)
 * Well... I suppose I can't argue with that. It is indeed true that most of Wikipedia's problems become easier to deal with by simply deleting them. Clayhalliwell (talk) 15:31, 8 March 2008 (UTC)
 * You know, BCBot does not delete anything. And, the folks that can, aren't robots. We usually look at the image, and, see if we can even figure out a rationale for it. Sometimes we can, and, we fix it. Often, we cannot, and, the image has to be removed. Sarcastic comments like that, really aren't very helpful in this situation. If you have a suggestion, on how to guess at how to create a rationale, for an image, that nothing is known about, I'm sure a lot of us would love to hear it. SQL <sup style="font-size: 5pt;color:#999">Query me!  22:07, 8 March 2008 (UTC)

RFArb
FYI: Maxim has opened a request for arbitration at ARBREQ. &#10154; Hi DrNick ! 01:25, 8 March 2008 (UTC)

Targeting images that already have been provided with Fair Use Rationale
Image:Negasonic.jpg

I uploaded this image years ago. Months ago I took the job of writting down the whole enchilada so I could bet that Bot off my back. Yet I got BettacommandBot's message of "your image has been tagged for not having fair use rationale and will be deleted" today. I don't know if this has happened before.--Gonzalo84 (talk) 16:06, 8 March 2008 (UTC)
 * I've explained the problem on Beta's page: you needed the full disambiguated title of the page it was on, which I have fixed for you. This is not a bug with BCB. --M<font size="-3">ASEM  16:08, 8 March 2008 (UTC)
 * It might not be a bug, but it certainly is rude. Whatever happened to people fixing the problems they find in Wikipedia themselves instead of hunting down and prosecuting the previous contributors? --Dystopos (talk) 19:36, 8 March 2008 (UTC)
 * Bots cannot fix Non-free use rationales. βcommand 19:38, 8 March 2008 (UTC)
 * They sure can climb all over people's backs, though, can't they? --Dystopos (talk) 20:03, 8 March 2008 (UTC)
 * Come on, that's not likely to help anything, now is it? SQL <sup style="font-size: 5pt;color:#999">Query me!  22:00, 8 March 2008 (UTC)
 * Does it help when BC replies with a stock "Bots cannot fix non-free use rationales" without making any attempt to address the problem (or letting anyone else address it)?  r speer  / ɹəəds ɹ  08:14, 10 March 2008 (UTC)
 * For certain categories of images a bot could probably use a boiler plate rationale that would work (for logos anyways). —Locke Cole • t • c 22:06, 8 March 2008 (UTC)
 * Where would you find the image source, say, for an image like this one? SQL <sup style="font-size: 5pt;color:#999">Query me!  22:11, 8 March 2008 (UTC)
 * That image has no source, that's another matter from an image lacking a rationale. FWIW, I'm not the original image uploader: I only converted the image to a PNG. Anyways, back to rationales, it's entirely possible to come up with a generic boiler plate. —Locke Cole • t • c 00:12, 9 March 2008 (UTC)
 * I wasn't intending to pick on your upload, that was just the easiest example to use... IIRC, isn't "Where you got the image" required by WP:NFCC, and, therefore, would be required in any boilerplate non-free template? I think, I might be misunderstanding exactly what you mean, however. SQL <sup style="font-size: 5pt;color:#999">Query me!  00:46, 9 March 2008 (UTC)
 * I see, I wasn't aware that the source and the rationale were rolled in to one. Okay, so a bot could conceivably "fill in the blanks" for most issues relating to (in my personal case) logos, but obviously if the source is missing that's another matter. IMO, it's much simpler to fix source issues (especially where the source information is already on the page, but the bot was unable to process it) than to write rationales out where a boiler plate could be used. —Locke Cole • t • c 02:22, 9 March 2008 (UTC)

This is explained above, but I'll Cliff's Notes it. BetacommandBot tags thousands of images. It is not Betacommand's responsibility to then fix those thousands of images. He does, however, ensure that notifications are handed out. He does this with community-written templates. If you find those templates to be rude and somehow to have it on your page leave you feeling "prosecuted", then please bring up those concerns on the template talk page(s). As far as the images being corrected, if it's too much of a hassle for you to correct a link, there's a good chance someone else will spend the necessary 10 seconds to correct the issue, as has been shown in this very case. Regards,  Lara  ❤  Love  21:40, 8 March 2008 (UTC)
 * It's probably quite possible to fix most logo issues automatically. If the image already has a logo copyright notice, and it's linked from an article with a name reasonably consistent with the logo copyright notice, a bot could insert the appropriate backlink to the using page automatically.  Approximate string matching technology is up to the job.  --John Nagle (talk) 19:55, 10 March 2008 (UTC)

Missing revision history
A significant chunk of this page's revision history is missing: see details Village pump (technical). --BrownHairedGirl (talk) • (contribs) 16:32, 8 March 2008 (UTC)
 * Ok. SQL <sup style="font-size: 5pt;color:#999">Query me!  22:01, 8 March 2008 (UTC)
 * This turned out to be a moved thread. Carcharoth (talk) 01:55, 9 March 2008 (UTC)

Community proposal
This does not address article space, only removal of redlinks/deleted categories from user space, including user page and user talk page.

Please read Template:Bots, and then after having read it: Should recognition and heeding of the bots/nobots tags be implemented into BetacommandBot's code for user pages and user talk pages? In other words, if BetacommandBot comes across a user page or user talk page that has the   or    tag on it, do you think BetacommandBot should have the capability to recognize those tags and if so, actually recognize those tags and perform its functions based on those tags and do you think this should be implemented?

There's no need to say "in userspace only" or "user and usertalk pages only", etc. because that's what it says above in the description of this proposal.

Support

 * 1) Support - <font size="+1" color="red">&#10032; <strong style="letter-spacing:1px;font-family:Verdana">ALLSTAR <font size="+1" color="red">&#10032; echo 05:54, 6 March 2008 (UTC)
 * 2) A no-brainer. -- Ned Scott 06:01, 6 March 2008 (UTC)
 * I would have no problem with reasonable exceptions to this, depending on the bot task. -- Ned Scott 08:24, 9 March 2008 (UTC)
 * 1) Support For user and usertalk pages only.  MBisanz  talk 06:17, 6 March 2008 (UTC)
 * 2) Support - Bot actions on user and user talk pages should probably be opt-in anyway. <font color="#4B0082">&mdash;Torc.  <font color="#4F7C4F">( <font color="#4F7C4F">Talk. <font color="#4B0082">) 07:05, 6 March 2008 (UTC)
 * 3) In userspace only. Will (talk) 09:00, 6 March 2008 (UTC)
 * 4) I can see the predictable "But no-one TOLD me there was anything wrong with the image!!" from some, but it's their choice to place nobots, so Support. The template could be more precise about images (per Zscout below) <b style="color:black;">Black Kite</b> 10:30, 6 March 2008 (UTC)
 * 5) Absolutely Support - It's logical and it should've been this way to begin with. Would've saved a lot of people headaches.  Enigma  msg! 17:51, 6 March 2008 (UTC)
 * 6) Support, will improve the ability of the Wikipedia community to maintain a control over the robots aiding its operations. Per Ned Scott, "a no-brainer". AGK (contact) 19:26, 7 March 2008 (UTC)
 * 7) Support in all namespaces, abuses (and the abusers) can be handled on a case by case basis. —Locke Cole • t • c 02:51, 9 March 2008 (UTC)
 * 8) Support in general, but especially for User talk: and Talk: namespaces. Orderinchaos 08:21, 9 March 2008 (UTC)
 * 9) Support -- SatyrTN (talk / contribs) 15:59, 9 March 2008 (UTC)
 * 10) Support, of course. -- No Guru (talk) 16:53, 9 March 2008 (UTC)
 * 11) Support I don't see any benefits of Beta's current system. It makes work more complicated for editors, and BetaCommand. Abuse of the tags has only occurred in the image namespace, and the current proposal only concerns User Talk. Puchiko (Talk-email) 21:44, 10 March 2008 (UTC)
 * 12) Strongly support; BC implements draconian "if you opt out, you can't comment on my bot" rules for his opt-out list. This is improper. If he won't change willingly, perhaps the community needs to let him know that's completely unacceptable. Bellwether B  C  04:20, 15 March 2008 (UTC)

Questions

 * 1) Will this affect on his notifications of fair use images? If so, then there should be a way people know about changes to their images (I assume having images on auto-watchlist when uploaded would be it). User:Zscout370 (Return Fire) 07:08, 6 March 2008 (UTC)
 * Well users do have to add the nobots tag, so in theory they should know they are foreclosing the option of a bot notifying them of things related to their editing. Auto-watchlisting is good, but I suspect those who care about their images will just forgo nobots and those who don't, won't follow the watchlist closely.  MBisanz  talk 07:24, 6 March 2008 (UTC)
 * As long as users who do that understand that point, then I will support the proposed idea. User:Zscout370 (Return Fire) 07:39, 6 March 2008 (UTC)
 * I added some rather specific language at the template page reiterating that. Others feel free to re-word.  MBisanz  talk 07:44, 6 March 2008 (UTC)
 * Users should be able to set permission for addition of material (i.e. notifications) and deletion separately. <font color="#4B0082">&mdash;Torc.  <font color="#4F7C4F">( <font color="#4F7C4F">Talk. <font color="#4B0082">) 11:04, 6 March 2008 (UTC)
 * Looking at the proposal, it has nothing to do with image notices, its about categories, this should not affect image notification. Mr.  Z- man  03:07, 16 March 2008 (UTC)
 * 1) Sometimes, users doing mass-bad uploads appear at WP:AN/I but it is usually only though the number of BetacommandBot warning messages on their talk pages.  or similar will prevent those messages.  Is there a way to find out the number of bad uploads by user, or problematic users, or something similar without their talk page?  (I appreciate that some users simply remove these warnings, but  prevents any edits in the history in the first place).  x42bn6 Talk Mess  11:45, 6 March 2008 (UTC)
 * This can be used to check and view uploads, but we have to review every image to see if it is good or not. User:Zscout370 (Return Fire) 15:19, 6 March 2008 (UTC)

Apparently this consensus is not meaningful to the BAG as the NFCC10C function bot was shut downa nd approved mid-discussion Bots/Requests_for_approval/Non-Free_Content_Compliance_Bot.  MBisanz  talk 21:21, 6 March 2008 (UTC)

Result
The result appears to be overwhelming consensus for this. So Betacommand, have you instituted this change requested by the community? —Locke Cole • t • c 02:48, 14 March 2008 (UTC)
 * has indicated that this is not consensus due to its size and location. I'd contact him to get ideas on how to transform it into something that would be respected and/or enforceable.  MBisanz  talk 03:02, 14 March 2008 (UTC)
 * To expand on my previous answer. The issue is that this is an infrequently trafficed page. Therefore this consensus has a self-selection bias in favor of people who have an issue with Betacommand.  So it may not statistically reflect the conensus of the larger population.  Ryan knows a lot about the Meta-space issues through his work with WP:RFR, so he would be a good person to advise on where and what conensus actually looks like.  MBisanz  talk 05:53, 14 March 2008 (UTC)
 * Either way, I agree with Ryan, one way or the other. This noticeboard is VERY polarized. SQL <sup style="font-size: 5pt;color:#999">Query me!  06:20, 14 March 2008 (UTC)
 * Yeah, and while that may be true, it would've been insanely helpful had someone spoken up before waiting for a week to pass before saying "thanks, but our princess is in another castle". —Locke Cole • t • c 06:25, 14 March 2008 (UTC)
 * As an aside, WP:AN/I routinely holds community ban discussions, so I fail to see why this would be any different. And this isn't even a proposal to ban him or his bot, just to get him to do something it should be doing anyways.. —Locke Cole • t • c 06:36, 14 March 2008 (UTC)
 * Short of putting this in MediaWiki:Sitenotice I don't know how else you'd expect to get more input than you've gotten here (or where, for that matter). —Locke Cole • t • c 06:25, 14 March 2008 (UTC)


 * Even though I'm supporting an opt-out feature from BCB, I'd have to agree that the discussion here isn't enough to force him (nor do I really want to force him). I think it's more likely that Betacommand will find some kind of opt-out feature that he likes in time. The best thing we can probably do at this point is to not be combative, but try to be helpful, and help find an acceptable solution. -- Ned Scott 05:31, 15 March 2008 (UTC)
 * See here for his solution. Be sure to read the fine print. —Locke Cole • t • c 05:36, 15 March 2008 (UTC)

You know, strictly speaking, Betacommand has absolutely no reason to do as Locke Cole asks. And if Betacommand becomes displeased, he could just shut the bot down at a whim. Would that actually be a net gain here? --Kim Bruning (talk) 09:36, 15 March 2008 (UTC)
 * "As I ask"? Are you pretending the other thirteen people above are my sockpuppets? —Locke Cole • t • c 16:05, 15 March 2008 (UTC)


 * Ill agree to follow nobots until that is abused. βcommand 16:08, 15 March 2008 (UTC)
 * If it's abused, report the abuse to the community and let us deal with the person abusing it. —Locke Cole • t • c 16:12, 15 March 2008 (UTC)
 * It has been abused for over six months now, that is why I refuse to follow it. If want to opt out here is your method to do so. it is the only thing I will support. dont like it? tough, I dont get a choice to opt out of harassment, personal attacks and trolling. If you want to opt out, I also get opt-ed out of your trolling. βcommand 16:18, 15 March 2008 (UTC)
 * Wait, now you're refusing to follow it? And you know the objections to your opt-out method already. BTW, your attitude really needs some work. —Locke Cole • t • c 16:28, 15 March 2008 (UTC)
 * Didn't you just say you agree to follow nobots until it's abused? Were you serious about that? --Conti|✉ 16:29, 15 March 2008 (UTC)
 * Conti, I was making a point, nobots has been abused for at least 6 months now, that is one reason that I will not follow it. I proposed a very secure method that cannot be abused and that is now up for deletion. If that gets deleted dont ever expect me to bother making an opt out method. βcommand 16:39, 15 March 2008 (UTC)
 * Just out of curiosity, do you have any diffs? If that feature is abused, you should probably report the abuse at WP:AN/I so the abuse will be stopped, instead of not using that feature at all. --Conti|✉ 16:43, 15 March 2008 (UTC)
 * Representations that there is any kind of community consensus on this are factitious at best. --Anticipation of a New Lover's Arrival, The 16:26, 15 March 2008 (UTC)
 * If you say so. My attitude is strictly the opposite, of course. —Locke Cole • t • c 16:28, 15 March 2008 (UTC)
 * If editors of long experience can disagree in good faith about whether there is consensus, then it is quite probable that there is no consensus--at least, not sufficient to warrant compulsion. --Anticipation of a New Lover's Arrival, The 17:04, 15 March 2008 (UTC)
 * So if even ONE editor can "disagree in good faith" consensus is torpedoed? That's nonsense, and I think you know it, Tony. Bellwether B  C  17:06, 15 March 2008 (UTC)