I think this is always an issue for me to explain, but for me security is two fold
Logical -> encryption etc.
It’s the last part that is more invisible, but if data can be found it can be corrupted/blocked etc. So it’s important, also hiding who uploads in our case is important (Freenet does some of this). So a bit of bittorrent for physical security is also good, but it’s the mix of randomly where stuff goes in bittorrent, so this is needed in a dht as well. If we can identify locations then we can bring stuff down, or be forced to.
Another HUGE area to consider with other projects is all the work we are doing in crust (still some to do) and this is NAT traversal, a complete PITA for p2p projects but required for real p2p, otherwise you need servers and manual port forwarding and possibly even static addresses. Worse many of these will also use a standard protocol and port, leading to more issues with banning/censorship.
I like them all and want them all to bring something to the table and I hope ipfs/bittorrent/bitcoin/ethereum for instance can use crust at least to make their nodes run from behind NAT/ routers as it will help them a huge amount. So this is not a we tick this box and they don’t it’s there is more to consider and if we tick a box we do so in a way that others can use that lib and also tick the box. Hope it comes across like that
I should state crust currently uses a load of threads and will internally switch very soon to a more OS level scheduler via the MIO library. It’s a task and a half but will make it super efficient.