Users of Twitter created the idiom "RT @suchnsuch said sumfink", and as with @ replies, RT's have been rolled in to Twitter's architecture. Now we have, what I think should be called, the native retweet.

It was turned on for early users and more of the "twittersphere" is getting the feature now. Certainly the first thing I wanted to see was what a native RT of 140 characters would look like. Well...truncated...but not really.


I've published 38 videos for new developers, designers, UX, UI, product owners and anyone who needs to conquer the command line today.

I posted this when I noticed native retweets were turned on:

I'm wondering: using the new retweet feature, what retweeting messages of 140 characters looks like to users that are not in the beta group.

So kindly, RellyAB (amongst others) retweeted for me.

Here's what it looks like with native retweets enabled:


...and here it is with out native retweets enabled:

Old School

Notice the ellipsis. No huge surprise there.

What's interesting is that the actual tweet is modified in the Twitter's view of the timeline, i.e. it's mashing together Relly's tweets and her retweets in to one view.

This can be seen in the new API method: home_timeline

Retweeting looks to be pitched as a thumbs up for a tweet, or "like" feature, but I personally agree with Cennydd when he said:

There's already a "like": Favourite. I think using that intelligently would have been wiser than the over-engineered RT.

But the upshot of this architecture change is that potentially the noise goes down. Since the retweets have their own API, the friends timeline can stay free (for now) of the extra noise. For example, in Tweetie, even though Relly had retweeted my experiment, it doesn't appear in her timeline:

Tweetie RT

Moreover, this is because the API call to user timeline is free of native retweets - so apps relying on it won't contain the retweet (for better or for worse - you may be using Snap Bird to find the tweet that was retweeted by Relly and fail to find it).

In fact, all of the native retweet APIs require authentication, so apps that rely on working without auth (such as Snap Bird) won't contain retweets at all in the future!

I'm not 100% sure whether this is good or bad, but it certainly mixes things up for the developers working with the API.

I think, if anything, it shows that Twitter are treating as a client to the API, and (rightly) they're aggressively keeping up to date with API changes, and I think that other twitter apps are going to have to do the same.


I've also spotted this (obvious now) functionality in Twitter - the ability to ignore retweets from particular users (via the green RT button on the right):


This is perfect for those people you follow and value their retweets, something you could have missed, and where you can choose to ignore others. Ignoring the developer implications for a moment, the user experience is definitely better, and this will pass down the chain to the third-party apps like Tweetie (once they update).

Obviously you'll still be able to bork the retweet feature by just adding it yourself, just like I can break the @mentions feature by adding a character (usually a period) in front of the @!