Other CAPTCHAs can be really annoying to encounter, such as Google’s reCAPTCHA. Some CAPTCHAs can be very hard to read, even for people with good vision. Basically, the intention of a CAPTCHA is to prevent spam from robots but they also cause inconvenience to real users especially blind and visually impaired people. There are various types of CAPTCHA including typing in the shown words or numbers, doing some simple maths, solving a visual puzzle, identifying objects, and etc. not trivial to fix for next release).If you’ve submitted a form or registered for an account on the Internet, you will have stumbled upon a CAPTCHA. I'll leave this assigned for 0.8.2 for now (together with ticket 46 on the addons repo), to keep track of adjusting the server side to do some throtteling, anything else is a mid-term issue imho (i.e. At the end of race client sends this processes token and #frames, from which the server can determine if a token is correct? Perhaps 'security through obfuscation': server sends random token to client, which applies a certain operation during the race. Then the gui needs to be threaded: a thread to download the captcha (so the user can exit the gui), error handling, displaying the image, getting the answer - yes, of course it can be done (we already doing this in other places), but it's not that trivial that I would suggest adding this for this release. Then we need to store the expected answer - so in case of a spammer we are then storing 1000's of expected answers. ), which adds load to our server, since it has to either download or create the captchas.
I agree with hating captchas - I've been declared non-human way too often )ĭisadvantages: more work on the server: We need to send the image from our server (otherwise we need to make the server address for captcha's configureable if we even are able to use an external server.
0 kommentar(er)
