How Radicle Works Under the Hood
radicle.xyz
How Radicle Works Under the Hood
1–10 of 18 posts
Re: How Radicle Works Under the Hood
#2Recent HN post about Radicle: https://news.ycombinator.com/item?id=39600810
Looks like 1.0.0-rc.1 was just released yesterday.
Re: How Radicle Works Under the Hood
#3Radicle 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.
I know that there is also a web-frontend (kinda like GitHub) for radicle: https://app.radicle.xyz/nodes/seed.radicle.xyz/rad:z3gqcJUoA.... But I haven't seen a guide how to set that web frontend up locally.
Re: How Radicle Works Under the Hood
#4Radicle 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 cop…
There's a manual way to run the UI locally for now: https://app.radicle.xyz/nodes/ash.radicle.garden/rad:z4V1sjr...
We'll be also working on packaging the js bundle so that it can be distributed and served locally without setting up a dev environment in the future.
Re: How Radicle Works Under the Hood
#5What is it with web3 sites and their obsession with marquees? https://radicle.xyz/faq
Re: How Radicle Works Under the Hood
#6What is it with web3 sites and their obsession with marquees? https://radicle.xyz/faq
Is marquee a design technique on the front end?
Re: How Radicle Works Under the Hood
#7What is it with web3 sites and their obsession with marquees? https://radicle.xyz/faq
It's actually a web1 thing: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/ma...
Re: How Radicle Works Under the Hood
#8Is 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?
Re: How Radicle Works Under the Hood
#9Is 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?
It seems to address data centralization issues. Government activists and pirates will likely find it attractive.
For the average GitHub user, it adds a lot of complexity for undetermined benefit. It basically ensures your repositories can’t get pulled if someone at Microsoft doesn’t like what you’re doing.
Re: How Radicle Works Under the Hood
#10Is 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?
Something like Suyu, or Great Firewall evasion. PRs (http/ssh in general) and mailing lists will end up being a game of whackamole.