Comments on: Twitter: No Plans to Build Desktop Clients

By: Doug Huber

Doug Huber — Mon, 20 Sep 2010 11:48:59 +0000

Dick Costolo, Twitter’s COO, expanded on the URL shortener at the Connections 10 conference in Indianapolis, Indiana last week. He said Twitter will be using a Columbian domain (www.t.co) as their URL shortener. Costolo said that having a URL shortener in house would allow them to police spammy links among other benefits.

By: jasson

jasson — Sun, 19 Sep 2010 11:13:05 +0000

They should look at Hashable. Very interesting co. in NY.

By: Alexander Ainslie (@AAinslie)

Alexander Ainslie (@AAinslie) — Sat, 18 Sep 2010 18:00:24 +0000

One more thing!

I understand that Twitter may not want to compete with their desktop client developer ecosystem even if they want to (which I suspect is the case). OpenSourcing the TweetieMac client would give Twitter an elegant way to say ‘we are not competing with you’ we are just supporting our OpenSource project where and when necessary.

I am confident that if Twitter OpenSources the TweetieMac code, the community will develop it into a robust ‘platform’ in no time.

Result: Twitter wins and its loyal Mac users win.

By: Alexander Ainslie (@AAinslie)

Alexander Ainslie (@AAinslie) — Sat, 18 Sep 2010 16:50:30 +0000

For those like myself who paid $’s to ‘support’ @atebits and his TweetieMac desktop client, Twitter should show appreciation and release the TweetieMac code as opensource so that it can be improved on by the community.

If Twitters view is that they will not update TweetieMac without releasing the code, then that is not acceptable.

What’s your take?

By: Williams: geen plannen voor eigen desktop client | Twittermania

Williams: geen plannen voor eigen desktop client | Twittermania — Sat, 18 Sep 2010 07:12:18 +0000

[...] Bron: Wired, GigaOM, Search Engine Land, Twittermania © [...]

By: James Mowery

James Mowery — Sat, 18 Sep 2010 04:16:06 +0000

Why would Twitter want to build desktop clients? If most of their users are currently using the website — which serves as a way to distribute advertising, page views, and other good-looking metrics — it would be somewhat silly to create a desktop application that might negatively impact page views.

They are obviously wanting to create an amazing application on the web, which makes perfect sense.

So why is it a shock that they don’t feel the need to build a desktop client? I think it would be a less-than-intelligent decision on the part to do so, unless the sole purpose was to convince users of other desktop Twitter apps to switch; therefore ticking off more third-party developers.

By: Jason Voidrum

Jason Voidrum — Sat, 18 Sep 2010 01:07:55 +0000

TweetDeck and Seesmic are doomed due to a fundamental flaw. They built a client before they built a server-side platform. Seesmic can add to their “client platform” all they like but without a robust server-side infrastructure to understand and organize the data as a whole and make intelligent decisions around how to surface it, they’re going to be left behind with the next generation of integration platforms like Flipboard. I’m personally keeping my eye on Cliqset and pip.io. Cliqset specically seems to have build an very robust integration service.

By: jasonwiener

jasonwiener — Sat, 18 Sep 2010 00:20:40 +0000

riiiiiight.