this post was submitted on 15 Jan 2026
49 points (98.0% liked)
Fediverse
38933 readers
385 users here now
A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, Mbin, 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
While LOLA is great, I'd really love an established handshake mechanism for having two accounts on two bespoke services represent the same user.
For example, I want to have a pixel fed and mastodon presence that can be authored between the two. However, you currently can't make two accounts that are effectively linked to each other. I feel like this linking is important for further decentralizing the fediverse (by effectively decentralizing the user itself)
I am unversed on all of this, but agree that interoperability between not only instances but also platforms like between lemmy and mastadon, and even a friend connection site to replace facebook, could help the fediverse grow to finally get a critical mass.
That's because AP as it is implemented today is crap, it's a superficial compatibility layer on top of a proprietary (as in, doing non-standardized stuff) platform. We need to take it on its head and make AP the actual core then build on top but that requires some work
What is this proprietary layer you speak of?
The mastodon api, or the lemmy api, or the xyz api. Eagh platform has its own. Being public doesn't make it standard, hence the "proprietary" qualifier
Oh I see. Yes, AP first apps would be great, but getting older apps connected via AP is important too.
NodeBB predates ActivityPub (or came around the same time), and so we added it recently. It works quite well with our existing code. Not much of a compatibility layer.
This is something I believe the ActivityPub API can tackle...