When #nostrdb implements #negentropy, queries to #strfry relays will only return events we don’t already have
Discussion
I’m following just in case I understand
✊
This is exciting.
What is #nostrdb? A custom DB that runs on relay servers? Or some kind of meta “distributed” DB?
Its a local, embeddable nostr database in the same design as strfry.
Ahh that makes sense. So it runs client side, and optimized to communicate with the relays
Optimized for ingesting events from the outside world in the most efficient way possible, so that notes can queried locally and mapped to data types in your app with no serialization overhead. Basically does all the heavy lifting so your UI can take care of Ui things
In theory you could use this for both clients and relays?
Yassssss! 🐳🐳🐳🐳🐳
I know you're working on this but I also know somehow @vitor will release it first in amethyst
Probably
Doesn't that bypass/obsoletes the NIP-01 protocol entirely?
Ok, this is some galaxy brain stuff 🤔
https://github.com/hoytech/strfry/blob/next/docs/negentropy.md
I am not doing anything crazy, just the usual SQL db. I might end up using your implementation as well. We will see.
Gotta finish Group Chats first, though :(
Amazing. Love all of this. 🫂🫂🫂
The history of Nostr will be defined by before and after local databases.
We will need bigger storage options on phones.
👀
Are we finally doing bloom filters? Where can I learn more?