Last modified: 2013-09-27 11:29:11 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 T47747, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 45747 - Create a tool like SpamBlacklist in AbuseFilter
Create a tool like SpamBlacklist in AbuseFilter
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
AbuseFilter (Other open bugs)
All All
: Low enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on: 44975
Blocks: SWMT
  Show dependency treegraph
Reported: 2013-03-05 19:45 UTC by James Forrester
Modified: 2013-09-27 11:29 UTC (History)
5 users (show)

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


Description James Forrester 2013-03-05 19:45:52 UTC
The SpamBlacklist is a very old extension, is not particularly easy to use, and can be functionally replaced right now by using the AbuseFilter extension.

However, editing a single monolithic AbuseFilter isn't a much better situation - perhaps a special kind of filter that can take multiple regex strings defined separately, rather than in a single block, with the ability to add resposibility/comments/dates against each line.

[Very much an enhancement!]
Comment 1 Marius Hoch 2013-03-05 19:54:19 UTC
While I like the idea (this could entirely replace the Spam blacklist extension) this isn't possible in case we want to use the existing parser. That would simply blow due to performance reasons. Using a different format will work, though.

This depends on the availability of global filters as this isn't very useful if it's local only.
Comment 2 James Forrester 2013-03-05 19:57:44 UTC
Agreed on both points - though note that global AbuseFilters are a few days away (he says, jinxing things).

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