Conversation

Notices

1. Embed this notice
   Émilio Gonzalez (res260@infosec.exchange)'s status on Wednesday, 28-Jan-2026 08:14:16 JST Émilio Gonzalez

   I love #activitypub but seeing how slow its development is compared to #atproto makes it hard to be excited about it. This goes for both protocol development and ecosystem development.

   ATproto has many cool projects popping up every month, the vision is clear and platforms integrate with each other.

   I don't see this excitement and work on the ActivityPub side :(

   • Embed this notice
     Evan Prodromou (evan@cosocial.ca)'s status on Wednesday, 28-Jan-2026 08:14:16 JST Evan Prodromou

     in reply to

     @res260 I think part of that is the API.

     In our ecosystem, we've normalized that you have to build the whole server side, with data storage and network interoperability and so on, for every single new kind of app.

     It'd be great if you could use a standard API to make cool apps, and leave all the plumbing to a general-purpose server.

     That's what we're doing in the ActivityPub API task force at w3c.

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

   • Embed this notice
     Evan Prodromou (evan@cosocial.ca)'s status on Wednesday, 28-Jan-2026 08:22:44 JST Evan Prodromou

     in reply to

     @res260 you and me both!

   • Embed this notice
     Émilio Gonzalez (res260@infosec.exchange)'s status on Wednesday, 28-Jan-2026 08:22:45 JST Émilio Gonzalez

     in reply to

     • Evan Prodromou

     @evan That would make sense. For ATProto, not being required to think about the PDS and the relays implementations must help a ton to get projects off the ground quickly. Hope the Social API changes that 🙏