The video recording of my foss north 2026 talk "Distributed CI with Radicle and Ambient" seems to now be public on Youtube. The talk itself is about 30 minutes, with about 15 minutes of Q&A, with many good questions.
https://www.youtube.com/watch?v=YxGT59EKhwM
https://liw.fi/foss-north-2026/ has links.
I use and love #crev & #vet — instruments for WoT crowd-review and supply-chain protection.
#TIL Tangled. It's like #Radicle. Unfortunately over the git too, but also supports jj, that isn't #pijul but not git.
I also read a very important blog post for me there: "combat LLM spam by building a web of trust" https://blog.tangled.org/vouching/ .
The only thing that rubbed me the wrong way was the possibly overloaded uses of the ssh-agent ... #radicle is not really using it for ssh, as far as I can tell, but just as a general public/private key client interface?
I typically use the authentication keys from an opengpg smartcard, and not entirely sure the ssh-agent interface is compatible with using arbitrary ssh keys...
Took #radicle the peer-to-peer code hosting platform for a spin yesterday... WOW. Just. Plain. Wow!
Everything feels like a fairly natural extension of git itself, for someone reasonably comfortable with git at the commandline.
git push and git fetch and such all behave as one would expect, using a git remote helper.
But also did a great job incorporating patch tracking, which, again, just feels like a special git push or fetch.
Issue tracking also feels similarly familiar.
5 of 5 stars!
A single-file browser tool for binding Nostr and Radicle identities.
@adingbatponder
#Radicle does the sort of sync you're talking about. For any repo, there is a top sigref, and with that you can easily see if other nodes are in sync with you or not (with 'rad sync status').
I think the biggest hurdle when you come from an SSoT perspective is getting used to the "eventually consistent" idea. That idea is not strange per se, that's how kernel development operates... but still, I understand that it takes getting used to.
This is the foundation for the broader radicle-nostr-bridge concept: publish Radicle activity (repo announcements, patches, issues) as Nostr events for discovery, while keeping the canonical git data on Radicle.
Lars Wirzenius
Shawn Webb
Boozook 🦀 
Vagrant Cascadian
metaend
Richard Levitte
adingbatponder 
👾