Finally got around to adding relay indexes to nostrdb today. This will enable relay feeds and better relay based filtering.
I may need to add a relays field as a filter extension. Like nip50 but for relays the note has been seen on?
Finally got around to adding relay indexes to nostrdb today. This will enable relay feeds and better relay based filtering.
I may need to add a relays field as a filter extension. Like nip50 but for relays the note has been seen on?
Would be great, and way ahead of many clients, if the notes are cached locally and then synced with negentropy or whatever so they are not redownloaded each time client starts up. Thoughts? 🤔
Yeah notedeck works this way. Me and nostr:npub13v47pg9dxjq96an8jfev9znhm0k7ntwtlh9y335paj9kyjsjpznqzzl3l8 are working on making ios work this way as well.
notes are cached locally on iOS, we just don't fetch from there on startup yet. The nostrdb version there is old and doesn't have query capabilities.
Ok, that makes sense. 🫡
T
R
E
X
🦖
??
Just a cool acronym for when relay feeds inevitably become nostr communities.
Stands for Topical Relay Explorers.
Lots of bullish talk on cornychat wya nostr:npub12r0yjt8723ey2r035qtklhmdj90f0j6an7xnan8005jl7z5gw80qat9qrx
yes i think you'll want to know where the note was seen, on a per note basis.. so you can take actions.
niice.
most clients have this i think? i guess the unique thing with the nostrdb implementation is that you can make it a part of your nostr query
For everything you add you have to take two things away. But you can phonetically say, aweigh.
#few