no need for captchas, just implement throttling per ip. like bcrypt dues for passwords. if a bot fills up a form(or whatever), so be it, but it won't be able to do it for another N seconds or minutes..so the problem then is lowered from per try, which can be thousands of submissions, all the way down to per period and per ip.
An Empirical Study and Evaluation of Modern CAPTCHAs
61–70 of 338 posts
Re: An Empirical Study and Evaluation of Modern CAPTCHAs
#62The solution could be a cryptocurrency which can be mined in the browser. Hashcash, which was one of the inspirations for Bitcoin, was initially invented to prevent email spam. Consumer devices have a lot of spare CPU and RAM. So a proof-of-work algorithm which consumes those resources for a minute might work? If it generates $0.01 for the website owner in that minute, maybe that would work?
Re: An Empirical Study and Evaluation of Modern CAPTCHAs
#63Google CAPTCHAs were designed and deployed as a mechanism to train AIs. That's why they are the way they are. Any security theater surrounding them is entirely incidental. So it's no surprise that the AIs are now good at solving them. We've trained them for years.
I still find it funny that Google, with the advantage of having millions of Internet users train their AI like galley slaves for free, hasn’t yet been able to crack vision driven self driving. Tesla had no such advantage when training their FSD to recognize traffic lights, bicycles, motorcycles, etc.
But they have? For years Google Street view has read signs, house numbers, phone numbers of businesses, etc. from the environment. It is safe to assume they have this built into Waymo as well.
I assume you might be trying to reference "vision only" self-driving, which is a fantasy made up by Elon Musk because nobody would sell him LiDAR sensors cheaply.
https://www.thedrive.com/tech/43779/this-tesla-model-y-dummy...
Re: An Empirical Study and Evaluation of Modern CAPTCHAs
#64I already had issues with captchas (specially on tor).... so now its going to get worst?
The price we pay for obfuscating the trust signals on our connection is that our connection is untrusted. As an American, I have a similar experience when I travel across the Atlantic. It's always funny to me when I land in the UK, start using websites I use normally at home, and get cookie verification modals from hell to breakfast.
Re: An Empirical Study and Evaluation of Modern CAPTCHAs
#65Re: An Empirical Study and Evaluation of Modern CAPTCHAs
#66Re: An Empirical Study and Evaluation of Modern CAPTCHAs
#67Does HN ever require CAPTCHAs? It seems to do pretty well with its basic but battle-tested moderation/antispam tools, and rate-limiting that seems to repel all but the most concerted DDoS attacks. I don't think HN has any unreasonable restrictions on scraping or third-party clients, either. And it manages to serve 5M unique visitors a month and 10M views a day[0]. [0] https://news.ycombinator.com/item?id=33454140
Re: An Empirical Study and Evaluation of Modern CAPTCHAs
#68Earlier quoted context omitted.
I've never seen a text version that lets me select the text, that's bizarre
@_rutinerad got it - on macOS you can select text in any image, and I just assumed you could do that on windows as well (I figure in the context of linux it would be much more dependent on specific configuration so unilateral assumptions on behaviour would be questionable). It's honestly annoying as it frequently interferes with dragging images out of safari, except on those occasions when I do want the text when it'…
Re: An Empirical Study and Evaluation of Modern CAPTCHAs
#69Earlier quoted context omitted.
Tesla, the company that just recalled 2 million self driving cars? In fairness, the company best positioned to harness user input to an AI that avoids crashes would probably be Rockstar. OTOH, that AI would definitely not obey stop signs or pedestrians.
By recall you mean a completely routine OTA software update done while the driver is asleep.
Re: An Empirical Study and Evaluation of Modern CAPTCHAs
#70The solution could be a cryptocurrency which can be mined in the browser. Hashcash, which was one of the inspirations for Bitcoin, was initially invented to prevent email spam. Consumer devices have a lot of spare CPU and RAM. So a proof-of-work algorithm which consumes those resources for a minute might work? If it generates $0.01 for the website owner in that minute, maybe that would work?
Tor has such a feature for denial of service protection.
https://blog.torproject.org/introducing-proof-of-work-defens...
A benefit of a token is you can recycle previous proof of work by using a small amount of Bitcoin, which could be transferred using Lightning. The value could also be transferred back some amount of time after registration given no bad behavior, allowing for larger sums than a cent, which could provide better protection.