![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
![[site community profile]](https://www.dreamwidth.org/img/comm_staff.png)
Allow users to pick with type of CAPTCHA test they see
Title:
Allow users to pick with type of CAPTCHA test they see
Area:
comments, entries
Summary:
Allowing users to choose which type of CAPTCHA (text-based or graphic based) they will see/take through Manage Account.
Description:
Users choosing what type of CAPTCHA they will see/take allows greater accessibility.
I have dyscalculia and the text-based CAPTCHAs are full of arithmetic problems, thus I keep failing them. As of now, there's no way to choose which CAPTCHAs you will take, only what type of CAPTCHAs others will see in your journal.
This suggestion:
Should be implemented as-is.
56 (71.8%)
Should be implemented with changes. (please comment)
1 (1.3%)
Shouldn't be implemented.
3 (3.8%)
(I have no opinion)
17 (21.8%)
(Other: please comment)
1 (1.3%)
no subject
no subject
And heaps of other options are only available for logged-in comments so that's cool too. OTOH it could be done as a cookie like the "view options" are for anon people if wanted.
no subject
When antispam knows that something's a genuine spammer evading a CAPTCHA, we put ... firmer ... measures into place.
no subject
no subject
no subject
One of the reasons I love Dreamwidth, and that I'm always willing to talk up the site on- and off-line, is the commitment to accessibility. CAPTCHAs have been a barrier to accessibility for a long time, and Dreamwidth has made more of an effort than any other site I've seen to overcome that barrier. I don't know what percentage of users continue to have problems with text-based CAPTCHAs, and I don't know what percentage of spam comes from circumventing CAPTCHAs, but it would really upset me to see that commitment to accessibility given a lower priority than a subset of spam. I'm not saying that better spam tracking is unimportant, but unless it's something already in progress that can be reasonably expected to be complete before there's time to write an accessibility fix, let's worry about accessibility and then make sure there's better spam tracking.
+1
Re: +1
Spam kills websites. If we don't prioritise fighting spam, the whole site can die.
no subject
Re: +1
But we are not actually at a spam level where I'm concerned about that when I think about this for more than 30 seconds.
Re: +1
Re: +1
no subject
I would like to give more background on where I'm coming from as well.
I view spam as not just an annoyance, but as a threat that has the potential to bring a site to its knees if it's allowed to gain a large enough foothold. It doesn't have that much of a foothold at the moment, but there was a large campaign within the last month that severely tested the human limits of the current system. There's been a bug filed for quite some time about spam CAPTCHA tracking, and if there is another campaign like this recent one before another developer has time to take up the bug, I'm likely to try my hand at development. My instinct says that passing information on whether a CAPTCHA was passed for a comment, and which one, back to the antispam team, would be easier than the ability to change which one is presented and make a setting for this preference, in that I'm able to imagine myself taking on the former as a very neophyte developer, but I don't know the code well enough to say for sure.
However, not only did I discount accessibility in favor of antispam when making my initial comment, I also ignored that people are already able to choose between visual and audio CAPTCHA with ReCAPTCHA. So not only was my prioritization inappropriate, it was also grounded in inaccuracy. Further user choice of method of CAPTCHA is unlikely to have an effect on spam penetration; it's the simple fact of whether a CAPTCHA was presented or not that's of immediate interest to the spamwhackers in the event of another large attack.
no subject
I'm not a development person, and know very little about the back-end of running websites, so I figured that there had to be more that I didn't understand, which is why I commented about how your statement appeared to me, rather than making assumptions about your intent.
Given your clarification, particularly since the option to choose already exists, it sounds to me like there's no reason for accessibility changes and spam tracking changes to be inter-dependent — one followed by the other — instead of independent but related.
no subject
no subject
no subject
See also: http://dw-suggestions.dreamwidth.org/1354499.html?thread=4218371#cmt4218371
no subject
no subject