1. 25

  2. 3

    I’d love to see some description of what use case scenarios are enabled/intended for this protocol, similar as in Secure Scuttlebutt. The article linked above would be interesting if I had more context, such that based on a background of “handwaved” use case scenarios, I could then dig down (through this article) to how exactly they’re implemented to understand the tradeoffs chosen.

    1. 1

      Thanks for your feedback. With this protocol, we are really trying to build most of the collaboration features available on GitHub (issues, prs, code browsing), but without reliance on a central third party. Radicle Link is fairly low-level, but the goal is for it to offer the primitives needed to build higher level “entities” such as issues, users, projects etc. on top of DVCSs. As we write about the other pieces of the puzzle, I think it will become clearer how it all fits together.

      1. 1

        I’m esp. interested in the “user scenarios” of the gossiping aspect a la Scuttlebutt - how could I share stuff with others if e.g. rarely being online & without the “pubs”/central nodes, how do I choose what gets “pushed” to others and how I choose what to download from others. Also stuff like identities, in Scuttlebutt there’s e.g. some limitation that “one device = one identity” IIUC, how do you approach this (same or differently).

        OTOH, you mentioning code browsing is a good point, so I’m also curious how from user perspective this could work - both when browsing code of someone “I’m in room with” without Internet, as well as browsing some strangers repos on public Internet aided by “pub”/central helper servers. Also how do I discover who’s out there, I guess.

        Finally, do you plan for it to be possible to somehow link to & browse repos from public Internet, via some kind of gateways, public servers, …, comercially- or self-hosted.

        SSB have this “love story” high-level overview from user’s perspective - that’s e.g. a kind of narrative I’m very interested in as a “quick intro”, and a basis for then digging deeper into purely technical docs as the one linked in the OP. If that’s something you still have on your TODO list, I understand, will be waiting, hope I don’t miss the post :)