matthew.britton wrote:

If you're making enough edits to flood recent changes, use a bot account; that's what they're for. :)

(In reply to comment #1)

If you're making enough edits to flood recent changes, use a bot account;
that's what they're for. :)

Bot flag is not the solution if the edits are important and should be shown. But to hide a persons's edits temporarily make sense when I search for other edits. It does not make sense to give the bot flag to every diligent user.

Changed component to "RecentChanges"

additionally: it would be very usefull for small project with few users that are very active - if I cannot filtre them out so other edits (not only vandalisms) get lost.

"Flood flag" and patrolled edits are only a partial solution, since the former can't resolve the problem for small projects, and the latter would hide all edits from all sysops or autoconfirmed users depending on the local configuration.

I think there is a use case in the intent the reporter has, but the specific request (providing an input field for user name on Special:RecentChanges for hiding that user's edits) seems rather specific and not a justified feature to have on Special:RecentChanges.

There are lots of use cases related to this, but I don't think it would be best served through this.

You can:

• Hiding patrolled edits (grant the 'patrol' right to mark individual edits as patrolled, grant the 'autopatrol' right to automatically mark edits of a certain user)

• Hiding your own edits

• Hiding bot edits (grant the 'bot' right to allow a user to mark all or some of their edits as bot edits).

• Etc.

As for extensions, CleanChanges does something like this: https://translatewiki.net/w/i.php?title=Special:RecentChanges