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 :(
@res260Émilio Gonzalez 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.
If you have a fediverse account, you can quote this note from your own instance. Search https://cosocial.ca/users/evan/statuses/115969598774465714 on your instance and quote it. (Note that quoting is not supported in Mastodon.)
