Wikipedia talk:Bots/Requests for approval/Archive 13

API rights to edit
I'm trying to figure out how to obtain action=edit rights for User:GreenC bot. I've never used the API for writing so not sure how rights works. Is there a place to apply or does it already have the rights since the bot account was approved, in which case it's simply a matter of logging in and obtaining a token? -- Green  C  15:18, 14 June 2016 (UTC)
 * Any logged in user can use the API to edit (technically you can also edit anonymously, but... don't do that). In the past it was pretty simple and you just logged in with action=login, but now because of the fancy AuthManager stuff it's recommended that you create an OAuth consumer and use action=clientlogin. See mw:API:Login and mw:API:Tokens. Also, Special:ApiSandbox may prove helpful. —  Earwig   talk 17:38, 14 June 2016 (UTC)
 * Slight correction: it's recommended that you create an OAuth consumer (likely owner-only for a bot), or set up a bot password and continue to use action=login if you can't use the more secure OAuth. Bots shouldn't need to use action=clientlogin, that's for interactive clients like mobile apps. Anomie⚔ 19:30, 14 June 2016 (UTC)

Semi-protected edit request on 29 August 2016
Hasdiehasnan2212 (talk) 09:46, 29 August 2016 (UTC)
 * Red information icon with gradient background.svg Not done: This is not an edit request. Topher385 (talk) 10:04, 29 August 2016 (UTC)

Semi-protected edit request on 17 October 2016
I would like to add my bot for review:

Navi-darwin (talk) 22:15, 17 October 2016 (UTC)
 * However, I did mark you confirmed, you should be able to add your request now. —  xaosflux  Talk 22:21, 17 October 2016 (UTC)

Semi-protected edit request on 21 October 2016
— Preceding unsigned comment added by PeterRakke (talk • contribs) 13:38, 21 October 2016 (UTC)
 * Red information icon with gradient background.svg Not done: And your BRFA was denied. Anomie⚔ 17:31, 25 October 2016 (UTC)

Sandbox Bot
SO I am new to the world of wikipedia bots. I wanted to create one and basically just experiment with what a bot can do. Is this allowed? I.E. I don't necessary have a specific task in mind yet. I have 10+ years of programming experience and just wanted to try my hand at writing some code. If I just want to experiment with the Ruby API and making changes from a local program should I just do that using my current user and only request a bot if I specific task in mind? Also, is there a better place I should be asking this question? Thanks in advance! -- Zackmann08 (Talk to me/What I been doing) 21:06, 11 November 2016 (UTC)
 * You can make an account that makes low speed edits to its own user: subpages without needing a BRFA approval. — xaosflux  Talk 21:59, 11 November 2016 (UTC)
 * Adding to what xaosflux says, Pywikipediabot is a good place to start. Dat GuyTalkContribs 22:00, 11 November 2016 (UTC)
 * By the way xaos, my bot is currently editing while logged out since Samtar started the task with a malformed username/password, and for some reason I cannot restart it after I applied the fix. — Preceding unsigned comment added by DatGuy (talk • contribs)
 * how is that preventing you from stopping it from running? — xaosflux  Talk 22:12, 11 November 2016 (UTC)
 * Permission error for when I try to restart it. When I try to stop it, it says it isn't running. See screenshot. Nobody with root access online on IRC. Dat GuyTalkContribs 22:19, 11 November 2016 (UTC)
 * Start by reading Bots/Requests for approval and the pages linked from there. That should give you an idea of the boundaries around experimentation. – Jonesey95 (talk) 22:14, 11 November 2016 (UTC)

Speedy bot closure
I believe that PrimeBot 6 does edit articles. It adds the AfD template to them. Dat GuyTalkContribs 13:30, 23 December 2016 (UTC)
 * Thank you - I misread that, and have reversed the speedy approval. Task is back open for comments. —  xaosflux  Talk 13:36, 23 December 2016 (UTC)

Taking over someone else's bot?
Is there a process for taking over a bot (account and functionality), if the current operator is willing to hand it over? The bot in question is, current operator is. See its BRFA for how the bot works.  Magic ♪piano 21:35, 5 January 2017 (UTC)
 * If the operator is willing to transfer the account, you can have them change the email and do a password reset or something. Then just make sure the wiki documentation is up to date on who is controlling the account. Legoktm (talk) 22:09, 5 January 2017 (UTC)
 * The more 'traditional' method is to take over the task, not the account, setting it up under your own bot account - and assuming it is on a server your own server access, etc. Getting this type of task approved should be simple. —  xaosflux  Talk 22:37, 5 January 2017 (UTC)
 * Dudeman is going on an extended wikibreak, and is willing to surrender the bot account to me. The bot code has some references to that account's user space, which it uses as a sandbox for query results and the like.  I could fork the code to adapt it to a new sandbox, but it seems to me that just taking the account over should suffice (especially since I can just return it to Dudeman should he decide to come back).  I don't intend to do more than maintenance to the code; I'm conversant in programming, but Javascript is not a particular forté of mine.  I would certainly update all the relevant places to indicate that I'm the bot operator.  Magic ♪piano 01:24, 6 January 2017 (UTC)
 * I would say as long as it's clear who has access to the account, i.e. full disclosure on the bot page, and you are able to maintain the code, wherever it lives, it shouldn't be too much of a problem. Just make sure to observe security practice and don't leak the new password to anyone.— CYBERPOWER  ( Happy 2017 ) 01:36, 6 January 2017 (UTC)


 * In this case, I think it would be best for to name you as an additional operator. Since there is only one of you operating "at a time" right now, disclosure of who will be operating and monitoring can be recorded at User:NationalRegisterBot. If the original operator was abandoning it, rather then just going on break (and presumably capable of reclaiming the bot in the future) then "transfer" would be more called for. —  xaosflux  Talk 01:40, 6 January 2017 (UTC)


 * If I understand correctly, naming additional operators would require altering the code that makes edits to ensure edit summaries record the active operator. It would also imply identification of those operators on the bot and operator user pages.  Am I missing anything?  Magic ♪piano 20:03, 6 January 2017 (UTC)
 * For this specific bot and its current tasks I'm fine with it just being listed on the on-wiki user pages (as there will only be one person using it at a time). — xaosflux  Talk 20:52, 6 January 2017 (UTC)
 * Magicpiano and Dudemanfellabra have both suggested to me that we have more than one active bot operator, mainly so we don't end up in another situation where the only active operator drops off the face of the earth for months and nobody's around to run the bot. While I probably shouldn't be the main operator right now, since I'm working on a lot of unrelated projects at the moment, I'm willing to be a second active bot operator if we go with the additional operator plan. (I could probably help with debugging too if necessary, since I have a basic understanding of Javascript.) TheCatalyst31 Reaction•Creation 01:07, 7 January 2017 (UTC)

Another questionable BRFA
I am surprised that trivial edits such as  would be approved as a standalone taks for a bot, but it seems the operator believes they are approved by Bots/Requests_for_approval/BG19bot_7. I have had some pushback from the operator about the issue, so I would like to get some outside opinions, especially from BAG members: is that task acceptable under the bot policy? Is that BRFA valid? &mdash; Carl (CBM · talk) 14:11, 22 January 2017 (UTC)
 * Those changes are perfectly fine to be done by a bot. Leaving any link piped to itself is going to cause editors to waste time wondering why the text is piped to to itself (after first wasting time trying to spot any difference between the two). In addition, such pointless links just clutter up the wikitext, making it harder to read. --NSH001 (talk) 14:35, 22 January 2017 (UTC) (not a BAG member)
 * IMO that BRFA suffers from some of the same "lack of consensus for every checkwiki fix" issues that are being brought up in Magioladitis's ArbCom case: the BRFA approves "checkwiki fixes" generically, but doubt has now been raised as to whether there is consensus that every checkwiki error overrides WP:COSMETICBOT when the fix is cosmetic. Anomie⚔ 20:27, 22 January 2017 (UTC)
 * These changes are very useful for people working with wikicode and helpful. -- Magioladitis (talk) 21:33, 22 January 2017 (UTC)

No comment on the usefulness of the task but User talk:Bgwhite was a totally inappropriate response from the bot's operator to a query from CBM, being needlessly aggressive while also avoiding the question asked. I have no knowledge of prior history between Bgwhite and CBM but this does not absolve responsibility of a bot's operator to adhere to WP:BOTCOMM. An indication from Bgwhite that he will improve in this respect would be welcome. &mdash; Martin (MSGJ · talk) 13:28, 23 January 2017 (UTC)

MSGJ take note that CBM ignored my reply in Bgwhite's page. -- Magioladitis (talk) 13:47, 23 January 2017 (UTC)


 * That is certainly a COSMETICBOT violation, but this is the first time I've noticed such an edit from this bot. Let's discuss and fix it. No need to escalate anything here. ~ Rob 13 Talk 13:36, 23 January 2017 (UTC)
 * This is not a COSMETICBOT violation. The task is approved via BRFA. -- Magioladitis (talk) 13:43, 23 January 2017 (UTC)


 * Would you mind providing or directing me toward a list of all CHECKWIKI fixes your bot currently does? Thank you. ~ Rob 13 Talk 13:38, 23 January 2017 (UTC)
 * User:Magioladitis/AWB and CHECKWIKI linked from WikiProject Check Wikipedia. -- Magioladitis (talk) 13:43, 23 January 2017 (UTC)

do you agree that when I bot does exactly what a BRFA say then there is no COSMETICBOT violation? -- Magioladitis (talk) 13:46, 23 January 2017 (UTC)

Also note that this task was even noted explicitly in the related Yobot BRFA. Also note that the error #17 "Category double" also makes no changes to the rendered output. -- Magioladitis (talk) 13:53, 23 January 2017 (UTC)

Note that MenoBot does the same set of edits Bots/Requests for approval/MenoBot 4. Error 17 was even chosen as a test task before the bot was approved. -- Magioladitis (talk) 13:55, 23 January 2017 (UTC)


 * Personally, I do think consensus for a specific task can override the general rule of COSMETICBOT. But, in this case, I think it is not clear whether the bot does "exactly what the BRFA says" because the BRFA in question does not seem to specify an exact task, nor point to any community-wide consensus about CHECKWIKI. The BRFA also says "I'd rather not do any CheckWiki errors that may be controversial.", and it is clear that edits such as (which the bot is continuing to make) are at least somewhat controversial.  In this case, I think that the BRFA may have been approved in error, which is why I would like the opinions of others about it, particularly BAG members.  Perhaps it would be better for all of the CHECKWIKI-related BRFAs to be refiled, so that consensus can be determined. &mdash; Carl (CBM · talk) 13:57, 23 January 2017 (UTC)
 * CBM I think you think controversial every single edit that does not affect he rendered output. Am I right? Since the BRFAs are accepted by multiple BAG members and there are done by 6 bots I think it;s the other way round. You should open an RfC. The current consensus is on Bgwhite's side. -- Magioladitis (talk) 14:03, 23 January 2017 (UTC)
 * The point of this thread is to help judge the current consensus. &mdash; Carl (CBM · talk) 14:04, 23 January 2017 (UTC)
 * CBM I agree. We should do it in a more formal way some how. Otherwise, we (not just you and me; I mean the community) will keep writing and making circles. -- Magioladitis (talk) 14:46, 23 January 2017 (UTC)


 * No cosmetic edits not explicitly listed in detail in BRFA. In this case, that means none. ~ Rob 13 Talk 14:22, 23 January 2017 (UTC)
 * We agree! All edits approved in BRFAs of MenoBot, Yobot and BG19bot should not be considered "cosmetic" (a formal definition ye to be written)). -- Magioladitis (talk) 14:45, 23 January 2017 (UTC)
 * Except that this approval never said any of its fixes would be cosmetic, nor did it spell them out. I'm saying a botop shouldn't be able to sneak these through. They should have to spell out that they will be a COSMETICBOT exception, this is what the edits will look like, etc. ~ Rob 13 Talk 14:48, 23 January 2017 (UTC)
 * It's clear because of the approval Yobot got. -- Magioladitis (talk)
 * Which itself didn't make clear that it was seeking an override of COSMETICBOT, and which later incorporated cosmetic-only fixes which weren't even in existence at the time the BRFA was approved. Either way, my recommendation at the moment,, is to hold for the ArbCom result and the BAG closure of the first section on this page currently. We should be tackling one thing at a time. I'll discuss this with Bgwhite off-wiki in the meantime in the hopes of working out a good solution for everyone. ~ Rob 13 Talk 18:00, 23 January 2017 (UTC)
 * Do you plan to go bot-by-bot and person-by-person? Don't you think a large community discussion is a better solution? Do you now understand that the latest series of edits I did was also part of CHECKWIKI? -- Magioladitis (talk) 18:50, 23 January 2017 (UTC)
 * The community has implemented WP:COSMETICBOT. It's policy. If you'd like to change it, you're welcome to start a discussion. A large-scale community discussion to revoke bot authorizations that no longer meet community standards (or never did, really) would be a bit of a disaster - too many tasks kicking around. I'd much rather do this slowly and with care. First, talk to bot operators individually. See if they'll be willing to voluntarily give up certain aspects of their bot tasks that don't appear to meet COSMETICBOT and which weren't clearly discussed in the initial bot approvals, with no prejudice against seeking consensus for those tasks at a broad community venue and then filing a new BRFA (which could be speedy approved if consensus is there for performing the aspects of the task that were cosmetic-only with a bot - that last bit is key). That's something that definitely needs to happen individually because each botop is different and reacts to a request like that in a different way. There's no one-size-fits-all for negotiating a path forward that satisfies everyone.
 * If a botop is willing to work to demonstrate consensus for the cosmetic-only aspects of their bot's editing and voluntarily separates those portions of their tasks off into new BRFAs, then there's absolutely no issue that even needs posing to the community. If a botop takes the hard line that they refuse to respond to community consensus, then the next step would be monitoring their edits and filing for revocation of the bot approval if they continue making problematic edits. I'd really rather not get there with any other operators. This can all be done reasonably if we handle this with care and don't brute force everything. We just need the bot operators to be willing to accept oversight and yield to consensus, two things that I think we can both agree are already mandated by the bot policy. Nearly all bot operators are perfectly happy to do so.
 * I've always understood your edits were often part of CHECKWIKI - parts of CHECKWIKI that did not exist when your BRFA was filed, which violate the bot policy, and which were not scrutinized at the BRFA (often because they did not yet exist!). Imagine if I requested approval to orphan Example template blah. Then I move every template I want to orphan to Example template blah before using my bot to orphan it. That's technically in the bounds of my bot approval, but it's also clear my bot wasn't really approved to do that. Similarly, your BRFA approved a set of existing fixes called CHECKWIKI at the time. When you later add a bunch of other fixes to the list, that's not the same thing. You've moved it to the name CHECKWIKI, but it's not what was approved. Do you see where I'm coming from? Moreover, do you understand my frustration that you're simultaneously stating you want community oversight but aren't willing to separate off the cosmetic-only pieces of your tasks and file a new BRFA for them? I've tried several times to provide clear examples of how you could have additional oversight that - either way the discussion went - would satisfy the consensus process and COSMETICBOT. You've never considered any of those proposals. ~ Rob 13 Talk 19:16, 23 January 2017 (UTC)
 * You know that the ArbCom is not about the templates because this was never the reason people really complained (apart from you perhaps?). Even if you check the evidence I was the one mainly reducing the list of the templates and not increasing it. So, please check my point of view and especially the various reasons other people complain. If you want to be part of the solution and not part of the problem, you should do that. Otherwise, you'll stick to the impression that the various complaints all have the same origin which is not true. It's good that you made these statements above. They explain better what you think as a priority problem. Let's hope someone has the time to check all the various facts and combines them to a good solution. Moreover, the CHECKWIKI project is open to you as to everyone ti participate. This is also a good road I guess. -- Magioladitis (talk) 19:28, 23 January 2017 (UTC)
 * Is this a serious response? The template thing above was an analogy. It was an attempt to illustrate why the CHECKWIKI totally open-ended task is extremely problematic because you're running fixes that were wholly unreviewed at the BRFA. If you can't get that, then I've seriously misjudged the locus of this dispute. ~ Rob 13 Talk 22:55, 23 January 2017 (UTC)
 * I don't know. I tried to give a serious response. I think this discussion is recycling in various places with aspects from policies, to projects, to bots and whatever. I have replied to every comment in my talk page and in bot's page. Please read them before leaving your next message because I think you try to help in something without knowing the full story. It's good that you decided to help us but please do it with caution. -- Magioladitis (talk) 23:19, 23 January 2017 (UTC)


 * I cannot recall what I was thinking 7 years ago when I approved that task, but it seems unlikely that I would have approved making an edit that was solely de-piping identical Wiki-links. I like to think that I would have approved it under the belief that the de-piping edits would have been skipped by the ""Skip if only minor genfixes" and "skip if only whitespace changed"" comment, but my memory is not sharp enough to make that assertion. In any event, I am in the current camp that such minor edits should not be made on a standalone basis unless they have an effect on some other aspect, like capitalization, category sorting, etc.  MBisanz  talk 03:44, 24 January 2017 (UTC)

