Why Is Twitter Scared Again? Oh Right
Late last week, Ryan Sarver (head of API and platform at Twitter) came out and announced that they would like it a lot if developers would focus more on stats and less on clients. Many people don't know this but, Twitter was basically jump - started into popularity by the myriad of clients that could access the API. In the early days, Twitter.com ( Ruby sometimes has scaling issues) was so unbelievably buggy that many of us early adopters relied heavily on these 3rd party clients just to access our tweets.
Now the folks at Twitter are asking these devs to stop? Something doesn't sound right...and here's why! Protect and defend instead of innovate and kick ass. Some strategy yah got there Dick.
What are the 3rd party clients you guys and gals are using or perhaps jazzed about at the moment? Anything cool coming down the pipeline that might be railroaded by this decision?