https://github.com/n0-computer/pigeons offers the same but with SSH.
I use it in my homelab extensivelly for access, tunneling smb, postgres and some other minor bits.
I'm a big fan of iroh, but I think iroh's holepunching algorithm is at least partly based on tailscale's, so it's not 100% accurate to say iroh got there first. (Just the "as a library without a control plane" bit.)
> I don't understand why anyone would still start a new software project in C today, given the long track record of mistakes developers can make in it.
If you think that unintended consequences can result from using C, boy do I have some news for you for "programmers" from 2026.
From the README.md: If "fancy new AI tech in an old-school minimalist package" sounds like your vibe, you might like this.
What is the question about:
A: Why start a 'new' software project? (instead of old, none, multiple, ...)
B: Why in 'C'? (instead of Mojo, Java, D, ...)
C: Why 'today'? (instead of Yesterday, Tomorrow, never, ...)
For me the beauty of this project is:
Someone tried to figure out for themselves what an end-to-end process would look like for what they wanted to do. What happens to the input? How are files written? What is sent to the LLMs?
And they used the tool they know best. No `import openai`.
Because despite all the fear, uncertainty and doubt thrown at the C language over the last 20 years, the truth is that its a relatively 'easy' language to use.
What do I mean by 'easy' ?
C books can typically be about 300-500 pages give or take. Compare that with modern languages especially a Java book in the 2000's, it would be closer to 600-1000 pages.
Why? Because half the book is talking about Object Oriented Programming.
C is simpler by comparison, once you get your head around it quirks and gotchas. Afterall, every language has their own gotchas!
To me, there is a difference between good C programmers and bad or non skilled ones. Those that understand C can write some good and efficient programs that care about performance and memory.
With all the above... the truth is that you could write this towards ANY language. They all have their pros and cons.
> I don't understand why anyone would still start a new software project in nodejs today, given the long track record of mistakes developers can make in it.
> I don't understand why anyone would still start a new software project in python today, given the long track record of mistakes developers can make in it.
> I don't understand why anyone would still start a new software project in java today, given the long track record of mistakes developers can make in it.
And dare I say this one...... ???
> I don't understand why anyone would still start a new software project in rust today, given the long track record of mistakes developers can make in it.
OK. You can argue that rust is not old enough to be labelled the "..given the long track record.." - but everything else stands.
Actually very similar, GitHub was also early in talking about Continuous AI. I think the biggest difference is that Continue is very focused on the use case of checks and gets a lot of the small details right that really matter because it's not built for generic non-AI CI workflows
Some of these are:
- Having a local experience to run them with Claude Code, etc.
- Making it easy to accept/reject suggested changes
- A single folder dedicated to just checks so you don't have to think about triggers
- Built-in feedback loops so you can tune your checks with feedback
- Metrics so you can easily track which have a high suggestion / merge rate
Let's say I have a religion that, as part of practicing it, restricts my diet.
If I try to make you - a non-practitioner - eat that diet, then your reply makes sense. It's a personal matter; I don't get to force it on you or anyone else.
But if you try to remove the option of me being able to get food that fits my diet out in public? Don't try to justify that by saying "religion is a personal matter". That's an absurd rationale.
> Let's say I have a religion that, as part of practicing it, restricts my diet.
> If I try to make you - a non-practitioner - eat that diet, then your reply makes sense. It's a personal matter; I don't get to force it on you or anyone else.
In the UK, it's becoming increasingly difficult to find restaurants whose meat is not halal. One could argue that a religious diet is in fact being forced upon those who do not practise Islam.
How does praying infringe on a public space? Does it leave behind wrappers? Hurt the local wildlife? Ruin the watershed?
Should we ban people quietly playing musical instruments in public spaces to? Perhaps people walking? Certainly people reading books - they could be religious books or even, gasp, depict sex.
Out of memory, it is often times Muslims praying in the middle of a road or pathway to block other people for no reason than being obnoxious. And then as a reaction they will get this stupid law.
The security researcher noticed that CodeRabbit runs linters against your code base and noticed that Rubocop was among the provided linters. Rubocop supports extensions that contain custom code, so he crafted an extension that exfiltrated the environment variables of the running Rubocop process when it linted the contents of his PR.
But where does the configuration for Rubocop come from? From CodeRabbit (e.g. you configure it on their server for your repo), from the repository or (new) config files in the PR?
Howon, you can stop posting that canned response. It's not helping the discussion in any way and matches the lack of detail the other commenters have pointed out.
https://github.com/n0-computer/iroh