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.
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.
Does that actually work out in practice? Do you/someone here have experience with that in Radicle?
IPFS in theory has a similar model, but in practice I've mostly found that if the original seeder goes away, at least part of a dataset becomes inaccessible.
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.
> 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.
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.
Does that actually work out in practice? Do you/someone here have experience with that in Radicle?
IPFS in theory has a similar model, but in practice I've mostly found that if the original seeder goes away, at least part of a dataset becomes inaccessible.
2 replies →
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...