When testing filters, its not always easy/productive to keep refreshing the filter's log to see new hits - I think it would be helpful to have a per-user "notify me when this filter hits" option.
This would obviously only be helpful on low volume filters, or when testing a filter - perhaps the per-user "notify me" option would be temporary to guard against it being left on and generating too many notifications, or would automatically disable once you have x new echo notifications?
I hope you don't mind me renaming this task. When I first saw it, I assumed it was asking for notifications when a filter is automatically disabled.
Good rename, though echo notifications for when a filter is automatically disabled would be a good idea..
https://meta.wikimedia.org/wiki/Community_Tech/Add_a_user_watchlist was declined by community tech and support and safety, noting, among other things, "This could turn into a tool that encourages harassment on wiki."
Given that this feature request could effectively create a user watchlist (eg filter: user_name === 'DannyS712 consequences: none, just echo notifications), suggest declining unless Community-Tech
and Trust-and-Safety explicitly approve such a feature
If you are on IRC you could use https://en.wikipedia.org/wiki/User:MusikBot/AbuseFilterIRC. If you want to subscribe to filters outside English Wikipedia and Commons, let me know and I can add whatever wiki you want. There are also live feeds of all activity for each wiki, so you could join the channel and set your client's "highlight words" to match the desired filter.
I don't think this is quite the same as the user watchlist. The "subscriber" of the filter would probably be limited to the AbuseFilter manager(s), or at least they control who is being watched, so this cancels out much of the risk of misuse for the purposes of harassment.
That said, I don't think echo notifications for filter hits is a good idea anyway. There could be many thousands in a short period of time. It would need to be throttled in some way, otherwise this would surely cause performance problems. Better would be a Special:AbsueFilterWatchlist interface or something.