@silverpill I agree that domain-specific APIs have their place and serve their communities well. Mastodon API, Lemmy API, etc. are certainly designed by experts in their respective domains.

Where I'd offer a different perspective is on the potential for improvement. I believe there's still significant room to enhance developer experience, especially for client apps aiming to provide optimal UI/UX.

My interest in GraphQL isn't about replacing domain expertise, but rather providing a more efficient abstraction layer that could:

1. Reduce over-fetching and under-fetching of data (getting exactly what's needed)
2. Provide better type safety and IDE integration
3. Simplify complex state management on clients
4. Enable more responsive UIs with optimistic updates

I see this as complementary to domain-specific knowledge, not contradictory. Domain experts would still design the underlying data models and relationships—GraphQL would just provide a more flexible way to query them.

As for ActivityPub C2S, I agree it should be the foundation of any universal client API. But the current C2S spec alone doesn't provide the ergonomics needed for modern app development. Ideally, we'd have something that combines ActivityPub's semantic model with more developer-friendly query capabilities.