Their Project:

Their Role/s:

Why Radicle?

• been following the project for a while
• FAN OF LOCAL FIRST SOFTWARE
  • Maintain open source software
  • Not interested in p2p or decentralization
  • Software which gives the user as much autonomy as possible. Where do these ppl hang:
    • word document —> hard parts is when u try to collaborate with other ppl. PERMISSIONLESS for local first…when u work with other ppl is more complicated. Local first doc is an email, and is collaborative.
    • Story: hospital automated checklist, then they automated from piece of paper to software. Productivtiy plummeted, got bad. Doctors would ignore qustions that wouldnt make sense. Once its a form of a central server, with someone else deciding what to put nito that. Best ppl to design a tool, are the ppl doing that work

Appealing about radicle: Its a protocol that allows u to talk about identity and code. Has openings to do more flexible things than pull requests.

ie.: like patches, looks more like the mailing list kind of workflow.

why pull requests and issues are quite annoying?

• issue threads are hard to read. No ability to do threading (bracket an issue and make sub threads)
• Pull request is annoying, is hard to see whats changed based on the feedback.
• Send patches in an email, is a lot easier to view.
  • Linux cornell and Git projects are being developed via email.
  • GitHub Issues are really crap for ux (not sure why)

Challenges with GH and other centralized platforms:

If you are willing to work with just github you are good to go. But as soon as you want to do work across platforms, sync models between github, attlassian, gitlab —> It’s hard to authenticate, sync up identities. It’s much more expensive.

• most devs work with multiple different tools. If a tool is well designed they don’t mind switching tools.
• Why an OSS protocol is a better solution? Hundreds of protocls can interact between each other. Integrations can be smooth. In order for taht to happen the economics have to make sense.

Where to find FOSS devs?

• Automege: Primary project - maintainer
• Work with indusrial research lab or institute for computing research —> discord
• Forum: Lobste.rs

Web3, local first, a lot of the goals align:

• autonomy interest —> not being controlled by a governmetn
• technical interests: p2p

Radicle problems solving:

• Nothing yet in value.
• its a way of doing mailing list style developement in the sense of styling (WHY?), like relying in 40 year old protocols.
  • How radicle is going to solve this:
    • protocol for distributing code an a cryptographic identity, and collaborative objetcs —> same workflows u do in email, but using protocols easier to use (WHY?)
  • supply chain security issues: A package manager based all code on radicle network: all that is signed by ppl trusted by the package member. CRAB - Rust attempt to solve that.
    • Trust auditors to audit code
    • withholding data → if they do it with
  • The risk being that maintainers can take code down on sth like GH. With Radicle, anyone can mirror. Have cryptographic evidence around who built code, and what they did. You can reconstruct code from all patches.