It might be useful to ignore a single bot (or more) and not all.
For example, MsnBot makes a lot of minor changes and my list is full of these changes, while they are not risky, so it's harder to track changes from other bots.
Topic on Talk:Edit Review Improvements/New filters for edit review
Ignore people would be done through a feature that would allow people to watch what people do. this feature has been abandoned to avoid harassement.
Maybe only apply it to bot-flagged accounts? What do you think?
Yes, for me it's only useful for bots. I want to follow most of them, but some make a lot of changes and I can't check them anyway.
So, applying this type of feature only to bot-flagged account will be perfect, and this will avoid the harassment of people accounts.
I've created a ticket about that, as a sub-task of the existing one about monitoring users.
Thanks !
Another useful way to reduce the visual number of results with attributes (authors, bots, categories, dates, tags, etc) not of concern would be to let users group results by such attribute(s) and then click to expand/collapse desired groups, and also specify such as part of saved filters and/or queries, as needed.
@Wikicat, I'm not sure to understand. You mean creating batches of edits from a given group, and then expand them?
The current system could do that, role by role (or by combining roles) if we create filters for those groups. There is a ticket about that, but declined with no explanations. I've reopened it.
@Trizek: Just a hierarchical sorting tree with collapsible branches, like a file-directory; and depending on which and what order attributes are selected each time, for example each "author" folder might contain all "months" for that author, and each "month" all "categories" that author edited that month, and each of those the pages; or each "month" might contain all "authors" for that month, and each "author" all their editing "days". Sorting first by "author", or "bot", or whatever, and not expanding selected top-level folders would hide all their activity in the results. This could also be a multi-sortable table with collapsible row-groups. Further, to save strain on the server, could dump top-level-sorted blocks of records to browser and do the remaining sorting in a wikitable. Also, this sorting-tool could apply to any generated list of pages.
It looks like a new tool, not an improvement of the existing filters. I'm afraid that's out of the scope of the small improvements that can be made through the maintenance process.