few understand we have one of the best protocols for efficiently syncing datasets between nostr nodes. nostr officially grows up when NIP-77 lands.

https://github.com/nostr-protocol/nips/pull/1494

https://logperiodic.com/rbsr.html

Reply to this note

Please Login to reply.

Discussion

What is a nostr node?

a relay or a client with a database

does that mean that some relays don't store any data?

the damus notification relay doesn't store any data

so by my definition of a "nostr node" the damus notification relay technically isn't a nostr node, since there's no way to sync notes between it and yours. maybe nostr node = node that understands nip77 could be one definition.

this could enable nostr to be more like a p2p network in the future with the right overlay network, with nodes syncing with each other via negentropy. me and martti and a few others have been thinking about this.

Hmm hmm . Indubitably

Hopefully as nip01, not as nip77.

maybe once nip77 adoption is widespread...

Chicken and egg.

What will NIP-77 make possible? No duplicates on the timeline?

it will save trillions of bytes of bandwidth. it is like rsync for nostr. the idea of fetching notes you already have will be an ancient concept.

this is even more important when you're pulling from multiple relays. right now you download tons of extra stuff for no reason. this fixes that.

Whats preventing it from being merged already?

think they are just working on minor details like error messages atm

Nice

my man

Plz update the Damus relay so we can sync with strfry 1.0? 🥺

Heck yeah, I put off messing with negentropy for a long time, but when I finally integrated it I was floored at how efficient it was.