Last modified: 2013-08-10 03:22:31 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T45761, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 43761 - Allow local disabling of global AbuseFilters
Allow local disabling of global AbuseFilters
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
AbuseFilter (Other open bugs)
unspecified
All All
: High enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks: SWMT
  Show dependency treegraph
 
Reported: 2013-01-09 05:42 UTC by Jasper Deng
Modified: 2013-08-10 03:22 UTC (History)
10 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Jasper Deng 2013-01-09 05:42:12 UTC
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).
Comment 1 Kunal Mehta (Legoktm) 2013-01-11 18:56:59 UTC
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?
Comment 2 Chris Steipp 2013-01-11 23:16:01 UTC
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.
Comment 3 Marius Hoch 2013-07-29 20:03:52 UTC
(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.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links