Last modified: 2014-02-25 23:01:13 UTC
To either slow down human abusers or weed out bots, please allow AbuseFilter to present a CAPTCHA & allow the change only if solved. Yes, I'm aware that captchas are mean to humans both blind and sighted (though of course a particular horror from an accessibility standpoint) - they'd have to be used sparingly etc, but that's a useful option IMO.
This will only result in annoying good editors. We already have throttling and disallowing at our disposal for problematic edits. I don't see the additional benefit of a CAPTCHA.
This would be no different in essence than wgCaptchaRegexes (only better in practice)
(In reply to comment #2) > This would be no different in essence than wgCaptchaRegexes (only better in > practice) Except that $wgCaptchaRegexes isn't open to tinkering by anyone with sysop status. :)
(In reply to comment #3) > (In reply to comment #2) > > This would be no different in essence than wgCaptchaRegexes (only better in > > practice) > > Except that $wgCaptchaRegexes isn't open to tinkering by anyone with sysop > status. :) > That's the point of this request.
(In reply to comment #4) > (In reply to comment #3) > > (In reply to comment #2) > > > This would be no different in essence than wgCaptchaRegexes (only better in > > > practice) > > > > Except that $wgCaptchaRegexes isn't open to tinkering by anyone with sysop > > status. :) > > > > That's the point of this request. And it's why I don't agree with it. As MacGyverMagic already said, the this would annoy newcomers trying to make useful contributions far too much (rather like the abuse filter itself...)
(In reply to comment #5) > And it's why I don't agree with it. Then don't enable it on whatever wiki you contribute to; the request is still valid.
(In reply to comment #6) > Then don't enable it on whatever wiki you contribute to; the request is still > valid. Oddly enough, I don't have total control over what gets enabled where. If it were that simple, I wouldn't be posting here. :) en.wikipedia has a history of conducting polls on technical features where 80% of the voters have no or little understanding of what it is they are voting for. Thus I consider feature requests that could damage the project best nipped in the bud.
(Batch change) These are low-priority miniprojects that I can mop up at some point when I'm doing general code work as opposed to working on a specific projects.
*** Bug 26765 has been marked as a duplicate of this bug. ***
*** Bug 31989 has been marked as a duplicate of this bug. ***
It would be great to have beside configuration variable in LocalSettings.php ability to switch on/off this function for a specific filter.
This would also serve as a workaround for bug 41522.
The variable should be named hate_blind_people or something. ;-) (Even a surly variable name like this would still be better than most of the other AbuseFilter variable names, heh.)
