Tech companies weren’t the only ones up in arms after Twitter walled up its API. As Nieman Lab noted back in August, when the company said they just want to “deliver a consistent Twitter experience,” developers for newsrooms like the Washington Post and news apps like Storify and Instapaper had a collective panic attack. For services like the Post‘s @MentionMachine, which tracks presidential candidates on Twitter, developers were forced to rework the front end in order to match Twitter’s style of tweet embeds.
To clear the air–and perhaps to encourage newsroom tech teams to keep developing on its platform (as if social media dependent-traffic hounds had a choice anymore!)–Twitter is hosting “Office Hours” in New York City next week. In an email announcing the event, the company said the session was prompted by a flood of questions and concerns from news developers.
Love Thy Developers
After being acquired by Facebook, the facial-recognition service Face.com–a local hackathon favorite–shuts down its developers API. Too bad the company promised the exact opposite a few weeks ago. [The Next Web]
Speaking of outlawing clients, Dave Winer thinks Twitter’s API is looking mighty corporate. [Scripting News]
SecondLife is a success story, Read More
This is a guest post by Orian Marx, a serial entrepreneur obsessed with tackling information overload. He has a computer science background with expertise in Flash and Flex front-end development. He’s a born-and-raised New Yorker who likes to swing dance when he’s not working.
I want to make something clear from the start: I love Twitter, though sometimes I wonder if I’m suffering from Stockholm syndrome. I have devoted much of the last three years of my life to working with the Twitter API and continue to pursue building the world’s best Twitter client for professionals in the form of Siftee. Recently Twitter staff has been reaching out to developers with a renewed vigor in the hopes of recapturing some of the goodwill and enthusiasm that has been squandered in the past two years. I applaud them for that. The new developer discussion site and documentation portal are significant improvements. Jack Dorsey has reached out for feedback. I recently spent time on the phone with Jason Costa, Twitter’s developer relations manager, at his request. I think these are all good signs for the ecosystem.
With that said, there is a lot of feedback to give. This post is a technical one focused on the API itself, not on Twitter’s relationship with developers. Although it’s technical I’ve tried really hard to make it readable to “normals.” :)
Without further ado, here’s what’s wrong with the Twitter API …