Hacker News new | past | comments | ask | show | jobs | submit login

As far as I understand, this is related to a very inefficient implementation with Web Sockets (probably why you don't see an additional request). They're trying to get rid of that as soon as possible is my understanding, so things should get better.

What helped in my case: Picking another username. It's possible that somehow it handles existing username errors weirdly which leads to the infinite spinner.




How does it find out if the username is existing when it does not seem to send any request at all to the server?


Check the Websocket traffic, it might be in there.


I'm not sure that this is the reason, could be totally unrelated. Just a theory. Also, check the web socket traffic to see more info.




Consider applying for YC's Fall 2025 batch! Applications are open till Aug 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: