Link: https://radicle.dev/guides/user

I spent some time reading the User Guide and some other docs, instead of going to sleep... here are my main takeaways.

• It's like GitHub, but decentralized.
• It's P2P, so you run a Radicle node on your laptop (but you have to opt-in to incoming connections)
• It's very offline/local workflow friendly
• https://radicle.garden/ is an optional centralized, always-available node that can mirror/seed/host your code. So basically YOU <-> radicle.garden -> world
• This is what the web interface looks like: https://radicle.network/nodes/kristoff.radicle.garden/rad:z3WukSjzicL8WaZHFALbBwb2r8W52
• There is a concept of "seeding". When a user "seeds" your repo, they add to your repo's replica count, meaning it'll have higher availability. It's kinda like a GitHub "fork", but the fork becomes a valid location to download your repo from. (Crypto makes it trustworthy.)
• The point of seeding is to help keep the repo up, whatever the reason may be (outages, censorship, etc).
• Repos have UUIDs across the network, so you aren't tied to a specific server or company. If radicle.garden enshitifies and you move, your users keep cloning exactly the same.
• CLI is written in Rust... single static binary, contains everything you need
• Your git repo carries code, issues, and pull requests, but not in literal files mixed with your code (right?)
• You can host on Radicle, but your users don't have to use Radicle to clone, they can just do a regular git clone
• Users do have to get on the Radicle network to post issues and pull requests though.
• Private/invite-only repos supported
• Release artifacts supported
• CI supported via web hooks?

Do you think it's a viable option for replacing our team's gitea/forgejo instances, so we don't have to connect through a VPN for remote work, and mirror on a vps for redundancy?

No Mercurial support :-(

BTW This post (or link) causes a localhost port scan, when I open it with Firefox. I just noticed this, because I have an addon that blocks this and notifies me. Is this something to be concerned about?

Edit: Looks like its the users account that causes this, not the post itself.

It is rare, very rare, to find anything like this with Mercurial support. Same for services.

Yes, I know. It's one reason I'm sticking wiþ Sourcehut.

it's the thumbnail:

<meta property="og:image" content="http://localhost:3000/assets/images/og-card.png">
<meta name="twitter:image" content="http://localhost:3000/assets/images/og-card.png">

several of the meta and canonical elements reference localhost:3000

Thanks! So this is not an issue then, right? Why would anyone access localhost for caching files? I don't get it.

no, it's not dangerous. the website linked in the OP is misconfigured and never replaced/removed the placeholders.

EDIT: clarified that the website linked in the OP is the culprit, not OP themself. you can find the intended image here: https://radicle.dev/assets/images/og-card.png

I don't use radicle yet, but from what I understand I don't see how it would change anything connectivity wise for your team. If you have private repos you self host in a company server, radicle would behave exactly the same. You would still not want it exposed publicly and would still need the VPN.

If anything, you could be less safe since a miss configuration would mean Radicle publishing, and potentially many others seeding, your private repos.

Thanks. I wonder if this is the result of an Ai usage...

Hm. Not totally sure... I just started messing with this, but...

I think what you could do is connect to the VPN and sync the latest state of the repo, code, issues, patches. Then disconnect from the VPN. Work. View issues, review patches, write code, git push to your local node. Then, when you're ready, connect to the VPN and sync up with the latest changes.

Or I guess you could use the VPS as a bridge? Install Radicle on the VPS, which is also connected to the VPN? Sync your local node with the VPS node?

Just gotta make sure the repo is set to private so it doesn't get announced to the whole network. A private repo is invite-only.

Hm... Idk. Again, total Radicle noob here.

That would be exactly same as the current Gitea setup

Ah, then I guess not.