As sad as it is, there seems to be a CAP situation when it comes to captchas. It's accessibility, security or privacy. Choose two.
You can go the Google route and choose accessibility and security, do massive user tracking, and don't even show CAPTCHAs at all for normal users. HN users probably see a lot, because they use some anti-js or anti-tracking stuff, but normal users don't.
You can go the Cloudflare route, requiring users to solve visual challenges, sacrificing accessibility, but keeping security and privacy.
You can also implement audio CAPTCHAS, which are easy to solve for robots, get accessibility and privacy, but less security.
> You can go the Google route and choose accessibility and security
This is not the case. After just a few captchas the audio challenge will be locked off no matter what browser you use.
> and don't even show CAPTCHAs at all for normal users
You see them in firefox from the start as well as on chrome after around the 2nd or 3rd captcha, this is with the default settings + ublock origin on both browsers.
You can go the Google route and choose accessibility and security, do massive user tracking, and don't even show CAPTCHAs at all for normal users. HN users probably see a lot, because they use some anti-js or anti-tracking stuff, but normal users don't.
You can go the Cloudflare route, requiring users to solve visual challenges, sacrificing accessibility, but keeping security and privacy.
You can also implement audio CAPTCHAS, which are easy to solve for robots, get accessibility and privacy, but less security.