51 comments

[ 3.3 ms ] story [ 104 ms ] thread
Grow up. Twitter doesn't owe you anything.
It's not about Twitter owing me, or anyone else for that matter, anything. If you release an API under the premise that developers are going to build apps that enhance and refine your existing service, then it is your responsibility to maintain a fair and open attitude towards them.
Responsibility is a strong word that is unwarranted. It would be nice for Twitter to continue to operate the API in an egalitarian and fair manner. They are under no responsibility to do anything.

But that's besides the point. The crux of it is:

Twitter took you all for a ride, and screwed you at the end. Your solution is to put together an online petition calling on the big bad man to see the light and do the right thing...?

You've got nothing on Twitter, they have no reason to listen to any of you. It's time to cut your losses, move on, and learn your lessons about building on closed platforms.

I agree that they have no reason to listen. In all likelihood, no single thing that any one person can do is going to get them to care at all. It's more about the collective voice and reiterating that you can't treat your developer community like crap.

Even if Twitter never listens, if this (or anything I write for that matter) causes anyone to think before they make a poor policy decision for their dev community, then I'd be a happy camper.

> "It's more about the collective voice and reiterating that you can't treat your developer community like crap."

But they can. The rode the 3rd party ecosystem all the way to the top, and now you're no longer needed. They can do whatever they want, which really sucks, and is kind of a dick thing to do, but even collectively you (plural, as in the whole of Twitter's dev base) have no sway over Twitter now.

I'm not condoning Twitter's actions, but IMO petitioning them when it's clear that this is the result of a major strategy shift, is just wasting your breath. It will aggravate you and be ultimately useless.

well Twitter certainly does not want Developers, to build successful apps using their API's. So the only way to solve this problem would be just, stop using their services.
You can't effectively say "they don't owe me anything" and say "they owe us a fair and open attitude" in the same sentence and expect to be taken seriously. They don't owe you anything. You don't pay them for anything. There's risk in piggy backing on another service. There always has been and always will be. This same reaction occurs every single time an API gets closed, changed, or altered in ways that developers don't like.

If anything, you provide a disservice to developers by invoking and promoting such a, pardon me but, whiny attitude towards something that should you should understand to be basic business.

Twitter does owe a fraction of its success to its developer ecosystem. By upsetting said ecosystem, they're hurting themselves.
I'm sorry but don't see what that has to do with the misplaced sense of personal entitlement.
It's not about entitlement so much as don't piss off the people who add value to your platform
I'm having a hard time viewing "responsibility to do something" and "owing someone something" as distinct ideas.
Actually, they do. Maybe not legally, but practically, Twitter owes many of its users to a handful of successful API clients. You can't just "use" developers (or, companies) to build up your user-base, and then as soon as it gets convenient for you, just ditch 'em all together...
> You can't just "use" developers

Actually, you can, they did, and any developers who thought they were entitled to anything from Twitter don't understand platform risk and learned a lesson.

At some point you start losing users who are affected by apps they use suddenly not working any more. If they care to find out why it makes a bad impression. If it happens multiple times they will think about switching to a rival service. There's virtually nothing keeping users on Twitter if a rival service popped up and their friends started moving there.
> There's virtually nothing keeping users on Twitter if a rival service popped up and their friends started moving there.

That's like saying, "There's virtually nothing keeping people on Earth if we develop cheap, reliable, faster-than-light space travel."

So you're saying creating a rival service to Twitter would be as hard as creating faster than light space travel?

All I'm talking about is gradual migrations like the ones from geocities and myspace. In the case of those services users had a lot of content they'd created that they had to leave behind. By it's ephemeral nature Twitter has very little of that.

No, I'm saying that the value of Twitter isn't the product itself, it's the people using it. I don't get on Twitter because of the allure of a 140-character-limited textbox. I get on Twitter because it's the only place I can receive regular personal updates from my idols, role-models, and colleagues, and even engage them in conversation. The more people on Twitter, the more valuable it becomes to me.

You can build a rival service if you want, but nobody will use it until it provides value, it won't provide value until people use it.

By that logic everybody would still be using Yahoo search
You're still missing the point. Search doesn't have lock-in via network effects. If all my friends use Yahoo search, it doesn't make my Yahoo search experience any better.
Then how about myspace?
MySpace was a thriving site with powerful network effects. However, Facebook was started just one month later, not years and years later. By contrast, attempts to dethrone Twitter come 6+ years after Twitter's founding.

