FediForum hot take
-
FediForum hot take:
@dmitri@social.coop: "the key to a successful ActivityPub C2S implementation is a headless AP server"
NodeBB can technically be run headless (although we have our own API)... one wonders...
-
pfefferle@mastodon.socialreplied to julian@community.nodebb.org last edited by
-
-
evan@cosocial.careplied to julian@community.nodebb.org last edited by
@julian @pfefferle There are a bunch of implementations! I think a headless server is a good idea, but we don't have a good Web-based general-purpose client for the ActivityPub API.
-
julian@community.nodebb.orgreplied to evan@cosocial.ca last edited by
@evan@cosocial.ca @pfefferle@mastodon.social that's true, I think Mitra might qualify? @silverpill@mitra.social
-
silverpill@mitra.socialreplied to julian@community.nodebb.org last edited by
@julian @pfefferle @evan @evan @pfefferle It's headless but honestly I don't see how that could help. Vendor-specific RESTful APIs won because they are easier to understand and easier to implement. In order to be competitive, standard C2S needs to provide something that can't be achieved with RESTful APIs.
I think the answer is FEP-ae97, which enables rich offline-first clients and data portability.
-
julian@community.nodebb.orgreplied to silverpill@mitra.social last edited by
@silverpill@mitra.social @pfefferle@mastodon.social @evan@cosocial.ca @dmitri@social.coop long story short, the session participants basically agreed that it was a bit of a chicken and egg problem.
Also looping in @thisismissem@hachyderm.io
-
thisismissem@hachyderm.ioreplied to julian@community.nodebb.org last edited by
@julian @silverpill @pfefferle @evan @dmitri
I was far more interested in the idea of delegating the publishing & distribution of activities to another server from existing AP software
-
trwnh@mastodon.socialreplied to thisismissem@hachyderm.io last edited by
@thisismissem @julian @silverpill @pfefferle @evan @dmitri
"delegating the publishing and distribution" is exactly what the AP C2S API does.
-
thisismissem@hachyderm.ioreplied to trwnh@mastodon.social last edited by
@trwnh @julian @silverpill @pfefferle @evan @dmitri
I mean like saying to Mastodon, Pixelfed or Peertube "hey, this is my AP actor over here, send C2S activities to it and it'll handle distribution"
-
trwnh@mastodon.socialreplied to thisismissem@hachyderm.io last edited by
@thisismissem @julian @silverpill @pfefferle @evan @dmitri right, i've oft said that mastodon/pixelfed/peertube/etc are in reality better fit as AP Clients rather than AP Servers (technically, they are monolithic implementations where the S2S bits are subsumed by the transformers/workers/controllers)
having mastodon et al implement AP C2S support against a generic AP server would help solve the chicken-and-egg problem as well as ameliorate a slew of others (portability, etc)
