4

Possible Duplicate:
The reCAPTCHA has become too difficult for humans to solve

As of recently the reCaptcha system has gone crazy for me. I often even cannot read the word you have to enter without some refreshes. And no I'm not talking about the other word in there which you should just neglect or fill in with nazi.

There is currently a question about this here on meta, but that question is more about the other word if I read correctly. Although there is an answer in there with some good examples of impossible to read captchas. If this question is an exact dupe after all please close (like I would need to tell you people).

Am I the only one who has problems reading them? Do I need glasses? Last time I checked I was not a robot. Then again maybe I was programmed to never find out I am.

Can something be done to the captcha system to fix this (I know it's a third party)?

marked as duplicate by Brad Mace, Aaron Bertrand, Ernest Friedman-Hill, Martijn Pieters, Adam Lear Aug 12 '12 at 17:48

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

  • 5
    "Last time I checked I was not a robot." ... nice try. – Bart Aug 12 '12 at 16:59
  • 1
    @BradMace Isn't that question about that other word. You know the one you don't have to fill in? "I am tempted to just enter the known word (an easy guess), and leave the other." I cannot read neither of them – PeeHaa Aug 12 '12 at 17:02
  • 3
    I don't know where you're getting that idea, but you haven't brought up anything new in your question. – Brad Mace Aug 12 '12 at 17:03
  • 1
    Maybe I do need a pair of glasses, because I read that question as I can read the known word, but not the other. – PeeHaa Aug 12 '12 at 17:05
  • 5
    Note, I failed the captcha three times today when submitting a comment on the SO blog. It is getting really friggin hard (again). If you haven't experienced it on the site recently, please hold your vote. – Tim Post Aug 12 '12 at 17:22
  • But @Tim, while I've experienced this same thing as well, shouldn't we vote on the previous question and close this one as a duplicate? – Aaron Bertrand Aug 12 '12 at 17:29
  • 3
    @AaronBertrand That question is old, and third party things change from time to time. If the captcha has become a nuisance again recently, well .. Duplicates aren't always duplicates. It's not like the captcha presents a version number. – Tim Post Aug 12 '12 at 17:31
  • I'm not trying to be difficult, but how will we know when the underlying captcha has changed? If this seems to fix itself and it happens again next week, won't we have no choice but to open a new question about it? – Aaron Bertrand Aug 12 '12 at 17:34
  • 4
    @AaronBertrand If a third party tool is indeed blocking people from using the system as intended, thus defeating a ton of work that went into an otherwise extremely considerate UI, it's a valid point to raise. I'm not closing this against a question from last year knowing that things have probably changed, and perhaps it needs attention again. As I mentioned, I also experienced this earlier today. – Tim Post Aug 12 '12 at 17:37
  • @Tim I understood, but shouldn't someone bring the existing question to the attention of the devs? In fact a bounty has been opened on the previous question presumably to draw more attention to it. As I suggested, I don't think we need a new copy of the question covering the same issue if it keeps occurring. – Aaron Bertrand Aug 12 '12 at 17:45
  • 1
    @AaronBertrand Meta is the bug tracker that the community can access. Throwing votes at an old question when the issue happens again is like screaming into a plastic bag. In this particular case, a new topic is likely warranted, it's not like devs count votes on old issues (or pay attention to bounties at all {proof here}) – Tim Post Aug 12 '12 at 17:50
  • @TimPost The other question, though old, has been getting a lot of attention lately, including a bounty. I'm not sure if there's much we can do about reCaptcha (we just use whatever Google gives us), though. But we'll see. – Adam Lear Aug 12 '12 at 17:50
  • 1
    @AaronBertrand "but I'm sure that the admins, mods etc. can make devs aware that an issue has come around again without creating a duplicate question explaining the exact same problem again" -> how? Commenting on an old thread stating: "I have this problem too" doesn't work. Should I always add a bounty to such questions? Also doesn't sounds ideal. – PeeHaa Aug 12 '12 at 17:52
  • 1
    The argument about whether or not devs will see this issue is moot, since I just passed it on. The system's working as intended. :) – Adam Lear Aug 12 '12 at 17:55
  • 1
    @AaronBertrand Tried that in the past didn't come much out of it :) – PeeHaa Aug 12 '12 at 17:57

Browse other questions tagged .