Iroh

@iroh.computer

IP addresses break, dial keys instead. I'm iroh.computer from the folks at n0.computer, a modular networking stack in Rust 🦀

Please be aware that this morning at about 07:10 UTC a malicious version (0.3.10, now removed) of the arrayref crate was published. This crate is a transitive dependency of iroh, via blake3 and might have made it onto your (CI) machine if you happened to cargo update between 07:10 and ~08:10 UTC.

At the IETF126 meeting in Vienna this week? Want to chat about iroh? About QUIC? Multipath? Holepunching? Ping us!

What a week! 1.0 launch on Monday, 10k stars by Thursday. Thank you so much everyone for all of your support 😊

Bild

Let's collect some cool stuff people are building on iroh :) Post your thing and we'll try to repost ✌️ 🧵

@pvh.ca speaks truth, but there's one more corner in the design space: you can federate the infrastructure instead of centralizing it. That's the choice we made for iroh relays: you can run your own (it's OSS!), and endpoints connected to your relay can talk to endpoints connected to other relays.

pvh@pvh.ca · 7mo ago

All peer-to-peer systems have to compromise one way or another on this: they can decide that direct P2P is essential and simply fail, they can provide centralized fallback alternatives, or they can try to find/convince/incentivize another peer to route traffic on your behalf.

The version number doesn't do it justice. This is the foundation for 1.0 and for many exciting features that will happen under the hood during the 1.0 series. It is also a big step for our plan to build iroh on existing IETF RFCs and RFC drafts as much as possible.