Not the ONLY argument, of course!
OP, thank you for copping to the fact that this is clickbait :-)
XMPP is missing features and the clients are not in line with modern expectations.
However, I shut down my Matrix server because it was so buggy and slow that I didn’t trust it anymore. I did an upgrade and - all of a sudden - no one could log in. Syncing took forever, etc.
Prosody is what I"m running for my XMPP server right now. I had it online in about an hour and it’s been super fast.
I have some iOS users and they aren’t so happy about XMPP right now, though.
XMPP definitely needs more work on the clients. Personally, I like my GTK and terminal clients though. So fast and simple.
Running a huge Python program (which the official software for running a Matrix server is written in) for something that focuses heavily on real-time comms feels awful, the Go rewrite of Synapse can’t hit stable soon enough.
Link has actually a more interesting discussion than just the Matrix Dev diss 🤦♂️
The most promising fediverse integration right now is probably movim.eu with the libervia ActivityPub gateway.
Yeah I’m a sucker for drama. Stayed for the in-depth from-a-place-of-experience discussion though.
«The current implementation of Matrix wouldn’t have been possible without SSD’s.» –https://toot.cafe/@Coffee/107914396376609675
@toneverends
… and the clients are bad
… and version- and xep-hell…
… and missing features
… and dev who say “nobody needs it, because i don’t need it”
… and missing capacity on devs
… and missing money for public relationsPinging @deadsuperhero@lemmy.ml
@toneverends
i really hope, gajims dev process gets faster… they always say “we are working on it”
and vcards… different an incompatible techonolgy for the same purpose…
i can set an avatar in ldap, and modern clients ignore this… gajim sets it on some places not everywhere…
reactions an postings… i love them. “xmpp” say “it’s nice. there is a xep. but nobody needs it, so we’ve not implemented it yet”.and OMEMO is really ugly… if you have more than one client. and if you use webclients as well (movim for example) you get plethiora of omemo keys… and you canct get rid of them. they stick on your account like dog-shit on your shoes…
One OMEMO key per device (browser) is really needed for secure e2ee though. Matrix has weakened their MegaOLM quite a bit by allowing devices to share one key per account. At some point you have to ask why e2ee at all when you water it down so much. Its not like normal TLS connections are unencrypted.
@poVoq have you ever tried to identify all your keys… and delete unneeded keys?
i tried a lot of clients. and now i have 50 keys or more, but need only 4 or 5 of them… not possibility to delete the others.
Conversations autodeletes after 42 days, but this makes for frustration at the other end: “conversations deletes dormant keys too soon” [paraphrasing] https://github.com/iNPUTmice/Conversations/issues/4147
If it is really only 4-5 why not just delete them all and make new ones?
I told you… try it… i does not work. not in gajim, not in movim, not in conversations…
i tried it.
@poVoq they will come back or are not able to be deleted…
I’m very interested in the problem you describe. i also had UX issues dealing with keys in xmpp clients. if you’d like to talk about it some time and write some (more complete) feedback i’d be happy to help :)
