Do we need indexing servers? A relay type (micro relay?) just to figure out where authors and events can be found?
Discussion
Bring it on!
Hey Vitor, rbr.bio already does it, check out https://rbr.bio/npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z . I wrote to you DM some time ago about it, but you didn't write back.
But rbr is just for contacts, right? We need a relay type that anyone can spin up and find any event in the ecosystem.
Been trying to find @Anil
I think we will. The trick in scaling nostr is going to be providing useful functionality like this without repeating a few mega relays that are basically clones of Twitter and Facebook now but using nostr.
I'd love a relay indexer.
I’ve been pondering this too.
How micro you thinking? Basically map event_id to relays that broadcast it (don’t event store the event), or map a pubkey to the latest kind 0/3/10023 events known? Both?
Because Nostr doesn’t have a HEAD concept, certainty around ‘newest’ meta events is hard to make foolproof.
I’ve added metadata_event_id, contact_event_id and relay_event_id to my API for the latest event id known for kinds 0, 3, 10002.
The two problem points I think an indexer should ideally address are:
1. How do I consistently get the latest event id
2. Where can I find that event body (which relay)
I think the problem space is mostly the meta events that can be replaced. And then secondly, in generate, where can I find an event id.
Is this what you were thinking?
I bookmark way too much. But, I might need it 👀 See -- there's the problem.