Nostr Web Client

The other analogy that comes to mind is a DB index. Nostr events are like noSQL DB entries (sure, they can be stored in a structured DB, but that's an implementation detail). The kind 30045 directory is an index for other Nostr events.

A DB implementation could take advantage of such events to optimize retrieval of any event kind that is part of a structure.

nostr:npub12262qa4uhw7u8gdwlgmntqtv7aye8vdcmvszkqwgs0zchel6mz7s6cgrkj are you picking up what I'm putting down?

semisol 6mo ago

That is exactly what I meant when I said I’m going to put a stack machine in your relay.

Not exactly, but what you can do is ask the relay “Hey, get this event, then find this entry, then retrieve that and so on” and it can do that and provide you the entire chain as proof.

NFDB will also support 4 retrieval modes:

- Metadata only (kind/created_at/pubkey/id)

- Metadata + content

- Metadata + tags

- Full event

The 1st one is extremely fast and does not incur any IA reads. The 3rd one could be made to not need IA

Reply to this note

Please Login to reply.

Discussion

Silberengel 6mo ago

Ah, I missed that point. I was thinking about how to setup the historization, when you posted it, so that's what my brain jumped to.

MichaelJ 6mo ago

I'll be curious to see the API and how much it extends the core Nostr API.