For Google ReCaptcha, simply install the Buster addon, it solves the captcha for you via speech-to-text.
For captcha's in general, I think we should stop pretending that we can prevent bot traffic from a dedicated attacker without annoying the users.
A simple captcha from the 2000's (the ones with lines over a word or number of letters and numbers), should be good enough to hold off basic script kiddies. Same for a basic TTS audio clip.
> A simple captcha from the 2000's (the ones with lines over a word or number of letters and numbers), should be good enough to hold off basic script kiddies
The problem is that while the kiddies may not be sophisticated their scripts can be - the solutions will work its way in the scripts sooner than later.
Fighting against AI cracking is the same battle that AV vendors have fought in the past decades. It ultimately ends by selling snakeoil.
Any dedicated attacker can nowadays circumvent your captcha solution, it's at best now to get the low level background noise to go away, similar to IP blocking SSH when an IP makes too many attempts.
If your site security relies entirely on the captcha not being broken, your site security needs an update.
The next release will use native messaging to send native user input events to the browser. It's already working well, I just need to finish the app installation bits.
This. Google just disables captcha immediately. Also I tried clicking the audio manually, it immediately disables with a notice that “we are getting .... please try again later”.
For captcha's in general, I think we should stop pretending that we can prevent bot traffic from a dedicated attacker without annoying the users.
A simple captcha from the 2000's (the ones with lines over a word or number of letters and numbers), should be good enough to hold off basic script kiddies. Same for a basic TTS audio clip.