Robin Thellend

Nevermind. My suggestion won't work. The only way this can work is if the stream ctx is tied to the conn ctx.

The problem with https://github.com/quic-go/quic-go/pull/4510 is that the context in the `http.Request` is no longer tied to the stream. The main purpose of the Request's context is to signal when the...

I think https://github.com/quic-go/quic-go/pull/4507 would be an improvement, but it wouldn't help my use-case. The ctx is buried too deep in the quic implementation. I have an alternative suggestion. It looks...

> This never properly worked. The context was derived from the send side of the stream, but you really want it to be derived from the receive side of the...

> @mattrobenolt @rthellend Could you take a look at https://github.com/quic-go/quic-go/pull/4510? Should we merge this PR? I will look at it today or tomorrow at the latest.

If I understand correctly, https://github.com/quic-go/quic-go/pull/4510 implements the original request that `ConnContext` be called only once per connection, without changing anything else. I think it is a very elegant way of...

This is not a bad idea, but it wouldn't be my first choice. Docker has lots of options for configuring logs: https://docs.docker.com/config/containers/logging/configure/

So, you won't allow local backup/restore on a phone? It seems like pretty basic functionality. Your FAQ says: > I don’t want to backup my stuff, I just want to...

I think the idea here is to make a backup of the encrypted data, i.e. export the encrypted files to external storage such that they could be restored if the...

And if the phone dies before the files are uploaded to the cloud?