About time that a fella called Angus was brought on board, now you know that we’re getting close to the action best of luck @aed900 getting up to speed and jumping in, fair play to you.
Data stored “in memory” here is not referring to something fancy, it just means in RAM on a client’s machine in the usual sense?
How does whether data is stored in memory or on disk relate to NAT traversal? It seems to be implied that data must be stored on disk for NAT traversal to become a possibility, and I don’t see the link. Maybe I’m missing something obvious.
Thanks for the update, its an exciting time.
Welcome @aed900, you picked a fine time to join us
I hope your stay is long, productive and satisfying.
The agogometer is emitting a steady thrum and I have been forced to lubricate it with Bruichladdich twice already this afternoon. It has been taken from the shelf and placed carefully on the floor. Minimise the PE in case of sudden excess KE and tears.
Edit: actually, I think it was written fine, I was adding a link between the two things. Upon a rereading here, it is totally possible to not make the jump I did. Anyway, all clear now.
Something I wonder: You mentioned a while ago that network is likely not stable with under 2000 nodes. Yet you seem to use only 24 in your testing. I’m sure it makes sense, but how?
why do we need 2000 nodes? I am imagining a app that would run ~20 nodes that would be your way of organizing and saving your data locally with de-duplication and reliably saved via redundancy!
but if the nodes are light maybe ~100 nodes? what is the target of reliable local network?
I would think that, for storing on the local drive, all chunks could be saved in one place and your browser or local host would just extract your chunks from there. I don’t see the need for running other node’s locally. The self encryption would still be pretty robust.
Kademlia has an interesting property most folks ignore, but until circa 2000 nodes, the performance is not great. Not broken but flakey. What Engineers can tend to do is try to “fix” that, and that is a slippery slope.
Like an ant colony that until it’s about 1500 ants is also flakey, kademlia needs
A decent size network (say 2000 nodes)
Nodes to be communicating across the network (i.e. our DBC store means nodes need to check the parent is Spent. That performs the cross-network lookups to keep routing tables fresh)
This is why doing a bit of Safe is not great. That cross-network chatter is important. The same goes for network size.
The network size is why I am keen on quic and not TCP. quic is much more resource friendly and running several hundred nodes per computer is easy.