Signal Is Up and Running
status.signal.org
status.signal.org
"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 https://github.com/signalapp/Signal-Android/commits/master"
Surely a timely reminder for all of us:
- Avoid infinite retry loops
- Build jitter and exponential backoff into retry logic
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).
[1] https://twitter.com/NovakDaniel/status/1350471722034745348
[2] https://github.com/signalapp/Signal-Android/commits/master
Edit to add: My point being, with their focuses (at least Signal's) being on offering end-to-end encrypted communication, it feels normal that they are not able to focus efforts on improving client experience. Hopefully something that they are able to achieve in the coming months.
Telegram's secret chat keys are never backed up. It's also faster and more reliable than Signal.
If E2EE is important to you, you can use secret chats.