@deadsuperheroSean Tilley One thing I always thought would be helpful, is some documentation around the actual implementations. People talk about ActivityPub like it's one thing. But every implementation is different, and has its own choices about what it does, and what its limitations are. For example: Mastodon will accept X activities but not Y activities. If you send a follow request to a PeerTube server it does Z. If you send Owncast an inbound Create Note it'll ignore it.

Having an overview of what the real lay of the land of the Fediverse is could add a layer of reality to the fairytale land we talk about when we say "everything will talk to each other and everything supports everything", when that can't be further from the truth. Every project has specifics that were made to accomplish its goals but those are dusted under the rug until you're an actual ActivityPub application developer and you learn them the hard way when things don't work.