On stage now, @django — arguing for widespread adoption of ActivityPub client-server (C2S) protocol.
I agree with him.
At the very least, to make extension of ActivityPub through JSON-LD namespaces possible.
But also to decouple Fediverse client development from Fediverse server development.
And more.
#ActivityPub #FediDev #FediDevs #Fediverse #FOSDEM #FOSDEM2026 #SocialWeb #SocialWebFOSDEM #SocialWebFOSDEM2026
@reiver I’d love to see this but is it feasible without mastodon on board?
@reiver @toddsundsted Which server softwares *do* support it exactly?
Re: On stage now, @django — arguing for widespread adoption of ActivityPub client-server (C2S) protocol.
@mcc@mastodon.social hmm...
Mitra from @silverpill@mitra.social and OMI by @mariusor@metalhead.club come to mind, but unsure of any more.
@julian @mcc @silverpill @mariusor There is also maybe Mike Macgirvin's Forte https://codeberg.org/fortified/forte/src/branch/dev/FEDERATION.md#c2s ?
Hm, Forte doesn't seem that difficult to install https://codeberg.org/fortified/forte/src/branch/dev/install/INSTALL.txt
Re: On stage now, @django — arguing for widespread adoption of ActivityPub client-server (C2S) protocol.
@toddsundsted@epiktistes.com absolutely.
In fact, the app that made the AP news rounds a couple months ago was Holos, an AP client on your phone that connected to a server elsewhere. That's the ideal use case for C2S, but alas they didn't go that route.
I'm hoping to look into using it to enable cross-instance activities. Think "liking and replying" using your Mastodon account while browsing a WordPress site.
