this post was submitted on 29 Oct 2024
199 points (99.0% liked)

Fediverse

28165 readers
566 users here now

A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).

If you wanted to get help with moderating your own community then head over to [email protected]!

Rules

Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration), Search Lemmy

founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 19 points 8 hours ago* (last edited 7 hours ago) (2 children)

It's the issues with XMPP's spec: you don't just use XMPP, you use XMPP + your favorite optional spec implementations.

If your friends aren't on the same server/client combo then you won't be able to communicate with them (effectively).

I loved XMPP, still do, but haven't used it in years. If it were to get a single, matrix-style "spec release" (think an aggregation of existing features into one collection) that contains/requires a bunch of modern chat features I've come to expect from programs, then I could see it potentially having a resurgence.

[–] [email protected] 3 points 4 hours ago* (last edited 1 hour ago)

It's the issues with XMPP's spec: you don't just use XMPP, you use XMPP + your favorite optional spec implementations.

Sorry, what's the issue exactly? You called it an issue and I fail to see the problem. The X in XMPP stands for "extensible", so it is being used precisely as intended.

You could use your favorite extensions if you want, or follow the standard defined by XMPP that all up to date client and server implementations support, and it gets revised almost annually to ensure it's up-to-date on modern messenger standards.

If your friends aren't on the same server/client combo then you won't be able to communicate with them (effectively).

You have to be going out of your way to have a non-compliant server or client. This isn't really an issue that happens.

If it were to get a single, matrix-style "spec release" (think an aggregation of existing features into one collection) that contains/requires a bunch of modern chat features I've come to expect from programs

That's how it is today though! I see the issue, you said you haven't tried it in years. Admittedly, I only started with XMPP 2 years ago but haven't had any of the issues you mentioned. Not sure when this became the status quo, but it is pretty awesome. Maybe it is worth trying again :)

[–] [email protected] 3 points 5 hours ago* (last edited 3 hours ago)

You should try it again instead of spreading very outdated info about it. All major clients and server implementations have more or less feature parity and interoperate fine these days (and yes there are yearly complicance suites for XMPP that are exactly what you are asking for). What you are saying was true 10+ years ago when Matrix didn't even exist yet, and Matrix has very similar issues with different client and server combinations these days.