Do you have a source for that? The article you linked doesn&#x27;t say that, and <a href="https:&#x2F;&#x2F;www.eff.org&#x2F;deeplinks&#x2F;2016&#x2F;01&#x2F;eff-confirms-t-mobiles-bingeon-optimization-just-throttling-applies" rel="nofollow">https:&#x2F;&#x2F;www.eff.org&#x2F;deeplinks&#x2F;2016&#x2F;01&#x2F;eff-confirms-t-mobiles...</a> also confirms that no encoding is taking place.<p>Separately, the article you linked from techdirt has a major misunderstanding of the EFF piece.<p>It says &quot;EFF also discovered that T-Mobile&#x27;s earlier statement that it can&#x27;t detect encrypted video is also misleading, as the company now claims it can&quot;<p>But the EFF part quoted is talking specifically about http, not https, as a close reading will reveal.<p>Also, the EFF test is a bit inconclusive, because https might be slower than http for other reasons. It probably doesn&#x27;t account for the large differences they observed, but a better study would have tested http&#x2F;https on other carriers, and on a T-mobile phone with Binge On turned off, to isolate the Binge-on effect.