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.)
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.
Coordination server does a lot apart from distributing IPs to the clients. Read the goddamn docs before spreading misinformation
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...
Also how do the public relays provides by Iroh compare with Tailscale’s public DERP servers, operationally wise?
DERP: very similar. iroh relay servers were initially modelled on DERP, but are now diverging more and more.