News for hackers. Stuff that matters.
Re:Just one QUIC bit by breatheoften on Wednesday March 28, 2018 @08:28AM (#16697161)
There are still environments where active policies described by network operators to manage traffic flows is _required_ for users to make any productive use of the network ... I used to work on research ships — 50 people at sea for months at a time with satellite internet having only 256kbps (800ms latency).

It was abysmal to watch as over time everyone became completely dependent on internet connectivity for their computing needs as all services moved to the cloud. Trying to provide a useable internet experience in that context involved blocking as much as we could that users machines were doing (usually without their awareness) in the background that simply couldn’t happen from that network — making the trade offs to try and select for things that _could_ work was a huge challenge.

It seems like QUIC offers better fundamental performance primitives but no way to solve for protecting users from themselves in this kind of environment ...

Re:Just one QUIC bit by tangent128 on Wednesday March 28, 2018 @09:28AM (#16697455)
The"correct" answer there is probably to make the network limits explicit, by explicitly requiring a proxy server or organization CA installed in the client. QUIC should still work with middleware that actually terminates the connection instead of meddling from outside.
Re:Just one QUIC bit by marshray on Wednesday March 28, 2018 @04:06PM (#16701418)
Sounds like Android at least can be told via DHCP it's on a metered connection:

https://www.reddit.com/r/networking/comments/4wk4rw/dhcp_opt...