there were bots approved simplifying wikilinks before 2011. -- Magioladitis (talk) 11:43, 24 January 2017 (UTC)
 * If you, as the approving BAG member, did not intend for the task to expand to include cosmetic-only edits, can you just clarify that your approval comes with the caveat that all edits must make a non-cosmetic change (or additional approval must be sought for the cosmetic-only edits)? That would fix this nicely. We shouldn't be bound by old approvals that were handled with less scrutiny when they're causing problems today, especially if the approving BAG member didn't intend to approve these sorts of edits. ~ Rob 13 Talk 18:49, 24 January 2017 (UTC)
 * it's obvious that all BRFAs can change if consensus changes. Has it? If it has then Yobot should change, unblocked and run under the new consensus. -- Magioladitis (talk) 19:59, 24 January 2017 (UTC)
 * Not so much changed as never there in the first place; the BAG member who approved both Yobot and the bot under discussion here has now stated he did not intend to approve the edits that are being made with regularity in the modern day. ~ Rob 13 Talk 20:03, 24 January 2017 (UTC)
 * Please be careful, I did not say that in 2010 I did not intend to approve of the edits being currently made. I said that I believe in 2010 I would not have approved of the edits being currently made, but that my memory is not sharp enough to definitively say if I considered the issue in 2010. I also appreciate that it is somewhat unfair to Magioladitis say that I can retroactively amend my approval simply because I did not document my thoughts at the time and currently believe the edits should not be approved (if I can amend my approval, why can't any BAG member amend any other member's approval at any point in time?). I am not familiar with the active ArbCom, but my suggestion would be to either: (i) have an uninvolved BAG member or admin close this re-examination of my approval of the BRFA per WP:BOTAPPEAL or (ii) for Magioladitis and/or Bgwhite to accept my retroactive amendment to remove approval to correct errors 9, 18, 22, and 64 (I assume those are the ones in question; I could also phrase it as "errors covered by WP:COSMETICBOT"), if those errors are the sole basis for making the edit.  MBisanz  talk 13:01, 25 January 2017 (UTC)
 * Nice. This means I did nothing wrong afterall. Everything it was big misunderstanding. Sorry nor realising earlier. Let's move forward then! -- Magioladitis (talk) 20:06, 24 January 2017 (UTC)
 * A bot approval does not mean we ignore policy, nor does it mean we ignore repeated community pleas at major venues, nor does it allow cosmetic-only editing from a main account. Having said that, if you're dropping the stick on the purely cosmetic edits, I'm certainly glad to see that. As I hope I made clear above and on Bgwhite's talk page, my goal is most certainly not to kill CHECKWIKI, only to enforce the community's standards on what bot edits are permissible. ~ Rob 13 Talk 20:09, 24 January 2017 (UTC)
 * I think here we have new evidence that totally affects the active ArbCom. This is a serious development. -- Magioladitis (talk) 20:12, 24 January 2017 (UTC)
 * For multiple reasons, I've more-or-less withdrawn from participation in the ArbCom case, outside of explaining my set of proposals to arbitrators as necessary, so I'll only say this one thing on that topic. I don't see this as a major development because repeated attempts to clarify the community's opinions about these tasks at ANI, the first thread of this page, your talk, your bot's talk, AN, etc. have all resulted in no change. I just have little confidence in any change in the absence of remedies. If there are no remedies, I'll certainly hope I'm wrong, but I struggle to AGF on future efforts when an experienced editor who understands consensus disregards it. ~ Rob 13 Talk 20:15, 24 January 2017 (UTC)
 * The ArbCom is far too complicated since it mixes various things. It's not only about who has the consensus and what the community really agrees that can be done. -- Magioladitis (talk) 20:29, 24 January 2017 (UTC)

