Congrats! Maybe I'm not the target audience for this, so pardon my ignorance when I ask what problem does this solve? Centralization and censorship?
Radicle: Sovereign {code forge} built on Git
61–70 of 101 posts
Re: Radicle: Sovereign {code forge} built on Git
#62Earlier quoted context omitted.
What are the things you would do differently?
Prioritize discoverability, and self hosting on my own domain, with more customization for the protocol and ui/ux aspects. Basically allow people to deploy something closer to gitea on a webserver initially, which has all the basic protocol features and sharing aspects implemented. Currently the focus seems to have been very much on just the seeding & p2p part which honestly is good but not very useful for me as a de…
Fwiw, I think this is a matter of UI/UX. I think radicle provides the foundation for everything you describe -- it is just the pr/patch & issue tracking substrate, and the p2p layer for federation.
To make an analogy, I think what you are saying is "Look, BitTorrent is great and all, but I want to be able to search for music and movies. I want IMDB with a download button." That's fair, but the problem BitTorrent is solving is more fundamental, and you can build Napster or ThePirateBay on top.
Radicle, like BitTorrent, is solving the transport layer.
Re: Radicle: Sovereign {code forge} built on Git
#63Indeed, this seems to be already planned. https://radicle.dev/faq "Radworks intends to offer services built on top of Radicle."
Re: Radicle: Sovereign {code forge} built on Git
#64Earlier quoted context omitted.
Would it? Realistically, what support could they add that would make it a selling point? Mercurial?
Jujutsu + stacked PRs.
Re: Radicle: Sovereign {code forge} built on Git
#65I tried to understand what this does... > What is Radicle? How is it different from Git/GitHub? > Radicle is a peer-to-peer code collaboration platform (“forge”) built on Git. Unlike centralized platforms like GitHub, there is no single entity controlling the network or user data. Repositories are replicated across peers in a decentralized manner. Radicle is an alternative for people and organizations who want full c…
I agree it's not immediately clear how it works, although I think I understand the role it's intending to fill. If you're not familiar with the distinction between git and github it could be even more confusing. As soon as I hear decentralized I have lots of questions about the underlying protocols. Their protocol page helps a little but also uses terms I'm not familiar with like "gossip protocol". It would be nice f…
Notice how each additional sentence makes the previous sentence worse, like a turducken of solutions looking for problems, or a nesting doll where every layer is a different kind of sadness. This, I presume, is what happens when you have a hammer and a screwdriver and a chainsaw, and you decide that every problem would be better solved by using all three simultaneously while riding a unicycle.
But seeing as it already does exist, it's pretty awesome.
Re: Radicle: Sovereign {code forge} built on Git
#66Radicle is really underrated, especially when working with agents. I find it a joy to use for my agentic workflows. If there's purely an agentic forge one day, it's likely going to be a distributed one, with cryptographic identities and signed artifacts by default.
What makes it a joy to use with agents?
Re: Radicle: Sovereign {code forge} built on Git
#67Is there a plan for jj repositories in radicle proper? I'm very tired of git shortcomings.
Re: Radicle: Sovereign {code forge} built on Git
#68Re: Radicle: Sovereign {code forge} built on Git
#69I discovered Radicle back in 2020 (when their website looked incredible: https://web.archive.org/web/20201201030505/https://radicle.x... ). I bounced off of it, in part due to being unable to effectively delete repositories. They used to have an FAQ about that—looks like it's gone now, though the public-private repository area is much more fleshed out (you can make a repo private, in which case no new updates will be…
The best response I’m aware of is to invalidate any secrets that have been accidentally shared. Sometimes that is easier said than done though. And of course there are plenty of other reasons someone might want to delete data.
Re: Radicle: Sovereign {code forge} built on Git
#70Earlier quoted context omitted.
I am surprised you don't use RustChat[1] [1] https://rustchat.io/
Doesn't even come close to Zulip in terms of features.