> 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.
I 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.
With the Artificial Inanity systems and the Rampant Orphan Botnet Ecologies (ROBE) beginning to spew tremendous amounts of crap (a technical term) onto the Ret, things are getting tricky for us ITA.
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 but it does mean other implementations are kinda in a state where there isn't anything to actually verify they work.
There's also a issue with quite a few vibe coded implementations that don't actually properly work filling the space.
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.
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 very 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.
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.
personally i find it a beautiful match
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.
With the Artificial Inanity systems and the Rampant Orphan Botnet Ecologies (ROBE) beginning to spew tremendous amounts of crap (a technical term) onto the Ret, things are getting tricky for us ITA.
I suppose it means it's easier to develop the protocol but it does mean other implementations are kinda in a state where there isn't anything to actually verify they work.
There's also a issue with quite a few vibe coded implementations that don't actually properly work filling the space.
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.
Is that even the right question?
I only read the intro message but the framing I arrived/guessed at was:
"open, distributed alternative to tailscale"
So I think my first usecase would be to use this instead of tailscale to connect to my Pi?