Such a tool would need the actions logged since it could be easily abused, and it also makes it easier to keep track of changes. It should exist at Special:Log/regexspam and called "Spam regex log" :) (for consistency with RegexBlock)
- Mentioned In
- T152253: SpamRegex should provide a reason in the edit form when someone submits an edit but triggers the filter (in action=submit)
T152165: Create a log for RegexBlock at Special:Log/regexblock
- Mentioned Here
- T228575: Decrease number of open tickets with assignee field set for more than two years (aka cookie licking) (March-June 2020 edition)
So logging into Special:Log isn't very tricky, but here we'll want to make sure that all entries are logged into $wgSharedDB's logging table instead of the local one for proper wiki farm support. Maybe all it takes is a $dbw->selectDB( $wgSharedDB ), or maybe it takes more than just that.
Another thing, when a person triggers the SpamRegex filter, that should be logged too (similar with AbuseFilter). Should they be separate logs? On a high-traffic wiki, and especially wiki-farms, there c/would be many entries where it was just triggering the filter, and it'd be hard (or at least, take a long time) to track down when a staff adds or remove a filter.
This task has been assigned to the same task owner for more than two years. Resetting task assignee due to inactivity, to decrease task cookie-licking and to get a slightly more realistic overview of plans. Please feel free to assign this task to yourself again if you still realistically work or plan to work on this task - it would be welcome!
For tips how to manage individual work in Phabricator (noisy notifications, lists of task, etc.), see https://phabricator.wikimedia.org/T228575#6237124 for available options.
(For the records, two emails were sent to assignee addresses before resetting assignees. See T228575 for more info and for potential feedback. Thanks!)