Skip to main content


Should ActivityPub and ATProtocol be Potentially Merged into a Single Protocol?


I know that this will most likely get me a ton of downvotes, but I’m genuinely curious: should ActivityPub and ATProtocol potentially be merged into one unified protocol?

If they were combined, Fediverse users and ATmosphere users could enjoy the benefits of each other’s ecosystems—like richer content interaction, better moderation tools, and more seamless identity management.

Bluesky and Mastodon users could interact natively without relying on bridging bots like Bridgy Fed.

Would merging the protocols strengthen decentralized social media, or would it create more complexity and friction between communities?

I’d love to hear your thoughts.

in reply to Teknevra

The two side philosophy and ideology is too different to for this to happen
in reply to schnurrito

No, it’s really not; this is exactly what this thread is about if you apply a little foresight
in reply to Teknevra

both do have scaling issues it seems, maybe some large scale investment would be nice - surely there’s some rich tech bros out there with cash burning a hole in their wallets
in reply to Teknevra

For my own project I'm looking for a way to be protocol agnostic and support either, and ideally more. If you have ideas git.benetou.fr/utopiah/biggu_s… please let me know.
in reply to Teknevra

I think ATProtocol is doomed, so no.

Bluesky got too big too fast and has too many greedy corporate weasels already involved. For the time being, they're pretending to actually prefer an open protocol, but I think that's just a marketing ploy and it will never last. They're going to EEE it sooner or later.

This entry was edited (4 days ago)
in reply to Teknevra

What about just using both #friendica has a plugin to support #at (as well as #rss and others)

Fediverse reshared this.

in reply to abeorch

wafrn connects to both too
This entry was edited (3 days ago)
in reply to Teknevra

No. You don't want bluesky making decisions on ap. It will end up in a Microsoft situation.
in reply to Teknevra

this question is basically equivalent to asking "should Rust and Kotlin be merged into a single language?". the two protocols are VERY different on a foundamential level, merging them is just not possible without very deep changes. the closest one can get is either using an application which implements both protocols, or use a bridge.