[potatolicious]

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.

[theyCallMeSwift]

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.

[potatolicious]

> "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.