136
This has always been a huge problem I have with signal. It's open source but it's not open infrastructure
So is any other frictionless messaging app, so...
Wake me (or rather the other people out there) up when federated doesn't mean worse than centralized.
When Reddit was down, most (all?) Lemmy and Piefed instances were still up. Aside from the number of users currently on the platform, I don't see any significant ways that Lemmy is worse for the average user than Reddit.
Federation is less friction imo. If you want to message someone who has a signal account, you have the friction of making yet another account to message them. If you then want to message someone who uses whatsapp, you need to make yet another account to message them. Etc, etc. That seems far worse than the awkwardness of trying to interact with microblog activitypub platforms within threadiverse activitypub platforms. Granted, you still have multiple federation standards (ie: email, activitypub, matrix) that don't directly interact at all (although that might be for the best).
With federated platforms, you can message anyone using the same federation standard. Unfortunately, there's more than one, so you need an email address to message anyone else who uses email regardless of whether they're icloud or google or aol or self-host. But you can't email someone using activitypub or matrix directly. And even within activitypub, its far from seamless to interact between different parts (piefed/mbin/lemmy all work pretty well together, but interactions between more different parts because more awkward).
This is why folks use Matrix. But it still needs a lot of work.
But it still needs a lot of work.
And that’s why folks use Signal.
It’s the most accessible privacy-friendly option. IMO we should be pushing for both things. Signal to implement decentralized infrastructure and at the same time improve existing apps like Matrix.
I'm using SimpleX with my family, to see if it's any good and I think it's pretty ok :-)
Element X got better recently, with space and thread support
Has it been pushed out yet? I've been waiting for this since seeing it in original Element.
Both are working, the features are "experimental" (you enable them in the settings) but they work
As it turns out, none of the services I run from my living room NAS or the one that I have hosted on a dedicated machine elsewhere had an issue.
And all three users rejoiced!
Seriously, while self-hosting is an option for some, it's not viable for the vast majority of humanity and unless something revolutionary happens, that's unlikely to change. Ultimately, technology is complex and our dependence on it will continue to create friction.
As it turns out, not every problem has a simple solution.
This article was posted here as well. Here's the comment I left there:
This article seems either very naïve, or fairly disingenuous. Signal is not precariously installed on one box, and if that box goes down, the service dies. It is distributed. It's running on many machines within AWS, and technologically, there's no reason it couldn't be in multiple regions of AWS, or even spread across multiple clouds (e.g. Azure, Google Cloud, Oracle, etc), to improve resiliency to outages. The only way in which it is "centralized" is that there's one foundation in charge of the whole thing. Are there drawbacks to this? Yes. But self-hosted, distributed, mesh/relay chats also have drawbacks. Servers in the mesh go down, people don't keep things updated, they don't necessarily connect to every other instance creating disjointed pockets, etc.
Also, to say "we don't need the internet" we need "mesh networks" is odd... The internet is a mesh. Hence "inter." Anything else is just a smaller version of the same thing, again with some benefits and some drawbacks.
Fighting a (relatively) successful platform that champions privacy and security, seems like a bad thing to do, when those are the same primary goals of the platform you support. It would be better to discuss the merits and use cases of each, and beat the privacy and security drum together.
In my opinion, this article is just spreading FUD. Signal is not perfect, but it's pretty good. And when there's an outage, we know why, and we know there's a team working on it. With a federatated service, it may be harder to take "the whole thing" down, but that doesn't mean nodes don't go down, service isn't disrupted, etc. Scaring people away from a (usually) reliable, open platform, that has been audited, that actively advances security research and keeps it's platform secure against emerging threats, is counter productive. It's just going to keep people using SMS and WhatsApp.
It's funny aws report didn't mention 40% of aws sysops people were replaced by AI right prior https://blog.stackademic.com/aws-just-fired-40-of-its-devops-team-then-let-ai-take-their-jobs-d9db9d298bfa
That's about à change that is multiple months old, only the article is from 2 days prior.