Release status: stable
|Implementation||User activity, Page action|
|Description||Allows privileged users to add entries to the spam blacklist right off of a diff page|
|License||GNU General Public License 2.0 or later|
|Translate the SpamDiffTool extension if it is available at translatewiki.net|
The SpamDiffTool extension allows users to add URLs to the SpamBlacklist extension easily without learning how to format entries for the blacklist and copy and paste, etc.
By inserting a link on each diff page, if an editor sees that a given page has been the victim of spam, they can click on "add to spam", which extracts all of the URLs the spammer has placed on the page, going back over their most recent edits on the article (similar to Rollback). Then, for each URL detected, the tool prompts the user the degree to which they want to blacklist the URL. The options are block:
- all links from the domain
- all links from the specific subdomain
- all links from the subdirectory and subdomain
- nothing - don't add this to the blacklist
The idea is to try to streamline the process of cleaning up spam, rolling back spam edits and blocking users. When the spam addition process is finished, the user is taken back to the diff page they were on to begin with. From there, they can rollback the edits as required.
This extension was tested with MediaWiki 1.35. You must have the SpamBlacklist extension already installed for this extension to do anything, because this is merely a more graphical, easier-to-use front-end for the functionality provided by SpamBlacklist.
- Download and place the file(s) in a directory called
- Add the following code at the bottom of your LocalSettings.php:
wfLoadExtension( 'SpamDiffTool' );
- Configure as required
- Done – Navigate to Special:Version on your wiki to verify that the extension is successfully installed.
To specify which article you use as a spam block list, change the
$wgSpamBlacklistArticle variable in your wiki's LocalSettings.php.
The default is to use the page called
Bugs and enhancements
Bugs or feature requests can be sent via Phabricator. There is a good chance the regular expressions are not 100% perfect.