> 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. -- ------------------------------------ personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * [email protected] -- LET'S GO FORWARD ... INTO THE PAST! ----------------------------------------
