Not to "um, actually", but I'm gonna "um actually" - technically, using git to host code in a decentralized fashion has been a standard capability of git since it's inception. So it's not really a new idea, just a new iteration
The Radicle protocol leverages cryptographic identities for code and social artifacts, utilizes Git for efficient data transfer between peers, and employs a custom gossip protocol for exchanging repository metadata.
So it has a gossip protocol to spread the repo, and a common format for artifacts (issues, PRs, etc) to act more like GitHub.
I don’t know too much more because I just started looking into it a month or two ago and haven’t done a deep dive. But it’s a layer on top of git to spread repositories peer to peer instead of manually having people add remotes.
Thanks for politely asking for more info. I find myself a bit brash sometimes as I live on crypto twitter as my day job. So sorry if the initial message was harsh; I deal with a lot of shit posters.
I hope ForgeFed will go into production soon,
then we can synchronize the code in between multiple Forgejo instances in a federated fashion. https://codeberg.org/forgejo/forgejo/issues/59
Amazing. The first medium project on radicle. If this node stops syncing this repo, it should be easy enough to have another node sync it.
However, I'm not sure if radicle has discoverability built in. With torrents, a magnet link allows finding it, and IPFS just has a hash allowing you to find it. If radicle just needs a hash to find a node with it, that would make it easy for nintendo to list all the nodes and send them a take down notice (which would or would not be heeded, depending on the operator). Regardless, radicle might support anonymous hosting with I2P, which would make nintendo or any other party powerless and unable to send takedown notices to the anonymous servers.
Additionally, it isn't clear to me how to contribute to radicle projects yet. Developers will have to learn how to contribute to P2P hosted projects now, but that's probably not a big learning curve.
They convinced the yuzu team to officially not work on yuzu anymore, but I guess the devs could still work on it using their private account or in form of another another team. The major problem was thir patreon locked pre-releases
I would think the devs wouldn't want to risk it. Assuming they are barred from working on it, if they slip up & reveal something about themselves while working or committing, they may be targeted even harder.
