On March 26th, we announced the first release candidate for Radicle 1.0. Today, after five months of feedback and 17 release candidates, we are ready to launch Radicle 1.0. If you've been waiting for the right moment to try Radicle or to reintroduce yourself to the stack, now is a great time to dive in: our website and guides should have all the information you need to get started. If you've been tagging along, thank you, it's been a bumpy ride and we couldn't have done it without you!

Topic: Collaborative Objects (COBs) Format: Study group -- people ask questions, it's a conversational format Feel free to add questions async in Jitsi chat Notes What are COBs?

New version $ rad rad 1.0.0-rc.13 (1848c2b8) Radicle command line interface Usage: rad <command> [--help] Common `rad` commands used in various situations: Profile management:

Image: https://www.dropbox.com/scl/fi/zneiv5a4ezfggnz2n8vvt/radinspect001.png?rlkey=ps0ud8l641jwlwfqn2ih1fly3&dl=0 Event title: Radicle Inspect #001: Collaborative Objects Virtual Study Group Date: Tuesday July 30th from 13:00 - 14:30 UTC

Radicle uses two important threshold concepts: Identity Threshold or ID Threshold: The number of delegate signatures required to approve changes to the repository's identity document. This is a system-defined value, calculated as (votes >= (delegates / 2) + 1). It cannot be changed by users and ensures a majority consensus for identity updates. Repository Threshold: The minimum number of delegate votes required for changes to be accepted as the repository's canonical state. This user-defined value, set in the repository's identity document, determines how many delegates must approve before updates to Git data (like commits, branches, or tags) become the new default state. This value is defined in the repository's identity document and can be adjusted by delegates to suit the project's needs. (alternate option: Git Threshold) These thresholds operate independently, providing separate controls over a repository's settings and it's data governance. Example messaging updates: radicle/src/cob/patch.rs

3. Selectively Revealing Repositories In his influential work, A Cypherpunk's Manifesto (1993), Eric Hughes eloquently encapsulated the essence of privacy, stating: Privacy is the power to selectively reveal oneself to the world. This notion of self-determination and control over one's personal information stands in stark contrast to the reality of using "private repository" features on traditional centralized code forges. In these systems, privacy is merely an illusion maintained by terms of service agreements, as data is stored in cleartext, fully accessible to the platforms employees, vulnerable to potential misuse, and

Download the tarball:​​​curl -O -L https://files.radicle.xyz/releases/1.0.0-rc.10-23-g484cf022/radicle-1.0.0-rc.10-23-g484cf022-x86_64-unknown-linux-musl.tar.xz Download the signature file for verification:​​​curl -O -L https://files.radicle.xyz/releases/1.0.0-rc.10-23-g484cf022/radicle-1.0.0-rc.10-23-g484cf022-x86_64-unknown-linux-musl.tar.xz.sig Verify the signature using the ssh-keygen command:​​​ssh-keygen -Y check-novalidate -n file -s radicle-1.0.0-rc.10-23-g484cf022-x86_64-unknown-linux-musl.tar.xz.sig < radicle-1.0.0-rc.10-23-g484cf022-x86_64-unknown-linux-musl.tar.xz The output should match the following, including the key fingerprint:​​​Good "file" signature with ED25519 key SHA256:iTDjRHSIaoL8dpHbQ0mv+y0IQqPufGl2hQwk4TbXFlw (Optional) Download the checksum file and verify the checksum:​​​curl -O -L https://files.radicle.xyz/releases/1.0.0-rc.10-23-g484cf022/radicle-1.0.0-rc.10-23-g484cf022-x86_64-unknown-linux-musl.tar.xz.sha256 ​​​sha256sum -c radicle-1.0.0-rc.10-23-g484cf022-x86_64-unknown-linux-musl.tar.xz.sha256 The output should be:​​​radicle-1.0.0-rc.10-23-g484cf022-x86_64-unknown-linux-musl.tar.xz: OK

