Welcome to the team @aed900
Hope you enjoy your time at Maidsafe and may your contributions be great.
17 Likes
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?
2 Likes
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.
5 Likes
I see a use case for nodes, lets say you have 4 RPies with 1 node each so you have redundancy
4 Likes
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.
24 Likes
Thank you for the heavy work team MaidSafe! I add the translations in the first post 
Privacy. Security. Freedom
10 Likes