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.
Any fediverse devs able to explain why? Is there a technical reason/limitation, or is it more about other considerations?
I'm looking for information here rather than speculation, thanks.
-
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.
Any fediverse devs able to explain why? Is there a technical reason/limitation, or is it more about other considerations?
I'm looking for information here rather than speculation, thanks.
@hugh According to one dev for GoToSocial:
"Implementing the C2S API is, I'm afraid, really out of the question, as it's totally underdefined, relies on the client to do almost everything, and would be an absolute nightmare project for us. That's a non-starter."
[feature] Dedicated GoToSocial client
gotosocial - Fast, fun, small ActivityPub server.
Codeberg.org (codeberg.org)
-
@hugh According to one dev for GoToSocial:
"Implementing the C2S API is, I'm afraid, really out of the question, as it's totally underdefined, relies on the client to do almost everything, and would be an absolute nightmare project for us. That's a non-starter."
[feature] Dedicated GoToSocial client
gotosocial - Fast, fun, small ActivityPub server.
Codeberg.org (codeberg.org)
Also #SocialHub #ActivityPub developer forum has a bunch of C2S-related topic. You can use the forum search facility.
SocialHub
Where ActivityPub developers coordinate their efforts to make the Fediverse a great space for cooperation
SocialHub (socialhub.activitypub.rocks)
A very detailed investigation on what is needed client-side can be found in the #AndStatus project. It was never completed AFAIK as there were among others no server implementations to test against.
Basic implementation of "client to server" ActivityPub protocol · Issue #499 · andstatus/andstatus
Note on current state (as of 2020-05-24) Pleroma Minimal "client to server" #ActivityPub implementation is available. It is tested at https://queer.hacktivis.me/AndStatus (that site has the latest Pleroma builds... some requests work at ...
GitHub (github.com)
-
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.
Any fediverse devs able to explain why? Is there a technical reason/limitation, or is it more about other considerations?
I'm looking for information here rather than speculation, thanks.
@hugh@ausglam.space investigation into the use of C2S for cross-instance posting is one of our goals for 2025 with support from @nlnetlabs@fosstodon.org
But yes, there's most likely a reason why it hasn't been adopted widely...
-
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.
Any fediverse devs able to explain why? Is there a technical reason/limitation, or is it more about other considerations?
I'm looking for information here rather than speculation, thanks.
@hugh In addition to the concerns expressed here, I argue in my book that Mastodon's status as the single largest ActivityPub implementer back in 2017 is a factor -- after all, Mastodon had an API at that point. People making clients chose to make them compatible with Mastodon's API instead of redoing everything for the then-new C2S spec.
-
@julian @hugh We will forward your credits to @nlnet, which supports #opensourcesoftware. Although the name is similar, we are a different foundation that develops open source software.
-
@julian @hugh We will forward your credits to @nlnet, which supports #opensourcesoftware. Although the name is similar, we are a different foundation that develops open source software.
@nlnetlabs@fosstodon.org oh! Oops
unfortunate name collision.
