← Back to context

Comment by jgtrosh

1 day ago

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.

14 comments

jgtrosh

Reply
dmos62  1 day ago

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  1 day ago

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

  • bombcar  1 day ago

    I was just wondering in another thread how much you could do storing things in git itself.

lorenzleutgeb  1 day ago

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

  • hobofan  1 day ago

    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_  1 day ago

      > 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  1 day ago

      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.

      3 replies →