RT done wrong

on

Retweet annotated with the new Twitter metadataSome time this summer Twitter announced its RT (retweet) API, a structured way of expressing the forwarding (often with comments) of others tweets that has, until now, been expressed informally by prepending the letters RT to another person’s tweet. The practice of retweeting (described in a forth-coming paper by danah boyd, Scott Golder, and Gilad Lotan) has evolved several conventions for crediting the source and incorporating comments. In addition to forwarding and commenting on the message, it can also serve as a useful mechanism to introduce people to others worth following.

The new API formalizes this notion, but also subverts established practice.

At the time the API was announced, I had mixed feelings about it:

By specializing and formalizing its capabilities Twitter may be undermining its position as a generic communication tool that people can use in whatever way they chose. One beauty of Twitter is that it can be so many things to so many people with a simple API. If the trend for adding more features continues, Twitter may reduce the versatility of its messaging system, both from the application programmer’s and from the end-user’s perspective.

The new mechanism ignores the important social aspect of commentary that is part of the existing RT practice and replaces it with an automated rebroadcast of the previous message, annotated with your credentials as the retweeter. The interface prompts you to reetweet,

Prompt for a retweetand if you click Yes, merely rebroadcasts the selected tweet as your retweet. It does not give you an opportunity to annotate it with your own take on the subject of the tweet. While the new style of retweeting doesn’t add to the length of the message because the retweet information is now carried separately from the text, the gain of a few bytes doesn’t seem to be warranted by the loss of an important social function.

Of course an argument can be made that the fideility of the channel is improved by removing the ability to edit the message being retweeted. The boyd et al. paper cited above documents some of the kinds of miscommunication caused by retweets, including changed attribution, changed meaning, and viral spread of bogus information. Yet removing the ability to highlight, to personalize, and yes, to edit, while giving credit to the originator in favor of preserving the message verbatim is throwing the baby out with the bath water.

It’s also interesting that Twitter chose to emphasize the “follower” notion in retweeting, whereas retweets also serve as a voting mechanism to highlight popular or important messages, and are a common way of understanding key themes in twitter streams associated with events that have little to do with one’s followers.

While this retweet metadata may make it easier to mine the twitter stream, by undermining some of the reasons for this form of expression it does a disservice to the community. It will be interesting to see how people’s practices adapt to this new capability: Will this feature be ignored in favor of the old-style RT, will the ease of a two click interaction suppress the current practice, or will Twitter be forced into modifying its API to include the possibility of a modified message?

10 Comments

  1. Hi Gene,

    I agree with you – a system that encourages everybody to mechanically parrot each other to pass along information loses a bit of richness, but this has to be balanced with the increased machine-readability of formalizing the RT (in Tweet, Tweet, Retweet, Boyd, et al. document the wide variety of markers used – “RT”, “Retweet”, “via”, etc.)

    A while back, I had suggested using a sort of hash-tag scheme to point to tweets that refer to other tweets (either RT’s or replys) (http://sanjaykairam.com/blog/2009/06/retweets-and-microsyntax/). While these aren’t very machine readable, clients like Tweetdeck or Tweetie could read tags like these that refer to other these tweets and easily group them into *real* conversation threads.

    The early problem was that tags like these were unwieldy, but now given the popularity of URL shorteners, I’m wondering if a URL shortener specifically dedicated for linking to other tweets might not be an interesting idea. Curious what people think. Thanks for the post!

  2. Sanjay, The new Twitter RT API takes an id of the tweet to be retweeted, but not the message, which it grabs automatically. It would have been trivial to do both in the API. That would express the structure but also preserve the usage. After all, they already do something like this with replies.

  3. Hi Gene, definitely true – as you said it would be redundant to pass the ID (a pointer to the original) and the text itself. The same is true within the message as well.

    If you passed just an explicit pointer to the original tweet, you could avoid quoting it verbatim (the way that the current system is implemented) and tools like Tweetdeck just could re-introduce this text as threaded conversation. This would free up a lot more room for personalizing and making comments, which is way more interesting.

  4. Twitter Comment


    @sharoda I think it’s only from your followers. Take a look at what I wrote a few days ago: [link to post]

    Posted using Chat Catcher

  5. Twitter Comment


    Posted “RT done wrong” [link to post] on new Twitter RT feature

    Posted using Chat Catcher

  6. Twitter Comment


    Not done with twitter RT ;-) RT @HCIR_GeneG: Posted “RT done wrong” [link to post] on new Twitter RT feature

    Posted using Chat Catcher

  7. Twitter Comment


    @ChrisDiehl RT API not so good for established practice around commenting. [link to post]

    Posted using Chat Catcher

  8. Twitter Comment


    @xamat I agree that was an interesting paper. Too bad #Twitter didn’t pay attention to retweet practices. [link to post]

    Posted using Chat Catcher

  9. […] seems like yet another problem with the RT API, and, like the lack of ability to add comments to a new style retweet, this behavior also seems unwarranted. It doesn’t really complicate […]

  10. […] Yet these examples are all around, ranging from IEDs and other tools of asymmetric warfare, to Twitter’s response to the RT convention adopted by its users, to the use of Internet technologies for the purposes of […]

Comments are closed.