<p>We have to go back <a href="/tags/activitypub/" rel="tag">#activitypub</a> <a href="/tags/c2s/" rel="tag">#c2s</a></p>
Edited 64d ago
c2s
<p>If I wanted to mess around with ActivityPub c2s clients what's a server I can host that has support for it?</p>
<p>I've been thinking about client-server interactions in the <a href="/tags/fediverse/" rel="tag">#fediverse</a>. <a href="/tags/activitypub/" rel="tag">#ActivityPub</a> <a href="/tags/c2s/" rel="tag">#C2S</a> isn't widely used, and most clients rely on Mastodon-compatible APIs instead.</p><p>What if we created a new standardized API based on <a href="https://graphql.org/" rel="nofollow">GraphQL</a> + <a href="https://relay.dev/" rel="nofollow">Relay</a> for client-server communication, while keeping ActivityPub for server-to-server federation?</p><p>The Mastodon-compatible API lacks formal schema definitions for code generation and type checking, which hurts developer productivity. And ActivityPub C2S is honestly too cumbersome to use directly from client apps.</p><p><a href="/tags/graphql/" rel="tag">#GraphQL</a> would give us type safety, efficient data fetching (only get what you need), and the ability to evolve the API without breaking clients. <a href="/tags/relay/" rel="tag">#Relay</a>'s features for pagination, caching, and optimistic updates seem perfect for social apps.</p><p>Would this be valuable to our community? What challenges do you see? How might we handle backward compatibility? And should this be formalized as an FEP?</p><p>Curious what others think about this approach.</p><p><a href="/tags/fedidev/" rel="tag">#fedidev</a></p>
<p>My fosdem talk is up! </p><p>I make a case for more platforms to support the ActivityPub client API, and how we should look beyond microblogging for future growth of the ‘verse</p><p><a href="https://fosdem.org/2026/schedule/event/QK7XSV-activitypub-c2s/" rel="nofollow" class="ellipsis" title="fosdem.org/2026/schedule/event/QK7XSV-activitypub-c2s/"><span class="invisible">https://</span><span class="ellipsis">fosdem.org/2026/schedule/event</span><span class="invisible">/QK7XSV-activitypub-c2s/</span></a></p><p><a href="/tags/c2s/" rel="tag">#c2s</a> <a href="/tags/fosdem/" rel="tag">#fosdem</a> <a href="/tags/fediverse/" rel="tag">#fediverse</a> <a href="/tags/activitypub/" rel="tag">#ActivityPub</a></p>
Edited 59d ago
<p>ActivityPub client development is coming along!</p><p>AP platform developers be warned, I be opening issues in your repo soon.</p><p><a href="/tags/activitypub/" rel="tag">#ActivityPub</a> <a href="/tags/c2s/" rel="tag">#c2s</a></p>
<p>(digital) doodling a little</p><p><a href="/tags/c2s/" rel="tag">#c2s</a> <a href="/tags/activitypub/" rel="tag">#activitypub</a> <a href="/tags/ios/" rel="tag">#ios</a> <a href="/tags/fediverse/" rel="tag">#fediverse</a> <a href="/tags/wordpress/" rel="tag">#wordpress</a></p>
