jb55 on Nostr: All nostrdb nodes (damus ios, notedeck, damus.io) are caching nodes. They have the ...
All nostrdb nodes (damus ios, notedeck, damus.io) are caching nodes. They have the ability to collect notes and note stats incrementally via relay hints. There is no single “global” view of the network, it’s a much more accurate reflection of what nostr is and how it works under the hood. With negentropy, you will be able to sync between any two nostrdb nodes.
This is true for the rust nostr-sdk as well (it’s even further along dev wise) but it may not collect note stats (like/zap counts , etc) like nostrdb does.
This is a really cool vision of the future of nostr: massive redundancy for nostr notes spread across millions of devices. Every device is a potential cache.
They tried to build internet v2 this way (ICN/CCN). We are way ahead of them with a practical implementation of a store and forward, information centric network. The only thing missing is an overlay network for linking nodes, but people can continue innovating on that front once we move beyond websockets.
This is true for the rust nostr-sdk as well (it’s even further along dev wise) but it may not collect note stats (like/zap counts , etc) like nostrdb does.
This is a really cool vision of the future of nostr: massive redundancy for nostr notes spread across millions of devices. Every device is a potential cache.
They tried to build internet v2 this way (ICN/CCN). We are way ahead of them with a practical implementation of a store and forward, information centric network. The only thing missing is an overlay network for linking nodes, but people can continue innovating on that front once we move beyond websockets.