Summary This guide aims to simplify the process of setting up a secure and private environment for Radicle users, ensuring that their repositories and communication remain protected behind the Tor network. Prerequisites Ensure Tor is installed on your system Ensure you have Radicle installed on your system and an identity created (see Chapter 1 of User Guide) Steps Configure Tor as a hidden service (see Tor Configuration Details for your operating system) and start Tor (see Tor Commands for your operating system) Stop your node if it's running: rad node stop

manual wrapped oa isdj oaisdj oaisdj oaisdj oaisdj oaisdj aiodj aiosdj iasjd oaidjs aoisdj oaisdj oaisdj ioasdj oiasjd ioasdj ioa oiajsd oiajsd oaisdj oiasjd oaisjd oaisjd oiasjd oiasjd asiodj ioajsd ioajd oiasjd oiasjd ioasjd ioasjd ioajsd oiajs dioasjd ioa oaisdj oaisdj ioasdj ioasjd ioasdj ioasdj ioas dj auto-wrapped jjjij asidj aoisdj oaisjd oaisjd oiasjd oiasjd oiasjd oiajs doiaj sdoiajs dioja sdoija siodja siod jaoisdj a sdoija siodja sodij aosidj asodi j

1. What is Radicle? How is it different from Git/GitHub? Radicle is a peer-to-peer code collaboration platform built on Git. Unlike centralized platforms like GitHub, there is no single entity controlling the network or user data. Repositories are replicated across peers in a decentralized manner. Radicle is an alternative for people and organizations who want full control of their data and user experience, without compromising on the social aspects of collaboration platforms. 2. Who is using Radicle currently? How many users does it have? Radicle is still in beta and hasn't officially launched yet. Many people in the community are already using it internally. The product is set to launch in March 2024, and we are just starting to onboard users. 3. What is the business model/monetization strategy for Radicle? We have not disclosed our monetization plans yet. Radicle has raised $12 million in venture funding previously. 4. What is the relationship between Radicle and the $RAD cryptocurrency?

Can I collectively maintain more than one branch with my repository delegates? No, you can only collectively maintain one branch now, the defaultBranch. In the future, there may be the possibility to collectively maintain multiple branches. Can you explain the difference between soft forks and hard forks in Radicle? In Radicle, when you clone a repository you are creating a soft fork, where the intention is for code contributions to be pushed back to the original RID, while hard forks intend to diverge code bases hence require a new RID. Hard forking a repository is only supported using the cli at the moment. How do I hard fork a repository? You can git clone <repo url> and then rad init. This will create a unique RID for you hard fork.

Introduction Software is the fundamental way in which we interface with data that comprises our current reality, and code is the language of software. Most software systems were created through a collaborative process involving multiple people. If we accept that software is important and collaborative by nature, then a shared system for communicating about code and collaborating is needed. This system shouldn't be owned by one company, as code is too important to be monopolized. 📖Learn more: Microsoft acquired GitHub in 2018. They also own 49% of OpenAI. One of our prophets of the future, the author Philip K. Dick, has shown us many projections of alternate dystopian realities that emerge when corporations amass too much power. While some may question the reliability of his visions as he was often fueled by substances that would make even psychonauts raise an eyebrow, consider this: the Oracle at Delphi's officiant claimed to glimpse through the veil by inhaling naturally occurring gasses emerging from the ground. Furthermore, our world is increasingly polarized, and this reality is finding its way into software companies and therefore into software products. Users are banned from using a platform because of their geographic location or the ideas they stand for. This is not tenable. This is why we’ve created Radicle, an open protocol that enables users like you to collaborate on your code within a sovereign network. It's a neutral environment where you have full ownership of your data and you have the autonomy to set the rules of your code universe as you see fit. You can work on software projects (and ultimately more) even when offline, while also being connected to a broader network, through which you'll eventually be able to find contributors.

