Radicle shows a lot of promise. As far as I understand it, every participant runs a local radicle node in true peer-to-peer fashion. Every node can seed git repositories which then get replicated on the network. From the perspective of a git command line user, radicle acts as a git-remote that is running on your local machine. The repositories that you push to are then pulled by any other radicle nodes who want a copy. These other nodes will then also seed your repository.<p>I know that there is also a web-frontend (kinda like GitHub) for radicle: <a href="https://app.radicle.xyz/nodes/seed.radicle.xyz/rad:z3gqcJUoA1n9HaHKufZs5FCSGazv5" rel="nofollow">https://app.radicle.xyz/nodes/seed.radicle.xyz/rad:z3gqcJUoA...</a>. But I haven't seen a guide how to set that web frontend up locally.
Recent HN post about Radicle: <a href="https://news.ycombinator.com/item?id=39600810">https://news.ycombinator.com/item?id=39600810</a><p>Looks like 1.0.0-rc.1 was just released yesterday.
Is it something that's aimed at a specific problem I have never encountered or is it something that can improve everyone's workflow? It feels like it's something closer to git + mailing lists than typical PR workflow, which I do find interesting because PRs are... a lot of unnecessary work. But this has to be better than mailing lists, right?
I don’t think I understand how this protocol is supposed to solve the problems of the commons that arise in any peer to peer app, such as how to deal with malicious or misbehaving peers, illegal or unsavory content, and so on. Every P2P app needs to put those problems front and center in their design and I never feel the proposed solutions are adequate. But in this case, I simply don’t see them acknowledged at all.
What is it with web3 sites and their obsession with marquees? <a href="https://radicle.xyz/faq" rel="nofollow">https://radicle.xyz/faq</a>