1/ It’s a big day for the Radicle community :space_invader: We're excited to announce the rollout of our first release candidate for Radicle 1.0 — our most significant update to date :tada:
Start collaborating today
Here’s an overview of what’s new
2/ This release marks the stabilization of Heartwood, the peer-to-peer protocol that powers Radicle with a sovereign data network for code collaboration and publishing, built on top of Git. Heartwood addresses the usability and performance concerns faced during previous protocol iterations while doubling down on Radicle's secure and resilient primitives.
Learn more about Heartwood:
https://radicle.xyz/guides/protocol
3/ Radicle 1.0 features the core primitives for code collaboration, including patches and issues, with CI coming soon :corn:
Typically, artifacts like patches and issues are only found on centralized platforms like GitHub or GitLab, or their self-hosted counterparts. In Radicle, they are stored directly inside repositories and replicated between peers. This means that social artifacts inherit the same properties as source code: they are local-first, user-owned, and cryptographically signed.
4/ Instead of depending on a centralized server, Radicle users run nodes connected via a peer-to-peer network. Nodes host and synchronize Git repositories across the network, using a gossip protocol, alongside Git’s transfer protocol.
With this release also comes the launch of the Radicle Network, which lets users provide bandwidth, storage, and data availability to peers of their choice.
To seed is to give back
5/ Already, the Radicle Network is growing:
6/ If you've been waiting for the right moment to try Radicle, this is it! We’ve got some shiny new guides to help you get started:
User Guide → https://radicle.xyz/guides/user
Seeder Guide → https://radicle.xyz/guides/seeder
We need neutral and permissionless infrastructure to truly free the web
Reliance on centralized forges is not sustainable for the future of free and open source software. We built Radicle to change that.
Try Radicle. Free your code.
@amolith I'm nor sure about the tags. May I ask you to join the Zulip to ask? The people who know Radicle deeply are there.
@liw that’s really cool! One terminology concern though - there’s a glaring conflict between “git remote” and “local first storage” that will really really confuse people (and git is already confusing!).
@andrewg I've forwarded that to Zulip.
@liw you’re kind of stuck because of git’s existing terminology, so maybe the best that can be expected is some clarification in the docs
@liw this radicle looks very interesting. is there also some web-frontend even if only read-only - for the casual drive-by oooh-that's interesting kind of stumbling over projects and poking at their intestants?
@stf Yeah, there is bot a "web site" where you can browse a node's repositories and a "web app" where you can browse your own and (still experimental) manage issues and comment on patches.
@liw
It's a really cool project but now I wish they would make a presence on the fediverse too (and not just twitter). Can't be bothered to create yet another account on their zulip instance or whatever it's called
@liw
Hmm how do they even announce releases? Would love a RSS feed
@lmas We're working on it. No promises on when it'll be ready.
@lmas Apparently for read-only access, Zulip doesn't require an account. The #annoucement stream is where releases are announced, but we intend to broaden from there.
@liw
Oh you're part of the team! Alright that solves both my issues then, thanks for your replies. I'll take a look at the announce channel and eagerly follow your first release