Noq: n0's new QUIC implementation in Rust
od0
179 points
24 comments
March 19, 2026
Related Discussions
Found 5 related stories in 51.1ms across 3,471 title embeddings via pgvector HNSW
- Quad9 Enables DNS over HTTP/3 and DNS over QUIC itchingsphynx · 54 pts · April 02, 2026 · 52% similar
- Show HN: Open-source distributed quantum compute network cadillion · 11 pts · April 02, 2026 · 51% similar
- Show HN: I built a DNS resolver from scratch in Rust – no DNS libraries rdme · 92 pts · April 02, 2026 · 51% similar
- An incoherent Rust emschwartz · 160 pts · March 23, 2026 · 49% similar
- Rust zero-cost abstractions vs. SIMD Sirupsen · 14 pts · March 03, 2026 · 49% similar
Discussion Highlights (8 comments)
tekacs
https://github.com/quinn-rs/quinn/issues/224#issuecomment-38... It's lovely to see the polite and respectful back and forth in this comment thread where the Iroh folks are talking about deciding to fork. :)
jeffbee
I was just reading the QUIC multipath RFC. Didn't it come out literally yesterday? I guess it's common to have the implementation foreshadowing the RFC but it's jarring to see them back to back like this.
adityamwagh
Love the folks from n0. I regularly use their sendme cli for peer to peer file transfer!
agg23
iroh seems like a very well positioned product in the era of people rapidly building applications for personal use. I'm really interested in seeing how they continue to grow. I personally have been looking off and on at providing an "app relay" using it, where people can get an OSS, self-hostable (if desired), zero config way to remotely access their app/data on their network. This would be separate than a "network relay" (a la Tailscale), as this is done selectively as part of the application server and client, requires no knowledge or configuration as the user, and exposes a much smaller surface area.
dangoodmanUT
The iroh team keeps cooking, unreal. I’m excited to have a weekend to just sit down and tinker with iroh, it’s been on my list for a while. I want to make an overlay network like nebula with it
Kazik24
Excuse me if this is explained somewhere, but how does noq/iroh relays QUIC packets between peers? How does relay know which QUIC packets it receives should be sent where, since QUIC is famously hard to track? Do you stream to relay new/retire_connection_id packets through different connection so that it can link them to specific peers? Or is the relayed QUIC wrapped in different protocol?
mrbluecoat
> noq (”number 0 QUIC”) Wouldn't that be n0q then?
superkuh
Can this establish an QUIC connection without the other end having a CA cert? Or, like most other QUIC libs will it default to only allowing connections to corporation approved domains?