this post was submitted on 22 Apr 2025
90 points (95.0% liked)
Fediverse
32985 readers
346 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)
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Activitypub and the matrix protocol are different things, they aren't supposed to interact with each other. Matrix servers using matrix implementations (synapse, tuwunel, conduit, etc) can interact with each other, since they are all based on the same protocol. Same way we do it, how AP servers with mbin,piefed,lemmy interact all with each other, since they are all based on the same protocol, too.
Revolt doesn't federate at all. They even admit this. ~~I stand corrected on rocket.chat, they actually implemented the matrix protocol, so it's interoperable with matrix.~~ See poVoq's reply
I think your last point is flawed, since even with multiple revolt instances; they don't interact at all. Which, is not federation. Matrix is federated, there's no other way to look at it and they're not comparable, and not meant to be compared at all.
They originally planned this, but realized along the way that the Matrix specs are overly complicated and change at the wim of Element, so they ended up only supporting a link to Synapse via the appservice system, which isn't great as it means you have to run both Rocketchat and Synapse on the same server for it to work.
Ah, matrix being a PITA; what a surprise :D
Yeah, it's a far fetch calling it federated at all. Will edit, thanks.
I'm not very familiar with the matrix protocol but rocket.chat advertises itself as having implemented the matrix protocol. What you said is also true according to their documentation, so now I'm confused about what is actually going on. Based on what rocket.chat implemented, is it wrong to say that they use the matrix protocol? And what are the limitations of their approach as opposed to a full implementation of it?
I guess they are being creative on marketing with having implemented a small part of the matrix protocol via their appservice bridge.
The disadvantage is that it is just a bridge like many others and totally dependent on Synapse, which is a resource hog and open-core.
I reached out to them and they told me they are currently working in implementing the native protocol and they'll replace the bridge with it.
Well, lets see when that actually happens. I am doubtful.
I guess i was taking the more generous route with the term then, I was treating capability to interact on the platform as federated which in hindsight doesn't make as much sense as in the normal context of it.