I proposed this project to improve on Radicle’s p2p model by using Tor for universal, straightforward seeding of git repos.

Original discussion thread - https://bounties.monero.social/posts/207/

One of the project’s git repos linked in that thread - https://radicle.network/nodes/iris.radicle.network/rad:z2ydYmUCJvDfNFTVTpEbQmm55EPt1/history

Project website - https://cradicle.xyz/

The dev who took the project also expanded it into a project to reimplement Radicle in C.

Since I’m not a coder and I don’t have any git repos of my own, I can only test from the viewpoint of an average layman using the GUI app to seed repos.

It’s impossible for me to properly gauge how the project is progressing without engagement from coders who try using it for their git repos.

If the project doesn’t currently interest you, your suggestions on how to start getting users on board would also be welcome.

Edit - bear in mind that because decentralized discussion platforms like this are currently quite broken, there are comments showing up in the thread when I’m not signed in that don’t show up for me when I’m signed in. Here’s a screenshot of all the comments showing up for me right now where I’m signed in and able to reply, as of UNIX time 1779670288

aqhH5rVg9opRagM.png

I’d encourage discussion of this project moreso on nostr (equally broken but my preferred platform) or the discussion thread linked above (seemingly more functional)

  • whoever loves Digit 🇵🇸🇺🇸🏴‍☠️@piefed.socialOPEnglish
    11·
    5 days ago
    • Guide: you can’t compete with github using a CLI guide while there’s no one click solution. With BitTorrent in its constant state of DDoS and fragmentation despite having easier seeding, radicle’s harder seeding makes the math even worse.
    • Fork: it was up to radicle whether to implement the proposal in their mainline release or require a fork, but I don’t see how or why you’d pretend a fork wasn’t required after a fork is already the thing that happened faster (and a massively rewritten one, too).
    • C rewrite: indeed, as I said to begin with that was an expansion by the dev that took the proposal, beyond the scope of the original requirements.