Raffi, You wrote, "...focus your efforts on that and just follow our lead with tweet rendering and interaction".
This approach perpetuates and aggravates the fears and hostility in the developer community that you (Twitter) sprouted when you bought Tweetie, and absolutely nothing has been said or done by Twitter to address or allay any fears or concerns that Twitter will, soon or at some point in the future, rake in another segment of developer- provided functionality. Since so much money and potential lie in analytics, it will not surprise me in the least if that will be the target of Twitter's next take-over. You've already clearly illustrated: a) The willingness and capability to grab a segment away from the ecosystem; b) The willingness and capability to guide and even force developers out of that segment. Meaning, you have the blueprint of how to do it to any of the other segments that you're now encouraging developers to focus on. This is like deja vu. It's the pre-Chirp discussion all over again. Much has changed and nothing has changed. Twitter has not yet answered the following question, even though it is a question on everyone's minds and has been since last year: "Why should anyone believe you will not encroach and push developers out of the segments that you now encourage them to focus on?" -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
