Andrew , Thank you for such a measured response. I'm not looking at the immediate action of stopping whitelisting by twitter. I must add, that, if a certain feature requires an application process, I had doubts in my ability to convince twitter, that, I really deserve to be in the list.
I believe I've also mentioned in my mail ,that , we, as a team/company, have already made arrangements which does not require us to use whitelisting. Perhaps, since, my initial mail was a rant, but, not a structured 'reply' it got lost in whatever I said. What I say is essentially this. Twitter seems to be discouraging developers whose products have the potential who increasing their userbase. It almost as If I'm hearing that, 'WE DONT WANT ANYMORE USERS' . We're tired of managing the existing number. I don't disagree that nobody should make plans on features which have no guarantees [whitelisting], that, they will continue in future. But, by putting such limits isn't Twitter running the risk of becoming just another product. The creation of the facebook development platform was responsible in spawning a market leader in gaming field i.e ZYNGA.But, These limits by twitter dont allow someone to think about a new idea. He will stop thinking that ; what if I get traffic ? Anyhow, twitter will block me if I cross their rate limit. How can an innovator think in such an environment? I'm not sure if you find this as conjecture. This , to me , is a logical line of reasoning. Anyhow, We ,as a team , have planned on working with a worst case scenario. twitter's search API is very important to us. We never planned for whitelisting, we dont need it. The only worry is if tomorrow, (hopefully), if we generate traffic from our product, will twitter just stop the 'SEARCH API' . We need to know that. Clarity in this will go a long way. I hope I haven't offended anybody here. These are views , since, we as a team , feel that we can create something path-breaking using twitter as our backend resource. We will only help twitter that way. Thanks & Regards Umashankar Das On Sun, Feb 13, 2011 at 11:48 PM, Andrew W. Donoho <andrew.don...@gmail.com>wrote: > > On Feb 13, 2011, at 08:53 , Umashankar Das wrote: > > Now, Twitter and it's API groups claim that, they, are putting artificial > limits of rates to ensure proper delivery for regular service. > > > > > Mr. Das, > > While you make many interesting points in your "rant", I think many of them > are conjecture and opinion. As reasonable people can > disagree about opinions, I've edited them out of my reply. I wish to focus > on some unambiguous issues. We each have to make our business bets > with respect to the Twitter platform. (I speak as the developer of ch@tter™, > an iPad Twitter client. In many ways, Twitter destroyed my > business opportunity when they purchased Tweetie and made it free. I mention > this for context and not as a cause to rant at Twitter. I'm making plenty > of money as a result of building ch@tter™. The iOS consulting business > is very healthy.) > > It is clear from this thread that many developers made, perhaps unwisely, > product plans based on Twitter's continued support for white listing. In my > case as a client developer, the increase of my API count from 150/hour to > 350/hour due to moving to OAuth totally removed my need for white listing. > If user streams was supported, I could easily live with 150/hour limit. If > they would stand behind their user streams API, I would switch to > it immediately. (Beta status is not, frankly, good enough. If they cannot > make a commitment to their new API, why should I? By my count, user streams > has been in beta for almost 6 months.) > > Changing a platform's API is hard. Twitter is discovering this the > hard way. Every developer has an investment they would like to preserve > in the status quo. That said, Twitter's API evolution practices, > presumably approved by their CTO, Mr. Sarver, are not, in my opinion, > helping their partners grow with Twitter. That they are turning off white > listing while not having yet made a production commitment to user streams, > is a great example of an evolutionary stumble. That they haven't announced > any other methods of enhancing Twitter's ability to scale while supporting > functionality enabled by the large white lists is an oversight. The outrage > expressed in this thread is good, unambiguous evidence of the stumble. > > Another example is the closed roll-out of promoted tweets. I think every > third party app developer would love to find a way to further > monetize their Twitter application. Twitter did announce that they would > find a way to allow their developer partners to participate with the > promoted tweets program. That has not yet happened. Currently, as Twitter > has made a floor price of $0.00 for iOS apps, I have to resort to Apple's > iAds to capture revenue from my labors. I don't mind but it does cut my > other market-making partner, Twitter, out of the revenue stream. As it > reduces my revenue opportunities, I think this is sub-optimal. I win when my > partner wins. > > A third example is the annotation feature. I am sure all of us could > find an excellent use for annotations. I have many ideas on how to use > them. But I cannot. > > A fourth example is Chirp? When is it? Will they hold it in a large enough > venue? Or is it going to be like their announcement of #NewTwitter. A major > announcement whose video was streamed by Robert Scoble? The sound was poor. > The image sucked. And, BTW, thank you Robert Scoble. Without him Twitter > could not have gotten their message quickly out. > > In contrast to these missteps, I have to publicly thank Mr. Singletary, Mr. > Kalucki and Mr. Harris. Without their constant engagement on this list, the > Twitter ecosystem would not be what it is. > > Overall, everyone needs to remember that we are dealing with a company that > publicly claims to not yet be trying to capture revenue from their platform. > We are seeing from their experiments the collateral damage. Rolling with the > punches is painful. That is the cost of trying to access the almost 200 > million Twitter users. > > What do I want? I want a better developer experience. Both Apple and > Microsoft show what a good experience can be. I want user streams, a > promoted tweet API and annotations. I hope Twitter can deliver these > technical features to enable new business opportunities for themselves and > the Twitter app ecosystem. Myself included. > > > > Anon, > Andrew > ____________________________________ > Andrew W. Donoho > Donoho Design Group, L.L.C. > a...@ddg.com, +1 (512) 750-7596 > > Knowing is not enough; we must apply. > Willing is not enough; we must do. > -- Johann Wolfgang von Goethe > > -- > 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 > -- 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