Google Updates ReCAPTCHA With Easier CAPTCHAs For Humans
An anonymous reader writes "Google today released an update to its reCAPTCHA system that creates different classes of CAPTCHAs for different kinds of users. In short, it makes your life easier if you're a human, and your work much harder if you're a bot. Unsurprisingly, Google wouldn't share too much detail as to how the new system works, aside from saying it uses advanced risk analysis techniques, actively considering the user's entire engagement (before, during and after) with the CAPTCHA. In other words, the distorted letters are not the only test."
The CAPTCHA is influenced by what you do after you exit it?
They're extending the user categorisation checks. It checks your IP address against a risk and Geo database. You're all smart enough to know what makes certain users riskier (eg: excessive requests, certain countries, is a Tor exit node etc.). They're just doing that properly now.
She ends up on a bum IP and ends up getting hopelessly indecipherable gibberish as the verification for paying her electric bill?
Not sure blacklisting is the best way to go about this...
On those ones have you ever tried hitting the button that's supposed to say the captcha out loud just in case you can't read it?(Which is most of the time) I swear it sounds like some sort of inhuman moaning straight from the Necronomicon that would be more appropriate to summon some sort of demon.
Did you know 80 to 90% of the moderators on slashdot wouldn't recognize a troll even if one dragged them under a bridge.
What it could mean is that Google has caught up with the Copyright Term Extension Act of 1998 and finished all notable books in the English language published before 1923. Google has to set reCAPTCHA to read house numbers for Google Maps to pass the time until 2019 when copyrights will start expiring again barring yet another legislative extension.
If the earlier checks suggest it's likely to be a bot, use a harder captcha to double check. If it's likely to be a human, use an easier captcha as confirmation.
If the system is pretty sure it's a returning user, FaceTuring doesn't require a captcha at all. I don't know if recaptcha ever goes as far as not requiring the captcha at all.
1. Google uses analytics and other techniques to find the IP addresses that are "captcha-busters".
2. Automate their captcha generator to feed into these with honeypot pages to see which ones they can bust.
3. Assemble lists of ones they cannot.
4. Profit!
It's a dynamic, revolving door, but when automated it's great. BTW I wouldn't mind a new job there, hint hint.
(-1: Post disagrees with my already-settled worldview) is not a valid mod option.
I've been whining about this for years.
...no doubt the same techniques used in their excellent spam filter setup on gmail. You know, the one that will repeatedly mark incoming mail as spam even though you have already marked it over and over as "not spam". Or the classic: Google marks as spam incoming mail with a sent-from address that matches an already verified alias in your own account.
Yeah, I know, there's no way I can be right in light of the thousands of PhD's employed by Google. The collective brainpower is staggering, so Google will always be right in everything they do.
What you describe can happen if the headers in the email appear to be forged. *That* can happen if your email is being routed strangely.
Here's one example: my organization uses hosted gmail for our domain email. However, our *institution* sold out to Microsoft. We were allowed to continue to use our hosted gmail. "Whew, dodged that bullet!", I thought, until email from other gmail users started being marked as "Person X may not have sent this email", and my Amazon.com order/shipping notifications started being sent to the spam folder.
What happened? Our institutional overlords required that our email be routed through MS' outlook.com servers. Thus all our inbound email appeared to have forged headers. GMail legitimately ignored my whitelist filter rules when it appeared that the field values for "from:", etc, were forged.
This may not reflect your situation, but I'm sure there are other weird scenarios where email to/from gmail can appear to be forged.