81–89 of 89 posts
Unfortunately whenever I see the name, I am always reminded of part of the anatomy
I am not a native speaker, but I can't figure out what you are getting at. I have a hard time imagining you meant this: > The reticulum is the second chamber in the four-chamber alimentary canal of a ruminant mammal. I guess, on the internet nobody knows you're a ruminant mammal...
Earlier quoted context omitted.
> robust protection against abuse I would say it has a fairly reasonable number of protections with things like being able to prioritise certain interfaces and controlling the announce rate from a node and rate limiting the number of announces a destination makes. What in particular is abusable?
I can't see any effective protection against the classic tactic of flooding the network. There are some defences in place, but they seem easily overcome with minimal effort. If everything has to be whitelisted, the project would lose its core goal of being a free network.
Yeah it seems like you are in fact right...
[1] https://rns.recipes/forum/general/rns-150-testing-traffic-pr...
Earlier quoted context omitted.
I can't see any effective protection against the classic tactic of flooding the network. There are some defences in place, but they seem easily overcome with minimal effort. If everything has to be whitelisted, the project would lose its core goal of being a free network.
There's a thread by the author of Reticulum [1] on recent flooding attempts of weird clients connecting, spamming path requests and leaving, and attempting to mitigate their impact on the nodes. Yeah it seems like you are in fact right... [1] https://rns.recipes/forum/general/rns-150-testing-traffic-pr...
Earlier quoted context omitted.
I am not a native speaker, but I can't figure out what you are getting at. I have a hard time imagining you meant this: > The reticulum is the second chamber in the four-chamber alimentary canal of a ruminant mammal. I guess, on the internet nobody knows you're a ruminant mammal...
Or maybe "rectum".
Earlier quoted context omitted.
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?
The full protocol spec is there, I built mine from this without even touching the reference implementation.
Earlier quoted context omitted.
That should be rewritten in Go instead of the dead-slow Python release under 32 bit machines.
There's an RNS implementation in Go at https://github.com/Quad4-Software/Reticulum-Go but
Earlier quoted context omitted.
That should be rewritten in Go instead of the dead-slow Python release under 32 bit machines.
do it
Porting Nomadnet is not easy task at all even with these nice TUI libraries for Go...