Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
eupolicy.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
This Mastodon server is a friendly and respectful discussion space for people working in areas related to EU policy. When you request to create an account, please tell us something about you.

Administered by:

Server stats:

224
active users

eupolicy.social: AboutProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.6

#c2s

0 posts0 participants0 posts today
洪 民憙 (Hong Minhee)<p>I've been thinking about client-server interactions in the <a class="mention hashtag" rel="nofollow noopener noreferrer" href="https://hollo.social/tags/fediverse" target="_blank">#<span>fediverse</span></a>. <a class="mention hashtag" rel="nofollow noopener noreferrer" href="https://hollo.social/tags/ActivityPub" target="_blank">#<span>ActivityPub</span></a> <a class="mention hashtag" rel="nofollow noopener noreferrer" href="https://hollo.social/tags/C2S" target="_blank">#<span>C2S</span></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 noopener noreferrer" target="_blank">GraphQL</a> + <a href="https://relay.dev/" rel="nofollow noopener noreferrer" target="_blank">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 class="mention hashtag" rel="nofollow noopener noreferrer" href="https://hollo.social/tags/GraphQL" target="_blank">#<span>GraphQL</span></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 class="mention hashtag" rel="nofollow noopener noreferrer" href="https://hollo.social/tags/Relay" target="_blank">#<span>Relay</span></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 class="mention hashtag" rel="nofollow noopener noreferrer" href="https://hollo.social/tags/fedidev" target="_blank">#<span>fedidev</span></a></p>
Strypey<p><span class="h-card" translate="no"><a href="https://mastodon.social/@naturzukunft" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>naturzukunft</span></a></span> <br>&gt; rdf-pub.org is providing c2s</p><p>Awesome, so that's at least 3 server packages to test clients against. Pleroma, Epicyon, and rdf-pub.org.</p><p><a href="https://mastodon.nzoss.nz/tags/ActivityPub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ActivityPub</span></a> <a href="https://mastodon.nzoss.nz/tags/C2S" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>C2S</span></a></p><p><span class="h-card" translate="no"><a href="https://social.coop/@smallcircles" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>smallcircles</span></a></span> <span class="h-card" translate="no"><a href="https://jawns.club/@skyfaller" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>skyfaller</span></a></span> <span class="h-card" translate="no"><a href="https://ausglam.space/@hugh" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>hugh</span></a></span> <span class="h-card" translate="no"><a href="https://epicyon.libreserver.org/@bob" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>bob</span></a></span></p>
ExploreLive feeds
About