thanks for looking into it. Error 18 was disactivated in December 2015 (more than 1 year ago; in case someones confuses with 2016), error 22 has been disactivated in July 2016. Error 9 last month had 5 (five) pages, 2 in November, 7 in October and in fact it it already done manually. The only interesting case is error 64. Total: 2 error already disactivated by the CHECKWIKI team, 1 not really done by bots, 1 in question. It is nice that you are very specific and given explicit error numbers. -- Magioladitis (talk) 13:13, 25 January 2017 (UTC)

One of the reasons that we keep error 64 is that we detect more things like this one where the syntax was broken. This is the majority of pages. Parentheses, brackets, quotes, all get mixed up in many cases. We try to detect all this together. This really helps Visual Editor in its current state. -- Magioladitis (talk) 13:19, 25 January 2017 (UTC)
 * Additional tasks that are purely cosmetic include 1, 17, 38, 42, 52. ~ Rob 13 Talk 17:36, 25 January 2017 (UTC)
 * 38 is not. better do a better research. -- Magioladitis (talk) 17:38, 25 January 2017 (UTC)
 * How does replacing this with this change the rendered page? ~ Rob 13 Talk 17:40, 25 January 2017 (UTC)
 * MOS:ITALIC -- Magioladitis (talk) 17:42, 25 January 2017 (UTC)
 * Moreover strike is a deprecated HTML tag. The correct one is -- Magioladitis (talk) 17:43, 25 January 2017 (UTC)
 * That doesn't answer my question, nor does it demonstrate any understanding that there's a difference between things that can be fixed and things that should be fixed at high volumes with a bot. Deprecated =/= non-functional, and there's similarly no rendered change to the page. ~ Rob 13 Talk 17:44, 25 January 2017 (UTC)
 * Mediawiki sill soon remove all deprecated tags.
 * 52 is an indication that the category is misplaced or lacks colon i.e serious potential error. -- Magioladitis (talk) 17:45, 25 January 2017 (UTC)

If you check the numbers of strike there are less than 2 pages per month! In fact we had no new pages since July 2016! -- Magioladitis (talk) 17:46, 25 January 2017 (UTC)

We an certainly re-evaluate all tasks and see what can be done and what does ot need to be done by bot. But I think the best page for that is WP:CHECKWIKI's talk page! I don't claim to know the one and only truth! -- Magioladitis (talk) 17:52, 25 January 2017 (UTC)

Note that the are 3 all-around bots approved by 3 different BAG members. So the CHECKWIKI page IMO is more appropriate. -- Magioladitis (talk) 18:05, 25 January 2017 (UTC)


 * I don't think that it makes sense to have open-ended approvals that are just discussed by the participants on the CHECKWIKI pages. The overall question in this thread is about one of those bot requests - the person who approved the BG19bot one says the intention was not to improve edits such as the ones I pointed out at the top of the thread. I don't think the existing CHECKWIKI bot requests are really compelling evidence of consensus. &mdash; Carl (CBM · talk) 02:21, 26 January 2017 (UTC)

Request to modify Yobot authorization
This is a proposal to revoke all approval for Yobot's bot jobs. Currently this bot is easily the most problematic on the whole project and problems date back to 2010 or earlier. The bot has been blocked 18 times previously, but each time the operator User:Magioladitis has managed to convince an administrator to unblock based on assurances that the bug had been fixed and will not occur again. The main issue with the bot is violation of the WP:COSMETICBOT rule, performing useless edits which fill up editor's watchlists.

When asked recently by User:SlimVirgin whether he could re-apply for permission to run these jobs, his uncompromising reply can be read here. So I am here to ask the community and BAG to revoke these permissions.

The advantage of forcing the operator to seek reauthorisation is that proper scrutiny can be given to each job and the method of working. It is possible that some of these processes are no longer supported by consensus. And it would give an opprtunity to spell out whether AWB's WP:GENFIXES may be used or not. I view this as a last chance for Yobot and Magioladitis's automated editing in general. If unresolved the next step is likely to be a community ban against all automated editing. &mdash; Martin (MSGJ · talk) 09:06, 20 December 2016 (UTC)

MSGJ Let's do this in steps then. I would like to check BRFAs 1-10 for starts. -- Magioladitis (talk) 09:09, 20 December 2016 (UTC)

And now I notice that some of the tasks requested for reapproval have already been abandoned by me. This makes no sense. Why should I get a new approval for tasks that were one-off or got outdated? -- Magioladitis (talk) 11:14, 20 December 2016 (UTC)
 * I think it would be fair to say that should this go though, you would not have to seek re-authorization for any task you didn't want to reopen... — xaosflux  Talk 13:31, 20 December 2016 (UTC)
 * so it's going to be me the one to redo all the job because someone just does not feel right about it? -- Magioladitis (talk) 13:34, 20 December 2016 (UTC)
 * That started with a big if - if the community consensus is that these tasks should be deauthorized, and then you want to later restart them you would have to re-request. It will take more than "someone" to deauthorize all those tasks. —  xaosflux  Talk 17:58, 21 December 2016 (UTC)

MSGJ to explain that last part. -- Magioladitis (talk) 11:15, 20 December 2016 (UTC)

