Râu Cao ⚡ (npub1rau…dees)quoting nevent1q…ez6lOne easy solution would be https://nips.nostr.com/18#generic-reposts: 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).
Turns out relays are a great abstraction, infinitely flexible and easy to use and reason about. Relay feeds and other types of custom relay usage could be the thing that differentiates Nostr from all other Twitter clones and are vastly underexplored today.
One example that does one form of "curation" today is
quoting nevent1q…afg2Here's an example of a relay that uses artificial artificial intelligence (i.e. human intelligence) to build a curated feed of potentially interesting notes: https://relays.land/spatianostra
You can probably access its feed by clicking on wss://relays.land/spatianostra if your client supports relay feeds, or use Jumble: https://jumble.social/?r=relays.land/spatianostra
Try also wss://algo.utxo.one, but we need more!