I myself have XMPP accounts but almost never use it as my friends are not there at the moment (since years).
My XMPP account is email@example.com. You can say hi to me there!
@ademalsasa I opened a xmpp account in advance. In case people around me decide to wake up and start looking for alternatives for the dreaded WhatsApe.
@ademalsasa exactly the same situation. I have xmpp client always running, because I wish it spreads more.
@ademalsasa I don't use XMPP because no one that I know uses it and I found encryption to be hard to set up.
Thanks for the comment. I'm not XMPP-savvy enough to know how the OMEMO works and how the keys are exchanged to either parties. I didn't even know that one "message" can have two distinctive parts (one encrypted message, and one unencrypted placeholder). If this is true, this sounds such a big overhead that every single message is shipped with extra attached text. Is there any resources you can point me to to learn more?
The link in your message explains OMEMO and also links to the XEP where the protocol is documented.
That a message can convey multiple things is an integral part of XMPP. It's how we can evolve the protocol without fragmenting the network. Whether to include this fallback is up to the sender, it's not mandatory. The alternative is older clients silently ignoring messages.
@Mehrad @hund @ademalsasa @hbenjamin
Clients are gradually adding support for https://xmpp.org/extensions/xep-0380.html which allows them to understand that a message is encrypted even if they don't understand the protocol/algorithm. That would allow them to produce a nicer UI (e.g. localized, rather than whatever text the sender client adds).
Sending clients could probably be smarter too... e.g. stop including the fallback once they receive an encrypted reply (i.e. the recipient is actively using OMEMO).
@ademalsasa I don't think that XMPP has a good future, because Matrix is - for my opinion - way better. And I only know about 1-3 XMPP-users and everyone of them uses Matrix too.
I think that is a viable observation. It's not like "facts" or a huge argument.
I think one of the biggest problems with XMPP right now is that it's a community that isn't really interested in trying to become what matrix is heading off too.
Matrix is suceeding really well now too
Element's system is kind of it's own thing
But it's not as easy to just equate matrix to element anymore as there are so many new clients out now of high quality.
I've personally tried to engage in the XMPP community. But all I met was a dying breed strongholding a protocol that I feel is not something I could push to people as the answer to instant messaging. Particurarly when we have protocol like matrix that does all the right things for effective change
@hund I like XMPP, but clients are not so polished as Matrix ones, what makes it a hard time for newbies. My wife consider Blabber "way too difficult to use" when she wants to send an audio message, for example. Not to mention things as the OMEMO, that simply does not work when we try to log in a new device to reply old messages.
@hund Not bad, but still an issue for some: no reply function, only mention. Sending audio/video message needs an extra clicks (one to start, one to finish and one to send) etc.
In a server side, it is better at my view. It is simpler, faster and lighter. But I miss some specifications and the clients need too much polishing to compete directly.
@hund hello Hund, what is your XMPP handle? I've shared mine above and I hope we all can be friends.
For people who care about, support, or build Free, Libre, and Open Source Software (FLOSS).