What a horrible status page, for a project of 1 person or 1 million persons, this is slightly above useless.<p>Stripe [0] and Segment [1] have pretty useful status pages, which provide, in my opinion, the real reason for a status page -- to confirm there isn't a problem on your end or that an issue you're facing is or isn't a problem with the service so you can escalate accordingly.<p>0. <a href="https://status.stripe.com/" rel="nofollow">https://status.stripe.com/</a><p>1. <a href="https://status.segment.com/" rel="nofollow">https://status.segment.com/</a>
There's an interesting fork of Signal, called 'Session', that aims to remedy many of the flaws in Signal's infrastructure/strategic choices. It's young - needing a lot more analysis & track record before earning serious credibility – but you can check it out at: <a href="https://getsession.org/" rel="nofollow">https://getsession.org/</a><p>Some of its Signal-contrasting goals include:<p>* no phone numbers needed<p>* onion-routed messages<p>* multi-device sync<p>* no central point of failure<p>I also don't see anything in Session's materials that they're placing Intel™ SGX™ at key points in mandatory introduction/contact-uploading/cloud-backup steps – as Signal likes to do.
Explains why I was having issues this morning. Was receiving messages on the desktop app, but not my phone, and none of my messages where bring received regardless of where I sent them from.<p>Oh well, had they're working on it.
I presume it might be them struggling to deal with increased traffic from the quarantined crowd? Although I'm not sure how many users Signal has now and how much of an increase it's experienced.
Signal's quality issues are why I switched to telegram. The performance, quality, and UX are years ahead of Signal. Plus, I've never had a message drop on telegram, very much unlike Signal.<p>The one drawback is chats aren't e2e encrypted by default, but there is an option to have "Secret Chats" which are e2e encrypted.
Has it ever not been? I've been unable to receive messages on desktop for 6+ months. The mobile app constantly loses message history and fails to receive notifications as well.<p>I've submitted multiple detailed support tickets with screenshots, steps to reproduce, etc, to no avail, never even got a response.
this only serves to highlight how critical it is for signal to switch to a distributed design. Its a great technology, but worthless if regimes can just QoS it into oblivion or block it entirely.