Nostr Web Client

30040 and 30041 events aren't expected to have matching titles. 30040 events act as an index of multiple 30041 events, so the name of the index/collection will likely differ from the names of the individual 30041 fragments of which it is composed.

il_lost_ 1y ago

are the "e" tag events in 30040 events 30041? they will have to match somehow I think.

Reply to this note

Please Login to reply.

Discussion

MichaelJ 1y ago

Yes the e tags in 30040 events reference 30041. The reference format is kind+pubkey+d-tag, IIRC. So the e tag references should include a d tag that shows up in some 30041 event.

Laeserin 1y ago

e tags in 30040 can reference any event kind, includind 01 or other 30040. We just defined 30041 as the default kind.

MichaelJ 1y ago

Ope I hadn't thought about that yet! We'll need to add some extra rules for rendering non-30041 events in our viewer.

Laeserin 1y ago

That was the path that was causing so much confusion for nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft . He didn't realize that 30040s can contain any event.

We should probably stick to human-written content, for the first run-through. Kind 01, long-form, wikis, 30041s probably enough. What do you think nostr:npub1m3xdppkd0njmrqe2ma8a6ys39zvgp5k8u22mev8xsnqp4nh80srqhqa5sf ?

liminal 🦠 1y ago

I see other directions, but for now let's stick to the article use cases to render in the Alexandria client.

Laeserin 1y ago

So, plain-text, markdown, asciidoc.

Laeserin 1y ago

Yes, the e tags can include 30041 events or any other event.