this post was submitted on 02 Sep 2024
32 points (97.1% liked)

Fediverse

28396 readers
244 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 !moderators@lemmy.world!

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
ruud@lemmy.world
Xylinna@lemmy.world
MrCenny@lemmy.world
TragicNotCute@lemmy.world
automodbeta@lemmy.world
woelkchen@lemmy.world
32
Using messaging protocols (XMPP, Matrix, etc) for federated social media vs. ActivityPub? (lemy.lol)
submitted 2 months ago by matcha_addict@lemy.lol to c/fediverse@lemmy.world
19 comments fedilink hide all child comments
 

From a practical sense, ActivityPub may be the obvious choice as it gives easier interop with the largest federated platforms.

But what else? There are existing platforms built on these protocols, such as movim for xmpp, and another for matrix I forget.

From a technical standpoint, are there any major pros and cons?

you are viewing a single comment's thread
view the rest of the comments
[–] LodeMike@lemmy.today 1 points 2 months ago* (last edited 2 months ago) (1 children)

And what do you do about other clients? What happens when the user wants to clear messages on the server when they're fetched, but doesn't want to do that for the social network rooms? What about moderation.

XMPP is good at a very specific thing and I don't think its users would like all the necesary changes.

[–] rglullis@communick.news 4 points 2 months ago (1 children)

None of your questions are about the protocol, but implementation details of the application.

[–] LodeMike@lemmy.today 1 points 2 months ago (1 children)

My point is that the protocol doesn't work well for the use case.

[–] rglullis@communick.news 3 points 2 months ago

And my point is that the your complaints are not related to the protocol, but the applications using it.

Not only that, we are talking about different layers of the OSI model. XMPP should be compared with HTTP, not ActivityPub. There is absolutely nothing stopping someone from implementing the ActivityStreams vocabulary on XMPP.