YouTube's road to HTTPS
youtube-eng.blogspot.com
YouTube's road to HTTPS
1–10 of 97 posts
Re: YouTube's road to HTTPS
#2> We found that HTTPS improved quality of experience on most clients: by ensuring content integrity, we virtually eliminated many types of streaming errors
Wow, what were carriers doing to the streams?!
Re: YouTube's road to HTTPS
#3> In short, some devices do not fully support modern HTTPS.
I'd love to know which devices, and what "modern HTTPS" features they don't support.
Re: YouTube's road to HTTPS
#4> We found that HTTPS improved quality of experience on most clients: by ensuring content integrity, we virtually eliminated many types of streaming errors Wow, what were carriers doing to the streams?!
Attempting to inject adds? Reduce the size by applying JPEG compression? :)
Re: YouTube's road to HTTPS
#5> In short, some devices do not fully support modern HTTPS. I'd love to know which devices, and what "modern HTTPS" features they don't support.
Android PayPal were originally going to stop supporting non TLS 1.2 (TLS 1.1, 1.0, SSL 2, SSL3) connections in June - they've now pushed this to next year: https://devblog.paypal.com/upcoming-security-changes-notice/
Re: YouTube's road to HTTPS
#6> We found that HTTPS improved quality of experience on most clients: by ensuring content integrity, we virtually eliminated many types of streaming errors Wow, what were carriers doing to the streams?!
It's long been known that some carriers purposefully degraded quality of youtube to keep from saturating their interconnections. That's the reason[1] behind the Google Video Quality Report[2]. Youtube does (did?) redirect you to a comparison of how well your ISP streamed content compared to others when there were streaming problems in some cases to combat this.
1: Well, I'm assuming, but it seems likely this was the main reason.
Re: YouTube's road to HTTPS
#7> In short, some devices do not fully support modern HTTPS. I'd love to know which devices, and what "modern HTTPS" features they don't support.
My NAS has security settings for modern, intermediate and old browsers that says it's to do with cipher suites they support -
Re: YouTube's road to HTTPS
#8What a strange thing to automatically (I assume) add to the end of these blogposts:
> Sean Watson, Software Engineer, recently watched "GoPro: Fire Vortex Cannon with the Backyard Scientist."
> Jon Levine, Product Manager, recently watched "Sega Saturn CD - Cracked after 20 years."
Re: YouTube's road to HTTPS
#9> We found that HTTPS improved quality of experience on most clients: by ensuring content integrity, we virtually eliminated many types of streaming errors Wow, what were carriers doing to the streams?!
Attempting to inject adds? Reduce the size by applying JPEG compression? :)
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
#10> In short, some devices do not fully support modern HTTPS. I'd love to know which devices, and what "modern HTTPS" features they don't support.
My NAS has security settings for modern, intermediate and old browsers that says it's to do with cipher suites they support - https://imgur.com/a/PmaUE
Those settings are likely to be derived from Mozilla's recommendations with the same names:
https://wiki.mozilla.org/Security/Server_Side_TLS
You can read the details, rationale, and information about supported clients there.