Hacker News Reader

> 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?

View on HN

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...

So it has already begun. It's kind of sad/impressive how every single network or group project gets flooded with abuse as soon as it gains any tiny bit of attention.

Reply on news.ycombinator.com