On Sun, Jan 31, 2010 at 8:26 PM, Cameron Kaiser <[email protected]> wrote: >> I think Twitter's engineering team does understand the issues. But I >> think the primary responsibility lies with us developers, and I for >> one don't see the point in investing effort building desktop Twitter >> applications, given >> >> a. They're tough to scale down to mobile platforms, and mobile usage >> seems to be where the growth and action are in social media, and >> >> b. oAuth or not, desktop applications are difficult to secure. >> >> c. The Streaming API isn't designed to play well with desktops / >> laptops / mobiles. > > So don't develop one. But, speaking as a dev who eats his own dog food, I > prefer to have a console open running TTYtter than mashing refresh all the > time in Camino. Desktop apps are a useful part of the ecosystem, and I > wouldn't be participating in Twitter anywhere near as much as a user if I > had a much higher barrier to do so or had to trust a third-party service and > add another layer on to do so on my behalf. I assume @funkatron's users > have the same opinion.
Yes, I write my own desktop apps too, but I don't distribute them. I never saw the need to use a desktop client when the browser worked just fine. Then again, I don't own a Mac and don't use Windows very often. Maybe a desktop client on a Windows or Mac makes more sense than it does on Linux. Assuming, of course, that a Linux desktop itself makes any sense - there aren't a lot of folks who agree with me on my choice of desktop. ;-) -- M. Edward (Ed) Borasky http://borasky-research.net "I've always regarded nature as the clothing of God." ~Alan Hovhaness