Protocol Guide Item 1 Every Radicle user, irrespective of their role or activity, operates a node by installing a Radicle Node on their device. The Radicle Node hyperlink needs to be fixed "operates a node by installing a Radicle Node" is an odd statement, as the word "node" is redundant.option 1: simplify it with "installs a Radicle Node on their device." option 2: In a later section, this is said "To run a node and connect to the network, users install a Radicle client." which also seems inconsistent with saying users install a Radicle node ? Should above sentence in question also say client instead of node? Item 2 Users configure nodes with a seeding policy which specifies the list of repositories they are interested in seeding, in addition to retention rules. This means that nodes aren’t just seeding random repositories, users have an active role in deciding which repositories should be stored on their device.

Requirements Principles should be more oriented around technology/technical, as opposed to "soft" cultural principles Principles should be generic enough that it allows Radicle as a protocol to expand beyond being a code collab protocol They should be principles (vs values), but we dont have to be pedantic about it Wants something playful like Yearn - they have single word, plus a short phrase, then longer description. Look at the following source materials in developing the principles:https://radicle.blog/towards-decentralized-code-collaboration.html https://app.radicle.xyz/nodes/seed.radworks.org/rad:zPUsinVa3gP71g6Dt47LP76phAWd/tree/purpose.md https://hackmd.io/ie38RcSOR0yakmJMuAZt3g Updates

To seed is to give back. By seeding repositories on the Radicle network, you offer bandwidth, storage, and data availability to Radicle users. In this guide, we'll go through the various steps required to setup a Radicle Public Seed Node on a Linux system. To seed only requires an internet connection, a public, static IP address, and modest hardware. Getting started For this guide, we'll focus on setting up a seed node using systemd. If you're running a different service manager, you should be able to follow along

Changelog & Notes Date Name Notes 2-Jan-2024 Stellar All of the sections now have more comprehensive summaries. There are more details on images as well. Please review the comments.

Resources RIPs: https://app.radicle.xyz/nodes/seed.radicle.xyz/rad:z3trNYnLWS11cJWC6BbxDs5niGo82 Lars arch: https://app.radicle.xyz/nodes/seed.radicle.xyz/rad:z3gqcJUoA1n9HaHKufZs5FCSGazv5/tree/07e455dc597b7c368ce658ba65b866a92b9a88c4/architecture/arch.md -https://app.radicle.xyz/nodes/seed.rhizoma.dev/rad:z21RZuyuZwmmqB72Lq5A7hF8NGUF1 under slides/ man pages: https://app.radicle.xyz/nodes/seed.radicle.xyz/rad:z3gqcJUoA1n9HaHKufZs5FCSGazv5/tree/rad.1.adoc setting up seed node (outdated): https://github.com/radicle-dev/radicle-client-services Radicle 1.0 feature set: https://hackmd.io/CP_hhnhuTby-f_O6_E-Zew?both COBs: https://github.com/radicle-dev/radicle-link/blob/master/docs/rfc/0662-collaborative-objects.adoc Onboarding experience: https://hackmd.io/5_VS0D1DR_GTCyEhd39wTA

Components radicle-node radicle-httpd rad caddy (reverse proxy) Run seed node install radicle (sh <(curl -sSf https://radicle.xyz/install)) rad auth (obtain radicle keypair) set environment variables RAD_HOME, RAD_PASSPHRASE

Protocol OctoberFetch v2 - in the review phase. Done by Fintan, reviewed by cloudhead. NAT-traversal - in review phase. Done by Andrew Cann, review by cloudhead and Fintan. Fetch signed refs announcements - Fintan will be working on it. Assumed time: 1.5 weeks. NovemberCache for COBs. Arastoo is working on it, it will be reviewed by cloudhead. ls-refs for rad sync - Fintan will be working on it. Assumed time: 2 weeks. December

Author(s): cloudhead Type: Org Created: 2023-11-03 Status: