Robin Thellend

I think you're being purposely obtuse. If you don't want users to be able to backup their data without first going through your cloud service, just say so. But, if...

I agree this would be a nice feature. I don't know how feasible it is. It would require parsing all the udp datagrams, keeping track of all the quic connections...

@marten-seemann _TLS passthrough_ is a popular feature of network proxies / load balancers where a proxy terminates the _TCP_ connection, but not the _TLS_ connection. The proxy inspects the Client...

> > Among other things, the instrumentation for ingress/egress metrics (and everything that depends on them, e.g. bw limits) will probably need to be removed. I don't think it will...

I understand the idiomatic pattern. However, the consumer here is code that now expects a quic.Conn, for example https://pkg.go.dev/github.com/quic-go/[email protected]/http3#Server.ServeQUICConn It is now impossible to send an instrumented `quic.Conn` to `http3.Server.ServeQUICConn`,...

I think this is a case where the only solution that works is the right solution: make OpenStream() and friends return interfaces. I can't think of anything else that would...

To summarize: The API change in `quic-go` and `quic-go/http3` changed the `quic.Connection` and `quic.Stream` interfaces to concrete types. The motivation was to be idiomatic: return **concrete** types, accept **interfaces**. The...

> Where does the standard library do that? The standard library provides interfaces for interoperability everywhere. The `io` and `net` packages are prime examples. These interfaces are used in other...

io/fs comes to mind. https://pkg.go.dev/io/fs

I'm just answering your questions, not pushing on anything. Feel free to un-CC yourself. Let me know if you need anything else from me. My plan for tlsproxy right now...