chucker
failing gracefully with busy server
With 1.4 when I tried to login to my instance (mstdn.ca) it was quite difficult because the instance is throwing 502 errors on almost every request. It is successful about 1 of 3 times. This made the initial login/account creation on 1.4 quite tedious even when I managed to get past the App authorization step. Just logging in was throwing an 'authenticator error'. After about the 8th try of just clicking the login button in Mastoaut, I finally got through and logged in successfully.
Suggestion: some sort of background process to try logging in a few times if the initial request is rejected/502 and then throwing a more specific error or just a more specific response/fail when receiving 50x errors from the servers.
thank you for the work!
