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.
Wordpress
Commenting Should Be More Social, Discuss
May 26th 2010, 07:05pmWhen you find a blog post that’s interesting and you are motivated to comment on it, where do you discuss it? Â Once upon a time you’d have had the conversation right there, on the site, on that page. Â Essentially a one-to-one with the author, other posters reading it might come along and join in (perhaps friends you recommended it to). Â Just as likely now, you make your recommendation along with your comment, on Facebook or Twitter, and the discussion kicks off there.
I’ve been looking at commenting systems over the past couple of days. Â This is motivated partly by curiosity (a vast number of sites I look at offer login via something called Disqus) and partly because I think it would be neat if the conversations could be brought back together. Â Here are some of the advantages systems like IntenseDebate and Disqus (the two of looked at) can offer:
There are probably other things, those interested me the most.
There are some alternatives that can do just some of these things, and there are some drawbacks: Â There are plugins for WordPress that do 1 & 2. Â (And, it turns out, 3). Â And the drawback with 6 is that it only applies where the commenter has commented on another blog that also uses the same commenting system (the classic dilemma for social networks/IM systems/mobile phones etc.)
Yesterday the Independent adopted Disqus. Â Now, I don’t read the Indy, but it was the final straw that broke the camel’s back. Â I installed Disqus on the blog, and it’s there now. Â But it might not be in a couple of hours. Â There are some niggles, in ascending order of niggliness:
Also I don’t yet know to what extent I’ll be able to style the comments back how I want them (they’re functional and usable, but I want them to fit in with the Little Storping aesthetic!)
I can just switch Disqus off anytime. Â All the comments get duplicated into the WordPress system anyway. Â So, if I can do 1, 2 and 3 (using the Backtype plugin) how much value should I place on 4, 5 and 6.
Maybe the most important thing is what the users think… Â Oh. Ahem. Um, comments, please?
11 Comments »