[noman-land]

Radicle is really cool. I've been running a node for months but havent pulled the trigger to use it as primary yet.

We need better forges and they need to be p2p to survive. p2p is the only viable future for the web.

[endiangroup]

AD: Thank you for your contribution! I also run a permissive seed node, vote by participation!

[endiangroup]

AD: Whats holding you back from using it as your primary?

[hosh]

Not the original OP — I had been thinking about this for years, though my interest is in resiliency rather than a sovereignty (though they overlap):

- is there a mirror adapter to push to a non-radicle node, such as Github or say, sourcehut? (Mirroring nixpkgs, for example)

- is there a mechanism to control syncs so it can be used on low-bandwidth, unreliable networks, or ad-hoc bluetooth networks?

- is offline seeding possible or in the works?

- language package managers often can reference a git or github. Would I be able to directly reference my local radicle node and have it manage (or perhaps even discover) the correct repos? (Or maybe this is a different problem and package repos themselves could be decentralized and sovereign)

On that last point, I mean that the whole build chain and supply chain can be made sovereign: I see radicle is written in Rust, which means dependencies on Cargo, the Rust toolchain, and so forth.

[noman-land]

Honestly it's mostly lack of other users to interact with. It's my same problem with things like gitea. Someone needs an "account" to participate in your project.

I'm also not sure how to sync issues and pull requests with Github.

It's largely I haven't researched deeply enough yet.