top | item 38929165

(no title)

dannysullivan | 2 years ago

I work for Google Search. Apologies for this! It’s been fixed now and posted to our search status dashboard https://status.search.google.com/incidents/hySMmncEDZ7Xpaf9i...

discuss

order

QuinnyPig|2 years ago

Fortunately, the issue was reported in the proper / only place to get support from Google: the front page of Hacker News.

rtsil|2 years ago

Thank god for procrastination!

lovelyviking|2 years ago

And what approach would be effective to get any buttons work on login page of ChatGPT?

In IOS 14 ‘ login’ button simply does nothing regardless of the browser.

It’s been reported and yet last time I’ve checked it doesn’t work. It’s more than two months already and as it seems simply no body give a sh….

jedahan|2 years ago

Would love to hear what the bug and/or fix was

stephenr|2 years ago

I'm more interested in why ua sniffing is considered acceptable for this.

Uptrenda|2 years ago

It's ok, sure it's stressful when something like this happens. Software is a hard field and the amount of things that can go wrong is immense. When I think about how few errors and downtime some of the larger services have I realize how much work must be involved.

code_biologist|2 years ago

I'd divide "things going wrong" into forced and unforced errors. Your upstream service providers sending subtly malformed data is a forced error. It happens. Doing user agent sniffing for presentation, poorly, is an unforced error.

It's not amateurish to have problems. It is amateurish (or malicious) to have problems caused by this specific class of issue.