Thread

Zero-JS Hypermedia Browser

Relays: 5
Replies: 1
Generated: 18:51:05
the problem is that the event type has a filter that the client does and not the relays, because you have ["type", "magazine"], but you can have an event that is only for magazine and that follows for that specific one, so it'ok. It is probably already possible to do what I say in Coracle, this is an example https://njump.me/naddr1qvzqqqrujgpzqkfzjh8jkzd8l9247sadku6vhm52snhgjtknlyeku6sfkeqn5rdeqy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qgkwaehxw309ahx7um5wgkhyetvv9ujuctswqhszyrhwden5te0dehhxarj9ekk7mf0qythwumn8ghj7mn0wd68ytnnw3skkete9ehx2ap0qqfrqvfc8ymnyv3jxqcnqvphxcenjvehzzdp38
2025-06-18 10:23:14 from 1 relay(s) ↑ Parent 1 replies ↓
Login to reply

Replies (1)

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.
2025-06-18 12:09:05 from 1 relay(s) ↑ Parent 1 replies ↓ Reply