|
Top-level
To preform the following actions, in loosely-coupled fashion, across #SocialMedia enclaves (or #DataSpaces) you need an open protocol (what #ActivityPub offers): 1. Create Posts (or Notes) The collective arising from ActivityPub usage is the #Fediverse. Mastodon has made the above both popular and broadly accepted. 3 comments
@kidehen @Mastodon @tallship @Gargron @peepstein @blaine @atomicpoet Interesting point. If the "Fediverse" is about federation then the S2S aspect of #ActivityPub enables that federation, not the AP C2S part (which doesn't even require a federated server). For that reason, I think clients using the Mastodon C2S API are actually Fediverse clients (among others). If you'd like a challenging exercise, try defining the full Mastodon C2S API using the AP C2S spec (including event streaming, etc.) Yes, Server-Server (#S2S) is handling the federation aspect, but it gets tripped up in the broader sense of loose-coupling of clients and servers which is quite important. The #Fediverse benefits from clients with rich #UI/#UX available to all #ActivityPub servers rather than just @Mastodon -- especially if that's kinda forced via its platform-specific #API. This concern is from experience re #SocialMedia platform dynamics 😀 |
Gregory's Server
@steve,
The @Mastodon and #Fediverse confusion is partly due to the fact that Mastodon only supports the Server-Server aspect of #ActivityPub while using its own #API for Client-Server interactions. Net effect, it has the lions share of clients generally perceived as Fediverse clients -- which is a strategic point of vulnerability over the longterm, IMHO.
/cc @tallship @Gargron @peepstein @blaine @atomicpoet