"Thank you to all of the developers who have participated in the ecosystem throughout the years." I'm not sure "thank" is the word they wanted.
well, it has a vowel and ends with 'k'.
Retiring the Netflix Public API
41–50 of 79 posts
Re: Retiring the Netflix Public API
#42R.I.P. NetflixItNow - a weekend hackathon Greasemonkey/Chrome extension that sent you an email when user-selected movies became available for streaming (not just disc delivery).
Though the project was short lived, I am very sad that it is no longer possible to implement similar projects.
Netflix API code (very simple): https://github.com/swanson/netflix-it-now/blob/master/check_...
Video demo: https://www.youtube.com/watch?v=h-zXOUsyXjA
Entire repo: https://github.com/swanson/netflix-it-now
Re: Retiring the Netflix Public API
#43My comment from an earlier post: I was disappointed to get that email, I have an API key and am using it for an ongoing (small) side project of mine. It seems counter to everything else Netflix engineering promotes with its tech blog and open source contributions. To be so public and open on one hand, and then shut down the public API on the other seems strange. Trying to cut down on third-party access to user accoun…
Same here, have a working side project that has been working like a clock watch for the past 3 years, with a few thousands regular users. I will now need to see if scraping is a solution that can work. At the same time, when they announce last year they were stopping the new API keys, I was wondering how long it will take for them to terminate the existing ones.
If you only need movie information, that there are arguably better sources available now like TheMovieDB.
Re: Retiring the Netflix Public API
#44> To better focus our efforts and to align them with the needs of our global member base, we will be retiring the public API program What a sad statement, there is no need for this corporate-drone talk. "We're shutting it down because it doesn't make us money, and we think we will be better off being a closed platform" would have ringed much better, not necessarily in these words. Honesty is always appreciated.
> What a sad statement, there is no need for this corporate-drone talk. I've always wondered if PR-types think that people "buy" stuff like this. It's somewhat expected from "old" companies but you would think a company like Netflix would be different.
[deleted]
Re: Retiring the Netflix Public API
#45This is the problem with modern web companies:
Protocols, not companies. There should be a Netflix protocol that any business could host. There should be a Twitter protocol so anyone could set up a Twitter server.
Re: Retiring the Netflix Public API
#46> To better focus our efforts and to align them with the needs of our global member base, we will be retiring the public API program What a sad statement, there is no need for this corporate-drone talk. "We're shutting it down because it doesn't make us money, and we think we will be better off being a closed platform" would have ringed much better, not necessarily in these words. Honesty is always appreciated.
Well, nobody wants to be the bearer of bad news. Being honest about these things usually means it will be seen as bad news. So you try to shift the focus to make it seem like the opponents (customer in this case) need was the trigger instead. Keeping some of the applications was a nice touch in addition to, apparently, announcing some kind of partner program.
They should read through the http status code list again though. 404 means that the server is currently unable to find the resource requested. 410 means that the resource is gone and never expected to return. Sure, I'm being picky but if they are refocusing their development efforts it doesn't seem to much to ask that they read up on http status codes and use them correctly.
Re: Retiring the Netflix Public API
#478 projects made that they are now incorporating into the product proper.
These 8 projects were at cost of management of the public API.
If true that more projects of equal caliber will be developed in the future, what is the opportunity cost of maintaining the API? How would you measure this opportunity cost?
Corollary: If Netflix had gone Tesla with the public API, I'm talking a full developer tool marketplace platform- what would be the opportunity risk/reward conversation look like? I'm thinking would be a very valid strategy for cornering the video media marketplace, setting the groundwork to take a bite out of YouTube/Twitch/etc's marketshare.
Re: Retiring the Netflix Public API
#48Writing was on the wall as soon as they stopped releasing API keys.
Re: Retiring the Netflix Public API
#49> To better focus our efforts and to align them with the needs of our global member base, we will be retiring the public API program What a sad statement, there is no need for this corporate-drone talk. "We're shutting it down because it doesn't make us money, and we think we will be better off being a closed platform" would have ringed much better, not necessarily in these words. Honesty is always appreciated.
>because it doesn't make us money
false: it's provided them with 8 projects worth incorporating into the project proper.
Re: Retiring the Netflix Public API
#50> To better focus our efforts and to align them with the needs of our global member base, we will be retiring the public API program What a sad statement, there is no need for this corporate-drone talk. "We're shutting it down because it doesn't make us money, and we think we will be better off being a closed platform" would have ringed much better, not necessarily in these words. Honesty is always appreciated.
Well, nobody wants to be the bearer of bad news. Being honest about these things usually means it will be seen as bad news. So you try to shift the focus to make it seem like the opponents (customer in this case) need was the trigger instead. Keeping some of the applications was a nice touch in addition to, apparently, announcing some kind of partner program. They should read through the http status code list again t…
I think the point is that the resource requested won't exist anymore.