Page MenuHomePhabricator

Create a log for SpamRegex at Special:Log/regexspam
Open, Needs TriagePublic

Description

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)

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptDec 2 2016, 1:30 AM
SamanthaNguyen renamed this task from Create a log for SpamRegex at Special:Log/spamregex to Create a log for SpamRegex at Special:Log/regexspam.Dec 2 2016, 1:31 AM
SamanthaNguyen assigned this task to ashley.
SamanthaNguyen updated the task description. (Show Details)

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.

Aklapper removed ashley as the assignee of this task.Jun 19 2020, 4:15 PM
Aklapper added a subscriber: ashley.

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!)