Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

[insert yet another comment about having short product introductions at the top pf blog posts]

From their docs page:

> Iroh lets you establish direct peer-to-peer connections whenever possible, falling back to relay servers if necessary. This gives you fast, reliable connections that are authenticated and encrypted end-to-end using QUIC.





and iroh-blobs: provides blob and blob sequence transfer support for iroh. It implements a simple request-response protocol based on BLAKE3 verified streaming

https://www.iroh.computer/proto/iroh-blobs


How does the use case differ from e.g. Tailscale?

Tailscale is a system service / DevOps deploy-time architectural middleware tool for putting entire devices onto managed OS-level networks.

Iroh is a development-time library for building software that forms open decentralized application-specific networks.

The closer comparison for Iroh would be to something like libp2p. (Or maybe libzmq, given its toolkit-of-very-well-thought-out-primitives approach. I might describe Iroh as the decentralized complement to libzmq.)


I'm going to guess that the difference is that Tailscale lets your machines find each other within a managed flat virtual network where as Iroh lets your applications talk to each other without any regard to which machine anything is running on.

Not sure about tailscale coordination server but once you establish connection to a headscale server, the clients don't strictly need headscale after that (although it's recommended to keep it active). So, maybe the only difference is headscale acts as a relay for once

Headscale is just a open source implementation of the Tailscale coordination server.

The coordination server just provides the IPs by which you use wireguard to connect. It can see that metadata (what machines are in a tailnet), but not anything else.


I am well aware of what headscale is. Why would I even mention it if I didn't know about it? How about stop commenting just for the sake of it?

Coordination server does a lot apart from distributing IPs to the clients. Read the goddamn docs before spreading misinformation


> Not sure about tailscale coordination server but once you establish connection to a headscale server

I was responding to the context here.

> How about stop commenting just for the sake of it? Coordination server does a lot apart from distributing IPs to the clients.

But in general, lmao. Chill out bro.

edit: Looking through your comments, I see that this is common.

> Read the goddamn docs before spreading misinformation

https://tailscale.com/kb/1155/terminology-and-concepts#coord...


sounds like exactly the sort of thing missing from kde connect

I’m also wondering if it’s possible to use MoQ from iroh, for streaming unidirectional broadcast data that don’t need historical buffers, mainly to freeload on Cloudflare’s free MoQ relays.

Also how do the public relays provides by Iroh compare with Tailscale’s public DERP servers, operationally wise?


MoQ: yeah, MoQ runs on top of QUIC so you can run it on top of iroh. I think some version of this will happen sometime.

DERP: very similar. iroh relay servers were initially modelled on DERP, but are now diverging more and more.


Or zenoh?



Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: