How DoS protection is implemented?
I’m wondering, how Radicle can protect against malicious actors that can create a bunch of useless issues?
I’m wondering, how Radicle can protect against malicious actors that can create a bunch of useless issues?
To my knowledge as of writing this, one obvious option is
rad block $NID. But worth pointing out here is that the aforementioned command must be run on a seed the repo maintainers control and that block will only affect that node. Also if that user has legitimate contributions on other repos they’ll get removed too, since it’s a seed-wide block, not repo-wide.IMO while it’s great having this command I feel like it’s both not strong enough and too strong. It would be nice to have more fine-grained variants that act per repo, per specific issue or comment, and which would ideally propagate across the network in a manner that can also be abuse-resistant.