Live data from Hacker News

Google's Captcha in Firefox vs. in Chrome

grumpy.website

161–170 of 503 posts

Re: Google's Captcha in Firefox vs. in Chrome

#161

When confronted with reCAPTCHA I always switch to the audio-version as that: - is generally easier to solve (download the sound clip using curl or wget, type in the nonsense it says, done) - does not turn me into a mechanical Turk training Google's AI - works in 'any browser' by circumventing the browser (by using wget/curl), thereby not allowing Google to punish me for not using their dragnet/browser.

> does not turn me into a mechanical Turk training Google's AI

I’ve been wondering about that. Are you sure you’re not training their speech recognition AI?

Re: Google's Captcha in Firefox vs. in Chrome

#162
post #144
post #43

Turbo Tax uses Google Captcha when trying to import information from financial institutions. While filing taxes, on several occasions I had to just give up and try again after several hours because the Captcha won't let me pass through and after several attempts Turbo Tax will throw an error - to come back later. It was literally a Nightmare

It's a bit more expensive, but for this type of thing and other reasons, I now use a CPA.

... who then use an Intuit product to file your taxes

Re: Google's Captcha in Firefox vs. in Chrome

#163
Happens to me in chrome every single day. I think it's a bug in how they're detecting potential bots. Of course no one at Google will listen when you submit reports. Especially the one about selecting street lights/stop lights/crosswalks.

Re: Google's Captcha in Firefox vs. in Chrome

#164
Sometimes it's stairs, and they ask you to click all the stairs, but there's an inch of stairs overlapping one window, so you aren't sure if you should click that window because of the pixel or not.

This whole captcha joke and firefox made me hate Google more than anything else.

Re: Google's Captcha in Firefox vs. in Chrome

#165
It's simple; any shitty website that uses this garbage—don't use it. If there is a "contact us" page or email, tell them why you will no longer use it.

If it's your bank's site, move a bank. You say "oh, it's a lot of work just for some captcha"; yes it is, but this is the only way this clowns will learn. When 1000 people leave a bank for a competing one and say "I left because your site employs captcha", it will magically disappear. I've seen it happen.

Re: Google's Captcha in Firefox vs. in Chrome

#167

Earlier quoted context omitted.

To make it more expensive for bots to try this at scale, obviously. Unfortunately it's making it more expensive for humans too.

you may be right about the fade-out and delay but the time spent fading in only hampers humans not bots. As soon as it starts fading in the image is present in non-faded form and the bots can start processing it.

> the time spent fading in only hampers humans not bots

Not necessarily, contrast adds detail and mistakes are expensive, so bots too are incentivized to wait for the final picture (this assuming that network communications aren't monitored to get the incoming image out of the request).

Also clicking on that image too early is a good signal that it's a bot.

Re: Google's Captcha in Firefox vs. in Chrome

#168

Earlier quoted context omitted.

reCAPTCHA also just doesn't work in the most populous country in the world. translate.google.cn does, but Google's reCAPTCHA does not. This is a big pain point. Thanks for the link to turingtest, I will certainly test it.

To be fair, lots of things on the internet don’t work in the most populous country in the world.

Could it have something to do with the most populous country in the world blocking the rest of the world? For fear someone might massacre square...

Re: Google's Captcha in Firefox vs. in Chrome

#170
I've never understood what happened to reCAPTCHA, it was originally so great and is now just so, so toxic.

Originally it was an awesome solution based on OCR'ing books that usually worked quickly on the first try, and almost never took more than two.

Then it turned into a single checkbox (analyzing mouse movement) so it was even faster... and I remember some simple image-based like "select the images of cats" that were also easy to get right. So even better.

But THEN... in the past couple of years, the image-matching started asking exclusively for analysis of street images, that has two huge problems:

1) The images are so blurry and ambiguous it's really hard to get right, it feels like a test designed to make you fail

2) You never know how far you have to go -- you keep clicking items, they keep replacing them with new ones, and there's zero indication of if you're almost done or if you're getting better or worse.

Once I did one for three minutes straight, neither passing nor failing, until I just gave up and left the page... if it's a bug, that should never happen. If that's supposed to be able to happen, that's the apex of asshole design. Either way, it's a failure in every way.

Post reply on HN