I’m not sure I follow. As far as I can tell, you’re saying that there are multiple ways available already to achieve a curated list on nostr. I’m aware. I just like this one for all the possibilities I can see for this and I’m trying to implement them to see if it will work out as I imagined. The root index event that describes the magazine is replaceable and can be updated whenever and the npub that created the magazine can also publish an RSS-like nostr feed.

An editor or publisher would create a magazine npub first, then the events, instead of publishing with their own npub. And the root event can be used as a reference to build out the whole magazine either with my client or a custom web interface in any style.

Reply to this note

Please Login to reply.

Discussion

if you create a new npub it's the communi-keys approach, (I'm not saying this to follow this or that), but as difficult as it is https://nostrhub.io/naddr1qvzqqqrcvypzp22rfmsktmgpk2rtan7zwu00zuzax5maq5dnsu5g3xxvqr2u3pd7qqxxxmmdd46ku6fdddjhjucmuj5a3

Nusa has extensive experience with index events and isn't intimidated by the hierarchical structure.

Communi-keys have their own thing going on. It all overlaps on some level, but my focus are publications. I’m aiming at a special purpose interface that is clear and useful, specialized for this one thing - creating magazine style publications.