5 ms·

Attempting to inject adds? Reduce the size by applying JPEG compression? :)

TD-Linux 10y ago
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.
- dublinben 10y ago
  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.
  - ianlevesque 10y ago
    Not ideal but that's a lot less intrusive.
  - mhurron 10y ago
    > 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.
    - dublinben 10y ago
      If your ISP applies artificial traffic shaping, your ISP is broken.
      - rhino369 10y ago
        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.
        mahyarm 10y ago
        You can turn it off, but it removes the zero rating. Up to you either way.
        rhino369 10y ago
        I'm on the light package so I don't even get the zero rating.
      - amscanne 10y ago
        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.
      - mhurron 10y ago
        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.
        bisby 10y ago
        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.
    - azernik 10y ago
      That shaping should not be broken by HTTPS. The only things that would be affected by HTTPS is carriers munging the bits.
- chakalakasp 10y ago
  I used to think it was silly to use a VPN on a cellphone not on WiFi. Not these days, not so much.
- acdha 10y ago
  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 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.”

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.

dublinben 10y ago
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.
- ianlevesque 10y ago
  Not ideal but that's a lot less intrusive.
- mhurron 10y ago
  > 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.
  - dublinben 10y ago
    If your ISP applies artificial traffic shaping, your ISP is broken.
    - rhino369 10y ago
      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.
      - mahyarm 10y ago
        You can turn it off, but it removes the zero rating. Up to you either way.
        rhino369 10y ago
        I'm on the light package so I don't even get the zero rating.
    - amscanne 10y ago
      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.
    - mhurron 10y ago
      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.
      - bisby 10y ago
        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.
  - azernik 10y ago
    That shaping should not be broken by HTTPS. The only things that would be affected by HTTPS is carriers munging the bits.
chakalakasp 10y ago
I used to think it was silly to use a VPN on a cellphone not on WiFi. Not these days, not so much.
acdha 10y ago
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 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.”