Yobot is the 4th (or 3rd) most active bot on English Wikipedia. So I don't this is the "most problematic on the whole project". "Citation" needed or as the shortcut fans would write "cn". I also recall some other bots that were completely blocked for malfunctioning. So I guess Yobot is in a better shape than them. Moreover, Yobot has earned 9 barnstars for its edits. -- Magioladitis (talk) 11:21, 20 December 2016 (UTC)


 * per this section, I think  raises a valid point.  They state that bots should be dynamic, I couldn't agree more.

Consider vandalism removal, it's dynamic and as a result, is quite effective as a tool to keep wikipedia clean. Same could be said bot operations. If a bot is approved for say, fixing a reference in one article, and that reference happens quite a bit, why not add in an extra fix for, say another problematic reference in another article. The base mechanism of the bot already has approval, the second reference isn't problematic or controversial, so why not. To be clearer, let me state it this way, if the change is non-controversial, nor problematic, why not let the bot operator of an approved bot add that change in to his or her bot . Wikipedia certainly doesn't benefit by holding long week or longer discussions on such a change, just make the change ! Kosh Vorlon ''' 14:34, 20 December 2016 (UTC)
 * Suggestion: Yobot's tasks, as far as I can tell, are valid, but if the bot finds that the error it is looking for is no longer present, it should skip the article. I believe that would fix all valid editor complaints. Mag: please don't fight this. You will lose, and the project will be worse for it.


 * One side note: Editors sometimes complain about valid, approved tasks that this bot and perform, like removing spaces and non-printing characters for accessibility. These are approved bot tasks that are not cosmetic, even though they do not appear (to most people) to render the finished article any differently.  – Jonesey95 (talk) 14:54, 20 December 2016 (UTC)
 * The comparison with dynamic anti-vandalism bots is seductive, but ultimately it fails. No one is going to complain about reverting vandalism, but many editors complain about Yobot.  I wouldn't have so much of a problem with dynamic working if the operator immediately stopped making an edit (I mean a "dynamic" one without community consensus) that someone complained about.  The fact that someone is complaining means that it wasn't actually all that uncontroversial and consensus should be sought.  That is generally not the response from Yobot's operator.  More often than not there is a refusal to stop and a claim that the task has consensus when really it doesn't, it was just something that happens to be in genfixes, and the contents of genfixes are not reviewed by BAG.  And there is the problem, some Yobot tasks rely on genfixes to work, but genfixes, in general, doesn't have community consensus.
 * The issue that led to Yobot's current block for making cosmetic-only edits was substituting template redirects, which most editors consider cosmetic edits. Now I understand why AWB needs to maintain a list of template equivalences - some processes depend on that, but I don't understand why bots need to be running around actually substituting them.  I don't even understand why AWB human operators are being suggested to do this, let alone bots.  So in short, I think it right that at least current Yobot tasks implementing genfixes should be re-examined. Spinning<b style="color:#4840A0">Spark</b> 15:50, 20 December 2016 (UTC)

most of the complaints I get are not from the "usual suspects" but for adding "orphan" in pages. This is because many people do not understand the concept of "orphan". Similar,I get many complaints who do not exactly disagree with me or my bot but with the policy/guideline itself. As I wrote WP:GENFIXES links to all templates affected. The documentation of each templates explains what it does. You wrote that genfixes do not have enough documentation. This is not true. There are many links. Moreover, this page was created after AWB's code expanded and not the other way around. It was difficult sometimes to even determine what each piece of AWB's code does. -- Magioladitis (talk) 16:01, 20 December 2016 (UTC)
 * I don't know where you think I said that genfixes doesn't have enough documentation, but if it's where I said that it does not have an audit trail then that is a very different thing. <b style="background:#FAFAD2;color:#C08000">Spinning</b><b style="color:#4840A0">Spark</b> 16:15, 20 December 2016 (UTC)
 * A large part of the documentation was written by who is not of the developers. It's very difficult to keep the documentation, the changelog and the program all up-to-date. I also keep a log of all changes that affect CHECKWIKI. See how many cases are now fixed compared to 2014. Yobot is by far making much fewer null edits than in the past. -- Magioladitis (talk) 16:17, 20 December 2016 (UTC)
 * I think it's clear we need more copycats of Yobot and more bot operators involved. -- Magioladitis (talk) 16:34, 20 December 2016 (UTC)

