I've been doing some initial testing with @radicle ... https://radicle.xyz/

First thoughts ...

  • it's an interesting idea, and I really like the concept.
  • It's a lot of new concepts I need to get used to, learn a lot of new terminology
  • I need to learn stop comparing more directly against how things works in Codeberg/GitLab/GitHub
  • it's pretty fast after all
  • Searching for existing projects on radicle seems to be an impossible task or based on pure luck. The "random" rad:z3g..... strings identifying a repository (needed for rad clone) are even worse to remember than IPv6 addresses. I'm missing a "DNS" equivalent for looking up those RID values.
  • There seems to be more URLs out there pointing at documentation for various versions. Several of them are completely outdated and examples no longer work. In other words: Confusing documentation for newcomers.

I have so much to learn, and need to sit down and read the docs way more carefully. Just need to find the right ones.

#programming #source_code #version_control #vcs #opensource #foss #git #radicle

Canonical References

Sovereign code infrastructure.

@dazo

Regarding discoverability, there is https://search.radicle.xyz/ if you want to search for public repositories on the Radicle network by name. Also, if you know the DID of one of the repo delegates, you can find all their repositories via Radicle Explorer (e.g. in my case https://radicle.defelo.de/~defelo should redirect to a page listing my repositories).

For documentation, the guides on https://radicle.xyz/guides should be up to date.

Radicle Search

@defelo A question about your radicle URL with ~defelo ... How does that work? Something you configured yourself on your web instance, or something I can do with my Radicle identity?
@dazo Yeah, right now it's just a static redirect to the explorer page in my nginx config. But it could probably be extended to look up DIDs by aliases of nodes that I'm `rad follow`ing for example.
@defelo Ahh, alright. It's not a bad idea. Might even be possible to (ab)use DNS records for such lookups too. But then you'd need to know a domain as well, unless there is a 1:1 relation between git author/committer e-mail address and the Radicle alias name.
@dazo Sure, actually there already have been some experiments to use DNS/DNS-SD for peer discovery (see https://radicle.defelo.de/nodes/radicle.defelo.de/rad:z2UsLkj3UXjbxWZMGpQ9VeVLDCYUQ/tree/rad-dnssd for example or `avahi-browse -artd radicle.xyz` and https://radicle.defelo.de/nodes/radicle.defelo.de/rad:z254T5p17bdFPmzfDojsdjo4HjpoZ/tree/dns/dnsconfig.js for the DNS config). Perhaps you could even use DNS to not only look up DIDs/NIDs but also for repositories, so you could do something like `rad clone heartwood.radicle.xyz`.
Radicle Explorer

Explore the Radicle network

@defelo Nice! I'll check that out 😀