This system is tracking the anatomy and life of a Tweet. I sent out the following Tweet on July 8 16:49:00 PDT:
@BarrettLyon #RTME Click http://blyon.com/rtme and watch the realtime results the
other RT/clicks! RT this as much as possible!
The concept is simple, I wrote a stats engine to track the data of each user that clicks on the embeded URL in the tweet.
As people click on the link and retweet, the data on this page populates and rows near realtime.
What you are looking at now is 2 minutes from realtime results of the life of the Tweet.
Tweet Click-Throughs by Time
Interactive Click-Throughs Map
Click-Throughs by Country
So far we’ve seen 95 countries:
|
|
|
Click-Through Broswer Type
There have been 13886 different browser types:
|
|
|
User Profile Page Click-Throughs
|
|
|
Retweets by ASN (network)
|
|
|
About the System
There’s anti-game code in this, each click on rtme only counts once. One click, one vote!
The stats should stay about 120 seconds behind realtime. Please send me comments, I can update the code anytime.
Tags: Retweet, Twitter, User Habits, Web Research

[...] This post was Twitted by scerruti [...]
Barrett, this is amazing!
Wholey sexy analytics! A girl of my disposition could really get excited about something like this.
Cool B
probing tweetspace, nice work dude.
I’ve seen those graphs before…. looks like a dashboard I use every day. Barrett: the UD government may need your help now to defend us against cyberattack from N Korea!
Hey Nick, these graphs are from AMCharts.com they are free graph libraries. I just used them here because they were fun and easy to implement with the code I wrote to make this all work.
I’m also kinda surprised I have not been contacted regarding the DDoS stuff, but chances are they need to connect with Cisco and spend a lot of money with them first.
Thanks for this…Is it possible for me to use this tool. is it available anywhere for downloading. Let me know via my email.
Thanks,
Great post! And thanks for the info on the graphs. I can see some possible uses for communications here.
[...] This post was Twitted by tweeterland [...]