Hi Raffi So if I'm reading what you wrote correctly, simple clients that just display a timeline, post etc are thinking too small and there is no business there, something I can agree with.
However many of us have, what I'd call a value added client. Sure we have the basics of a client, but we have what I'd like to think are added value services such as tweet scheduling, augmented reality of tweeters around you, user streams, draft management, and so much more. Are we to think that these are actually going to be fine for the time being, so long as obviously we comply with the ToS. What you guys seem to be saying though is don't build clients because it won't make money, but some people seem to fail to grasp some of us develop apps like this because we enjoy it... it's a hobby and a passion and that doesn't always involve tons of profit. Services such as Seesmic started out in the simple Client business, remember Twhirl, etc. Sure they grew into something enterprise, but most of us start out at the bottom and with the basics. Richard On Mar 13, 2:39 am, Raffi Krikorian <ra...@twitter.com> wrote: > in reading your blog post, i think you're misunderstanding what > @*rsarver*wrote. > > the API is open -- i personally love seeing all the innovation around > getting content into twitter (/1/status/update). there is a cafe in france > who's oven tweets whenever its done baking. that uses the platform to get > content in there. there was a NYU project that enabled your plants to tweet > when they needed water. that uses the platform to get content into twitter. > then there are people who match tweets to context. seeing twitter in > action with a television show, or a newspaper article, or a conference, or a > band -- that's how people really understand and get twitter. they see it > through the lens of what's happening in the world. > > what @*rsarver* said, effectively, was building a business around > *simply*rendering > /1/statuses/home_timeline was probably-not-the-best-thing-to-do. please go > still innovate. just don't bet money on simply making an API call to > grabbing a user's home_timeline and rendering it. that's thinking too > small, and @*rsarver* is telling you that. > > On Sat, Mar 12, 2011 at 4:29 PM, Shannon Whitley > <shannon.whit...@gmail.com>wrote: > > > I was hoping that Ryan was just a few weeks early for his April Fools' > > post. > > > "Don't build clients?" It sounds like a bad joke. > > > I wrote a letter to Ryan on my blog in response to this post: > > >http://www.voiceoftech.com/swhitley/index.php/2011/03/a-letter-to-rya... > > > I know you guys can't be serious about this. Stage a mutiny if you > > have to, but don't let this boneheaded decision stand. > > -- > Raffi Krikorian > Twitter, Application Serviceshttp://twitter.com/raffi -- 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