The codeberg issue is kind of still an ugly scratch pad rn. The thing awaits a follow-up where stuff is more organized and easier to drill down into. Proper docs eventually.
A first step may be to name the discrete and granular building blocks that one should focus on when starting out on an #ActivityPub client-to-server adventure quest. Give them consistent names. And then to map all the various projects to that as a MDN-like who-supports-what table.
@smallcirclesjust small circles 🕊 GoActivityPub servers support following things for Client to Server:
* Accessing objects and collections
* Filtering the collections through query parameters (eg. ?type=Create)
* Support for OAuth2 actor endpoints information and authorization
* Support for .well-known information (webfinger and now, OAuth2 client registration)
* ACLs for accessing them based on recipients list - this includes collection filtering of individual items
* ACL principal extraction from OAuth2 Bearer token (or from HTTP-Signature)
* Outbox Activity validation & processing (which I think is the main one :D)
If you have a fediverse account, you can quote this note from your own instance. Search https://metalhead.club/users/mariusor/statuses/115724822179841754 on your instance and quote it. (Note that quoting is not supported in Mastodon.)
@