Live data from Hacker News

Radicle: Sovereign {code forge} built on Git

radicle.dev

71–80 of 101 posts

Re: Radicle: Sovereign {code forge} built on Git

#71
post #63

Unfortunate that they aren't using the AGPL license. It will allow SAAS companies to Embrace, Extend, and Extinguish. Indeed, this seems to be already planned. https://radicle.dev/faq "Radworks intends to offer services built on top of Radicle."

AD: Radicle is protocol driven, my hope as a contributor is it becomes infrastructure.

Re: Radicle: Sovereign {code forge} built on Git

#72
post #70
post #37

Earlier quoted context omitted.

Doesn't even come close to Zulip in terms of features.

Zulip used to have a really neat feature where you could open up certain channels to be indexable by search engines. Basically turning it into an open forum. The feature is still sorta around but completely broken. Quite unfortunate imo. It was a really neat solution to the walled garden problem with team chats

Zulip product lead here -- I'm not aware of anything in this space that used to work and no longer does.

There's long been a way to make Zulip channels searchable with zulip-archive (https://github.com/zulip/zulip-archive), and that continues to be available.

Making the app-native web-public channels accessible to search engines is a big technical project, tracked as https://github.com/zulip/zulip/issues/21881.

Re: Radicle: Sovereign {code forge} built on Git

#73
The story for sensitive/proprietary repositories doesn't feel well-fleshed-out yet:

> Radicle supports private repositories that are only shared among a trusted set of peers, not the entire network. These are not encrypted at rest but rely on selective replication and are thus completely invisible to the rest of the network.

There's no structural separation of public / private repositories; this is one bug or fat-finger away from a leak.

I was looking into how to get a radicle node running, but connected to only my own devices.

You can't seem to start the radicle node without it automatically connecting to the (generously provided) global shared seed nodes, and you can't examine/change the config without starting the node (at least with rad subcommands).

If you do `rad auth` and then delete the four seed addresses from ~/.radicle/config.json before starting the rad node, it helpfully re-adds them on startup:

  [...]
  INFO  node     Opening node database..                                                                                                                                                                           
  INFO  node     Address book is empty. Adding bootstrap nodes..                                                                                                                                                   
  INFO  node     4 nodes added to address book
  [...]
(It doesn't add the bootstrap nodes if I instead add a seed "@10.254.254.254:8776".)

Is there a guide to using Radicle like one might use Fossil within a small company / within a small group of people (disconnected from the iris/rosa radicle.network seeds)?

Re: Radicle: Sovereign {code forge} built on Git

#75

Earlier quoted context omitted.

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…

Someone looked at git - a distributed version control system that already works, that has been working since 2005, that Linus Torvalds wrote in a fit of pique and spite, and that currently hosts approximately all of the world's source code - and said, "This is good, but what if we added BitTorrent?" And then, presumably after consuming substances that I cannot legally inquire about, they continued: "And what if we ad…

AD: You missed the part about CRDT's!

Re: Radicle: Sovereign {code forge} built on Git

#76
post #51

I 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…

In general, whatever has been made public, is hard to unmake public. There can always remain a copy.

It is acutely true for peer-to-peer distributed systems like Radicle, but is still true for the more centralized GitHub, and for the Web in general. If you want to be able to walk something back, better don't publush it.

Publishing a token or an ssh key should not be a big deal, such a token or key should be immediately revoked, which is as good as deleted. The problem occurs when the fact is not noticed immediately. A git hook can help avoid such mishaps.

Re: Radicle: Sovereign {code forge} built on Git

#78
post #29

Earlier quoted context omitted.

AD: Feel free to post on our Zulip [^1] about your experiences of agentic workflow if you haven't already! Some of the team are interested in developing the agentic workflow experience. [^1]: https://radicle.zulipchat.com/

I am surprised you don't use RustChat[1] [1] https://rustchat.io/

How does it compare to MatterMost [1]?

[1] https://mattermost.com/

Re: Radicle: Sovereign {code forge} built on Git

#80

Earlier quoted context omitted.

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…

Someone looked at git - a distributed version control system that already works, that has been working since 2005, that Linus Torvalds wrote in a fit of pique and spite, and that currently hosts approximately all of the world's source code - and said, "This is good, but what if we added BitTorrent?" And then, presumably after consuming substances that I cannot legally inquire about, they continued: "And what if we ad…

[flagged]
Post reply on HN