Conversation

Notices

1. Embed this notice
   Neo-Rodneyite: Yap Szn ✍🏿📖 (jalcine@todon.eu)'s status on Thursday, 14-May-2026 01:36:18 JST Neo-Rodneyite: Yap Szn ✍🏿📖

   NGL I wish that C2S was more viable on here. That'd make AP so much more *interesting* to me.

   • Embed this notice
     Evan Prodromou (evan@cosocial.ca)'s status on Thursday, 14-May-2026 01:36:15 JST Evan Prodromou

     in reply to

     @jalcine I say "ActivityPub API" rather than "C2S"; see here for why:

     https://ghost.evanp.me/why-i-use-activitypub-api-or-social-api/

   • Embed this notice
     Evan Prodromou (evan@cosocial.ca)'s status on Thursday, 14-May-2026 01:36:16 JST Evan Prodromou

     in reply to

     @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.

   • Embed this notice
     Evan Prodromou (evan@cosocial.ca)'s status on Thursday, 14-May-2026 01:36:17 JST Evan Prodromou

     in reply to

     @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.

   • Embed this notice
     Evan Prodromou (evan@cosocial.ca)'s status on Thursday, 14-May-2026 02:06:43 JST Evan Prodromou

     in reply to

     @jalcine We have a task force at the Social Web Community Group working on the ActivityPub API. I'm excited about it.

     https://github.com/swicg/activitypub-api/

   • Embed this notice
     Neo-Rodneyite: Yap Szn ✍🏿📖 (jalcine@todon.eu)'s status on Thursday, 14-May-2026 02:06:45 JST Neo-Rodneyite: Yap Szn ✍🏿📖

     in reply to

     • Evan Prodromou

     @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)

   • Embed this notice
     Evan Prodromou (evan@cosocial.ca)'s status on Thursday, 14-May-2026 20:48:30 JST Evan Prodromou

     in reply to

     • Steve Bate

     @steve @jalcine what you do is up to you! Use the term that best describes the technology to the audience you're trying to reach.

   • Embed this notice
     Steve Bate (steve@social.technoetic.com)'s status on Thursday, 14-May-2026 20:48:31 JST Steve Bate

     in reply to

     • Evan Prodromou

     @evan @jalcine Just to be clear, I refer to it as ActivityPub C2S API or C2S protocol (which covers both read and write capabilities), not just C2S.

   • Embed this notice
     Steve Bate (steve@social.technoetic.com)'s status on Thursday, 14-May-2026 20:48:32 JST Steve Bate

     in reply to

     • Evan Prodromou

     @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.