Home | Notifications | New Note | Local | Federated | Search | Logout

Note Detail

dansup@dansup@mastodon.social (2026-05-16 22:59:54)
When it comes to ActivityPub c2s (client-to-server), I understand why it's unpopular and not widely supported.

Mastodon and Loops have wildly different APIs, and it would make no sense to try to adapt c2s for these platforms because then you have to duplicate validation and other logic, and for what?

The 2 people who actually use this?

A unified ActivityPub API for s2s would only work if every implementation handled every schema the same way, and again, difficult to get done.

s2s for the win

---Replies---

Gregory@grishka@mastodon.social (2026-05-16 23:05:51)
@dansup c2s is simply impractical, too. Both on the client and on the server.

On the server, you have to merge two disparate streams (feed and notifications) into one inbox.

On the client, you have to split them back apart. You also have to load a lot of non-optimized stuff from different servers. You just have to make lots of requests to do simple things, and now imagine all that on 2G.

I can imagine a "minimal" server that implements c2s but almost no UX of its own though.