this post was submitted on 16 Nov 2023
613 points (97.5% liked)
Technology
60052 readers
3783 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
What is a better alternative than signal?
Try out any of these:
- Session @session
- SimpleX @simplex
- Threema @threemaapp
They all don't require a phone number, which makes them immediately better than Signal, for devices that don't have a SIM.
@rustyriffs
@u_tamtam
As I wrote elsewhere in this thread, XMPP would be my preference. It just works. In fact that's what the other messengers (at facebook, Google, …) already use, but chose to put behind a walled-garden.
What matters is that whatever comes next (or, from the past in the case of XMPP) is federated, so no single organization has a single-handed control/monopoly over the network. Matrix and SimpleX are federated alternatives to XMPP, but I don't see Matrix stabilizing any time soon, and SimpleX just isn't ready yet. XMPP can offer you today an experience that's comparable to WhatsApp/Signal/Telegram/…
What's the issue with Matrix? I've tried both Matrix and XMPP but stuck with Matrix because it just works. XMPP is also good but it lacks a good Android client (The available clients look very outdated, and honestly, pretty ugly). It's also kinda hard to know if your client or server even supports all the extensions that are needed.
And so did I but ended up with XMPP instead of Matrix. Self hosting my messaging was important to me, and the cost of doing so is prohibitive with Matrix, the protocol and its implementations are just that inefficient, and there has been no progress in this area for as long as I've been keeping an eye on it. In my eyes, Matrix is broken by design.
Now, Element is indeed a decent client, and above the average of all XMPP clients, but what matters is for XMPP to have at least one great client per platform, which is undoubtedly the case. In practice, all my daily messaging happens over XMPP, the people I interact with are far from the nerdy type, and to them it's pretty much equivalent to WhatsApp & al.
Back to Matrix, besides the fact that after a decade there hasn't been any progress towards diversifying implementations (it's so messy, complex and changing that it's basically the same people implementing both client and server sides, and there is only one viable implementation to this day, by one entity), which is a big fat red herring, the entity who's behind 95% of the code of Matrix is now facing severe financing challenges. The future of Matrix is all but certain because of that, and there are reasons for concern.
I don't "hate" Matrix/Element/the Foundation, I just don't understand why they painted themselves in the corner they are in today, and rode the pipe dream of their broken protocol for so long. Would they cease to exist, it would look like natural selection to me. They are just not competitive and sorry if it hurts.
Try monocles chat
I already have
I love XMPP, but I can't recommend it as a reliable alternative to Signal. I find that encrypted communication is hit or miss with it. I had a problem just this week with it. I got a message delivered to a dormant Movim account I use, and I received it in my mobile xmpp app, Cheogram. I received it fine, I replied once fine. I went to send another message and it failed. I went to Movim in my browser, logged in to my account and was able to send. This is pretty typical in my experience-- some kind of mismatch or failure to negotiate between clients.
Sorry to hear. I've been using omemo (e2ee) without a single message lost since.. perhaps 5 years ? I also don't use movim (I don't trust its model and level of stability/maturity, especially with regards to doing e2ee in the browser). I would not recommend "XMPP via Movim" either.
Edit: a word
I don't really use Movim either. I set up an account some years ago while testing different federated social networks. However, I have had that same type of issue with more 'normal' xmpp chats. It seems to me that the development is a bit too fragmented. I am hoping for continued improvements though :)
My only problem with XMPP (and a lot of other federated protocols) is really the lack of quality clients. Most of them (especially on systems beyond Android and Linux) don't really have that good of a UX, or their UI is kind of bland or dated.
It's something that I hope gets improved eventually. Because having a variety of choices doesn't mean much if none of the choices feel particularly good.
Want a modern android XMPP client? Try monocles chat. Its UI is kind of modern.
I got mom to use Conversations.
What's up with monocles dev? They have a bunch of forked projects with their own name.
Monocles Launcher is based on KISS Launcher.
mail is based on K-9 Mail
What the other responders said (there are great clients out there, that fit mainstream and niche needs).
Also, it is not a problem of "federated protocols" per se, but of community-led projects. On the downside it may lack consistence and direction, but on the upside you can step in and contribute feedback, tests, documentation, and why not, code :)