Page MenuHomePhabricator

Allow AbuseFilter to force the user to solve a captcha
Open, LowPublic

Tokens
"Like" token, awarded by Luke081515."Like" token, awarded by Ricordisamoa."Like" token, awarded by Pcoombe."Like" token, awarded by Gryllida."Mountain of Wealth" token, awarded by jayvdb."Like" token, awarded by He7d3r.
Assigned To
None
Authored By
bzimport, Mar 23 2009

Description

Author: mike.lifeguard+bugs

Description:
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.


Version: unspecified
Severity: enhancement

Details

Reference
bz18110

Event Timeline

bzimport raised the priority of this task from to Low.
bzimport set Reference to bz18110.
bzimport added a subscriber: Unknown Object (MLST).
bzimport created this task.Mar 23 2009, 2:35 AM

MacGyverMagic wrote:

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.

mike.lifeguard+bugs wrote:

This would be no different in essence than wgCaptchaRegexes (only better in practice)

matthew.britton wrote:

(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. :)

mike.lifeguard+bugs wrote:

(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.

matthew.britton wrote:

(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...)

mike.lifeguard+bugs wrote:

(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.

matthew.britton wrote:

(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. ***

beau wrote:

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.)

jayvdb awarded a token.Dec 5 2014, 4:21 AM
Pcoombe added a subscriber: Pcoombe.
Ricordisamoa added a subscriber: Ricordisamoa.
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptJan 26 2016, 12:58 AM
Luke081515 added a subscriber: Luke081515.
Meno25 removed a subscriber: Meno25.Feb 22 2016, 5:55 PM

After so many years without this feature I'm not sure if it is still required or an idea we've got when the feature was first deployed to WMF.