One easy solution would be a publication pubkey would repost specific events from other people. In fact that reminds me I should support that on narr and noflux, should be easy. But I've seen that question come up many times and in my mind the ideal solution that composes better is specific publication relays. A publication would have its own custom relay (well, just its website would act as a relay too underneath, like fiatjaf.com does) and everything you could found inside that relay would be part of that publication feed. The events could have a NIP-70 "-" tag to tell all other relays to not rehost them so articles written by someone for a specific publication wouldn't be found in that person's normal feed (or they could choose otherwise, of course).

Replies (1)

Hmm. I always thought the basic idea of Nostr is that events are not tied to domain names or URLs or anything of the sort. Off the top of my head, I see 3 issues with this special-relay approach: 1. It diminishes censorship resistance 2. Seeing publications tagged (and linked) in articles before having subscribed to a special relay is good for discovery. I would definitely want people to be able to subscribe to all my articles by just subscribing to the pubkey itself. 3. It adds a burden on publishers to run special infrastructure