For collaboration stuff, I like the idea of creating shared access to a Pubkey managed by a nsecbunker. That way the owner can easily add or remove access
say I create a document about "Stalin" and I add ["p", "<nostr:npub1mygerccwqpzyh9pvp6pv44rskv40zutkfs38t0hqhkvnwlhagp6s3psn5p >", "editor" ]
this would mean that the most recent version of my version of Stalin is whatever comes back from the REQ { "#d": ["stalin"], authors: [
Discussion
yeah, but that has more overhead, this would be an in-protocol solution
the nsecbunker approach makes more sense imo for teams and stuff like that where the collaboration is more structured/formalized
More overhead for people writing the articles, much less overhead for people reading and much less complexity in-protocol.
The users main key would act as a nip46 ephemeral signer