4 ms·
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
by shafyy 3y ago
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.
- distcs 3y agoHow does it find out if the username is existing when it does not seem to send any request at all to the server?