I also think that backfill will have a side effect of connecting the threadiverse and the rest of the fediverse. Exposing context collections will mean consumers will be able to see both *verses. Once Mastodon starts consuming them I predict you will start seeing much more engagement from the microblogs. The same would apply if Piefed or Lemmy begin consuming them as well. That is an angle I had not even considered until now!

You're right! NodeBB serves an outbox but doesn't put anything in it. Happy to work towards rectifying it... It just didn't seem to break anything and you're honestly one of the first who even noticed

Hey evan@activitypub.space, I am all-in on more, simpler FEPs over monolithic impenetrable FEPs. I take it that points 1 and 2 are due to concerns raised by thisismissem@hachyderm.io about how OAuth2 properties are already advertised in a standardized manner (I believe per OIDC or similar?) — no objections there. On the topic of scopes, I know benpate@mastodon.social's 3b86 (Activity Intents) had some ideas on defining intents that have some parallels to scopes. I don't agree with hardcoding them all into the FEP itself, but I'm interested in exploring how we structure scopes so that they're more straightforward as not quite as fine-grained — a single scope for every ActivityStreams activity type might be a bit of overkill.

That's a really good question, I am not actually aware of any list of software implementing the ActivityPub API. silverpill@mitra.social and steve@social.technoetic.com may have some leads.