
For those of you who are in the Twitter "retweet" beta test, I have a word of advice: proceed cautiously.
Here's why. Currently, retweets that are executed via the Twitter web "retweet link" are visible to your followers who are using the web interface to read your tweets but are not visible to popular third party clients.
Let me say that a different way: popular third party applications are currently not displaying RTs executed via the Twitter web interface "retweet" link. In other words, these retweets are MIA in a follower's timeline in popular third-party clients. The exception: Tweetie2.
This may be a "cart before the horse" problem. In other words, third party applications may not have had a chance to integrate the new API. Or it may be that Twitter privileged Tweetie2 developers. I don't know.
But if most of your followers read your tweets using third party desktop clients, this "bug" could have a serious impact on your personal retweet rate in the short-term. Experiment wisely. And mindfully.
See the story in pictures on WiredPen.
I've never been concerned about my personal retweet rate. Should I be?
RT rates aside, there's still the courtesy conundrum of protected tweets. At times it can be a real challenge to respect a friend's right to Twitter privacy when they've shared some RT-worthy brilliance.
You're in Easy Mode. If you prefer, you can use XHTML Mode instead. |