News for hackers. Stuff that matters.
Re:Netflix Pulls Plug on Public API by Animats on Sunday November 16, 2014 @02:46PM (#8615182)
APIs are something a service offers when it needs help to grow. Once the service gets big, the API goes away, or becomes a pay service.

Google once allowed search queries via a SOAP interface. That's gone. They also dropped RSS feeds. But the API for submitting paid ads, that works. The paid cloud services are fine.

Twitter doesn't like third party Twitter clients any more and will pull the API key of anyone who writes one. A third party client might have a spam ("sponsored tweet") filter.

Re:Netflix Pulls Plug on Public API by smacktoward on Sunday November 16, 2014 @05:04PM (#8615644)
> APIs are something a service offers when it needs help to grow. Once the service gets big, the API goes away, or becomes a pay service.

I wouldn't phrase it exactly that way. All the examples are of something much more specific: APIs go away when a company embraces an advertising-driven revenue model.

Google offered a SOAP API because back then they weren't an ad company. When they became an ad company the API went away, because you could use it to get Google search results without the ads. Twitter supported third-party clients because back then they weren't an ad company. When they became an ad company the API went away, because you could use it to read tweets without seeing the ads.

Once you decide your company is going to make its money via ads, the strangulation of any channel people can use to get to your service without seeing the ads inevitably follows.

Re:Netflix Pulls Plug on Public API by lukifer on Sunday November 16, 2014 @05:21PM (#8615711)
I agree that this is the pattern generally, but it doesn't explain Netflix's decision specifically, unless they're secretly planning an ad-based revenue model, which doesn't seem likely.
Re:Netflix Pulls Plug on Public API by x0x0 on Sunday November 16, 2014 @03:03PM (#8615229)
Twitter is back to trying to lure developers in; there will be another batch of whiny posts in 2 years when they pull the rug out from this new set. Devs should stop playing charlie brown.
Re:Netflix Pulls Plug on Public API by msie on Sunday November 16, 2014 @03:43PM (#8615368)
Did I miss something? What has Twitter done lately for devs?
Re:Netflix Pulls Plug on Public API by wahnfrieden on Sunday November 16, 2014 @03:57PM (#8615401)
Re:Netflix Pulls Plug on Public API by msie on Sunday November 16, 2014 @04:05PM (#8615424)
Yeah, that's a joke. What developers really care about is Twitter's API.
Re:Netflix Pulls Plug on Public API by AznHisoka on Sunday November 16, 2014 @08:33PM (#8616384)
I agree. Nobody cares about Fabric. Who cares if it goes down, your business won't die. If their API dies, you can bet a whole lot of companies and their employees are basically screwed. Hootsuite, Adobe Marketing Cloud, BrandWatch, Buffer, Salesforce, SimplyMeasured, Oracle marketing cloud, etc, etc.
Re:Netflix Pulls Plug on Public API by teacup50 on Sunday November 16, 2014 @03:33PM (#8615328)
Perhaps people will rediscover the value of standard protocols and platforms that allow for competing client AND server implementations.

Or not.

Re:Netflix Pulls Plug on Public API by voltagex_ on Sunday November 16, 2014 @04:22PM (#8615482)
I really wish XMPP had taken off. Perhaps the most important place for standard protocols is in chat applications - i.e. how we communicate with each other electronically. Email is unlikely to go away but if I want to communicate with all my friends I need:

* Google Hangouts

* Facebook

* Twitter

* SMS

* Whatsapp

* iMessage (cost prohibitive)

When really I should just be able to log into xmpp.voltagex.org and talk to everyone.

(Also, why isn't there a standard for "dialling" email addresses yet?)

Re:Netflix Pulls Plug on Public API by seanp2k2 on Sunday November 16, 2014 @11:38PM (#8616859)
GChat used to use XMPP, as did Facebook IIRC. I also remember reading that iMessage uses it, and HipChat definitely uses an extended version. These could all be made to work together, but how would that keep users on the site where they're force-fed ads? It makes a little less sense in the HipChat / iMessage use-case.

Basically the same reason that little is available via RSS these days, and what is always has the "click here to read the whole article on our site, where we can show you ads!" after a few sentences / paragraphs.

Re:Netflix Pulls Plug on Public API by kuschku on Sunday November 16, 2014 @06:07PM (#8615896)
Actually, you can do SMS, Facebook and Hangouts in one app.

There are SMS services who support XMPP, and additionally Facebook and Hangouts support the XMPP client-side. It’s not as convenient as sending from [email protected] a message to [email protected], but it still works quite nice.

Re:Netflix Pulls Plug on Public API by ivionday on Sunday November 16, 2014 @06:18PM (#8615946)
Isn't Facebook XMPP going away? https://developers.facebook.com/docs/chat/
Re:Netflix Pulls Plug on Public API by voltagex_ on Sunday November 16, 2014 @06:17PM (#8615936)
That's interesting. Which SMS services? (is SMS service a tautology?)
Re:Netflix Pulls Plug on Public API by corobo on Tuesday November 18, 2014 @04:52AM (#8623169)
Short Message Service service

Looks like it is yeah

Re:Netflix Pulls Plug on Public API by saurik on Sunday November 16, 2014 @04:20PM (#8615477)
> APIs are something a service offers when it needs help to grow. Once the service gets big, the API goes away, or becomes a pay service.

This isn't so cut and dry. iTunes offers database dumps, for free, to any developer building music discovery sites and apps: this is why virtually everything has a "buy this on iTunes" button. Walmart has an API for people who want to add "buy this from Walmart", as does Amazon (also Best Buy and Sports Mart, but they are not clearly dominating like Walmart and Amazon in their respective markets). There has to be something different about how this plays out for Netflix than for these other companies.

Re:Netflix Pulls Plug on Public API by walterbell on Sunday November 16, 2014 @07:12PM (#8616117)
Is there a database dump available for app metadata?
Re:Netflix Pulls Plug on Public API by kalleboo on Sunday November 16, 2014 @09:15PM (#8616528)
If he's talking about the iTunes EPF program, then yes.
Re:Netflix Pulls Plug on Public API by saraid216 on Sunday November 16, 2014 @05:18PM (#8615700)
Wasn't Google pretty dominant when their SOAP API was available? Aren't they less dominant now?