Daniel Novak on Twitter posted this[1] after reading the Signal-Android commit history[2]:<p>"I think the @signalapp apps DDoS'ed the server. Servers ran over capacity due to influx of users and started to return HTTP 508 which was not handled by the app and millions of apps started retrying the connection at once. Judging from recent commits in <a href="https://github.com/signalapp/Signal-Android/commits/master" rel="nofollow">https://github.com/signalapp/Signal-Android/commits/master</a>"<p>Surely a timely reminder for all of us:<p>- Avoid infinite retry loops<p>- Build jitter and exponential backoff into retry logic<p>The code isn't terribly hard to write, but remembering to write it can be (if your HTTP client doesn't do it by default).<p>[1] <a href="https://twitter.com/NovakDaniel/status/1350471722034745348" rel="nofollow">https://twitter.com/NovakDaniel/status/1350471722034745348</a><p>[2] <a href="https://github.com/signalapp/Signal-Android/commits/master" rel="nofollow">https://github.com/signalapp/Signal-Android/commits/master</a>
I'm afraid that some people who were trying to jump over or who had done so recently had a horrible experience and might go back, especially since Whatsapp is delaying the policy now
Signal is back. <a href="https://nitter.net/signalapp/status/1350595202872823809" rel="nofollow">https://nitter.net/signalapp/status/1350595202872823809</a>
While this kind of issue happen everytime when something becomes promoted all of the media, everywhere, overnight, i am glad i went with Telegram instead of signal, 24 hours downtime is huge for a messaging app
Compared to other chat services, Signal sadly doesn't offer a feature rich/ergonomic chat platform. I am actively using it but I feel I have gone backwards in terms of user experience.