Earlier quoted context omitted.
> You can implement basic defenses like hidden input forms or checkboxes that are masked by CSS rules or served on the client side with JavaScript to weed out bots from human users, among other less intrusive techniques. Umh, anything that will end up in the POST request will be reproduced by a bot, I don't even actually look at the page when implementing screen scraping modules, but just at the Network tab of the Ch…
No no, the hidden input fields would not be filled in by a human (because they're positioned off screen by CSS, for example), whereas a bot would fill them in because the bot is just scraping the HTML for all input fields and filling them in with something. It seems like you had that backwards -- hope that clears it up.
reCAPTCHAs are finally readable by normal humans
21–30 of 40 posts
Re: reCAPTCHAs are finally readable by normal humans
#22...and why, pray tell, are they still providing turing tests to humans, if they already know who the humans are, you ask? Well! Very obviously, any human can behave just as maliciously as a bot might! So captchas are there to slow us down. Point blank. They are flood control. They prevent spam, be it from bot or human. The real question is, why would Ars Technica be so chicken-shit, that they can't come out and say t…
Re: reCAPTCHAs are finally readable by normal humans
#23Earlier quoted context omitted.
No no, the hidden input fields would not be filled in by a human (because they're positioned off screen by CSS, for example), whereas a bot would fill them in because the bot is just scraping the HTML for all input fields and filling them in with something. It seems like you had that backwards -- hope that clears it up.
Why would I have my bot fill them in? One glance at the site and I know that my bot should skip those fields.
I think that's where the issue lies: these tools do different things. Honeypot fields defend against general bots. Captchas defend against specific bots, too, but also have greater friction, so are only used when specific bots are an issue.
Re: reCAPTCHAs are finally readable by normal humans
#24Re: reCAPTCHAs are finally readable by normal humans
#25Re: reCAPTCHAs are finally readable by normal humans
#26Earlier quoted context omitted.
Why would I have my bot fill them in? One glance at the site and I know that my bot should skip those fields.
It's meant as a defense against non-targeted bots—the ones that roam the web looking for forms to fill out. I think that's where the issue lies: these tools do different things. Honeypot fields defend against general bots. Captchas defend against specific bots, too, but also have greater friction, so are only used when specific bots are an issue.
Re: reCAPTCHAs are finally readable by normal humans
#27Re: reCAPTCHAs are finally readable by normal humans
#28Google knows your searches, and I am pretty sure google knows every site you visit, via google analytics, which most sites run. Combine this with browser fingerprinting (your browser's fingerprint is incredibly unique), and the fact that you probably have a google account. There is a high probability they know who you are. From your history they can determine if you're human or not.