yep, I have similar feeling of it. Still using #xmpp with my family members. It's much simpler to host and it just works. It has good android app #conversations and pc apps #dino and #gajim
Getting started with XMPP/Jabber and PGP for federated, encrypted messaging
This is a short thread where I explain how I started using the XMPP protocol and PGP encryption for secure messaging. I am not a security expert, but I am a mathematician and I am confortable with the Linux command line. This guide is for people who want to use PGP for secure messaging easily. You will need to be okay with typing commands into the Linux command line in order to do this, but I will tell you exactly what to enter.
Part 1: XMPP
Mastodon is like email, but for social media. You sign up for an account with a server, and then you can talk with any other accounts that are signed up on other servers, as long as your servers are getting along. (No one wants emails from the sketchy spam server, and we want to be able to choose between Yahoo, Gmail, etc.) XMPP (a.k.a. Jabber) is the same thing for text messaging.
Just like signing up for an email/Mastodon account, you need to sign up for an account. You can find a list of servers at list.jabber.at/ and will probably at least need to provide an email addess when making an account.
Once you have made an account, you need a client. On Linux, I've been having a good time using Dino (dino.im/). You can then enter your account name and password to log into your XMPP account and start chatting! There are both public rooms and you can also message directly with your friends.
Why don't you include the federated #XMPP (aka Jabber) protocol as an alternative? There are plenty of good clients for the phone and PC, like #Conversations, #gajim, or #dino. With the modern extensions like Omemo E2EE and various improvements for mobile use, it is very useable even on phones, while keeping the flexibility and resilience of a federated service (just like the Fediverse).
#XMPP enthusiasts out there: what would you say the ultimate Achilles heel of the XMPP ecosystem is, at present? Fragmentation of clients? What?
My sense is that it's this: when one goes to store an XMPP address in one's addressbook, there doesn't seem to be standard way to store an XMPP address. #Android doesn't have that as an allowable field, and #Thunderbird and #Nextcloud have an "Instant Messaging" field, where the type can be set to "XMPP". But are these two compatible with each other when trying to sync between them? Edit: Yes, but there's a catch: *the XMPP address must be prefixed with "xmpp:"*
So "user@foo.bar" is not an OK XMPP address, but "xmpp:user@foo.bar" is.
Then to make matters worse, now there's a wish to change the labeling of "XMPP Address" to "Chat ID": gultsch.social/@daniel/1140129…
It might be a long time before the address synchy-ness ever works again between Android <-> #Davx5 <-> Nextcloud <->Thunderbird
Note: Android allows a "Jabber" type for an IM address, where you *don't* prefix the address with "xmpp:".
(#DeltaChat gets to gloat hard here, as they have plain-old email addresses)
During the Berlin XMPP sprint, some XMPP developers worked on message formatting. Previously, formatting was done using simple markup (e.g. *bold*), which sometimes leads to unintended formatting and is limited in functionality. We now decided to transmit formatting information outside of the normal text, with optional fallback to markup for legacy clients. We worked on improving the specification and on support in three different clients, including @dino.
Over the last months, we've completely redesigned and rewritten @dino 's accounts and settings dialogs. The dialogs are combined into a single one now, which is adaptive and offers additional features like an option for OMEMO by default. The rewrite also resolves a number of issues and feature requests that were raised with the old implementation. It's still work in progress and will require further polishing.
We have an XMPP booth at the Chemnitzer Linux Tage. Join us for discussions about federated instant messaging and for stickers. #xmpp #dino #conversations_im #clt2024
@🆃🅸🅼🆃🆃🅼🆈 @Snikket @thomholwerda #XMPP is excelent choice although unfortunatelly #Dino is not keyboard and #screenreader accessible on linux and windows thus it may not suit some people. For majority I think it's awesome. #Conversations is fully accessible and hopefully it'll stay like this in the future.
You were right, the #Windows fork works nicely. I hope patches will be merged back to #dino upstream.
For basic users the GTK file dialog can be a bit distracting as it is different from what they are used to. The rest GTK design should be ok for them by my opinion.
Wow, #xmpp client @dino released new version with full 📞 #call support. I tested both 🔈audio and 🎥video between #conversations and #dino. It worked perfectly. 👍 👍
#xmpp client @dino released new version with full 📞 #call support. I tested both 🔈audio and 🎥video between #conversations and #dino. It worked perfectly. 👍 👍
