> Radicle’s Collaborative Objects (COBs) provide Radicle’s social primitive. This enables features such as issues, discussions and code review to be implemented as Git objects. Developers can extend Radicle’s capabilities to build any kind of collaboration flow they see fit.
There is no an explanation of what Radicle is/does in the announcement.
I'm not sure that this will actually solve the problem. This seems more like a facade for a move they wanted to do anyways.
Every user has their own node, and everyone's node talks to several seed nodes. Even if the official HardenedBSD seed is down, there's still going to be another node to sync with.
Not even a facade really. They say this further down in the thread:
> Given our previously communicated desire to migrate to #Radicle, this is a good motivating factor for moving in that direction.
My guess is the model is let the Github mirror repo be hit by bots and just do the dev work on the Radicle node.
- [0] https://hardenedbsd.org/article/shawn-webb/2024-09-23/harden...