News for hackers. Stuff that matters.
Re:Retiring the Netflix Public API by cnanney on Friday June 13, 2014 @06:44PM (#7891215)
My 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 account functions like managing queues could be understandable, but I hope there is some kind of access to basic Netflix library data. Otherwise people will just turn to custom scraping solutions to get the data anyway.

Re:Retiring the Netflix Public API by yoda_sl on Friday June 13, 2014 @11:33PM (#7891992)
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.

Re:Retiring the Netflix Public API by psychometry on Saturday June 14, 2014 @01:35AM (#7892136)
If you only need movie information, that there are arguably better sources available now like TheMovieDB.
Re:Retiring the Netflix Public API by yoda_sl on Saturday June 14, 2014 @10:29AM (#7892826)
Unfortunately no, the project in question was specific to Netflix.