News for hackers. Stuff that matters.
Re:YouTube's road to HTTPS by TD-Linux on Monday August 01, 2016 @02:43PM (#12204835)
When I had Sprint, they did in fact scale down and recompress all images in lower quality JPEG.

Some carriers even attempt to realtime transcode video into a lower bitrate. The implementations of this are universally poor and produce rather broken files.

Re:YouTube's road to HTTPS by dublinben on Monday August 01, 2016 @02:50PM (#12204897)
The more modern implementation of this (I'm looking at you, T-Mobile) is just to throttle all connections to content providers. They rely on the content providers' own adaptive streaming technology to deliver the appropriate 480p video when presented with a constrained connection.
Re:YouTube's road to HTTPS by mhurron on Monday August 01, 2016 @03:20PM (#12205135)
> The more modern implementation of this (I'm looking at you, T-Mobile) is just to throttle all connections to content providers.

If YouTube can't handle traffic shaping, Youtube is broken.

Re:YouTube's road to HTTPS by dublinben on Monday August 01, 2016 @03:46PM (#12205318)
If your ISP applies artificial traffic shaping, your ISP is broken.
Re:YouTube's road to HTTPS by amscanne on Monday August 01, 2016 @04:44PM (#12205784)
What's "artificial" shaping?

The average consumer ISP has an over subscription ratio of 70-to-1.

Unless you want to pay 70x as much for your "100mbit" connection, there are going to be times when packets get dropped.

Isn't it better to drop packets fairly among subscribers? No shaping would result in whoever is using the most dominating everyone else.

This basic principle is still neutral; you don't have to shape based on destination / content provider.

Re:YouTube's road to HTTPS by rhino369 on Monday August 01, 2016 @03:52PM (#12205370)
I should be able to turn it off, but I like that tmo throttles my video. I only get 2.5 gb, I don't need 1080p.
Re:YouTube's road to HTTPS by mahyarm on Monday August 01, 2016 @05:03PM (#12205957)
You can turn it off, but it removes the zero rating. Up to you either way.
Re:YouTube's road to HTTPS by rhino369 on Tuesday August 02, 2016 @12:50AM (#12207898)
I'm on the light package so I don't even get the zero rating.
Re:YouTube's road to HTTPS by mhurron on Monday August 01, 2016 @05:06PM (#12205988)
What the ISP is doing isn't any different than what any private network could do. If YouTube can not handle that, Youtube is not playing well with standard network practices and is broken at a technical level.

Your ISP doing traffic shaping is a question of if they should, not a technical question.

Re:YouTube's road to HTTPS by bisby on Tuesday August 02, 2016 @10:03AM (#12209975)
In this case, that's what "broken" means. Not that there is something technically wrong, but that they are doing things that they shouldn't.
Re:YouTube's road to HTTPS by azernik on Monday August 01, 2016 @06:34PM (#12206590)
That shaping should not be broken by HTTPS. The only things that would be affected by HTTPS is carriers munging the bits.
Re:YouTube's road to HTTPS by ianlevesque on Monday August 01, 2016 @03:20PM (#12205132)
Not ideal but that's a lot less intrusive.
Re:YouTube's road to HTTPS by acdha on Monday August 01, 2016 @04:05PM (#12205464)
The most common implementation of this appears to be from a company called Bytemobile which also injects some pretty buggy JavaScript into HTML content.

The good news is that you can disable all of their degradation by adding "no-transform" to your Cache-Control headers:

https://kornel.ski/en/proxies

“The standard HTTP header Cache-Control: no-transform which tells proxies not to modify responses was respected by all proxies I've encountered. This is amazing! It wins an award in the "Best Supported Obscure Header" category.”

Re:YouTube's road to HTTPS by chakalakasp on Monday August 01, 2016 @03:00PM (#12204980)
I used to think it was silly to use a VPN on a cellphone not on WiFi. Not these days, not so much.