pull down to refresh

Uncentralizability
Reticulum assumes that every peer on the network is potentially hostile, and every link is potentially compromised. It is designed with no "privileged" nodes. While some nodes may act as Transport Instances - forwarding traffic for others - they do so blindly, and they only know about their immediate surroundings, and nothing more. They route based on cryptographic proofs, not on administrative privilege. They cannot see who is talking to whom, nor can they selectively manipulate traffic without breaking their own ability to route entirely.
49 sats \ 0 replies \ @Fenix 31 Mar

Reticulum is one of those niche internet ideas that's so good it makes me think, "How did I not know about this sooner?" The part that interests me most is LXMF using a mesh network, but since I still don't have my mesh nodes, I haven't tested it yet. It works well in the apps that use the network, and I had a node running Nomadnet.

Those messages printed on QR codes with a thermal printer have that garage-cyberpunk vibe, really cool.

The project's creator stepped away; I hope they keep the project going with the same passion.

reply

I was really into this, it is a good read.

But I stopped here

Currently, the usable performance envelope is approximately 150 bits per second to 1200 megabits per second, with physical mediums faster than that not being saturated. Performance beyond the current level is intended for future upgrades, but not highly prioritised until the wire format and API has been locked in.

https://reticulum.network/start.html

reply