Re:Open Netflix replacement API available
by Afforess on Monday November 17, 2014 @12:46AM
(#8617017)
It's unfortunate that consumers of the netflix API will have to resort to this sort of web-scraping solution. Web scraping is more complicated than using a provided API, and more computationally expensive for both the servers and clients. It's a lose-lose.
I can't really understand Netflix's decision to close down their API. Surely the cost of maintaining it was not so high that it was a worse alternative than this.
Re:Open Netflix replacement API available
by codeusasoft on Wednesday November 19, 2014 @01:12AM
(#8628530)
Netflix reason when we had our few phone conferences was more so because of data inaccuracy. A lot of developers were not updating Netflix data and thus it was reflecting poorly on them.
That was their reason for me wanting to close mine down, they felt I was reflecting inaccurate data.
Re:Open Netflix replacement API available
by mattmanser on Monday November 17, 2014 @07:27AM
(#8617846)
It's not lose for Netflix. The programmer time maintaining an API is much more expensive and restrictive then the few dollars in computational resources you allude to.
Re:Open Netflix replacement API available
by benbristow on Monday November 17, 2014 @04:35AM
(#8617482)
This looks really nice. While I'd probably be unlikely to use this; I'm sure a lot of developers would love this.
Nice to see some very simple wrappers as well!
If I could suggest an improvement; it would be to support other countries' Netflix's. The templates are very similar so it's a case of using a VPN on some of the scrapers to access other countries' Netflix.
Re:Open Netflix replacement API available
by Stoo on Monday November 17, 2014 @05:09AM
(#8617567)
"Finally the Flix/Netflix Roulette API will feature localization (finally), this will include all current regions Netflix is supported in and any future ones (its literally checking every second to see if a new country gets added)"
Re:Open Netflix replacement API available
by giancarlostoro on Monday November 17, 2014 @06:14AM
(#8617700)
A TOS applies to how you use the service, and what they would do if you violate their service i.e. terminate your account. I highly doubt Netflix would close your account if you used something like this, although they may email the author and tell them to discontinue development, that's another route altogether.
I can't really understand Netflix's decision to close down their API. Surely the cost of maintaining it was not so high that it was a worse alternative than this.
That was their reason for me wanting to close mine down, they felt I was reflecting inaccurate data.
Nice to see some very simple wrappers as well!
If I could suggest an improvement; it would be to support other countries' Netflix's. The templates are very similar so it's a case of using a VPN on some of the scrapers to access other countries' Netflix.