9 ms·
Netflix and Fill
- justinsaccount 10y agoWeird.. $ curl https://techblog.netflix.com/2016/08/netflix-and-fill.html -vv * Trying 2607:f8b0:4002:c06::d6... * Connected to techblog.netflix.com (2607:f8b0:4002:c06::d6) port 443 (#0) * Server aborted the SSL handshake * Closing connection 0 curl: (35) Server aborted the SSL handshake Fails from at least the 3 locations I just tried across the country.. Google outage?
- Thaxll 10y agoWhy do you use HTTPS? The link is HTTP, their blog doesn't support HTTPS.
- vonmoltke 10y agoTheir blog is directing me to an HTTPS link when I go to "techblog.netflix.com". It does it even when I specify HTTP.
- justinsaccount 10y agoDo you have https everywhere installed too?
- vonmoltke 10y agoNo. Firefox seems to be doing this on its own.
- justinsaccount 10y agoAh.. https everywhere seems to think it should support it. Oddly have never had a problem with it until now.
- diggan 10y agoThis gets mentioned every time a blogpost from Netflix appears on HN. I've mentioned it too! https://news.ycombinator.com/item?id=12217900 https://news.ycombinator.com/item?id=12217900 According to kpcyrd, this is what happens: " I have the same issue, even though the link actually is http, my browser tries to open the https version, no matter what. It looks like https://netflix.com https://netflix.com had hsts with includeSubdomains at one point in time which my browser has still cached. "
- nathancahill 10y agoWhich is why you should only enable HSTS if you plan on supporting it permanently.
- peterwwillis 10y ago"But there's no reason to not use HTTPS! What could go wrong?" But, you know... we have to secure our blog posts from MitM...
- eterm 10y agoNo, you have to secure your blog posts because cookies against the top level domain can be in the request headers sent to the subdomain[1]. It's a bit bizarre you'd blame HTTPS, what is your alternative, don't use https? [1] I say "can" because it depends on how the top level cookie is set, whether the browser respects the secure flag, and individual browser versions.
- bpicolo 10y agoThe google docs diagrams are being 403d for me Edit: Working now :)
- drewg123 10y agoI've just notified the authors.
- rickcusick 10y agoLooks like permissions on the diagrams hasn't been set properly. They need to make the link viewable by anyone who has it.
- dankohn1 10y agoKudos on the excellent blog title pun [0]. [0] https://en.wikipedia.org/wiki/Netflix_and_chill https://en.wikipedia.org/wiki/Netflix_and_chill
- nomy99 10y agoOnly on hacker news would you need to attach a reference to something most people should know..
- EdSharkey 10y agoModern slang has no class. I'm pleased that I didn't know the term until I clicked the link.
- goshdarnheck 10y agoJust modern slang eh?
- jeremiep 10y agoYou do realize your slang was seen the same way by your parents and their slang was seen the same way by your grandparents right? Time changes, people don't.
- andrepd 10y agoQuite so, my dear fellow. It's ever so pleasant to cross paths with a fellow gentleman with class, unlike the rabble of today's youth. I do tip my hat to you dear sir.
- justinlardinois 10y agoRelevant xkcd: https://xkcd.com/1227/ https://xkcd.com/1227/
- TeMPOraL 10y agoNot everyone here is an US teenager. I'm grateful for the reference (though after reading it, I'm having second thoughts).
- niftich 10y agoThis is one of my favorite blogs, because they go into satisfying detail about how their stuff works; it's always entertaining to see a big company write about how they accomplish what is it they do. I wonder if they use HTTP or Bittorrent to serve out of S3; S3 can serve Bittorrent, and the protocol solves a lot of their 'fill hierarchy' optimization on its own reasonably well.
- merpnderp 10y agoWeird, I'm getting a Firefox not secure connection error. Port 80 forwards to 443, and then 443 in Firefox throws throws the error. Curl just aborts on 443 also.
- e28eta 10y ago> Because we can predict with high accuracy what our members will watch and what time of day they will watch it Not only can they predict it, but I imagine to a large extent they control what people watch. Our usage often involves browsing the recommendations on the home page and picking something. I wonder when (or if) the availability of content in a cache close to the viewer will play a role in the home page content? Obviously it already works in the other direction (cache what we think they'll want to watch), but do they penalize the ranking of a title (or category) because it hasn't been cached? It'd be a useful feature for Netflix because they could cut down their bandwidth costs. It could even be useful for some users: those who could watch a movie at full quality from a cache but their ISP can't deliver a full quality non-cached title.
- netflixuser 10y ago> Not only can they predict it, but I imagine to a large extent they control what people watch. Oh man, new sinister revenue stream for Netflix incoming. Next Google is going to realize that they can control which billboards or storefronts you drive by based on your Maps directions.
- CaptSpify 10y agoThey kind of already steer people around with maps. Looking for lunch places near my office is terrible. It's mostly larger places. Good luck if your a mom&pop shop. I've also noticed that Youtube keeps trying to steer me towards videos I don't want to watch, and I don't really have a good way of telling it to stop.
- dlandis 10y ago> Not only can they predict it, but I imagine to a large extent they control what people watch. This is similar to what happened with Google Play Music. They used to have a really nice feature that enabled you to browse through all genres and continue to drill down several levels into very specific sub genres. It was a great way to discover new music. The problem was people were streaming way too much music that was not optimally cached and it was causing scalability issues for them. The solution? Remove the subgenre browse feature and transition to a radio station-based approach. You now have the choice of a limited set of predefined radio stations, each with a limited number of tracks, which I assume are all cached in an optimized way, but you cannot drill down nearly as far into the sub genres. If you browse the google forums there have been thousands of comments about the reduced functionality over the past year or so.
- kristianc 10y agoThe title of this post shows such amazing self-confidence from Netflix in its own culture and tone of voice. At 90% of companies the size of Netflix (and even some self-important, bloviated startups) an equivalent title would have been an absolute non-starter. As a result you get websites that all look the same and sound the same. Kudos to Netflix, even in quite a small way, for having the confidence to do things differently.
- justinlardinois 10y agoI think it's more a reflection that the phrase "Netflix and chill" has become such a cultural touchstone―and a parody of itself―that even Netflix itself is in on the joke. Sort of like what this did for "Thanks Obama": https://www.youtube.com/watch?v=uhY9Zxv1-oo https://www.youtube.com/watch?v=uhY9Zxv1-oo
- bluthru 10y agoNetflix is cool enough to be in on the joke, but not cool enough to know that it's lame when a corporate entity has self-realization of the joke.
- adrusi 10y agoI think this is a bit different from when you get a mass email from a company along the lines of "We know you love to netflix and chill, so here's five new blockbuster hits we've added to our catalog". This reads like something written by one engineer and reviewed by their boss. It's not nearly as bad as the regular /r/fellowkids stuff.
- justinlardinois 10y agoI think the mass email would be amusing if they only sent it to people who watch certain types of content at certain times of day.