Unfortunately whenever I see the name, I am always reminded of part of the anatomy
I think it was named so for a reason:
https://en.wikipedia.org/wiki/Endoplasmic_reticulum
personally i find it a beautiful match
Reticulum – Decentralized Mesh Network
21–30 of 89 posts
Re: Reticulum – Decentralized Mesh Network
#22https://ratspeak.org/ seems like a modern fork of Reticulum built in Rust and with a fairly active community
[flagged]
Re: Reticulum – Decentralized Mesh Network
#23The resistance is out there somewhere?
People don't seem to get this was a genuine question. What is a network without people using it? Anyone here on reticulum? The internet may be ripe for disruption, as it has been domesticated for corporate use. It is no longer ours. Browsers have become an operating system unto themselves. Something much simpler would work also. Corporate bloat is continuing to pile up, while markdown evolves to do everything we want…
People do use it but it's definitely a small community. It has the NomadNet Page protocol which is basically small no client side script webpages (forms and links only) in a fairly bandwidth efficient form.
Re: Reticulum – Decentralized Mesh Network
#24No published specification, single Python implementation. Shame, as this solves a problem that badly needs to be solved well.
There is a published spec, I built a clean-room implementation from it. And mine makes at least two Python implementations. The protocol itself is solid, the spec just isn't marketed.
Re: Reticulum – Decentralized Mesh Network
#25No published specification, single Python implementation. Shame, as this solves a problem that badly needs to be solved well.
The author of Reticulum's take is that the implementation is the specification, so if another implementation works with the standard Python one and implements enough of it's features then it implements Reticulum.
I suppose it means it's easier to develop the protocol only having to update one Python codebase but it does mean other implementations are kinda in a state where there isn't anything to properly verify they work.
There's also a issue with quite a few vibe coded implementations that don't actually properly work filling the space.
Re: Reticulum – Decentralized Mesh Network
#26I had a lot of hope for reticulum, but it's a one man project with a near burned out maintainer, taking on an absolutely monstrous task. I'm now cautiously optimistic. This or something similar is likely the long term future of mesh networks, but in the short to medium term, meshcore is the way to go.
The protocol itself is more mature than the maintainer situation suggests. I built a complete independent implementation from the public spec in a few sessions. If one person can do that without touching the reference codebase, the foundation is solid. The risk is to Mark's implementation, not to Reticulum as a protocol.
Re: Reticulum – Decentralized Mesh Network
#27No published specification, single Python implementation. Shame, as this solves a problem that badly needs to be solved well.
There is a published spec, I built a clean-room implementation from it. And mine makes at least two Python implementations. The protocol itself is solid, the spec just isn't marketed.
Where is the spec?
Re: Reticulum – Decentralized Mesh Network
#28Re: Reticulum – Decentralized Mesh Network
#29Why are there not more developers? Is ratspeak where they all prefer to be?
Also reticulum and crypto seem like they go together. Non-http crypto transactions?
What about entirely-non-http blockchains?
A new bitcoin that is completely off the internet as we know it??
Re: Reticulum – Decentralized Mesh Network
#30> Reticulum does not use source addresses. No packets transmitted include information about the address, place, machine or person they originated from. Sure, but if it’s anything like MeshCore, a few observer nodes will be able to see which repeaters the message first entered the network from and from that know roughly where it was located.
Reticulum packets include a hop count of how many nodes it’s been through (to prevent packets looping indefinitely) and the destination address. Two way links use tables on each node to reverse the route back to the origin and don’t use origin addresses.
The worst part privacy wise could be the announce packets which include a hop count and the address for the origin so if you had enough interfaces you could roughly say where a node is on a network graph (geo locating that is an entire other problem)
Privacy also depends on what interfaces you communicate over, eg TCP reveals IP addresses to the nodes you directly connect to (combine with hop counts to see if a packet definitely originated from that node), LoRa gives an idea of how close it might be because of its range limits and the fact radio emissions can be located.