Also, MySpace was a technical fiasco. (Although it wasn't quite as bad as Friendster, which was so slow it was unusable.) Facebook and Twitter are never going to allow pages to become painfully slow, have unreadable backgrounds, or blare music automatically.

Thirdly, Facebook's network effects were more powerful than MySpace's. Their school-based distribution strategy guaranteed that your relevant friends would be on the service. Features like "events" gave everyone a reason to join. And, ultimately, Facebook appeals to everyone age 4 to 100+. MySpace's main appeal was to music-loving teenagers. The more people you appeal to, the stronger the network effects.

Long-story short, it's not impossible to beat Twitter at its own game. But it's really, really fucking hard. It's not simply a matter of building a slightly better Twitter. Likely, Twitter would have to fuck up their basic user experience in a major way, AND you would have to devise an extremely superior user acquisition model.

Of course you can.

Just like the developers would ditch Twitter for the next big thing if it ever pulled a MySpace.

There was a mutually beneficial relationship that is no longer (as) beneficial to one of the parties.

To continue the analogy it would be as if George Washington agreed to become King instead of continuing the revolution and becoming president. Twitter promised to be a platform. A shining message bus on the hill. Twitter rejected the revolution and chose Kingship and monarchy. Are you surprised that people after laying down their time, their content, their development effort, and their dreams are a little pissed?
> Twitter promised to be a platform. A shining message bus on the hill.

Serious question: Ignoring that little bit of melodrama/hyperbole in the last sentence, is this true?

I'm sorry, but this is absurd. It's not tyrany and oppression, it's Twitter's API and they set the terms they want. You agree to those terms (and to the fact that Twitter can change them at will) the exact moment you start using the API.

Twitter won't be affected in any way: they already said that they don't want third party clients. Developers creating apps that Twitter accepts (analytics, social media for business, etc) won't stop supporting Twitter (they would lose users, opportunities and money). Only developers who create "non-OK" apps would join this, and if we did Twitter would be happier than ever as they stopped us without any action on their part.

And no, I don't support Twitter API changes, but we knew that we were taking risks when developing for a closed platform.

EDIT: added last paragraph.

The tyranny and oppression bit is satire. And disallowing the creation of third party clients is only a minor piece of a much larger puzzle. When good services like IFTTT are forced to stop using the API, there's obviously something wrong.
Twitter removed access for Instagram, Linkedin and Tumblr - IFTTT chose to remove features based on the new policy changes.
TC reports that IFTTT was actually infringing terms before the API changes: http://techcrunch.com/2012/09/20/ifttt-has-actually-been-in-....

I suppose that they've just noticed it and decided to take it down.

And yes, of course there's something wrong. It's not fair to grow helped by third party apps and them trash them, but, as I said, we all knew that this could happen. We can't trust that any company won't be evil during all of its lifetime, specially when that company needs to show real money to investors.

I don't think you know how to use satire, then. You're making a mockery of your own cause by injecting satire into this, and you come off as ignorant and ridiculous.
> We hold these truths to be self-evident

Really? Really guys? We're going to invoke the Declaration if Independence on an impotent campaign page about Twitter?

Just stop using Twitter. Problem solved.

Please just change the heading font to something more readable!
"Fork the project on Github, and add yourself as a signer in a pull request."

Seriously? Just because they redesigned the profiles to look like Facebook that doesn't make the forks the new "like".

I actually thought that the whole "fork to add yourself" thing was interesting, in that it would add a tiny bit of weight to the signatures. The bar for signing is to have a Github account, and to know what "fork" and "pull request" are. The probability that someone who can add their signature is actually a developer is presumably somewhat higher than if there was a big green button that any disgruntled user could casually press.

[EDIT] I don't use or care about Twitter, so I'm not trying to defend the goals of this particular petition. I just thought "fork to sign" was kind of interesting.

Say this catches on and you have two push requests, which one are you going use, because odds are you need to merge the second one by hand. This is not practical, but at least you get a fork.
I'll gladly manually merge in this case. It doesn't scale obviously, it's more novelty than anything else.
Has anyone actually offered Twitter money for the API? Like, give Twitter a reason to allow access to their rather valuable data?
What percent of developer frustration falls under "We're making money off Twitter without paying Twitter anything and now we're upset that we can't do that anymore"?
I'm guessing... 100?
I clicked for the headline but won't sign it because because it would mean I still have interest in using twitter as a developing platform and I don't.

I rather just ignore it and let it fade away and hope it to take all it's egotic celebrities, teenies, morning-tv-moms, smartasses, attention seekers, ads, media & marketing businesses, and all the rest of waste with them, feeling good!

Develop for status.net then? They don't have the user base, but if you make a killer app that runs there but not on twitter, well, you'll still win. If not, it's twitters fault they will fail when all 3rd party devs get new projects.
The man who controls the press, controls the speech.

Twitter undeniably controls the press in this case - they can do whatever they feel like.

I see there are about 10 signatories. Wow. Big :-/

Would a better "declaration-of-independence-by-github-fork" be to encourage people to fork tentd, and install to <insert free hosting service here>