|
Top-level
 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. 7 comments
5/ Already, the Radicle Network is growing: π > 100 nodes online daily 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 πΎ πΎ πΎ 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. @liw after figuring out how I needed to start/integrate ssh-agent, this was easier than expected!
https://app.radicle.xyz/nodes/seed.radicle.garden/rad:z34saeE8jnN5KbGRuLSggJ3eeLtew/tree/a7798af05efafafaaff3b30f3757a901eb351d1f |
Gregory's Server
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 π±