I’ve got an idea for how Twitter should fix the reweet. Currently there are two ways to reweet (ie repeat a twitter message to share it with your followers) and both are widely used. This post is not about my personal preference (though for the record I agree with this) but about how to fix the problem that using two different systems amplifies the disadvantages of both.
Briefly, the advantages of the old style reweet is that you can edit to add your own comments. The advantages of the new style reweet is that you can see the provenance (seeing exactly what was originally said, and when). You can see who has retweeted you either way (through @replies for the former, through a less obvious dedicated “your tweets, retweeted” page for the latter).
The old style reweet is low-tech: stick RT @originatorsname in front of their tweet, or have your favourite client do that for you. The new-style was developed by Twitter supported by dedicated API methods. There’s no way of stopping people using the low-tech old way (and quite right too, since I prefer it) but equally Twitter are unlikely to remove their new version and it’s when both are used that you get the kind of compound disadvantage that is greater than the sum of its parts – for example, a tweet new retweet of an old retweet cannot be traced by the original tweet’s author.
Twitter should evolve their new retweet “feature” into a successor to the old manual retweet which delivers the benefits of the new – essential combining them. They should do this in much the same way they’ve evolved the user-generated @reply functionality, where building on the convention that replies begin with @usernames they also allow the reply to include a reference to the tweet it is a response to.
Allow us to do an old-style retweet in the sense of quoting the text (allowing us to edit and augment) but include a reference to the original tweet.
Developers would be able to build on the API to allow users to see both the edited and the original tweet, allowing the conversation to develop whilst revealing its provenance. Rather than just seeing a list of who retweeted, originators would be able to see a timeline could showing how the conversation had developed. And by combining this with the conversation threads the extant reply links allow, developers could present visualisations that map an original tweet with both all the retweets, and the conversations they developed. This would unlock the value in the connections that retweeting creates.