Nostr Web Client

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.

hasky 1y ago

Complicated stuff eh , to transform from traditional fetching data collection based on IP address into fetching data by data identifier without IP address . Is data centric address working as an IP address for the data ?

Reply to this note

Please Login to reply.

Discussion

jb55 1y ago

you can imagine sending out a REQ into some gossip overlay network, if there is some node willing to service that request it could initiate a negentropy sync with you.

The ideal scenario is:

1. send to immediate subnet to see if there are any other devices on my network who can service it

2. send it into some wider local area network

3. reach out to gossip on the internet

4. reach out to oribtal relays to see there is anything cached off planet..

5. reach out to the mars relay to se... ok getting silly but still

Maybe ICN can even help is here somehow if that ever gets implemented.

One thing that comes to mind is having TTL on the packet to limit the reach of each tier of request.

Let's say you send out N REQ packets, each with different TTL. Then at the router where the packet is about to expire, the router can see if there are any nearby nostr nodes to service the request.

All this would require is new kind of IP protocol outside of the regular ones (TCP, UDP, etc) so maybe this is a bit far off for now 😂

hasky 1y ago

Hmm like “In Gossip network Caching “ man can cached any node on that gossip network something like that , can fetched data faster and faster reload origin … no?

Forget mars .. you silly

jb55 1y ago

yes it would mean that your node will get synced as quickly as possible with nodes closest to you.

if you get data quicker from local nodes, the negentryopy sync at furhter and further layers would return less and less data, assuming closer nodes already have the data

Cameri🐦‍🔥 1y ago

May sound silly after 4 but I very much like that idea!

jb55 1y ago

I realize this is basically multicast but you can't multicast to the wider internet.

I'm going to at least try with the local network (eventually) and then look into overlay networks for the wider internet

jb55 1y ago

now that I think about it, any nostr node could join a nostr multicast group via IGMP. Then anytime you post, it could be sent to alls other nostr nodes on your local network. you wouldn't need internet relays for corporate networks. your nostr apps could communicate on your local network without internet.

would be a cool tech demo.

Cameri🐦‍🔥 1y ago

This would be cool to demo at a Nostr unconference 😁

hasky 1y ago

Nostr conference ? Where when ?