I was not aware of Radicle; it's a truly peer-to-peer Git forge which aims to guarantee commits are signed by current maintainers (among, I suppose, other goals).

The article mentions an us and a you, but I feel like it would have been an useful occasion to explain why move (from where?) and why Radicle. Maybe this was already discussed elsewhere?

I suppose similar discussions regarding GitHub are happening today and could explain why this was posted to HN.

▲

dmos62 5 hours ago | parent | next [-]

Radicle is pretty cool.

> 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.

▲

donatj 3 hours ago | parent [-]

I know I'm not supposed to make jokes, this is not reddit, but you might even say it's pretty radical.

	▲	dmos62 2 hours ago \| parent [-]
		I think apologetic jokes are very on point for HN, so no worries!

▲

heresie-dabord 2 hours ago | parent | prev | next [-]

If it helps:

https://radicle.dev/

There is no an explanation of what Radicle is/does in the announcement.

	▲	swed420 14 minutes ago \| parent [-]
		Some previous discussions: https://news.ycombinator.com/item?id=19367916 https://news.ycombinator.com/item?id=25313010 https://news.ycombinator.com/item?id=39600810 https://news.ycombinator.com/item?id=41509713 https://news.ycombinator.com/item?id=46732213

▲

lorenzleutgeb 5 hours ago | parent | prev [-]

For the reason of hbsd moving, see https://bsd.network/@HardenedBSD/116437657126172879

▲

hobofan 4 hours ago | parent [-]

So instead of their self-hosted Gitlab instance being hammered, now their self-hosted Radicle instance will be hammered (and if they are lucky some of the other seeders will tank some of the load)?

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.

	▲	QuantumNomad_ 3 hours ago \| parent \| next [-]
		> This seems more like a facade for a move they wanted to do anyways. 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.
	▲	Skinney 2 hours ago \| parent \| prev \| next [-]
		The load will be spread across the network, but I guess the main benefit is that everything continues working even though HardenedBSDs official seed is down. 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.
	▲	sunshine-o 4 hours ago \| parent \| prev [-]
		Yes they have been looking into decentralized technologies like mesh networking, reticulum, etc. for a while now. 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...