Took me a full week to nail down some of the bugs, but Negentropy on native Android/Kotlin is now done and fully compatible with the C and JavaScript implementations.
Next adding it to Amethyst... https://github.com/hoytech/negentropy/pull/15
Took me a full week to nail down some of the bugs, but Negentropy on native Android/Kotlin is now done and fully compatible with the C and JavaScript implementations.
Next adding it to Amethyst... https://github.com/hoytech/negentropy/pull/15
Why don’t we have a nip for negentropy? It feels like it could be an important part of the nostr ecosystem but it’s kind of invisible.
Oh damn. Awesome. I need to keep up with the nip PRs.
I do hope it becomes part of nip-01 (mandatory for all implementations).
I don't think Nostr survives the massive amounts of data without very fast SYNC protocols.
Looks really promising.
Negentropy should NEVER be mandatory. There is a whole usecase for relays as private communities where users do not want their notes to go anywhere but that specific relay and this NIP would just kill that use case. Its also very complex and makes building a simple relay more difficult. Optional NIP is the best option IMO.
Negentropy is to sync between clients and relays, not between relays. Even single relay communities need it.
I don't know what this is, but I like it. Progress!! 😁
will amethyst sync everything from all relays? does it store all events in a relay running on my phone?
Syncing directly between clients where they have a local relay gives nostr the offline peer to peer functionality that exists in secure Scuttlebutt. That’s a big feature when it comes to true censorship resistance.