I'm in support of MSGJ's request here. It has become something of a mess; let's clear the slate, and get some decent scrutiny (and community consensus) for each of the proposed tasks going forwards. Hchc2009 (talk) 17:02, 20 December 2016 (UTC)
 * Hchc2009 which task is not clear to you then? -- Magioladitis (talk) 17:05, 20 December 2016 (UTC)


 * Support revoking approval for Yobot's jobs. Looking through some of the talk-page archives (by no means all), I've found around 130 threads about Yobot's or Magioladitis's cosmetic-only edits or ref reordering, and this does not include complaints about other issues. Magioladitis is deaf to all concerns, blaming issues on a bug that has been fixed or is being fixed. Other bots do not attract this number of complaints. The discussions have wasted hundreds of hours of volunteers' time; the most recent AN is at Administrators' noticeboard/Archive279, 28 January – 19 February 2016. Yobot has been blocked 18 times because of it and Magioladitis five times. Better to wipe the slate clean and start again than to argue over the details. SarahSV (talk) 18:01, 20 December 2016 (UTC)
 * SarahSV There is no consensus against ref reordering yet. I am now reviewing the discussion. -- Magioladitis (talk) 18:18, 20 December 2016 (UTC)


 * Support, if that was not clear enough from my previous comments. <b style="background:#FAFAD2;color:#C08000">Spinning</b><b style="color:#4840A0">Spark</b> 19:14, 20 December 2016 (UTC)
 * Oppose this seems to be the continuation of disagreements between SV and Magioladitis by other means.  If anyone has any issues, let them challenge the individual BRFA.  A blanket revocation, causing Magioladitis (and others) hundreds of hours of work to re-do them all seems a sledgehammer to crack a nut.  All the best: Rich Farmbrough, 19:37, 20 December 2016 (UTC).


 * Well the first problem there is that of the last 100 edits Yobot made prior to being blocked, not one of them indicated which approved task the bot was implementing. So how is an ordinary editor supposed to know which BRFA they wish to challenge?  Or even find out that there is such a thing as BRFAs in the first place? <b style="background:#FAFAD2;color:#C08000">Spinning</b><b style="color:#4840A0">Spark</b> 14:27, 22 December 2016 (UTC)
 * For most bots, the use of a task list on their userpage and good edit summaries normally suffice. When there are many tasks it can get confusing. It is fairly easy to incorporate this to an edit summary (example) - would having that type of information help? —  xaosflux  Talk 15:05, 22 December 2016 (UTC)
 * I replied at User_talk:Spinningspark. -- Magioladitis (talk) 15:50, 22 December 2016 (UTC)


 * Oppose per Rich. I'm all for additional scrutiny given the recent disagreements, but it should be on the proposer to specify what tasks are problematic or may no longer have consensus. Especially for such an active bot, the solution to disagreements can't be to just revoke it and start from scratch. Besides that, I think Jonesey95's point about how removing white space for accessibility reasons hasn't been given enough attention. Just because it doesn't change the output of your page doesn't mean it's cosmetic for other editors using screen readers and other devices. Wugapodes [thɔk] [ˈkan.ˌʧɻɪbz] 20:57, 20 December 2016 (UTC)
 * Your statement makes no sense. If the change does not change the rendered output, that's the very definition of WP:COSMETICBOT.  Screen readers would still interpret the output the same way.  HTML syntax allows rendered out put of up to one space using whitespaces.  The rest need to be coded in with HTML syntax.                If you observe, the spacing between the start of this sentence and the previous one, is more than one in the edit window, but still renders as one in the output.—<sup style="color:green;font-family:Courier">cyber power <sub style="margin-left:-13.5ex;color:red;font-family:Comic Sans MS"> Merry Christmas:Unknown 03:07, 21 December 2016 (UTC)
 * I suppose I should have linked directly to the BRFA for BG19bot 9, where white space removal by a bot was approved to fix an accessibility problem.


 * That said, there are many complaints about Yobot making cosmetic edits because it fails to find something to fix. Here's one on the bot's talk page right now, from just nine days ago. As far as I can tell, Yobot made a purely cosmetic edit in that case, and Mag replied "The bot failed to fix this (link). Changes to CHECKWIKI affected bot activity. I am on it." If the bot fails to find something to fix, it should take no action. I am not a bot admin, but this should not be hard to change.


 * Can someone here please help Mag fix Yobot so that it skips edits instead of making purely cosmetic edits? Other bots appear to do it just fine. For an example of an editor who has no problem with this issue, see the query at User talk:GoingBatty/Archive5 about "Civilian casualty ratio" and the response from the bot operator. Maybe Yobot is different somehow? – Jonesey95 (talk) 06:54, 21 December 2016 (UTC)
 * My plate is full. IABot generally doesn't reformat a cite template unless it's actually doing something with it.—<sup style="color:green;font-family:Courier">cyber power <sub style="margin-left:-13.5ex;color:olive;font-family:Comic Sans MS"> Merry Christmas:Unknown 14:25, 22 December 2016 (UTC)


 * Comment I don't recall a specific BRFA being the cause to when people start complaining about his cosmetic edits. If Yobot has to go thru BRFA's again, will Martin, SlimVirgin, Spinningspark and Carl be fighting tooth and nail or will the BAGs be able to do their job?  Bgwhite (talk) 02:44, 21 December 2016 (UTC)
 * As far as I'm concerned, only currently live tasks that have approval to apply genfixes need re-evaluating. In fact, I would be happy if just Yobot's use of genfixes was discussed in general rather than each individual task.  Everything else can be nodded through.  I can't speak for others of course. <b style="background:#FAFAD2;color:#C08000">Spinning</b><b style="color:#4840A0">Spark</b> 03:19, 21 December 2016 (UTC)
 * I think you would find that most if not all of Yobot's jobs involve genfixes. So you would effectively be reviewing all the jobs, which is why I believe a clean start is necessary. &mdash; Martin (MSGJ · talk) 09:35, 21 December 2016 (UTC)
 * That may be so, and it might be helpful if Magio declared which jobs are applying genfixes if that is different from the ones on which he has explicit approval to apply genfixes, but I think it is going to be a lot more productive to have an overarching approval (or denial of approval) on the use of genfixes, rather than have Magio repeat the same rationale over and over in multiple applications. From his comments, that is clearly going to be a great source of unnecesaary annoyance to him. <b style="background:#FAFAD2;color:#C08000">Spinning</b><b style="color:#4840A0">Spark</b> 11:45, 21 December 2016 (UTC)


 * Comment I've seen this get out of hand at ANI, recalling User:Bgwhite and User:Magioladitis quibbling over User:Yobot. To be honest I found it to be a bit childish, and both sides could have handled it better.  I'm not going to support or oppose this because a bot op should be able to comply with basic bot policy.  It's not difficult.  If COSMETICBOT is the problem, use the API's parser to compare rendered output between the new and old version.  If they are the same skip the edit.  The API has a beautiful parsing function bots can use.  It certainly makes IABot's life easier when rendering embedded templates in cite templates.—<sup style="color:green;font-family:Courier">cyber power <sub style="margin-left:-13.5ex;color:red;font-family:Comic Sans MS"> Merry Christmas:Unknown 03:15, 21 December 2016 (UTC)
 * . True. But I think the problem is that some people would oppose changes that actually change the html output. -- Magioladitis (talk) 08:53, 21 December 2016 (UTC)
 * Well in that case I would have to say a widely advertised RfC is in order to see what the community really wants. I wasn't happy when I encountered Yobot initially as it kept moving a comma around in the article I created.—<sup style="color:green;font-family:Courier">cyber power <sub style="margin-left:-13.5ex;color:olive;font-family:Comic Sans MS"> Merry Christmas:Unknown 14:25, 22 December 2016 (UTC)


 * Support. Yobot has been operated in a problematic way for years; the operator has refused to fix several longstanding problems. The first is the continual pattern of cosmetic edits. The second is lack of clear edit summaries. BAG missed an opportunity to remedy/prevent these issues in the first round of bot approvals for Yobot. Usually these issues aren't a problem because other operators follow best practices. A second round of approvals could remedy the situation now that the pattern of bad edits is known. &mdash; Carl (CBM · talk) 13:50, 22 December 2016 (UTC)


 * Support. Extremely problematic behavior from this bot for years. I've run into downright head-scratchers here regularly, and some of these approvals are incredibly broad to a degree that would never be approved today. It's clear this bot operator needs some oversight, and all these blanket approvals aren't sufficient in providing that. I think this is the best course of action for both the community and the bot operator, as it will give them a better idea of how they must operate to remain inside the bot policy if BAG members are overseeing their tasks more regularly. ~ Rob 13 <sup style="margin-left:-1.0ex;">Talk 06:46, 27 December 2016 (UTC)
 * How willing would you be to take a look through all bot tasks and voluntarily revoke Task 16 and others that are blanket approvals (which have been problematic in the past from Yobot)? I could be persuaded to oppose a blanket revocation if good-faith steps were made to get rid of the problematic approvals. If this is something you'd be willing to seriously consider, I'll try to put together a list of what I think needs re-examination. It does go beyond task 16, but possibly not that far beyond. Some of them are really ancient blanket approvals that would be unlikely to be approved in modern times. ~ Rob 13 <sup style="margin-left:-1.0ex;">Talk 09:41, 30 December 2016 (UTC)
 * examples of blanket approvals? -- Magioladitis (talk) 09:43, 30 December 2016 (UTC)
 * Task 9 approves project tagging for all projects, including any method of changing parameters, with no restriction on how complicated or cosmetic that may be. Compare, for instance, to my many project tagging bot approvals in the modern day. These days, such tasks are typically sent through one-at-a-time to check consensus, at the very least. I haven't checked systematically yet, but that one springs to mind. ~ Rob 13 <sup style="margin-left:-1.0ex;">Talk 09:47, 30 December 2016 (UTC)
 * If I recall correctly this was asked from you because you were not 100% familiar with the Wikiproject concept by that time and in a perspective at some point to grant you a blank approval after the Wikiprojects get aware of your bot and you become more experienced. But anyway, this one is from the tasks I asked people to take over. You are of on my candidates to take this. -- Magioladitis (talk) 09:57, 30 December 2016 (UTC)
 * Actually, I never requested blanket approval for this sort of task because I just don't think it's appropriate. There are so many permutations of how WikiProject tagging work that I see it as worthwhile to have a BAG member check over the consensus, determine if it's really similar to past tasks in implementation, and then either speedy approve or request a trial based on how things look. I will freely admit I specifically have an issue with you doing certain tasks (mainly, Task 16), because of past history with cosmetic changes. But this is something I'd want revoked from anyone, because I don't think it's an approval that stands up to community norms of bot approvals in the modern day. I'd be more likely to oppose a blanket revocation if you voluntarily gave up the tasks that I think are problematic regardless of who the botop is. (And you're welcome to send projects that need tagging done my way, although I'll accept/reject such requests based on my own standards of what's appropriate for project tagging. I learned long ago not to take projects at their word on tagging.) ~ Rob 13 <sup style="margin-left:-1.0ex;">Talk 10:05, 30 December 2016 (UTC)
 * As I wrote: Yes, the biggest problem is Task 16 and I am OK if Yobot stops doing most of it. I have skip conditions for CHECKWIKI #16, #78 and some others which Yobot can continue doing. I am OK if BG19bot, MenoBot and other do the other tasks instead of Yobot. Some other tasks I already have given or tried to give to Dexbot. I am usually the bad guy because I always jump into the new errors. Notice, that the entire logic for fixing new errors is based on Yobot's bugs that were reported and fixed. -- Magioladitis (talk) 10:22, 30 December 2016 (UTC)


 * Comment I think the only problem is Task 16 due to its nature. I can work with on which CHECKWIKI errors should be discontinued in bot mode after recent changes. -- Magioladitis (talk) 10:42, 27 December 2016 (UTC)


 * The issue of cosmetic and unapproved edits has come up over and over with Yobot, for numerous bot tasks, not just one CHECKWIKI error.  In my mind, the best solution would be to disable all "general fixes" and only apply the very specific change described in each bot request. If a bot request is not specific enough to say the precise change that will be made, it can always be resubmitted. &mdash; Carl (CBM · talk) 17:41, 30 December 2016 (UTC)


 * Above, I was hoping to go through the tasks and work out a way to only support rescinding some of the tasks, but I just saw something that convinced me full revocation is the way to go. The bot operator has now stated in Special:Diff/757725689 that he routinely runs Yobot after making substantial untested changes to how it operates. That alone should be enough to rescind all approvals. No wonder there have been such large error rates! The bot approvals process can provide the structure to test changes, and with more narrow approvals, I think Yobot can get to the point where it runs smoothly. ~ Rob 13 <sup style="margin-left:-1.0ex;">Talk 11:37, 1 January 2017 (UTC)
 * In the last year there were 4 or 5 changes that affected the lists. I should be more careful to see that some lists exploded. I am aware of that that's why I asked that the lists now contain the number of items in their edit summary. I feel like you Wikilawyering. -- Magioladitis (talk) 11:55, 1 January 2017 (UTC)


 * Comment. Pardon me if this seems like a "Captain Obvious" thing to point out, but as someone who has used AWB a lot for the past 2 1/2 years, I know a little about the tool. :)  This particular factoid never seems to make an appearance with respect to Yobot.  That factoid is: "Skip only cosmetic changes" is a feature in AWB, and it's a mere checkbox.  Yobot uses AWB.  So, why doesn't Yobot have this checkbox checked?  And if it does have it checked, why is AWB failing to skip cosmetic edits?  Stevie is the man!  Talk • Work 18:51, 4 January 2017 (UTC)
 * I have filled a bug report in April this year -- Magioladitis (talk) 19:05, 4 January 2017 (UTC)
 * On this aspect, I truly feel your pain. :)  Stevie is the man!  Talk • Work 20:04, 4 January 2017 (UTC)

