The war for convo starting:

SNIP

Not all developers are happy, and many see this as the latest change from a company that already has a shaky history with third party applications. As one such developer, Aaron White, wrote today, “I’m done developing for Twitter…They’ve demonstrated not once to me, but twice, that they have no desire to work with developers, but rather antagonize them as they see fit.”

So what’s a LinkedIn user to do? Not content to sit idly by while Twitter changes the rules of the game, Roslansky and LinkedIn suggest that users shift their order of operations. The post on LinkedIn’s blog, as well as an email blast to LinkedIn users, advocated starting conversations on LinkedIn and syndicating them to Twitter, rather than vice versa.

It's clear that Twitter believes that developers exist to serve their interests:

He outlined the company’s desire to “build engaging experiences into Twitter” and allow “developers to be able to build applications that run within Tweets.” In other words, Twitter wants to be the story, not just the headline...

Twitter’s latest implementation, called Twitter Cards, will display headlines, photos, bylines and teaser blurbs for articles and other content around the web.

But Twitter still has no API to show you replies to a tweet. The APIs they do have are unreliable.

They really don't care about developers at all: http://restrictionisexpression.com/post/26144987502/im-done-developing-for-twitter

Compare this with Apple, who do their best to give developers incentive to develop for their platform.