I’ve been intending to play with it more, it’s given me so many little project ideas that otherwise would be a pain
* fetch any sub-sequence of bytes, verified on send & receive * fetch sub-sequences of bytes in collections (sets of blobs / directories) * store on disk, inlining small blobs into the database for faster lookups * fan in from disk & the network * "multi-provider" fan in that can re-plan a fetch on the fly * should land support for WASM compilation (browsers) soon! https://github.com/n0-computer/iroh-blobs/pull/187
We're hard at work on making the API more ergonomic, but as a foundational protocol it's truly impressive. Rudi has been working with the BLAKE3 authors on both perf testing & the hazmat API.
disclosure: I work on iroh
> But Connection is Clone, so in principle there is nothing stopping you from cloning the wrapped connection and losing the lifetime tracking. Don't do this. If you work with connections from the pool, you should pass around either a ConnectionRef or a &Connection to make sure the underlying ConnectionRef stays alive.
Hmmm...
I'd like to see the incovenient API. Or maybe there's a bit more work that could be done to make it convenient? Is there an insurmountable problem that prevents completely hiding the underlying Connection?
[0]: vanadium.github.io
It uses a third server to facilitate initial p2p connections but I keep loosing/fail to connect to this server. I don't know if it's because of many restarts during development or something else.
Windows Defender nukes this from orbit, making it nearly impossible to ship to clients in a trusting fashion. But I guess any program which punches through the firewall is suspect.
throwup238•3mo ago
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.
mudkipdev•3mo ago
https://www.iroh.computer/proto/iroh-blobs
umanwizard•3mo ago
gbin•3mo ago
ttul•3mo ago
gear54rus•3mo ago
udev4096•3mo ago
John23832•3mo ago
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.
udev4096•3mo ago
Coordination server does a lot apart from distributing IPs to the clients. Read the goddamn docs before spreading misinformation
John23832•3mo ago
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...
xeonmc•3mo ago
Also how do the public relays provides by Iroh compare with Tailscale’s public DERP servers, operationally wise?
flub•3mo ago
DERP: very similar. iroh relay servers were initially modelled on DERP, but are now diverging more and more.
derefr•3mo ago
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.)