This is progress, believe me ๐Ÿคฃ Per @npub1m4ny...c2jl's suggestion, I've added filters that pare down the fetched kind 30040 events to just events that comply with the NKBIP-01 specification (Wikistr link below). From this I learned that we haven't yet uploaded any test events that comply with the new specification! I used the opportunity to improve the app's loading states, and to add a message in the case no matching events show up in the feed. Article display functionality is almost complete; next I'll be working on an article writer interface. I'd love to hear y'all's suggestions on the article writer UX! #alexandria #gitcitadel #development #otherstuff image https://wikistr.com/nkbip-01*dc4cd086cd7ce5b1832adf4fdd1211289880d2c7e295bcb0e684c01acee77c06

Replies (18)

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.
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.
That was the path that was causing so much confusion for @PABLOF7z . 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 @liminal ๐Ÿฆ  ?
โ†‘