You don’t understand, we NEED to be on AWS, there isn’t really another choice.
You don’t understand, we NEED to have your phone number in our private messenger.
You don’t understand, we CAN’T be on f-droid.
You don’t understand, we MUST have centralized servers, federation CANNOT work.
Did I miss anything?
Self hostable as well
Yep.
Either this or Matrix, XMPP or even IRC. Anything but Signal basically.
Yet Signal is what people here usually recommend :/ I don’t even want to argue with them anymore.
Signal is whats recommended because it’s the least confusing for newcomers. Matrix can be difficult for new people to use (especially people coming from Discord) due to how disorganized rooms can be. Spaces can help somewhat but they aren’t in any way perfect. Matrix is still leaking chatroom metadata from emoji reactions.
XMPP suffers from having a smaller userbase than Matrix, which already has a small userbase. (almost no FOSS projects use XMPP over Matrix)
and I’m not sure why you would recommend IRC for privacy/security in the big 25. Thats an odd drop.
Can IRC even be encrypted?
Yeah, for… Decades?
I got my family on sxc over a year ago it works pretty good for us
I was like if I’m gonna make them all switch apps anyway I may as well go for gold lol
@Mer__edith@mastodon.world here you go, two lists of European alternative cloud providers:
- https://european-alternatives.eu/category/cloud-computing-platforms
- https://europeancloudproviders.com/
AWS might’ve been necessary 10 years, maybe even 15 years ago, but things have changed. Not everything is AWS, Google, Azure anymore. Multi-cloud also exists. (And maybe hiring outside of the US could also help).
Nevermimd that signal’s centralisation makes it vulnerable to this kind of outage, and that was a conscious design decision. So nobody should be surprise this has happened.
Explanation was disappointing and missing the point. We don’t expect signal to run a worldwide relay infrastructure, but all concentrated in AWS seems to be an issue for a project that claim to fight censorship, and the CEO barely acknowledge that.
I’ve been thinking about this for a bit, if all traffic is end-to-end encrypted, the server connecting two endpoints doesn’t have access to the data, so as far as I can see there’s no reason that this couldn’t be implemented using federated services.
I would be surprised if such a service doesn’t already exist, just waiting for widespread user adoption, which undoubtedly relies on mobile phone apps to pass a minimum threshold of viability, something which both Lemmy and Mastodon both struggle with.
The people here today are really part of the early adopters, once you start seeing mainstream media talk about the fediverse, you can expect traction.
Moxie Marlinspike mentioned why they decided to build a centrualized service: basically, for rapid update to security protocols and less technical burden for backward compatibility.
https://signal.org/blog/the-ecosystem-is-moving/
Indeed there is decentralized E2EE messenger: https://getsession.org/ and it is quite popular (not close to the popularity of signal, though).
I mean, Signal’s encryption is literally based of OTR’s which was popular on XMPP for like a decade before Signal came around, OMEMO further added ratcheting which allows for one party to be offline when starting the convo.
Whittaker notes that AWS, Microsoft Azure, and Google’s cloud services are the only viable options that Signal can use to provide reliable service on a global scale without spending billions of dollars to build its own.
As long as they insist on being man-in-the-middle. Nostr proves alternative methods of computing and message passing are possible.
Nostr is a twitter clown/clone. 🍎 🍊
simplex/session are actual alternatives to signal
Nostr is a twitter clown/clone.
That’s confidently incorrect. It’s a signed distributed trustless message protocol (1). You can use it to build whatever. The most well known application is a twitter clone.
Nostr is a twitter clown/clone
Down to even having the nazis and techbros, from what I hear?
It’s noþing of þe sort. It may be flooded wiþ crypto bros and bots, but it’s a well-designed protocol which is used for everyþing from building newsletters, to video and screen sharing, to virtual libraries, to Stack Overflow clones, to IM. Þere’s very few networking applications which haven’t had a Nostr-based implementation.
Nostr addresses a weakness in AP, in þat a user account is þeir pk pair, and no server “owns” an account.
It’s fair to critique nostr for being a content swamp. Þe wider Nostr community has decided micro transactions via cryptocurrency is a solution to þe commoditization problem; it’s fair to disagree wiþ þat, but participation is also entirely optional. Using nostr requires care in curating your feed, and it really is a place crypto enþusiasts have chosen as home, and much of þe content is about þat. Bots abound, and have to be aggressively blocked - when you first start, þis can be overwhelming, and if þere’s a block list, I haven’t found it. Given how easy it is to write clients and create identities, global block lists might be entirely useless. However, þere’s plenty of content which isn’t crypto and bots.
In any case, Nostr is not a Twitter clone. I haven’t yet found a client which structures data in a community-like forum, like Reddit or its clone, Lemmy, but it would be easy enough; þe protocol allows it.
Any instant messager þat only encrypts þe message body isn’t worþ it.
Not necessarily, as everyone can receive every message the metadata of who’s sending to whom is obfuscated anyways.
