Twitter's new retweets fail to fix an unbroken system

Twitter’s new retweet system isn’t exactly new anymore, but the way in which it is implemented feels like it would be an older system, reducing ease of use and accessibility. Prior to the ‘upgrade’, retweeting consisted of a simple tweet including the original tweet, tweeter and a marker. The marker first started as ‘RT’, but over time, variations were ‘invented.’ In the early DestroyTwiter days, Josh Corliss suggested using ‘>’ instead of ‘RT’, which saves a character and simply looks better. Many users reference tweets with ‘(via @username)’ or ‘/via @username’ to summarize instead of using word-for-word retweets. All of these options can be edited, daisy-chained, and commented on. They also appear in the retweeted user’s mentions timeline, notifying him/her of a retweet. With the new system, all of these features are either diminished or elongated.
To give an idea of the work on the developer, the new retweet system introduces the following API methods:
1 2 3 4 5 6 7 | statuses/retweet statuses/retweets statuses/id/retweeted_by statuses/id/retweeted_by/ids statuses/retweeted_by_me statuses/retweeted_to_me statuses/retweeted_of_me |
The original system requires only two:
1 2 | statuses/update statuses/mentions |
Of course, the new system brings more control, but is it all necessary? In order to see which tweets of yours were retweeted and by whom, the statuses/retweeted_of_me method must be called, followed by the statuses/retweets method for each tweet. Unless you’re whitelisted (have 20,000 API calls), calling these methods, in addition to the common methods, could certainly add up quick. On top of that, both methods would need to be polled consistently to stay up-to-date in case additional retweets were made. Unless the developer of the app you use wants to bend over backwards to notify you of new retweets, you’re forced to visit Twitter.com to check.
Now, is it really such a big deal to know how many times or by whom your tweets are retweeted? Not entirely, but I personally gauge which tweets my followers react to the most by how many times the tweets are retweeted. If I tweet about DestroyTwitter and it’s retweeted a dozen times, then I tweet a video of my cat that only results in crickets, I’ll know to lay off the cat videos—but that’s just me. Other users find new people to follow by seeing who retweets their tweets.
With the new system, Twitter makes it harder on both developers and users. The original system worked and worked well. Many users, like myself, reject the new system and continue to use the original one. Because of this, users must reference multiple locations instead of one. This once simple-as-can-be feature is now a nuisance.
Twitter used to be simple. It still can be depending on which app you use, but if other features are ‘improved upon’ as retweets were, we might end up with unavoidable obstacles. I’m growing tired of services that start out beautifully, then take a turn for the worst after being packed full of unneeded additions. A prime example is Facebook, but that’s for another time.
(photo property of DreamWorks and Universal Studios)






