@mariusormarius
@smallcirclesπ«§ socialcoding..
@evanEvan Prodromou C2S has client-side and server-side aspects (different, but overlapping, behavioral requirements, etc.). Both sides consume *and* produce AP data (pull and push for S2S, currently only pull for C2S). Fetching AP data (URI dereferencing) is common to both C2S and S2S.
@steveSteve Bate
@mariusormarius
@smallcirclesπ«§ socialcoding..
@evanEvan Prodromou this is a huge thread, but off-cuff comment: C2S will need a "proxy" where you can fetch a remote object **with** identity/authentication
If you have a fediverse account, you can quote this note from your own instance. Search https://hachyderm.io/users/thisismissem/statuses/116103607107421101 on your instance and quote it. (Note that quoting is not supported in Mastodon.)