32
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 02 Sep 2024
32 points (97.1% liked)
Fediverse
28262 readers
580 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
- Posts must be on topic.
- Be respectful of others.
- Cite the sources used for graphs and other statistics.
- Follow the general 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
And... that if "activitypub just works" , so does XMPP.
And... XMPP servers offer better performance and taking less resources than any of the leading AP projects.
And... XMPP already has E2EE.
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.
None of your questions are about the protocol, but implementation details of the application.
My point is that the protocol doesn't work well for the use case.
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.