After an RFC, the Global AbuseFilter expansion of AbuseFilter extension was enabled on small and medium Wikimedia wikis in 2014. It will greatly improve the response to cross-wiki vandalism and spam, while also increasing community control over these global actions.
The global AbuseFilter allows privileged users (stewards and Meta administrators) to create, modify and delete filters which act on most Wikimedia projects. Individual filters could be designed to affect certain wikis, either inclusive or exclusive to a list. The range of projects affected by each filter would be determined by what the filter would be targeting, and would ensure that the filters are not active on projects that they shouldn't be. The global AbuseFilter is hosted at Meta, and modified by users with the
abusefilter-modify-global right. Global filters can be disabled and marked as private, like local filters.
Detailed logs are available for local and global filters with separate rights, meaning that local communities can keep their preferred settings on the local AbuseFilter log while a global standard can be set for the global filters.
The global AbuseFilter has the following options:
- The ability to log all actions which trigger a global filter.
- The ability to tag edits on local wikis for further review.
- The ability to provide a warning to users who trigger a filter.
- It is not yet known how this feature would work.
- The ability to prevent an action on a local wiki if it triggers a global filter.
- A variable which identifies the project that the filter is triggered on
The exact changes to implement the filter can be seen in this code entry and this Gerrit change.
Locally disabled actions
Some AbuseFilter actions have been added to $wgAbuseFilterLocallyDisabledGlobalActions.
Global filters with the below locally disabled actions enabled will still log the hit, but will not apply the disabled action.
Global AbuseFilters are used to prevent spam and vandalism across many Wikimedia wikis. As such, they should only be made to stop patterns that affect many wikis. Global filters must be as specific as possible, and should be enabled for the shortest possible time. An exception to this policy are filters designed to just tag edits and not take further action. These filters can be left up indefinitely, since their purpose is to filter edits for further review and they do not take any automatic actions.
Global abuse filters were first enabled on metawiki, mediawikiwiki, and the testwikis on February 2013. On September 2013, it was enabled on three additional wikis: incubatorwiki, specieswiki and outreachwiki. On January 25, 2014, global abuse filters were enabled on all small wikis. Global abuse filters were enabled on all medium-sized wikis on November 2014. The private and fishbowl wikis are excluded.
In June 2018, global abuse filters are still enabled on all small wikis and all medium-sized wikis, but also on some big wikis: enwikisource, frwiki, ptwiki, specieswiki, wikidatawiki (with specificities in the main and Property namespaces), incubatorwiki, mediawikiwiki, metawiki, testwiki and test2wiki.
All wikis are capable of being included within the framework of global abuse filters. Those wikis that do not currently use global abuse filters may do so by achieving a consensus of the community and then creating a Wikimedia site request in Phabricator.
See Special:AbuseFilter for the full list.
- ↑ T332521
- ↑ Gerrit change #48070: Deploy Global AbuseFilters to Meta-Wiki, MediaWiki and test.wikipedia
- ↑ Gerrit change #82649: Enable Global AbuseFilter for more wikis
- ↑ Gerrit change #109435: Enable global AbuseFiters for all small wikis
- ↑ Gerrit change #170311: Enable global AbuseFilter on medium sized Wikis
- ↑ Configuration file (search for