On 25/11/12 13:50, billinghurst wrote:
I would like to see some simplicity to be available to be retained, and not the never-ending complexity of trying to write complex abuse filters.
+1 I think MediaWiki should keep this simple feature, without having to write abuse filters or needing to install specific extensions.
I replied on the bug addressing their specific request.
Is it possible to write AbuseFilter so that it is able to make use of both bad and good lists stored within the MW namespace? I especially like that if we are able to utilise that in the global space. We have had global vandals come along and start spamming or vandalising by the addition of an image, or a singular image with coding. To be able to slow down that process with a global filter, would be excellent.
We could easily use a global bad image list right now. The discussions on meta of "OMG you are censoring usage of this image in all the wikis" could be endless, though. But if people fighting crosswiki vandalism really want it, I'm for it.
I would see that a simple AbuseFilter that says inhibit (in whichever flavour) 'this' edit based on finding a filename found in 'Mediawiki:Bad image list' as a base feature would be the simplest response.
Using lists on MediaWiki NS in AbuseFilter is a good idea.
Default the behaviour to on (for WMF) and it replicates the present case. If wikis wish to then further develop these filters, excellent. I also see that such filter behaviour could allow wikis to battle other forms of vandalism, and one that I know that I have put into bugzilla previously. We had a vandal who was putting sexually explicit pictures on contributors' user and user talk pages. If this wiki was then able to write a filter that basically said block the addition of images to such and such local namespace, from such a such category at Commons, and/or matching such and such keywords from a filelist, rather than have to try and write an abusefilter that had all the series of swear words and references to sexual appendages, BRILLIANT!
The hard part would be to fetch the categories from commons cleanly. But what you propose can be done. Remember however that you will need to list the whole category subtree you want to ban, not just the top one. :)