Live data from Hacker News

Noq: n0's new QUIC implementation in Rust

iroh.computer

1–10 of 43 posts

Re: Noq: n0's new QUIC implementation in Rust

#4
post #2

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. :)

I very much agree, a nice contrast to so much open source drama

Re: Noq: n0's new QUIC implementation in Rust

#5
post #2

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. :)

I very much agree, a nice contrast to so much open source drama

disclosure: I work on the team behind noq. Can't emphasize enough that the quinn maintainers are really lovely people, and quinn is an excellent project.

Re: Noq: n0's new QUIC implementation in Rust

#6
post #3

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.

It's been a draft for a long while, and was only recently approved

Re: Noq: n0's new QUIC implementation in Rust

#8
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.

Post reply on HN