4 ms·
Do you have a source for that? The article you linked doesn't say that, and https://www.eff.org/deeplinks/2016/01/eff-confirms-t-mobiles-bingeon-optimization-ju
by ikeboy 11y ago
Do you have a source for that? The article you linked doesn't say that, and 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... also confirms that no encoding is taking place.
Separately, the article you linked from techdirt has a major misunderstanding of the EFF piece.
It says "EFF also discovered that T-Mobile's earlier statement that it can't detect encrypted video is also misleading, as the company now claims it can"
But the EFF part quoted is talking specifically about http, not https, as a close reading will reveal.
Also, the EFF test is a bit inconclusive, because https might be slower than http for other reasons. It probably doesn't account for the large differences they observed, but a better study would have tested http/https on other carriers, and on a T-mobile phone with Binge On turned off, to isolate the Binge-on effect.
- fryguy 11y agoIf you look at the chart about halfway down, the "Normal" (red) is HTTPS, and the "Binge-on" (blue) is HTTP.
- ultramancool 11y agoYes but they could easily add the ability to do this over HTTPS too by using SNI or knowing the CDN IPs.
- ikeboy 11y agoExactly. The part about detecting video is specifically binge on/http, and the techdirt article completely misunderstands it and claims it's talking about encrypted video.