151–160 of 262 posts
Probably related to the AWS outage in Virginia
Genuine question - why not distribute over a) multiple AWS regions and b) distribute over multiple providers so that 'small' outages dont take down apps like this?
But after this outage, clearly not.
What's a good alternative to Signal on Android for casual messaging? I don't think Element is a good fit since it's not easy to ask a friend or family member to sign up for Element whereas it's simple to install Signal.
I ditched Signal about a month ago. Transferred my last group chat to iMessage. Most of my friends don't care about privacy, I tried to love Signal for 2 year, I recommended it to friends, only to give up and make a fool of myself. But after so long, the fact that I regularly don't get notifications of new messages is inexcusable. So in my inner cirle, Signal has damaged people's willingness to improve privacy. Thank…
After reading it, you might want to reconsider Signal again.
Earlier quoted context omitted.
moxie the creator of it is so against decentralizing signal its insane so thats never going to happen sadly, it really would fix the problem just have a few thousand server people start running and it connects to the network and gets sent messages to send to its destination
Decentralization is not some great magic. Its a gigantic pain in the ass to fix even a single simple issue across all those servers.
Earlier quoted context omitted.
moxie the creator of it is so against decentralizing signal its insane so thats never going to happen sadly, it really would fix the problem just have a few thousand server people start running and it connects to the network and gets sent messages to send to its destination
Did he give a reason for why he's against decentralization?
*edit
https://signal.org/blog/the-ecosystem-is-moving/ here is a post from moxie himself about why its centralised not decentralised
Wonder is it's related to the AWS's Degraded EBS Volume Performance in Northern Virginia? https://status.aws.amazon.com/
Earlier quoted context omitted.
moxie the creator of it is so against decentralizing signal its insane so thats never going to happen sadly, it really would fix the problem just have a few thousand server people start running and it connects to the network and gets sent messages to send to its destination
Did he give a reason for why he's against decentralization?
... is the article in question. Basically the argument is that federation slows down the possible rate of change. If you have but the one server in a system you can change things whenever you want and then push out any client changes.
The root concept here is that constant protocol and feature change is the most desirable state. Not all of us accept that.
Earlier quoted context omitted.
I haven't had reliability problems, but I do find it annoying that if I don't update my app frequently enough, they just cut communications entirely. That is, I don't get notifications that I've received new messages anymore. I usually find out about this when someone emails me to say they've sent me a message on Signal, but I've not responded. Instead of silently failing, I wish they would pop up a notification that…
I can't imagine this is an intentional choice by Signal. Always assumed it had something to do with the OS silencing unused applications.
Earlier quoted context omitted.
WhatsApp has awful usability and no desktop version.
I'm not a WhatsApp user, but the circumstantial evidence of every single non technical friend I have happily using WhatsApp every day strongly suggests its not a complete UX shitfight. What do you find "awful" about it's usability?
Whatsapp sucks for me because of an unusable desktop client. Their backups system is extremely slow. I've found that messages get sent and received slowest on whatsapp when comparing with other messaging apps even if the gap is almost inconsequential. There's a woeful lack of features that I love on telegram that make the app very barebones and dull. You cannot edit messages. The replying UX is a bit irritating. There's tons of stuff but this is a small gist
Earlier quoted context omitted.
Genuine question - why not distribute over a) multiple AWS regions and b) distribute over multiple providers so that 'small' outages dont take down apps like this?
I always thought they did distribute among AWS, Azure, Cloudflare and GCP as the output from running their domains on runson.cloud seems to suggest. But after this outage, clearly not.