nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 Have you thought about NIP-23 feeds for publications instead of pubkeys?
I.e. one could subscribe to a feed of a specific blog that multiple authors write using their own pubkeys. Most blogs in my RSS reader work like this, and I think it's crucial for NIP-23 to be as useful as it can be. The cool thing about Nostr feeds vs normal RSS feeds is that the content would be properly attributed to each author and can be gathered and rendered outside of a centralized blog/feed as well.
I was thinking about creating a new kind for announcing a "publication" (i.e. blog, magazine, etc.), which holds metadata similar to a kind 0 profile (display name, avatar/icon, description, ...). The pubkey "founding" the "publication" would then add tags for authorized author pubkeys, so clients could verify that when a kind 30024 article is tagged with one or more publication IDs, it's not spam or impersonation.
One problem with this (and with a system without time in general) is that when a founder would remove authors later on, it would appear as if they never wrote for a certain publication. But I'm not sure it's actually a problem in practice.
What do you think? Maybe I'm thinking about this all wrong? Or maybe someone has solved this already?
We have a pull request for curated publications. They are composable and editable lists of content, and the metadata for each publication/event is contained within the event. Not exactly what you're speaking of, but seems related.
https://github.com/nostr-protocol/nips/blob/c96a0b1f5aa887f7a914a50881bbfa38b483f7c5/62.md
You can see the early version of our client here:
Starting off with one publication - an event composed out of a list of sections:
Take the full article, using the root kind 30040 event as an entry to a root event titled "Publications from our authors", which handles the aggregation and distribution of articles.
On the other hand, a person that wants to look back at what they've read can slot in other user publications, or sections like a collage into their own root kind 30040 titled "notes" that they can look back to. Which takes care of the collaborative use cases.
