points by DaSHacka 4 days ago | 0 comments
After the absolute embarrassment that was accidentally leaving intra-node communication completely unencrypted and unauthenticated[0], I am doubtful on the level of seriousness of the whole project.
What ever was wrong with just selfhosting your own git server, again? Or mirroring it to a handful of different providers in different countries.
[0] As previously covered on HN: https://news.ycombinator.com/item?id=49817524
[–] iamnothere 3 days ago
[–] armchairhacker 3 days ago
They still haven’t fixed it according to the FAQ, hasn’t it been long enough? https://radicle.dev/faq#:~:text=Private%20repositories%20sho...
Selfhosted git servers don’t automatically replicate without extra tooling and don’t provide collaboration and project tracking features. The goal is to replace something like Github with a distributed, automated, integrated setup. Not easy to accomplish.
Once it’s mature, this will create the ability to easily host project infrastructure across multiple nodes, owned by multiple people, where you can verify integrity as long as you accessed the repository in the past. If the hosting nodes are behind Tor, this will be a very secure setup. For repos that may face legal attacks, like emulators and tools like yt-dlp, this is huge.