Nostr Web Client

This is progress, believe me 🤣

Per nostr:npub1m4ny6hjqzepn4rxknuq94c2gpqzr29ufkkw7ttcxyak7v43n6vvsajc2jl'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

https://wikistr.com/nkbip-01*dc4cd086cd7ce5b1832adf4fdd1211289880d2c7e295bcb0e684c01acee77c06

https://geyser.fund/project/gitcitadel

Reply to this note

Please Login to reply.

Discussion

Laeserin 1y ago

We have now also learned that some consoles require a content tag, even if it's empty.

Laeserin 1y ago

Should we still demand no content tag, or also accept an empty one?

MichaelJ 1y ago

We can accept an empty one.

Deleted Account 1y ago

Write

il_lost_ 1y ago

I haven't found two titles that match.

ISBN tag maybe needs to follow the spec in NIP 73 for 30040.

MichaelJ 1y ago

I'll check out NIP-73 👀

Laeserin 1y ago

Ah, I see. ISBNs there have an "i" tag. Thanks, nostr:npub1ty3ftnetpxnlj42lgwkmwdxta69gfm5f9mfljvmwdgymvsf6pkuswhxq4p

https://github.com/nostr-protocol/nips/blob/master/73.md

MichaelJ 1y ago

What do you mean about matching titles? If you give some more context I can investigate.

il_lost_ 1y ago

I was looking for two events one 30040 and one 30041 with the same title.

MichaelJ 1y ago

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.

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.