"Twitter, what kind of bird are you becoming? Are you still that cute little bird that everyone loved, or are you becoming a scary bird of prey? We need you to clarify this ASAP," he wrote in the preamble to an online petition hosted at Change.org. "We, the undersigned, urge you, Twitter, not to betray the trust and goodwill of your ecosystem of millions of developers and users. And we urge you to clarify your intentions for your APIs and the huge ecosystem of third-party apps and services that rely on these APIs to connect to Twitter, right away."
Spivack is the CEO of Bottlenose, a social media dashboard and search engine currently operating in a free open beta--with advertising and commercial plans for social media monitoring to follow. Twitter is certainly one of the most important data sources for Bottlenose, but Spivack said in an interview that the issue is much bigger than his company. The problem is not so much anything Twitter has done, so far, as with lingering uncertainty about what it might do.
[ Read 5 Social Skills IT Pros Must Have. ]
Open application programming interfaces (APIs) have been a big part of the story of Twitter's development as a social network, allowing the creation of all sorts of apps for reading and writing to the Twitter stream or analyzing the content of Twitter posts. As Twitter the company has matured and tried to figure out a viable business model, however, its leaders have grown increasingly concerned that other companies were capturing too much of the service's revenue potential. Application developers, in turn, have become increasingly nervous that Twitter will pull the rug out from under them. Some users also worry that Twitter's new corporate leaders will ruin the service they love or turn it into "the next MySpace."
Since Spivack launched the petition drive six days ago, it has attracted more than 370 signatures toward a goal of 500, with those endorsing it including some prominent people such as John Perry Barlow, co-founder of the Electronic Frontier Foundation, and Binh Tran, a Klout co-founder.
Xavier Damman, CEO and cofounder of Storify, said his business is not dependent on Twitter API access but he signed because he agreed the messages coming from Twitter "have been really worrying." In particular, Twitter's statements leave too much room for speculation about what changes are coming, he said. "Twitter has been helped all along by developers who use the API to augment the system and do good things with it," Damman said, and if that stops Twitter won't really be Twitter anymore. "I think the problem is they actually don't know themselves what they are going to do," he said.
At the end of June, Twitter's director of consumer product Michael Sippey put out a blog post on delivering a consistent Twitter experience in which he said the company would be "introducing stricter guidelines around how the Twitter API is used." He reiterated concerns Twitter executives had been expressing for some time about applications that get between Twitter and its audience, interfering with the experience it wants to deliver. Ultimately, everyone understood that to also mean not getting between Twitter and its desire to deliver advertisements and create a profitable company.
That same day, LinkedIn announced it had lost the right to redistribute the Twitter posts of members on its own site. LinkedIn retained the ability to have status posts recorded on its own site reposted to LinkedIn, but said it would no longer be able to offer two-way integration. The end of that relationship led others to wonder who's next.
Since then, Spivack said he has been asked in every press interview how he will cope with losing access to the Twitter APIs, a question he can't answer because he doesn't know what exactly Twitter is going to do. "It was an announcement that we're going to make an announcement. We're going to be changing some stuff that's going to affect you, and we'll let you know. That has created quite a bit of FUD--fear, uncertainty, and doubt," he said.
Spivack doesn't object to Twitter's desire to profit from its own service, but he believes the simple solution would be to include advertising in API feeds and require third-party applications to display them, according to Twitter specifications. In the process, Twitter ought to come out ahead, expanding from an operation dependent on ads displayed on a single site and turning itself into an ad network. Twitter also could offer the option for application developers to pay for API access without that advertising. To the extent that Twitter is concerned about the display of its content, as well as its advertising, it can set terms and conditions for the handling of rich media posts, he said. The only thing that's unacceptable is to leave questions about the future of API access unanswered, he said.
In the end, Spivack suspects the action Twitter takes will be nowhere near as draconian as some have feared. "I've spoken with people at Twitter whom I know, and they've given me reassuring messages," he said. "Here's the problem: this vague rumbling they made created an atmosphere of dread in the industry, and it's causing real damage to their ecosystem and to their partners." Business plans based on innovative use of Twitter data can't get funding, investors are jittery, and all sorts of social CRM and social media analytics firms are seeing their future is in jeopardy, he said. "Everything is grinding to a screeching halt."