Twitter’s new mobile developer conference is tomorrow. Marco Arment writes about whether developers should give Twitter another chance:
"Twitter started out as a developer-friendly company, then they became a developer-hostile company, and now they’re trying to be a developer-friendly company again. If I had to pick a company to have absolute power over something very important, Twitter wouldn’t be very high on the list."
Dave Winer responds that for now, we’ll be okay trusting Twitter:
"Twitter is not going to screw us in the short term. They need us as much as we need them. Independent developers are where wholly new ideas come from. You can't hire people to do that to work inside companies."
The unique tragedy with Twitter’s changing attitude toward developers is that so many of Twitter’s early innovations did come from third-party developers. The new leadership displayed an incredible disrespect for the value developers added to both the ecosystem and core platform.
Unfortunately in the “short term” it’s still happening. Not 4 years ago, not 2 years ago — just 1 month ago, TwitPic announced they are shutting down after a legal threat from Twitter. It’s a loss for the web, leaving millions of broken image links in old tweets. This latest third-party developer casualty from Twitter’s policies comes practically on the eve of their new developer conference.
I agree with Dave’s larger points, though, on mirroring content to your own blog in addition to Twitter and Facebook. His Radio3 is a step forward for RSS and the open web while still embracing social networks. We need more tools like it.
2 years ago I chose to stop tweeting from my personal Twitter account as a minor protest. I don’t expect everyone else to take such an extreme stance. We can agree on open formats and the power of microblogging while disagreeing on how to interact with Twitter.
(Skeptics say that leaving Twitter is a pointless gesture, like a pebble thrown into a river. The timeline flows on and the outrage is washed away as if it didn’t happen. If leaving doesn’t make an impact, why bother? But it does matter. It matters not for the change it creates directly for others, but for how it changed me. In the same way that writing an essay will solidify your thoughts on a subject, posting that last tweet has given me a new clarity from which to judge whether my own products are on the right track, living up to my ideals.)
Back to the present. On the flight up to Çingleton and back, I finally got around to reading the book Hatching Twitter. Since I was on Twitter near the beginning, I remember many events covered in the book: the launch at SXSW, the CEO shuffling, the names of early engineers who I’ve crossed paths with. I love how the book blends together things that I know are real with other details that must be more contrived or exaggerated, creating an engaging read that would seem to border on historical fiction if we didn’t know that it was basically all true.
Hatching Twitter captures the power struggles inside Twitter and fills a book with them. And that’s really the foundation for Marco’s post: based on Twitter’s history, we probably haven’t seen the last leadership change at the company. Twitter might have a strong future but it surely has an uncertain one.
My next product is about microblogging, and it has to launch in the real world where Twitter dominates. But I view that as a reality, not a feature requirement. I think I’ll be happier as a developer, and my app will actually be more compelling, if I design and build it for a world without Twitter.
✴️ Also on Micro.blog