Decentralized Co -development Of Radicle 1.5 Is Available

presented the release of the P2P platform radicle 1.5 , aimed at creating a decentralized service of joint development and joint development and joint development and Storage of code, similar to GitHub and Gitlab, but not tied to specific servers, not subject to censorship and working using resources of participants in the P2P network. The platform supports the typical elements of social interaction between developers, such as Issue, patches and reviews of code. It is possible to create private repositories and work through the Tor network. The project’s achievements are written in Rust and are distributed under the licenses of Apache 2.0 and MIT. Assemblies prepared for Linux and MacOS. Additionally, desktop-client , the web interface and console The interface .

radicle allows you to not depend when developing and distributing code from centralized platforms and corporations, the binding to which makes additional risks (a single point of refusal, the company can close or change working conditions). To control the code in Radicle, the usual Git is used, expanded by means of determining repositories in a P2P network. All data is primarily maintained locally (the Local-First concept) and are always available on the developer’s computer, regardless of the state of network connection.

Participants provide access to their code and artifacts associated with the code, such as patches and discussion of errors (ISUS), which are maintained local and replicated to nodes of other interested developers connected to a common decentralized P2P network. As a result, a global decentralized GIT-repository is formed, the data of which are replicated and duplicated on different systems of participants.

to determine neighboring nodes in the P2P network, a protocol is used gossip , and for data replication between the protocol headwood based on Git. Since the protocol is based on GIT, the platform is easily integrated with existing tools for development on GIT. Cryptography based on open keys is used to identify nodes and verification of repositories, without the use of accounts.

/Reports, release notes, official announcements.