tbc0's posterous

I went on a twrant this morning. (twrant -- n. To tweet multiple times on a single topic in rapid succession because one loses one's temper.) I learned that you have to read your stream via twitter.com to see twretweets (twretweet -- n. Twitter's new native re-tweeting feature.) I tweeted it, and now I'll say it here in more than 140 characters. I refuse to use Twitter native re-tweeting until @hootsuite and @tweed support it! Until then, I will simply include tweets worth sharing in my Twitter favorites until more clients support twretweeting. I encourage you to do the same. And to drive home the point I'm going to tweet every time I would have twretweeted, pointing people to this Posterous. The first time I twretweeted I said that it was a no-brainer to use twretweeting instead of Twitter's good old "favorite" feature. But now that I've seen how they implemented twretweeting, I think they really blew it. They should have added a "share" button that works the same as "favorite." That's all twretweeting really is. They already have data on favorites, they just needed to know why people were using that flag. I only have a couple of reasons. Neither use means "favorite," which is a meaningless way to describe the feature. Sometimes I use it simply because I want to follow-up later. I'm reading my stream on my phone, and I need a workstation to do some real work that resulted from what I've read on Twitter while mobile. I would simply call this "flag," or "star" like Google. The only other reason I use "favorite" is because I think the tweet is worth sharing with others. That's the purpose that twretweeting addresses. And I do like the twitter.com implementation. Don't get me wrong. I'm cheering this feature on. I saw the tweet, I read @ev's blog, and I bought his explanation completely. But the Twitter team blew the rollout. It's not ready to use until enough clients have caught up and will include twretweets in my stream the way twitter.com does today. I only care about HootSuite and Tweed.