nostr:npub14q6a856gru3kjnrw3m3st0u5vxlls9a2redvsdd9u3gke8d4ucxs0a4za2 I think the problem exists on multiple levels. One is the "all I need is one document and the code can minimally interoperate". Another is the equivalent of "what is REST"? -- ActivityPub etc has multiple abstraction levels, and variation points and potential architectural divergence on all of them.