I really don't buy the author's argument for more features. 1) He claims that there are all these features they could have just dropped in. But none of the fea

I really don't buy the author's argument for more features. 1) He claims that there are all these features they could have just dropped in. But none of the features the author describes seem like hit-me-over-the-head obvious features. I can live without "...tab-completion, threaded conversations, better URL shortening, marking of new tweets since last visit, in-line pictures, @replies from people one is not following in the main stream or groups yet..." 2) He states: "...one would think they’ll focus on enhancing the experience of using and developing Twitter apps, which in this case it means implementing OAuth. Yeaaah…wrong. OAuth has been made available just recently (before that, only selected developers could try OAuth) and is still in beta." But I wonder if the author has ever tried to implement a working, scalable OAuth system. It's a major pain in the ass and by no means a panacea. HTTPS + HTTP Auth is much more straightforward. I don't even think I would call Google or Flickr's OAuth systems perfect yet. They still have huge usability gaps that the end user has to get over (redirect to log in), let alone the technical issues that are likely lurking behind the scenes. Overall it seems like the author is focused too much on the idea of features for features sake and not whether Twitter has found a niche and done well limiting their service to meet the needs of that niche.