Correct! ;)
You could start with seeding the #Heartwood repository (the reference implementation of the #Radicle protocol), for sure!
In addition, you could look at a couple of community resources to help you decide:
- The awesome-radicle repo: https://app.radicle.xyz/nodes/seed.rhizoma.dev/rad:z3yQUb9HDAC7TQrUDGkQsXDsYFj9G
- A quick search tool to help you discover more content: https://radicle.kuehlewindt.com/
starting out with #Radicle
if you know good repos to seed, hit me up!
Hi @algernon o/
Would you mind if I asked "why" ?
I think it's important we capture that "why" on the #Radicle side, because our assumption so far is that exposing a homelab / laptop radicle-node as a Tor hidden service [1] was enough to get us around without having to worry about punching holes through NAT.
Maybe I should set up #radicle today.
Do you like @radicle but aren’t exactly enthusiastic about self-hosting your #codeForge?
Talk to us to find out about a hosted #radicle node offering!
Have us spin up your team’s seed node and CI runners and move your code to the global #peerToPeer network!
Today has been a good day for discovering #OpenSource resources.
First, a fedizen turned me on to @radicle and I happen to be looking into various options for migrating off #GitHub . The resistance to #llm scraping is a bonus.
Thanks to #radicle , I got reacquainted with @zulip . It's not yet in my stable of community apps, and I have been hoping for an excuse to use it more regularly.
So far #zulip exceeds expectations as an upgrade from #Slack , IMHO.
@positivedinosaur @liw @joshbressers
If you need any help when you try out #Radicle , do feel free to search for common issues and report any other you come across in https://radicle.zulipchat.com/#narrow/channel/369873-support .
@Gray Was the repo set up with just a single delegate?
Generally speaking, in cryptography (that #radicle relies on), it's pretty destructive to lose a private key and there isn't a way to recover from that.
It is recommended to set up repos with at least 3 delegates (2 delegates have the problem that if one key is lost, you can't reach quorum for further changes to the repository identity).
You might want to join https://radicle.zulipchat.com and the #support channel there for more details.
@liw
Just finished with the Open Source Security Podcast episode by @joshbressers with you.
Very interesting! I had no idea even cool stuff like #radicle existed. Next thing to try out :)
Also: I like the python script to upload PDFs to the rM2 without using the webinterface!
I long for the day when we at #HardenedBSD can switch to #Radicle as our code forge.
@jonathanmatthews I use Radicle, which syncs public repositories with other nodes. This includes issues and patches.
All my Git repositories are in Radicle. My primary laptop has a Radicle node with all the repositories I have. The laptop gets backed up (with rsync) to a USB drive and a server every day.
I also have a public Radicle node, but that only has a subset of the repositories I have on my laptop, so it doesn't need to get backed up. But I back it up daily to my laptop.
