What does HackerNews think of quic-go?

Pingora, the proxy that connects Cloudflare to the Internet | Sep 2022

There is quic-go[1] but i don't think that it's sufficiently optimized[2-4] to be used for this kind of workload. caddy will use it to provide HTTP/3 by default[5] in the upcoming 2.6.0 release.

[1]: https://github.com/lucas-clemente/quic-go [2]: https://github.com/lucas-clemente/quic-go/issues/2877 [3]: https://github.com/lucas-clemente/quic-go/issues/2607 [4]: https://github.com/lucas-clemente/quic-go/issues/341 [5]: https://github.com/caddyserver/caddy/pull/4707

HTTP/3 Is Fast | Dec 2021

Expand Context ↕

For sure, as a Caddy maintainer, all credit goes to the contributors of https://github.com/lucas-clemente/quic-go. Early on this was mostly Lucas Clemente, but Marten Seemann has been the primary maintainer for quite a while now, including the transition from QUIC to HTTP/3. https://github.com/lucas-clemente/quic-go/graphs/contributor...

HTTP/3 Is Fast | Dec 2021

Caddy maintainer here - we still have it marked experimental, not turned on by default. There's still some bugs. The actual HTTP/3 implementation comes from https://github.com/lucas-clemente/quic-go which essentially just has one maintainer at the moment. I'm hoping the Go HTTP team throws some effort on HTTP/3 sooner rather than later.

QUIC and HTTP/3 Support Now in Firefox Nightly and Beta | Apr 2021

Expand Context ↕

Yes, as UDP allows hole punching. They're using https://github.com/lucas-clemente/quic-go

QUIC and HTTP/3 Support Now in Firefox Nightly and Beta | Apr 2021

Expand Context ↕

Do you mean libraries for backend languages, like Go and Java, or servers, like Nginx and Caddy? Because for Go there is the quic-go module[1], and since Caddy is written in Go, it already has (experimental) support for HTTP/3[2].

[1]: https://github.com/lucas-clemente/quic-go

[2]: https://caddyserver.com/docs/caddyfile/options#protocol

Website Fingerprinting on Early QUIC Traffic | Jan 2021

Expand Context ↕

As you know from carefully reading the paper, it states that they cloned the sites with HTrack and served them on their LAN with "Caddy Server2". Perhaps then we could guess that the version of QUIC they tested is the version of QUIC that Caddy is using: https://github.com/lucas-clemente/quic-go (v0.19.3)

Show HN: Gfile, a WebRTC based file transfer utility in Go | Apr 2019

Expand Context ↕

You may want to look at QUIC. It'll be part of http/3 and it's on top of UDP. There is a go library called quic-go [1] that works quite well.

I was recently playing with a similar thing and used the lib [2]

[1] https://github.com/lucas-clemente/quic-go

[2] https://github.com/binwiederhier/natter

QUIC as a solution to protocol ossification | Feb 2018

For those of you using Go, it's been an absolute pleasure to use https://github.com/lucas-clemente/quic-go.

FWIW.

Chrome/macOS users in The Netherlands cannot visit google.com or google.nl | Mar 2017

Expand Context ↕

I suspect they are throttling UDP traffic on "non-web" ports, traffic might look like torrent encrypted stream :). Anyway you can test whats going on with https://github.com/lucas-clemente/quic-go

Caddy – HTTP/2 Web Server with Automatic HTTPS | Oct 2016

For a fun time, run it with the -quic flag and browse your site in Chrome.

Thanks to work by Lucas Clemente and Marten Seemann, Caddy ships with a functional (but still experimental) QUIC server implementation[1] you can try right now. Your site will load better over slow connections or while you switch from WiFi to cellular, for instance.

There was a lightning talk by Lucas Clemente just last week at dotGo about QUIC; looking forward to the video being posted!

[1]: https://github.com/lucas-clemente/quic-go