Take note that I never denied help and never claimed that the underlying huge problem of not having correct skip conditions has been solved. This can be resolved better in an eternal way similar to what WPCleaner does: It sends a call to the server and checks whether the error is still reported. This is time consuming ofcourse. For instance, right now the time to check whether the error has been fixed it takes me more time than to run general fixes in the page. has done great effort to reduce the time. We even found errors in the code last year. We are actually making effort on this by exchanging emails daily. This is not only the job seen on-wiki. Some people may not believe it but, and me spend several hours per day to fix things and synchronise three different programs. It's not an excuse when I say that I am not sure I have more free time to give. My entire is this.

I even tried to write which AWB function is called to fix each error and wrote it down at User:Magioladitis/AWB and CHECKWIKI. In some cases more than one function is needed or in other case the function called does much more thinhs than just fixing the error. -- Magioladitis (talk) 19:16, 4 January 2017 (UTC)


 * , the issue that puzzles people is that other bots don't have this trouble. Is there something different about Yobot that causes the problem? SarahSV (talk) 19:29, 4 January 2017 (UTC)
 * SarahSV what I think does is to do almost every single error semi-manually except a very small number done by his bot. It's amazing but also very cruel. Bgwhite spends hours doing everything manually. If we had more volunteers participating in the CHECKWIKI project we may not needed the bots at all. But 2 people fixing 1,000 pages daily (including weekends) it's cruel. I think he can speak for himself ofcourse. Other, like  tried to help but for various reason the are not so often on-wiki anymore. On the other hand, I invested my time reporting errors and trying to find patterns to fix as much as possible by bot. It's true than in some cases I reached the limits of AWB i.e. there were cases not fixed. I don't claim to to be an expert programmer. I usually give tasks to others. -- Magioladitis (talk) 19:48, 4 January 2017 (UTC)
 * , as I understood our conversation here and here, the cosmetic edits are a main feature for you. You see them as important because you want the wikitext to be perfect, so you don't switch them off. Other editors do switch them off. They check "Skip only cosmetic changes". Is that not the case? SarahSV (talk) 19:56, 4 January 2017 (UTC)
 * SarahSV There is no way to switch them off. There is a way to skip a page if only "cosmetic changes" happen. But this definition in AWB does not include bypassing redirects. -- Magioladitis (talk) 20:02, 4 January 2017 (UTC)
 * SarahSV Just a clarification: Yes, I enjoy doing little edits but this does not mean I do them with my bot account. By bot has a very specific approval and I try to respect that. There is not fun in sitting and seeing a program do the minor edits for me :) Moreover, that I enjoy this that does not mean that this is the main thing I do or that I do it that massively as it is implied by some others. Most probably, I combine my editing with something useful. -- Magioladitis (talk) 20:16, 4 January 2017 (UTC)
 * Okay, so I return to the question. Yobot makes lots of cosmetic-only edits. Other bots don't. AWB allows you to skip cosmetic-only edits. Why doesn't Yobot skip them, as other bots do? SarahSV (talk) 20:25, 4 January 2017 (UTC)
 * SarahSV I do. With the existing AWB code bypassing a redirect is not cosmetic. It changes the html output. -- Magioladitis (talk) 20:29, 4 January 2017 (UTC)
 * I'm not talking only about bypassing redirects, but about "cosmetic edits only" in general; for example doing nothing but add white space. Yobot does that a lot, so clearly the bot is not skipping pages when there are "cosmetic changes only". SarahSV (talk) 20:37, 4 January 2017 (UTC)
 * there's a setting for that too: "Skip Only whitespace" -- this can be checked at the same time. Magio, do you check this for Yobot? If not, is there a reason why not?  Stevie is the man!  Talk • Work 20:41, 4 January 2017 (UTC)


 * Of course, as a bot operator you are in complete control of the code that you run. There are several straightforward fixes to the problem, including (1) comment out all tasks other than the one the bot is meant to perform, or (2) make a test directly after the task that was supposed to be performed, and skip the page if that particular task did not change the page source. It is not reasonable for a bot operator to continue running flawed/buggy bot code, while simultaneously claiming that they are not able to fix that code.  That is the root of the issue here: when an error is found that is easy to duplicate, the bot should not be run again until the code is fixed. &mdash; Carl (CBM · talk) 20:14, 4 January 2017 (UTC)
 * CBM True. As I wrote above I am ready to have my list of CHECKWIKI errors fixed by bot drastically reduced. For example User_talk:Magioladitis. -- Magioladitis (talk) 20:19, 4 January 2017 (UTC)
 * That does not solve the problem, which is that the bot will still save edits when it should not, unless the code of the bot is changed to prevent it.  The template redirects issue that you mentioned dates back to 2010, but the bot continues to make the same error: .  There has been plenty of time for you to fix the problem; is time for all the BRFA approvals to be rescinded, and re-approved only with clear guarantees that this problem will not re-occur.  &mdash; Carl (CBM · talk) 20:24, 4 January 2017 (UTC)
 * Given Yobot uses AWB, that is technically "somebody else's code" (to a large extent save the specific fixes). Also, it already has a checkbox to skip cosmetic edits, except that it won't treat template redirect bypasses as cosmetic, unfortunately.  If that bug in AWB was corrected, and Yobot given a test period to run after that, maybe BAG could reasonably decide to not throw the baby out....  Stevie is the man!  Talk • Work 20:34, 4 January 2017 (UTC)
 * No, because bypassing redirects are not the only "cosmetic edits only" edits that Yobot makes. Why is this so hard to get across? SarahSV (talk) 20:41, 4 January 2017 (UTC)
 * It has gotten across to me. See my reply above about whitespace, noting that a whitespace only change will often be considered non-cosmetic by AWB, so skipping both cosmetic only and whitespace only seems the best way to go.  Stevie is the man!  Talk • Work 20:44, 4 January 2017 (UTC)
 * AWB might be somebody else's code, but once a bot operator chooses to use it they take responsibility not to use it in ways that cause problems, and to fix problems that arise. In this case, Magioladitis has refused to fix the issues with the bot for several years. If AWB is not an appropriate tool for Yobot, he should use a different tool. Other AWB operators manage to avoid the issue, by and large - I see many AWB bots on my watchlist, but not making the same errors as Yobot.  All in all, this is why I think that the focus should be on Yobot, rather than AWB. &mdash; Carl (CBM · talk) 20:49, 4 January 2017 (UTC)


 * It seems to be hard to get across that a "cosmetic only edit" is one that doesn't change the appearance of the page to a reader. Anything falling under that definition must (a) be done at the same time as a substantive edit; or (b) the bot needs special approval.


 * This discussion misses the point that M seems to want to make these cosmetic edits, because he wants the wikitext to be perfect (in his view). That's why he often adds a non-breaking space, so that he can also fix a redirect or add white space. If he didn't want to do this, it would not have been happening for eight years. It's that underlying issue that needs to be addressed, especially given that he says it is taking up all his time. We have a lose-lose situation here, and talk of bugs and code is missing that important aspect. SarahSV (talk) 20:52, 4 January 2017 (UTC)


 * I know what a "cosmetic only" edit means to the wiki community, but "cosmetic only" in AWB merely means if the HTML hasn't changed. That's why normally with using AWB, I also skip whitespace only and oftentimes skip only minor genfixes so it makes my job easier (but not as easy as proceeding with my eyes closed) to pinpoint a total save that doesn't have at least one substantive change in it.  That's why it's hard to use AWB for unattended bot purposes.  I won't speak to what Magio wants.  I'm trying to see if a better technical approach, combined with bug fixes, would resolve this.  Stevie is the man!  Talk • Work 21:05, 4 January 2017 (UTC)

