Yesterday, the response was pretty overwhelming to my blog post about Twitter shutting down StatTweets. And it got Twitter's attention. Within 30 minutes of the TechCrunch article @Crystal responded to one of my Twitter tickets. By the end of the day, @Ev replied to an email I sent him a couple weeks ago. Both re-stated their issues with my compliance with their TOS, so I re-stated my willingness to change the accounts as necessary. We'll see if anything comes from it. They've stated and restated their issues at least three or four times now (buying time?), so that should be really clear with everyone. What isn't clear are the actions they want me to take to rectify their issues.

Now for some stats. The bit.ly link I used to point to my blog post in my original tweet resulted in 6,300 clicks. My tweet or some variation was retweeted over 1,000 times yesterday and there were 7,700 visitors to my blog article. The story was picked up by a variety of media outlets, blogs, and web services including TechCrunch, Mashable, FT.com, Hacker News, and TechMeme. Much like the last time I had a blog post picked up by TechCrunch and Hacker News, the distribution of traffic was roughly the same with Hacker News still dominating any other source by a wide margin:

Hacker News: 1,500 visits

TechMeme: 480 visits

Twitter: 353 visits

TechCrunch: 345 visits

Google Reader: 295 visits

StumbleUpon: 176 visits

The Google numbers skew everything because those visitors could have been reading the TechCrunch article (or using the TechMeme feed) that linked to my blog.

Ultimately, I wish it hadn't come to me writing the blog post, but with Twitter not responding to my repeated inquiries, I didn't have any other recourse. It is still yet to be determined if my strategy to restore StatTweets will work. Stay tuned!

Posted by Robbie | Permalink | Comments

About StatSheet.com

Have a suggestion?
Let me know