Joined 2 years ago
https://github.com/markqvist/Reticulum/wiki/Frequently-Asked...
It covers questions like:
- How is Reticulum different from Insert System Here?
- What's the legality of the system?
- What's to stop someone from flooding the network?
And many others.
However when the network (and each node) is receiving enough announces to saturate that 2% chunk of most smaller links, those interfaces prioritize announces with less hops, and there is a queue, meaning it takes that interface longer to transport announces coming from further away. This makes it much more likely that nodes will form routes over a faster but longer path.
Of course it has issues running the in the background, but there are possible solutions to this, like having Reticulum run entirely on an RNode, and it is being worked on somewhat actively.
Scuttlebutt: Reticulum is a network stack for routing data in real time, not a decentralized social network.
Nostr: See Scuttlebutt
IPFS: Reticulum transfers data, it does not store it (though some protocols that work over Reticulum like LXMF optionally have functionality that allows for temporary message storage)
Yggdrasil is the closest analog to Reticulum you mentioned, but unfortunately from a cursory search I could not find any details about how it works. I can see that it currently works only over IPv6 (with IPv4 tunnels of some kind), unlike Reticulum which works over anything.
I suggest at least reading http://reticulum.network/manual/understanding.html to see how Reticulum works, if you are interested.
I think you’re looking for the C++ implementation of Reticulum made specifically for microcontrollers instead: https://github.com/attermann/microReticulum_Firmware https://github.com/attermann/microReticulum
Read this page to learn more about it: https://reticulum.network/manual/understanding.html
TL;DR it only flood routes packets that tell the network the location of a node; each node stores the “next hop” to get to every other node on the network. Everything else is routed along a single path determined by those “next hops.”
This means that announces are much more likely to be transferred over the faster medium first, resulting in paths that are on average the most reasonable balance between speed and distance.
If that doesn’t make sense at first, I get it. I find trying to visualize how it works really helps. Reticulum is conceptually so different from anything else out there that it takes a while to understand.
See http://reticulum.network/manual/understanding.html#the-annou... for more details.
