{"id":119756,"date":"2024-09-11T03:43:02","date_gmt":"2024-09-11T01:43:02","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/vypusk-deczentralizovannoj-platformy-sovmestnoj-razrabotki-radicle-1-0"},"modified":"2024-09-11T03:43:02","modified_gmt":"2024-09-11T01:43:02","slug":"vypusk-deczentralizovannoj-platformy-sovmestnoj-razrabotki-radicle-1-0","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/vypusk-deczentralizovannoj-platformy-sovmestnoj-razrabotki-radicle-1-0","title":{"rendered":"The release of the decentralized collaborative development platform Radicle 1.0.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

The release of the Radicle 1.0 P2P platform has been announced, aimed at creating a decentralized collaborative development and code storage service, similar to GitHub and GitLab, but not tied to specific servers, censorship-resistant, and operating using resources from P2P network participants. The 1.0 release signifies the stabilization of the protocol and the platform's readiness for widespread use. Starting with this release, the protocol will change while maintaining backward compatibility, and the toolkit will include capabilities for seamless upgrading of existing systems to the new version. The project is developed in Rust and is distributed under the Apache 2.0 and MIT licenses. Builds are prepared for Linux and macOS. Additionally, a desktop client, web interface, and console interface are being developed. <\/p>\n

Radicle allows developers to work on and distribute code independently from centralized platforms and corporations, which can introduce additional risks such as a single point of failure, and the company might shut down or change its terms of service. Code management in Radicle uses the familiar Git, enhanced with tools for identifying repositories in a P2P network. All data is primarily stored locally (a local-first concept) and is always accessible on the developer\u2019s computer, regardless of the status of the network connection. <\/p>\n

Participants grant access to their code and related artifacts, such as patches and discussions about bug fixes (issues), which are stored locally and replicated on the nodes of other interested developers connected to the shared decentralized P2P network. As a result, a global decentralized Git repository is formed, with data replicated and duplicated across various participants' systems. <\/p>\n

The Gossip protocol is used to identify neighboring nodes in the P2P network, while the Heartwood protocol, based on Git, is used for data replication between nodes. Since the protocol is based on Git, the platform is easy to integrate with existing Git development tools. Public key-based cryptography is used for node identification and repository verification, without the use of accounts. <\/p>\n

Each repository in the P2P network has its own unique identifier and is self-certifying, meaning all actions in the repository, such as adding commits and leaving comments on issues, are validated by the owner with a digital signature, allowing verification of data integrity on other nodes without the use of centralized certificate authorities. To access the repository, it is sufficient for at least one node containing its replicated copy to be online. <\/p>\n

Nodes in the P2P network can subscribe to specific repositories and receive updates. Private repositories can be created, accessible only to certain nodes. The concept of 'delegates' is used for managing and owning the repository. A delegate can be an individual user, a bot, or a group tied to a special identifier. Delegates can submit patches to the repository, close issues, and assign access rights to the repository. Multiple delegates can be associated with each repository. <\/p>\n

On user systems, Radicle repositories are stored as ordinary git repositories, which contain additional namespaces for storing peer and fork data currently being worked on. Discussions, proposed patches, and components for organizing reviews are also preserved in the git repository as Collaborative Objects (COB) and replicated among peers. <\/p>\n

Radicle 1.0 includes: <\/p>\n