Some whitespace fixing maybe coming from main functions while trying to do other stuff. Skip if only whitespace has prevented legit in the past. For example error #89 is about adding whitespace. -- Magioladitis (talk) 20:54, 4 January 2017 (UTC)
 * If Yobot is being used to fix an approved whitespace-oriented error, then, obviously, don't skip whitespace only on those runs. Otherwise, it seems best warranted to skip whitespace only and maybe lose out on a few legit edits to get gains in the bot's observed integrity.  Stevie is the man!  Talk • Work 21:31, 4 January 2017 (UTC)

SarahSV I don not want my bot to do "trivial edits". You miss that point. -- Magioladitis (talk) 21:02, 4 January 2017 (UTC)


 * I began collecting diffs of threads some time ago, in anticipation that this would go to AN/I or ArbCom at some point. I intended to post them on a user subpage in case they were helpful. I ended up finding so many that I didn't post the page, because it was a wall of shame. For eight years, editors have been stuck in a loop when dealing with you. "Don't do X." Sorry, it's a bug. "Don't do X." Please define X. "Don't do X." Sorry, it's a bug.


 * I would like to identify the underlying cause of that miscommunication, so that we can escape the loop. SarahSV (talk) 22:23, 4 January 2017 (UTC)


 * SarahSV Well, for eight year I am helping in improving AWB. I am a volunteer. This is the best I can do. I am not even a programmer. I learned to program some stuff in order to help and stop bugging the only 2-3 programmers who work with AWB. AWB is open source and I never denied patches. Thanks for thinking that I am super-human (judging by the time I spend online?) but I am afraid I am not. Many other bot owners just stopped and bot task were abandoned. I am still trying to find my successor. Yobot is not the best we have. It's still more optimal from many other things around. Do you know someone that could write me a custom module that will load all CHECKWIKI errors and have skip checks for them? I would be more than happy to run this module. I am writing you that my make effort to make things better, I provide you proof. You obviously want more. :) PS In latest Hackathon I organised in Greece I even asked students to help out with some of the bugs. -- Magioladitis (talk) 23:10, 4 January 2017 (UTC)
 * At the risk of being overly charitable, those bugs maybe really were bugs. As new fix tasks come aboard, new bugs become likely, and they have to be addressed each time.  As for the definition misunderstandings, I may have trouble being as charitable, because I think it's hard to escape understanding of what a substantive edit is and isn't in most cases.  Stevie is the man!  Talk • Work 23:36, 4 January 2017 (UTC)

