RE: https://toot.radicle.dev/@radicle/116681550667604095

If you've been meaning to check out #GitHub alternatives, moving to #Radicle has now become a tiny bit easier:

A hosted radicle.garden node means you don't have to worry about running infra yourself to keep your repos accessible. (Though you absolutely still can, if that's your thing!)

Here's a quick getting started guide if you want to try this out:

https://radicle.garden/blog/getting-started-with-an-always-on-node

... and if you have more feature requests, well... now you know whom to reach out to! 😉

The first #HardenedBSD patch submitted "the #Radicle way" made by not-me has been worked out!

It takes time to learn how inter-node syncing works, and how sometimes things can go stale between nodes.

Thus, this is the first real to-be-reviewed patch to our ports tree as submitted via the Radicle network:

https://radicle.network/nodes/rad.hardenedbsd.org/rad:z2XrdvALg77ycnuZRXgScb27yb3wM/patches/e89cbd0ed481f92678726a5fb31266617cd6df36

Radicle Explorer

Explore the Radicle network

So #radicle have started with essential networking traversal (like Tor and I2P), and once it actually works, they might tackle rare edge-cases like someone who's behind a NAT.

People can already do 'git pull' across a NAT or over tor. It feels like someone advertising their new trousers by saying 'one day it may have pockets'.

I really want to like #Radicle, but so much smells wrong.

- It's been years, but they have no LFS support. Even soft serve has LFS support.
- They hope to one-day support LFS...so people can train 'AI'.
- The training sets for LLMs are famously massive. Radicle will ensure that these sets are copied to many nodes.

How many people want to host these massive datasets?

The #HardenedBSD May 2026 status report is out! Main topic of focus is our migration from #GitLab to #Radicle : https://hardenedbsd.org/article/shawn-webb/2026-06-01/hardenedbsd-may-2026-status-report
HardenedBSD May 2026 Status Report | HardenedBSD

I organize a weekly office hour, for questions about Radicle CI, distributed CI, local-first CI, or related topics, in https://meet.ffmuc.net/radicleciofficehour (Jitsi, only needs browser, mic and webcam optional but helpful).

This week on Wednesday 07:00 UTC (09 CEST, 10 EST). I don't have any special topic this week.

cc @radicle

https://radicle-ci.liw.fi/

#Radicle #RadicleCI #ContinuousIntegration #officeHour

ETA day of week

Jitsi Meet

Join a WebRTC video conference powered by the Jitsi Videobridge

The one thing I would change with #Radicle: do not echo asterisks with each keypress when prompting for passphrase. Disable terminal echo during this phase.
I am currently in the process of migrating all my Git repositories from #sourcehut to the fantastic #radicle network. Now all I need is a CI platform 😬 Several repositories can already be found on my seed node: https://radicle.network/nodes/seed.this-is-fine.io.
Radicle Explorer

Explore the Radicle network

I have managed to get my Talos-based GitOps infrastructure repository into a (almost) publishable state. Beside the declarative setup, some primary features are the integration of an AI-Agent for Ops 🙈 and a Headscale-backed Cilium Cluster Mesh and -Gateway. Have a look at the code, but note this is a living repository - things may break: https://radicle.network/nodes/seed.this-is-fine.io/rad:z6MQ7ck2rSh7h4qEgbRYg3ftnrGv. #radicle #zeroclaw #fluxcd #talos #gitops
Radicle Explorer

Explore the Radicle network

One wonderful thing about migrating from #GitLab to #Radicle is that we got rid of our one and only #Linux VM. The #HardenedBSD dev/build infrastructure now runs 100% on HardenedBSD (rather than 99% 🙂).

Edit[0]: Clarified that it's the dev/build infrastructure that's 100% HardenedBSD. We do have one off-site backup system (maintained by a trusted third party) running OpenBSD.