Page MenuHomePhabricator

Allow local disabling of global AbuseFilters
Open, MediumPublic

Description

An admin of Wikipedia pointed out that global filters should be disablable locally, likely by those on the wiki with abusefilter-modify (or a split-off permission). This would allow a local community to avoid false positives without having to bother those trusted to modify global filters (stewards).


Version: unspecified
Severity: enhancement

Details

Reference
bz43761

Event Timeline

bzimport raised the priority of this task from to High.Nov 22 2014, 1:29 AM
bzimport added a project: AbuseFilter.
bzimport set Reference to bz43761.
bzimport added a subscriber: Unknown Object (MLST).
Jasper created this task.Jan 9 2013, 5:42 AM

I think this is something that is a good idea (similar to how you can override the global spam blacklist with a local whitelist).

Currently $wgAbuseFilterDisallowGlobalLocalBlocks only handles blocks and will stop all filters, rather than individual ones.

I'm not sure how you would go about implementing this though, should another column be added to database for which wikis have disabled it?

It would probably need to be done like SpamBlacklist's whitelist-- each wiki would keep a list of global rules it would ignore in their DB.

Like SpamBlacklist, the local wiki pulls in the global AbuseFilter rules, and then processes them. So to check against a local list of whitelisted rules wouldn't be too inefficient.

hoo added a comment.Jul 29 2013, 8:03 PM

(In reply to comment #2)

It would probably need to be done like SpamBlacklist's whitelist-- each wiki
would keep a list of global rules it would ignore in their DB.

Like SpamBlacklist, the local wiki pulls in the global AbuseFilter rules, and
then processes them. So to check against a local list of whitelisted rules
wouldn't be too inefficient.

I think the most convenient solution would be to implement a new sub page of Special:AbuseFilter where global filters can be (locally) disabled/ enabled. While the application code for this would be pretty easy to write it certainly would need DB schema changes.

It would be more worthwhile getting spam filters fixed/updated so we don't have these issues, especially if we have the situation that wikis are getting multiple false positives. I like the idea mentioned elsewhere in Phabricator about talk pages for spam filters to make it easier to report issues. I watch global filters and look to update them on the first occasion that a problem is noticed, so where we have a case of multiple situations seems unusual.

Glaisher lowered the priority of this task from High to Medium.May 3 2015, 12:07 PM
Restricted Application added a subscriber: JEumerus. · View Herald TranscriptApr 18 2016, 9:18 AM