Strypey
@strypey@mastodon.nzoss.nz  路  activity timestamp 2 months ago

@smallcircles
> what is needed client-side can be found in the AndStatus project ... there were among others no server implementations to test against

Seems like Pleroma had it working before mid-2020;

pleroma.social/announcements/2

The Epicyon server has support for AP C2S too, so that could also be used to test apps trying to implement it;

libreserver.org/epicyon/

Was any of this mentioned in the SH thread?

@skyfaller @hugh
@bob
small circle 馃晩 in calmness
@smallcircles@social.coop  路  activity timestamp 2 months ago
@strypey @skyfaller @hugh @bob

I did not mention a #SocialHub thread. There are multiple discussions where various aspects were discussed, that might still be useful. The search facility is best way to find them.

As for AndStatus the github issue lists their step-by-step progress in investigating what was needed, and what the challenges were. One of them was unavailibility of appropriate server back-ends to test against, mentioned *at the time* as challenge.

Would 鉂わ笍 more #ActivityPub C2S dev.
small circle 馃晩 in calmness
@smallcircles@social.coop  路  activity timestamp 2 months ago
@strypey @skyfaller @hugh @bob

> SocialCG

Certainly. And SocialHub with the FEP process. And countless other parties where people give their utmost to improve things. Very valiant efforts.

However there are 2 realities on fedi. One the near stalled (for 6 years!) open standards evolution. And the other where people implement new stuff that introduces protocol decay and tech debt. This increases 'whack-a-mole driven development' that's counter to and detrimental for broad interoperability.
Steve Bate
@steve@social.technoetic.com  路  activity timestamp 2 months ago

@strypey@mastodon.nzoss.nz @naturzukunft @smallcircles @skyfaller @hugh @bob There are other servers that implement C2S support (ActivityPods, Vocata, onepage.pub, ...). Lack of servers implementing C2S is not the problem. See the many other issues described in this thread for examples of why one can't built an interoperable AP C2S client with features a typical user would expect.