Which AWB fix/tweak would resolve the following editing error:. The bad edit summary compounds the problem, since there is no way to tell what the bot was trying to do, but certainly that edit was not what the bot was supposed to do. There was no accompanying whitespace change, I think. &mdash; Carl (CBM · talk) 22:53, 4 January 2017 (UTC)
 * I don't know how the summary is being set, whether manually edited, or using Find/Replace or module, so I can't speak to that, but for this to be saved by the bot at all, given "Skip Only cosmetic changes" is checked, is due to an as-yet unfixed AWB bug. I suspect that was part of a run where the intended fix wasn't necessary for that article by the time the bot got to it, but the template redirect bypasses were left -- and they sailed through because there's generally no reasonable way for AWB to stop them -- unless and until this bug is fixed or if genfixes aren't done at all for the time-being (but then, other potential substantive fixes won't happen). Stevie is the man!  Talk • Work 23:09, 4 January 2017 (UTC)
 * I'll limit my comments to the technical issues only. Current approach for these kinds of bot tasks aiming to fix a specific error seems to be:
 * get list of articles having the error from a reporting tool (e.g. CHECKWIKI), process all the articles
 * use a fixing tool (e.g. AWB) to process article by applying the tool's standard fixing routines
 * hope that the tool found and fixed the error
 * apply some basic or general checks to skip the edit in certain situations
 * So the fundamental technical problem as I see it is that an accurate bot task with a very low cosmetic edit rate needs to have two task-specific checking steps:
 * get list of articles having the error from a reporting tool (e.g. CHECKWIKI), process all the articles
 * check page currently has specific error, skip if it doesn't
 * use a fixing tool (e.g. AWB) to process article by applying the tool's standard fixing routines
 * check page no longer has specific error, skip if it still does
 * CBM's suggestion of only running selected genfix functions has some merits, however there are some functions that can make both significant and sometimes trivial/cosmetic changes, so again without specific checks, while that approach might somewhat reduce cosmetic/trivial error rate, it doesn't fully solve it. Other discussion about template redirects etc. to me misses the fundamental point about specific checks; one source of cosmetic/trivial edits could be template redirects today, but tomorrow could be stub whitespace, excess template pipes or one of potentially dozens of other items.
 * So what I'd expect is that the bot operators are asking other editors/contributors to the tools and editors with technical skills for help to configure these specific checks. Magioladitis' last comment suggests he's willing to go down that route. Rjwilmsi  23:29, 4 January 2017 (UTC)
 * I agree this could be looked at with a wider lens, and should be, but the specific case of template redirect bypassing is a pure cosmetic edit in the AWB sense -- no difference in HTML output. Fixing that won't fix everything that is possible to be fixed for the bot to run perfectly or nearly so, but nevertheless, fixing this will be a welcome and true improvement for AWB users in general, and somewhat ameliorates Yobot's troubles.  Stevie is the man!  Talk • Work 23:52, 4 January 2017 (UTC)
 * A standard algorithm to avoid this is to test the source of the page before and after the desired edit of the bot is applied. If there is no change in the source, then the page should be skipped. If there is a change, then general fixes can be applied. This algorithm is entirely local within AWB and does not require double-checking whether a page is or should be on any external list. It only requires saving/rendering a copy of the soruce code before and after a particular fix is run, and then comparing the two versions. So it is also very efficient. Is there a technical reason this cannot be implemented? It seems like it would resolve most of the cosmetic edits easily.  &mdash; Carl (CBM · talk) 01:01, 5 January 2017 (UTC)


 * This discussion should probably be postponed until the resolution of the Arbcom case because it's unlikely that Yobot will be unblocked before then, if at all. Ramaksoud2000 (Talk to me) 05:23, 5 January 2017 (UTC)
 * Well, we're discussing some technical principles so I think there's value in discussing even if any unblock wouldn't be soon.
 * The phab AWB ticket is now fixed, the "only cosmetic changes" skip check is now working e.g. for template redirects.
 * In summary I'm proposing task-specific skip checks, you propose task-specific logic to fix the targeted error. They would get to the same place, but with AWB one is easier than the other, which I'll explain detail below. So I don't disagree with you, am trying to describe an easier/simpler means of getting there.
 * To be clear, I think you mean checking the rendered page to see if there is a visible change. Yes, AWB already has this, though only to check the entire AWB edit, not a first part of it as you suggest. (It requires two API calls so technically I would not call it particularly efficient, but nobody here counts API calls so that's no matter) Secondly your suggested approach means the bot task has to develop its own code/logic to make the fix, separately for each task, test that for visible change, then apply genfixes. This would be possible in AWB but would require coding to have a custom module/external process to run a fixing routine developed per bot task, then apply the cosmetic change check, then only apply genfixes. So genfixes couldn't be used to attempt the fix of the error, which realistically means the fix logic would be trying to reimplement portions of genfixes.
 * That approach is unlikely to be something that bot operators such as Magioladitis have the technical knowledge to do. I am thinking the most feasible in AWB, and still fundamental technical solution, is for the bot task to add task-specific error checks. If the error comes from CHECKWIKI then it ought to be possible to import the error checking logic, which is probably based on regular expressions, into AWB, which if just regular expressions would be a matter of configuration of AWB rather than complex code. Run the check before to ensure the error is there, run again after genfixes to confirm error has gone away. Rjwilmsi  07:21, 5 January 2017 (UTC)
 * Checking the rendered page via the API would work, as well, but of course it is much slower. I was talking about something simpler, just checking the source of the page. As I understand it, the problem with Yobot is that it wants to apply a particular change to an article, and then apply general fixes. But it has no error checking to tell whether the initial change actually changed anything, so it just goes ahead and makes the general fixes and saves the page anyway. This is why it matters to keep the lists very fresh. At least, this is how Magioladitis has explained the problem several times.  If the system could tell whether the original, desired change actually changed the page's source code, then the system would be able to tell whether to save the page or skip to the next one. (The original change might be a specifically approved cosmetic change, as well.)  Of course, importing the CHECKWIKI logic would also work. &mdash; Carl (CBM · talk) 11:17, 5 January 2017 (UTC)
 * Carl, "the problem with Yobot is that it wants to apply a particular change to an article, and then apply general fixes" I think the problem is that "it wants to apply a particular change to an article" by applying general fixes, so then has difficulty determining if the change(s) made included fixing the issue or not. Bearing in mind that a visible change could still be cosmetic, and a visible and/or useful change may still not relate to the intended error, so there is no single generic check that can determine that; we agree that by some means a specific check as to whether the desired fix happened is needed. Rjwilmsi  11:44, 5 January 2017 (UTC)

FYI, fixed the "Bypasing redirects should be a cosmetic change". This means edits like the one Carl provided should not happen again. -- Magioladitis (talk) 09:46, 5 January 2017 (UTC)
 * Yes, with a working "skip if change doesn't affect the rendered page" check, you can be sure that the edit changed the page appearance, so will avoid some cosmetic edits, but that check still doesn't confirm whether the visible change made related to the error the bot intended to fix. Rjwilmsi  11:48, 5 January 2017 (UTC)
 * My (maybe limited) understanding of this case is that the "error rate" with regards to non-substantive saves was too high, with concerns about intended fixes not being made and inadequate edit summaries being secondary. Your fix to AWB (thank you) should reduce this error rate. Increased use of "skip only whitespace" could reduce it further. Better timing of article lists to work on before running the bot on them might help even more. What I'm left wondering is how much of an error-rate of non-substantive saves would BAG members tolerate.  With the AWB fix becoming available and improved use practices adopted, maybe Yobot should be given a test period to see if the problems that bother editors are significantly reduced.  Stevie is the man!  Talk • Work 12:19, 5 January 2017 (UTC)

Closure?
on the contrary I think it would be helpful if BAG could close this discussion sooner rather than later, as it is entirely within their purview and will probably streamline the arbitration case. &mdash; Martin (MSGJ · talk) 09:31, 5 January 2017 (UTC)
 * That's fine. I just didn't want people to continue to take the time to discuss something that may no longer be relevant soon. Ramaksoud2000 (Talk to me) 14:40, 5 January 2017 (UTC)

Sorry to ping you all, but it would be helpful to have an official closure of the discussion above by a member of BAG. The discussion has been open more than a month and has not been edited in the last two weeks. Alternaitvely if you decline to close the discussion (for whatever reason) perhaps a short statement to that effect would be useful so the arbitrators of Arbitration/Requests/Case/Magioladitis know where they stand. Thank you &mdash; Martin (MSGJ · talk) 14:06, 23 January 2017 (UTC)
 * Alternatively, ask for an uninvolved admin to close it at WP:ANB if no one from BAG is willing to do it. I don't think this can be left just hanging. <b style="background:#FAFAD2;color:#C08000">Spinning</b><b style="color:#4840A0">Spark</b> 14:13, 23 January 2017 (UTC)
 * It's not clear under current policy that admins can do that. If no BAG member will handle closing deauthorization discussions, we need to rethink how we handle bot approvals. Makes little sense to have a body who approves but won't withdraw approval. ~ Rob 13 <sup style="margin-left:-1.0ex;">Talk 14:20, 23 January 2017 (UTC)
 * The policy (WP:BOTAPPEAL) is quite vague on how this process should work. I think we should wait for BAG to close the discussion (or at least to indicate that they decline to act) before asking random admins. &mdash; Martin (MSGJ · talk) 14:22, 23 January 2017 (UTC)
 * Yes, BAG should make a statement, but that should not be to do nothing and leave it in limbo. My suggestion was that BAG themselves should ask for an outside closer if none of them feel able to do it. <b style="background:#FAFAD2;color:#C08000">Spinning</b><b style="color:#4840A0">Spark</b> 14:32, 23 January 2017 (UTC)
 * I'm speaking for myself that I don't specialize in evaluating consensus of large, contentious debates. Here we are discussing revoking all of Yobot's approved tasks. Those tasks were approved though, by BAG, so the thing we are supposed to specialize in was already done, and we're being asked to redo it. I sort of have my own opinions as well: some of these tasks seem helpful to me, but as some have said, they may no longer be supported by consensus. The consensus part I don't think you need BAG for. If there is a new consensus that an approved task should be terminated, it is my opinion that overrides any previous BAG approval, since consensus is a requirement for it to have been approved in the first place. This is no different than having a policy change based on new consensus after a discussion was closed by admin A, where you are amending an older policy change that was a result of discussion closed by admin B. Admin A does not really need to consult admin B, the community at large has changed their mind. So if it were up to me, I'd say any uninvolved admin or even experienced non-admin should be able to make the call here, especially since the issue seems to be closely tied to operator behaviour. I also think the outcome of this discussion should in some way be reflected at WP:BOTAPPEAL, as indeed this process isn't very clear &mdash; MusikAnimal  talk  16:30, 23 January 2017 (UTC)
 * I've looked this over, as well as much of the discussion in the ArbCom case, but I'm not seeing which way to go.
 * The initial premise here is "Yobot's cosmetic edits are too much trouble, let's wipe out all of its tasks and start over", which is a lot of wiping-out when it comes to a bot with twenty-some approved requests. As far as I can tell no one has even tried to identify which of those tasks are still active or which tasks besides Yobot 16 are the source of the cosmetic edits, but several people have brought up that point.
 * Checkwiki fixes in general seem to have started to be controversial. Again, it would be helpful if someone would identify which checkwiki errors have cosmetic fixes and which are "substantial", and then identify which of the cosmetic fixes have a consensus to override WP:COSMETICBOT (in the community beyond the few editors who actually deal with checkwiki).
 * The ideal thing here, if I'm reading the underlying discussion currents correctly, would be to stop the tasks that are using AWB general fixes to do the actual work while allowing tasks that have functioning skip conditions to proceed. If a "general fixes" task can be fixed to have a functioning skip condition (versus the historical "I'll try to make better lists" non-fix), I wouldn't oppose restarting it. Yes, I realize that may take a fair bit of work to untangle the actual fixes from the other general fixes, but it's work that seems needed if these tasks are going to continue. I'd also require identifying the particular task being run in each edit summary, which should be easy enough to do. I'd also like to amend the checkwiki tasks (whichever those are) to only make the cosmetic fixes (whichever those are) when a non-cosmetic fix (whichever those are) is being made too, but I can't be more specific than that because this whole gigantic discussion doesn't have any specifics.
 * So, with all that vagueness here, I've fallen back to hoping the ArbCom case will provide something to make this discussion irrelevant. Anomie⚔ 05:48, 24 January 2017 (UTC)
 * Part of the problem worth mentioning is that Yobot has historically not included task numbers in edit summaries, so I'm unable to identify which tasks are actually causing the problematic edits. (As an aside, project tagging has been separately an issue with this. See, for instance, User_talk:Yobot/Archive_9, where an admin nearly blocked Yobot for operating a tagging task against consensus. A lot of this stems from bot operator conduct, not the actual edits, which is part of why a complete revocation of the plethora of over-broad tasks is needed. If you look through these approvals, most of them would never be approved today due to the broad nature of them.) ~ Rob 13 <sup style="margin-left:-1.0ex;">Talk 05:53, 24 January 2017 (UTC)
 * thanks for looking and commenting. I agree there are a lot of considerations and it would be difficult to reach a conclusion with the discussion above. I believe (and it looks like you agree) that each individual task needs careful consideration (Is the task still active? Are there frequent cosmetic-only edits attached to this task? Do they have solid consensus?) and the best forum to undertake this analysis would be a separate BRFA for each task. This is why I am asking for revocation so that this can happen. Obviously inactive tasks will not need reapproval, so paring these tasks down should simplify the whole matter. &mdash; Martin (MSGJ · talk) 09:23, 24 January 2017 (UTC)

There is not a specific task causing the problematic edits. Last month it was error #104 that caused BOTH Dexbot and Yobot go wrong. The reason was that the list generated contained more pages that Yobot/Dexbot could handle or even should fix. All this misunderstanding started from there. Since the list was altered with pages that actually need fix, the issue should be over. At least for now. The last 2-3 months there have been some generalisations of the list in order to catch up with WPCleaner. We did them one by one. The comparison between the two lists can be shown in User:Magioladitis/AWB and CHECKWIKI. -- Magioladitis (talk) 08:32, 24 January 2017 (UTC)

I think the approach is wrong here. If someone wants a task to be disactivated, the should go to the CHECKWIKI page. For example, after the MEdiawiki pages errors 6/37 which are dealing with special characters in DEFAULTSORT where minimised to almost. After the removal of the interwikis from En.wp the same happened to all errors related to interwikis. The problem is that most people seem to find the tasks themselves useful for various reasons even not all of them change the visual output. From that point of vie we should distinguish the edits that fail to perform a task and the edits that do a task that we do not want to see it done as standalone. Because if we choose the first then we will see that Yobot apart from last month's fail, had very few fails in the last 2 years. The changes in the last 3 months results in some fails which were handled. Another example is error 69 (ISBN syntax fixes) which changed from a bot task to a manual task after the CHECKWIKI guys added more cases which actually need people to check them. ---Magioladitis (talk) 08:38, 24 January 2017 (UTC)