{"p":"","h":{"iv":"ROXSYW+cfvEbFHu5","at":"ocxplSQjdRC3tXEtB/9/wg=="}}

@davew @bix Also there is the "Client to Server" aspect of the ActivityPub spec, which might be along the lines of what you are interested in. It is basically not implemented by ANYONE, but the idea was to make the API surface of every ActivityPub server for *clients* the same for things like logging in, making posts, following, etc

2
Share
Share on Mastodon
Share on Twitter
Share on Facebook
Share on Linkedin
Darius Kazemi

@davew @bix so for example, if Mastodon conformed to the client-to-server spec, then you could easily point a client built for a different activitypub server to mastodon and it would be just fine.

There are people who implement multiservice clients but c2s would make it much much easier. And I think the additional effect would be something like the meta-layer you linked

0
2y
Steve Bate

@darius @davew @bix Do you think the #ActivityPub client-to-server protocol is specified well-enough to create an API adapter service for Mastodon? From my reading (still learning), it looks to me like there are several important aspects of the protocol that are either missing or underspecified.

1
2y
Replies