Post

Hey 😊 I'm one of the maintainers on @radicle.xyz, and came across your blog. It's super interesting and quite the undertaking – love to see it 😍 It would be great to explore how Flirt could work with Radicle. We've thought about some of these problems in the past too – without any solutions (yet!)

Remo Senekowitsch

@buenzli.dev

Very cool! I skimmed the user guide's sections on patches. It looks like Radicle doesn't have its own concept of code review? That's a good thing, from the perspective of making a Flirt-backend for Radicle. There's no need for an "adapter" between Radicle's and Flirt's concepts of code review.

7/11/25, 1:34 pm0 reposts1 like

Currently, there is a data model for reviews, but it's been more of a light-PoC, and definitely needs more thought. That's where linking in with Flirt would really help! Radicle is also extensible, so there could be a Flirt specific COB (Collaborative Object).

Remo Senekowitsch

@buenzli.dev

I think I'll have to read a little more about the Radicle protocol to understand what a Flirt backend for it would entail. It looks super interesting so far!

I'll be curious about how you want tackle consistency for comments. Diff algorithms have parameters that can be chosen by the end-user. So, we've wondered how to give power to the users while also having a consistent view 🧐

Remo Senekowitsch

@buenzli.dev

Ooh, great question. TBH I haven't thought about this too hard yet. I guess a comment could be attached to a line in the left or right side of a diff. The other side wouldn't necessarily be stable, depending on the diff algorithm. How to decide which side to attach the comment to... IDK.