XMPP Works fine when it's setup or when you don't manage the hosting, but God is it painful to self host an xmpp server. Then you have the clients that are all basically 10 years old at this point, except maybe Dino for linux. It even needs a special setup to work on restricted networks via port 80/443 because it wants port 5222 and 5223, and let me tell you, I've spent over a week trying to setup that reverse proxy, it was hell. I've never Hosted matrix so maybe it's worse, but this isn't the end of my gripes with xmpp. Most basic communication features in 2024 such as replies reactions quoting threads etc.etc. are unsupported ootb, and you need both a client that supports the extensions (often very slow to adapt "new" standards AND a server that has enabled the plugin for that feature.

Xmpp is plain old, and like many like to think, no xmpp was not "triple-E'd", people simply stopped using it because it's really inconvenient and the UX is horrible.

[–] poVoq@slrpnk.net 7 points 3 weeks ago* (last edited 3 weeks ago)

but God is it painful to self host an xmpp server

You are in for a world of pain regarding Matrix if you think xmpp is painful to host. Compared to hosting a Matrix server, XMPP is very pain-free to host. Sure, it takes a slight bit of effort to understand that there are other protocols than HTTP, but beyond that that initial learning curve, XMPP servers are extremely hassle free.

And you must have used extremely outdated clients. All the modern ones (which there are plenty) support replies and reactions etc. ootb. Let me guess, you only tried Pidgin? That client hasn't been updated for xmpp in 15 years or so, and is by far the worst.

[–] matcha_addict@lemy.lol 3 points 3 weeks ago

XMPP Works fine when it's setup or when you don't manage the hosting, but God is it painful to self host an xmpp server.

I recommend you use snikket if you're having trouble selecting plugins, because it has everything you need out of the box and its super easy to setup.

It even needs a special setup to work on restricted networks via port 80/443 because it wants port 5222 and 5223,

Isn't that just a configuration in prosody / snikket? What implementation did you use that didn't let you configure this? Or are you expecting major implementations to default to port 80/443? Because that would be quite problematic.

Most basic communication features in 2024 such as replies reactions quoting threads etc.etc. are unsupported ootb, and you need both a client that supports the extensions (often very slow to adapt "new" standards AND a server that has enabled the plugin for that feature.

This is already supported by the major clients. I know for sure that conversations on android (and I suppose the many clients based on it) supports it. For server implementations, it is available out of the box on snikket, and it is a plugin you have to enable on prosody.