mike.lifeguard+bugs wrote:

(In reply to comment #0)

It should be possible to mark actions like delete and protect as bot (to avoid
clogging RecentChanges) if a user has the 'markbotedit' right. This is probably
custom enough that it needs to only be implemented in the API.

Why would it be the markbotedit right as opposed to the bot right? Not sure whether both would make more sense, but certainly bots making these actions should be hidden, if that's not already the case.

(In reply to comment #1)

(In reply to comment #0)

It should be possible to mark actions like delete and protect as bot (to avoid
clogging RecentChanges) if a user has the 'markbotedit' right. This is probably
custom enough that it needs to only be implemented in the API.

Why would it be the markbotedit right as opposed to the bot right? Not sure
whether both would make more sense, but certainly bots making these actions
should be hidden, if that's not already the case.

Yeah, any action performed by a bot, both edits and entries made to Special:Log are hidden from recent changes.

Using both the normal UI and the API, logged entries seem to be getting the bot flag when done by a flagged bot (a user with the "bot" right).

I didn't test everything (tested delete, undelete, protect through normal UI; delete, move through API), if something isn't checking for the bot flag, this can be reopened.

I don't think this should be expanded to the "markbotedit" right, as that's currently just used to hide mass rollbacks by admins.

Reopening. The goal here is to be able to mark actions as bot without being in the bot group. Ideally, this would be implemented into the API first and then subsequently implemented in the interface later (sort of like 'move without redirect'). Probably would be best to have a new right "markbotaction".

(In reply to comment #4)

Ideally, this would be implemented into the API first and then
subsequently implemented in the interface later (sort of like 'move without
redirect'). Probably would be best to have a new right "markbotaction".

It should be implemented in the *backend* first. When that's done, it's quite simple to update the API and UI to pass a $markBot parameter to the backend function and add a parameter (API) or checkbox (UI) to toggle it.

Through my work with the write API I've become familiar with some of the backend functions concerned, but I've got better things (i.e. API stuff) to do at the moment. I'll take this if no one else does, but the API has a higher priority for me, so it might take me a while to get to it. In the meantime, it would of course be nice if someone else took this bug.

Changed component to "RecentChanges"

charitwo: Do you plan to work on a patch (or are you aware of somebody working on a patch), or why did you set the Target Milestone to 1.24?