NGL I wish that C2S was more viable on here. That'd make AP so much more *interesting* to me.
1
Post
Replies:
7
@jalcine Friend, you and I both!
There is a ratcheting process on this, I think.
We need a core of server software that supports the ActivityPub API, so that client developers have something to work against. I've made one (onepage.pub), and I know there are others happening.
Then, we need a set of interesting API clients, to show what having a standard API can get us. I've done a couple that I like (a geosocial checkin app and a movie review app), but it would be cool to have more.
3
@[email protected] @[email protected] I've successfully posted to a @[email protected] instance using C2S, partly because the project I'm using to do so is something I'd like to see work in a wide variety of places and I'm hoping that I can do my small part to resolve the chicken and egg aspect of server/client support by producing things that use the API from the client side. I'd love to see broader support.
@evan this might be the way (just making stuff and not necessarily being pressed). I think what's pulling me into ATProto is mainly the lack of a need to also handle users (like I can rely solely on OAuth) but I'm understanding that to be changing here (I've been following updates on https://codeberg.org/fediverse/fep/ and what not)
1
@jalcine We have a task force at the Social Web Community Group working on the ActivityPub API. I'm excited about it.
@jalcine with interesting clients, there starts to be pressure on other servers to support the API. "Why can't I use SomeCool.app with my Misskey account?"
As more servers support the API, it becomes more interesting for more clients to build on top of it. More clients -> more servers -> more clients -> and so on. It ratchets up.
1
@jalcine I say "ActivityPub API" rather than "C2S"; see here for why:
https://ghost.evanp.me/why-i-use-activitypub-api-or-social-api/
1
@evan @jalcine Thanks for sharing your rationale for using "ActivityPub API". Given "client to server" is used 22 times in the spec and "ActivityPub API" (which could also apply to the server to server REST API) is not mentioned at all ("Social API" is mentioned once), it could be considered more insider jargon than "client to server" (C2S). I've tried using the various terms in discussions and "C2S" or "client to server" tends to lead to less confusion. I suppose it's one of those YMMV topics.
