Reticulum is an elegant engineers approach to networking. It’s a complete replacement of the network stack, it’s entirely encrypted, and can communicate and can correctly organize global-scale mesh-networks over any connection >5b/s without the need for distributed hash tables, or any resource usage besides bandwidth. This makes it far lighter than GNUnet, and friendly to low-power, low bandwidth, embedded networks and devices.
This makes it viable as a global network, as it is super cheap to interact with. And it can run on any device, including your smartphone natively.
Bandwidth is a physical resource of the natural world. Reticulum is based on the principle of creating systems that (as far as is possible for a computer program) understand the physical limits of real-world resources, and manages them responsibly and intelligently, with well-thought out algorithms.
When that is ultimately not possible any more, human beings have to step in and expand capacity or make other thoughtful decisions on how to manage the available resources. I believe this is the most efficient, holistic and human-friendly approach to creating technologies that actually help us and better our lives.
- someone from forums
Interesting project, thank you for introducing. :)
I haven’t tested anything, but only checked their specs (sadly I didn’t find out how they manage without a distributed hashtable).
Sounds like mesh networks like I2P and (to a lesser degree, since its role is proxying out to the Internet) like TOR.
Sounds like TOR and I2P, but people’s convenience (easily resolving a name to an address) has created centralized resources on these nets, and will likely create similar resources on any network. An important matter is whether the central name resolver can retroactively revoke a name (in I2P for example, a name that has been already distributed is irrevocable, but you can refuse to distribute it to new nodes).
The same as aforementioned mix networks, but neither of them claims operability at 5 bits per second. Generally, a megabit connection is advised to meaninfully run a mix network, because you’re not expected to freeload, but help mix traffic for others (this is how the anonymity arises).
True for TOR and I2P. The address is a public key. You can move the machine with the private key anywhere, it will build a tunnel to accept incoming traffic at some other node.
As it should.
In mix networks, the keys used as endpoint addresses are not ephemeral, but permanent. I’m not sure if I should take this statement at face value. If Alice wants to speak to Bob tomorrow, some identifier of Bob must not be ephemeral.
Same for mix networks.
Same.
Same.
This may have some similarities on the surface, however this is a mesh radio network designed for an extreme challenge of navigating a un-known-sized network, with unknown structure, with extreme computing and bandwith limitations.
Yep, indeed, I’m already discovering differences too. :) A good document for techies to read seems to be here.
https://reticulum.network/manual/understanding.html
I also think I see a problem on the horizon: announce traffic volume. According to this description, it seems that Reticulum tries to forward all announces to every transport node (router). In a small network, that’s OK. In a big network, this can become a challenge (disclaimer: I’ve participated in building I2P, but ages ago, but I still remember some stuff well enough to predict where a problem might pop up). Maintenance of the routing table / network database / <other term for a similar thing> is among the biggest challenges when things get intercontinental.
Man your badass lol. Very cool, thanks for the resource.
GNUnet is more of an attempt to replace the entire internet, with replacements for every feature of the modern web, while Reticulum is a far more solarpunk and permacomputing vision. It’s a very practical, implementation-first approach.
It’s primarily a cheap, easy, practical tool for a local community, which can be linked with other communities around the world using any means practical.