Hacker News Reader

The state of error handling in general is woeful, they do anything to avoid admitting they're at fault so the negative screenshots don't end up on social media.

Blame the user or just leave them at an infinite spinning circle of death.

I check the network tab and find the backend is actually returning a reasonable error but the frontend just hides it.

Most recent one was a form saying my email was already in use, when the actual backend error returned was that the password was too long.

This takes down AI/search on chat.bing.com (GPT5, unauthenticated).

Funny, since I would have to prove to a an AI that I am human in the first place.

And others (ex. pinkbike) displaying "you have been blocked".

Always nice to see Pinkbike mentioned in the tech world :)

I think the site (front-end) thinks you have blocked the domain through DNS or an extension; and thus suggests you unblock it. It is unthinkable that Cloudflare captchas could go down /s.

Not only discriminating robots but actual people /s.