The protocol is reasonably private. Trying to find exact sources of a piece of traffic is about as hard as it can be. Reading the contents of the traffic is also at a very high bar.
The downside is, it still needs visible nodes to connect to, and the VAST majority of us only actually have access to TCP routed networks for that purpose. The only way you’re talking to that reticulum node in Norway from California is because BGP is delivering your crypto stream for you.
If you have a small neighborhood and you’re all like-minded, you could use reticulum over HaLow or LoRa network adapters to create a private, IP-less mesh and it could go as far as you can find more people willing to run the hardware. HaLow has enough bandwidth to stream video, LoRa is mostly only good for text. Of course, If someone is doing something like video, it won’t take much to saturate everyone’s connection. It’s not like someone could run a Plex server and everyone could be watching it in the neighborhood at the same time; that 30MBPS can only handle a couple of decent-quality streams.
The big problem with TCP IP is that it requires being assigned IP addresses and the border gateway protocol and other such infrastructure, which is not usable as an individual.
In Reticulum, you self-assign a destination address using your public and private keys and then announce that that service is available to the rest of the network through whatever connection you happen to have to the rest of the network.
I think once the user experience gets simplified down, Reticulum will be an amazing piece of technology. But right now, it’s just not very user-friendly with the user experience.
I can use it, and I bet you can use it, but I don’t know if my mom would be able to use it right now, as is.
ELI5, why bypass TCP? I’m looking this up, but an answer might help me and others understand this better. :D
The protocol is reasonably private. Trying to find exact sources of a piece of traffic is about as hard as it can be. Reading the contents of the traffic is also at a very high bar.
The downside is, it still needs visible nodes to connect to, and the VAST majority of us only actually have access to TCP routed networks for that purpose. The only way you’re talking to that reticulum node in Norway from California is because BGP is delivering your crypto stream for you.
If you have a small neighborhood and you’re all like-minded, you could use reticulum over HaLow or LoRa network adapters to create a private, IP-less mesh and it could go as far as you can find more people willing to run the hardware. HaLow has enough bandwidth to stream video, LoRa is mostly only good for text. Of course, If someone is doing something like video, it won’t take much to saturate everyone’s connection. It’s not like someone could run a Plex server and everyone could be watching it in the neighborhood at the same time; that 30MBPS can only handle a couple of decent-quality streams.
The big problem with TCP IP is that it requires being assigned IP addresses and the border gateway protocol and other such infrastructure, which is not usable as an individual.
In Reticulum, you self-assign a destination address using your public and private keys and then announce that that service is available to the rest of the network through whatever connection you happen to have to the rest of the network.
Ok, that sounds brilliant! Thank you! :)
Yeah, it’s actually pretty badass.
I think once the user experience gets simplified down, Reticulum will be an amazing piece of technology. But right now, it’s just not very user-friendly with the user experience.
I can use it, and I bet you can use it, but I don’t know if my mom would be able to use it right now, as is.
I’m convinced. I’ll check it out. :)