HardenedBSD migrated its core Git repos (src, ports, pkg) to Radicle, a peer-to-peer code collaboration stack, with basic ports-tree integration already working.
Key Takeaways
Three repos are live: rad:z2HLHXgL1xevBNQsf8BmQW7MpJmtm (src), rad:z2XrdvALg77ycnuZRXgScb27yb3wM (ports), rad:z3QDZAW2FAfuLvihrhiyDC9fAD8G9 (pkg); secadm is next.
Large repos require tuning ~/.radicle/config.json – set node.limits.fetchPackReceive to at least 3GB or seeding will fail silently.
Seeding workflow: connect to the HardenedBSD seed VM, run rad seed --from <peer-id> <repo-id>, watch the .tmp directory for promotion, then rad clone.
A naive USE_GITHUB/USE_GITLAB-style integration in the ports tree already pulls distfiles from a radicle-httpd instance – proven enough to build ports-mgmt/pkg.
Migration is partial and ongoing; the author flags sharp edges remain and will post updates as Radicle integration matures.
Hacker News Comment Review
Commenters new to Radicle flagged the project’s own landing page fails to explain what it is – discoverability and onboarding UX are a known weak point, not just a HardenedBSD docs gap.
The deeper concern raised: Radicle repos exist on the internet but not the visible one – no organic search indexing, limited cross-project discovery, making it hard for downstream users to find code without a direct seed address.
ATProto vs. Radicle p2p tradeoffs surfaced briefly; both approaches still depend on high-availability seed nodes, so neither fully escapes infrastructure requirements.
Notable Comments
@sunshine-o: notes Radicle has a search engine but discoverability remains the project’s hardest unsolved problem even after 5+ years.
@mkl: points out radicle.network links drop visitors on a dead page with no explanation of what Radicle is – an onboarding cliff for anyone following the announcement.
