AP Implementation Tracking

[RangerMauve]

This issue is for tracking the status of which other ActivityPub implementations we are able to interoperate with.

• Mastodon: Able to follow, send updates to
• ???

[fauno]

should i bring #11 here?

[fauno]

• ktistec: works
• pleroma: rejects the social inbox accepting the follow request, so you can't follow sites Pleroma doesn't support Social Inbox #11
• misskey: tester reported it wasn't working, haven't tested locally yet
• mastodon+glitch with authorized fetch on: waiting for tester to confirm it works after Sometimes remote instances require all requests to be signed #16
• mastodon: works
• pixelfed: haven't tested yet
• gotosocial: haven't tested yet

[RangerMauve]

One thing we were thinking is to keep state inside the inbox to know what was sent out and then on a follow from a new domain to send all known (or last N) activities over.

Unsure where it fits in the timeline yet, but this could help with instances that don't display posts.

We could also fetch the posts from the outbox and send those.

[fauno]

We could also fetch the posts from the outbox and send those.

This should be ok, we're saving the Create/Update/Delete activities as JSON-LD too, so you can just fetch and resend them.

[RangerMauve]

Pixelfed is having trouble. It's parsing the webfinger stuff but stopping at the about.json. Not clear what's wrong but we can read through the code to see.