Last modified: 2014-02-13 03:49:59 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 T20067, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 18067 - Decision tree for AbuseFilters
Decision tree for AbuseFilters
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
AbuseFilter (Other open bugs)
unspecified
All All
: Lowest enhancement with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-03-20 08:22 UTC by MacGyverMagic
Modified: 2014-02-13 03:49 UTC (History)
6 users (show)

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


Attachments

Description MacGyverMagic 2009-03-20 08:22:52 UTC
There have been several edits that triggered multiple AbuseFilters. This is particularly annoying for the people checking on them since unless you're looking for it, there's no indication why an edit isn't showing up in the editor's contribution log unless you figured out another filter was triggered that stopped the edit from going through.

Case in point: 
Filter 3 catches massive page blanking by new users.
Filter 43 catches removal of reference tags by new users.

When a massive blanking is done, both filters trigger, but there are instances when the blanking is not large enough to trigger filter 3. So both filters are needed.

It would be very helpful if we were able to ignore a certain filter if another one was already triggered.
This is easy to achieve if you simply base it on the filter number, but I think the servers could be saved from more strain by ordering the filters in a particular decision tree order that avoids anything already checked for earlier in the tree from being executed.
Comment 1 Andrew Garrett 2009-03-22 23:38:43 UTC
Some tools for filter interaction might be nice, yeah.

Ideas:
* Dependencies for filters.
* Variables for filters_matched.
* Some kind of scoring system.
Comment 2 Andrew Garrett 2009-07-16 16:47:52 UTC
Marking this bug as Lowest priority.

I've done this in a batch to (usually enhancement request) bugs where:
* It is not clear that this bug should be fixed.
* It is not clear how to fix this bug.
* There are difficulties or complications in fixing this bug, which are not justified by the importance of the bug.
* This is an extremely minor bug that could not be fixed in a few lines of code.

If you're interested in having one of these bugs fixed, your best bet is to write the patch yourself.
Comment 3 Helder 2013-07-15 19:35:01 UTC
Andrew Garrett, what do you mean by "Some kind of scoring system"?

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


Navigation
Links