This is just... wow. The guy spends three years developing a product on Twitter's platform and they just kill it off with one e-mail? It's fair enough if they n

This is just... wow. The guy spends three years developing a product on Twitter's platform and they just kill it off with one e-mail? It's fair enough if they need to change their API policy, but at the very least they could have acknowledged all the work that he's done and found a way to help him and the other developers in the same position to make the transition as painlessly as possible. Not... whatever corporate BS this was. Given how much Twitter is struggling already, is this really the time to be alienating more of its community? Personally, I've had a really nifty side project that I've been working on since last year that I wanted to launch on Twitter's platform, but as of a month ago I've all but given up on actively developing it. All the people that I know on Twitter with whom I wanted to share it have either left already, or are only sticking around because as-of-yet there's nowhere else to go that does what Twitter does. So I'm curious to hear some perspectives on this: clearly the direction that Twitter has taken is making a lot of devs unhappy, but what would be the right thing to do? What sort of API access would people ideally want to see it provide? What would be the ideal best-case scenario necessary for the devs to want to start coming back and putting their time into building the ecosystem?