@naturzukunft
> rdf-pub.org is providing c2s
Awesome, so that's at least 3 server packages to test clients against. Pleroma, Epicyon, and rdf-pub.org.
Posts
-
As far as I understand, most (all?) fediverse #ActivityPub software does not use the Client-to-server protocol from the specs (https://www.w3.org/TR/activitypub/#client-to-server-interactions) but rather use custom APIs instead. -
As far as I understand, most (all?) fediverse #ActivityPub software does not use the Client-to-server protocol from the specs (https://www.w3.org/TR/activitypub/#client-to-server-interactions) but rather use custom APIs instead.@smallcircles
> I did not mention a #SocialHub threadTrue. My mistake : )
> Would
️ more #ActivityPub C2S devAm I right in thinking SocialCG have been looking at improving standardisation on that front?
-
As far as I understand, most (all?) fediverse #ActivityPub software does not use the Client-to-server protocol from the specs (https://www.w3.org/TR/activitypub/#client-to-server-interactions) but rather use custom APIs instead.@smallcircles
> what is needed client-side can be found in the AndStatus project ... there were among others no server implementations to test againstSeems like Pleroma had it working before mid-2020;
https://pleroma.social/announcements/2020/05/10/pleroma-security-release-2-0-4/
The Epicyon server has support for AP C2S too, so that could also be used to test apps trying to implement it;
https://libreserver.org/epicyon/
Was any of this mentioned in the SH thread?