ReCAPTCHA: Difference between revisions
created page |
m format reference fix spilling link on monobook |
||
| Line 8: | Line 8: | ||
}} | }} | ||
[[wikipedia:ReCAPTCHA|reCAPTCHA]] was acquired by [[Google]] in 2009 and has since been used to protect websites from [[wikipedia:Internet_bot|botting]], crowdsource transcription work, and to mass train Google's other technical ventures such as artificial intelligence.<ref>https://googleblog.blogspot.com/2009/09/teaching-computers-to-read-google.html</ref><ref> | [[wikipedia:ReCAPTCHA|reCAPTCHA]] was acquired by [[Google]] in 2009 and has since been used to protect websites from [[wikipedia:Internet_bot|botting]], crowdsource transcription work, and to mass train Google's other technical ventures such as artificial intelligence.<ref>https://googleblog.blogspot.com/2009/09/teaching-computers-to-read-google.html</ref><ref>{{cite web |author=<!-- not stated -->|title= Google recaptcha intro on using reCaptcha to improve automation |url=https://www.google.com/recaptcha/intro/?hl=es/index.html#:~:text=Every%20time%20our%20CAPTCHAs%20are,and%20solve%20hard%20AI%20problems. |website=google.com |access-date=2025-02-15}}</ref> Google faced criticism over this crowdsourcing and training for using unpaid labor from millions of daily users around the world, even sparking an ultimately unsuccessful class action lawsuit in Massachusetts in 2015, with the court dismissing the amount of time spent by each user completing a CAPTCHA as "something for which [no] reasonable consumer would expect to receive compensation".<ref>https://digitalcommons.law.scu.edu/cgi/viewcontent.cgi?article=1904&context=historical</ref><ref>https://casetext.com/case/rojas-lozano-ex-rel-all-other-persons-similarly-situated-v-google-inc</ref> | ||
A video published by YouTube channel CHUPPL sparked renewed controversy with a video released in December 2024. The video cites and details how reCAPTCHA [[wikipedia:Doxing|doxxes]] users and how resulting user data can end up in the hands of the US government for unknown purposes, claiming exploitation of an intentional loophole in Google's terms of service allowing them to transmit user device and application data under the guise of "general security purposes."<ref>https://www.youtube.com/watch?v=VTsBP21-XpI&t=306s</ref> User data allegedly began being collected in 2014, when Google deployed reCAPTCHA v2, specifically the “No CAPTCHA reCAPTCHA” i.e. "the checkbox CAPTCHA," which primarily uses [[wikipedia:HTTP_cookie|cookies]] to whitelist users who reCAPTCHA identifies as humans. This opens up additional security vulnerabilities as once a user is identified as a human, a bot can take over and be given unrestricted access to all sites using reCAPTCHA without having to fill a CAPTCHA itself.<ref>https://homakov.blogspot.com/2014/12/the-no-captcha-problem.html</ref> | A video published by YouTube channel CHUPPL sparked renewed controversy with a video released in December 2024. The video cites and details how reCAPTCHA [[wikipedia:Doxing|doxxes]] users and how resulting user data can end up in the hands of the US government for unknown purposes, claiming exploitation of an intentional loophole in Google's terms of service allowing them to transmit user device and application data under the guise of "general security purposes."<ref>https://www.youtube.com/watch?v=VTsBP21-XpI&t=306s</ref> User data allegedly began being collected in 2014, when Google deployed reCAPTCHA v2, specifically the “No CAPTCHA reCAPTCHA” i.e. "the checkbox CAPTCHA," which primarily uses [[wikipedia:HTTP_cookie|cookies]] to whitelist users who reCAPTCHA identifies as humans. This opens up additional security vulnerabilities as once a user is identified as a human, a bot can take over and be given unrestricted access to all sites using reCAPTCHA without having to fill a CAPTCHA itself.<ref>https://homakov.blogspot.com/2014/12/the-no-captcha-problem.html</ref> | ||