3 ms·
The original comment is absolutely correct in that if the video stream is delivered via HTTPS it is impossible to downsample it. Now, whether YouTube et al actu
by ryandvm 10y ago
The original comment is absolutely correct in that if the video stream is delivered via HTTPS it is impossible to downsample it. Now, whether YouTube et al actually use HTTPS for the video stream, I don't know...
- toomuchtodo 10y agoNot true. You can throttle packets by source or destination IP block, and by throttling the connection, the player will be forced down to a lower bitrate rendition. This is how T-Mobile performs their throttling, and could be done to any class of traffic. https://www.eff.org/deeplinks/2016/01/eff-confirms-t-mobiles-bingeon-optimization-just-throttling-applies https://www.eff.org/deeplinks/2016/01/eff-confirms-t-mobiles...
- WhitneyLand 10y agoSo what happens when there is only one bitrate available at 1080p and it's encrypted?
- toomuchtodo 10y agoYour player is going to stutter hard if it doesn't wait to preload enough of the content. Disclaimer: My last job was infrastructure at an Internet-only video news org.
- 3pt14159 10y agoIs it possible to multiplex from various IPs? IPv6 has a huuuuge address space.
- toomuchtodo 10y agoA pretty easy traffic pattern to identify and respond to (just like bittorrent or OpenVPN over SSL).
- hiou 10y agoAs an aside this type of thing gets me throttled pulling down 500MB+ git repos. Not T-Mobile specifically but Clear.
- jsnell 10y agoThe majority of video traffic on the internet is encrypted. But it doesn't need to be downscaled directly by the operator, since almost all streaming services will adapt the actual video quality to the observed bandwidth. All you need to do is detect video traffic (quite easy to do even if it's encrypted) and selectively throttle it. The servers will take care of the rest.
- trav4225 10y agoIt doesn't need to be downsampled, though -- merely rate-governed.