Comments on: Tweetmeme’s Meteoric Rise Reveals Twitter’s Search Issue http://ryanspoon.com/blog/2009/06/08/tweetmemes-meteoric-rise-reveals-twitters-search-issue/ Tue, 16 Mar 2010 21:46:38 +0000 http://wordpress.org/?v=2.9 hourly 1 By: Ryan Spoon http://ryanspoon.com/blog/2009/06/08/tweetmemes-meteoric-rise-reveals-twitters-search-issue/comment-page-1/#comment-10791 Ryan Spoon Tue, 09 Jun 2009 10:49:33 +0000 http://ryanspoon.com/blog/?p=888#comment-10791 Agree... hence the blog post: 3.6m is a big number. <br><br>With regards to Quantcast and Comscore - Tweetmeme could be causing difficult because the apparent growth (if accurate) is so sudden. Agree… hence the blog post: 3.6m is a big number.

With regards to Quantcast and Comscore – Tweetmeme could be causing difficult because the apparent growth (if accurate) is so sudden.

]]> By: Chaz http://ryanspoon.com/blog/2009/06/08/tweetmemes-meteoric-rise-reveals-twitters-search-issue/comment-page-1/#comment-10790 Chaz Tue, 09 Jun 2009 10:46:31 +0000 http://ryanspoon.com/blog/?p=888#comment-10790 Something's weird about the Compete numbers. <a href="http://Tweetmeme.com" rel="nofollow">Tweetmeme.com</a> doesn't come up in either comScore or Nielsen as being sufficiently large to measure. Quantcast reports a less than a quarter million. I don't think it's in the millions.<br><br>Impressive growth in the past few months, regardless, and agree about the needs. Something's weird about the Compete numbers. Tweetmeme.com doesn't come up in either comScore or Nielsen as being sufficiently large to measure. Quantcast reports a less than a quarter million. I don't think it's in the millions.

Impressive growth in the past few months, regardless, and agree about the needs.

]]> By: Ryan Spoon http://ryanspoon.com/blog/2009/06/08/tweetmemes-meteoric-rise-reveals-twitters-search-issue/comment-page-1/#comment-10789 Ryan Spoon Tue, 09 Jun 2009 10:45:46 +0000 http://ryanspoon.com/blog/?p=888#comment-10789 Is that different than Digg though? Compete shouldn't be calculating those blog buttons in the calculations... unless a user clicks through.<br><br>You can certainly question the longevity of a user's visit (or the intent for that manner) - but that is also true of Digg, StumbleUpon, and so forth. Is that different than Digg though? Compete shouldn't be calculating those blog buttons in the calculations… unless a user clicks through.

You can certainly question the longevity of a user's visit (or the intent for that manner) – but that is also true of Digg, StumbleUpon, and so forth.

]]> By: OopsYouForgot http://ryanspoon.com/blog/2009/06/08/tweetmemes-meteoric-rise-reveals-twitters-search-issue/comment-page-1/#comment-10788 OopsYouForgot Tue, 09 Jun 2009 10:33:29 +0000 http://ryanspoon.com/blog/?p=888#comment-10788 Oops, you forgot that <a href="http://tweetmeme.com" rel="nofollow">tweetmeme.com</a> receives the combined traffic of thousands of blogs. Like yours. Because of that retweet button. People aren't actually visiting <a href="http://tweetmeme.com" rel="nofollow">tweetmeme.com</a>, their browsers just load javascript from that site. It's unproven whether people care about the filtering that Tweetmeme does. Oops, you forgot that tweetmeme.com receives the combined traffic of thousands of blogs. Like yours. Because of that retweet button. People aren't actually visiting tweetmeme.com, their browsers just load javascript from that site. It's unproven whether people care about the filtering that Tweetmeme does.

]]> By: Ryan Spoon http://ryanspoon.com/blog/2009/06/08/tweetmemes-meteoric-rise-reveals-twitters-search-issue/comment-page-1/#comment-9572 Ryan Spoon Tue, 09 Jun 2009 03:49:33 +0000 http://ryanspoon.com/blog/?p=888#comment-9572 Agree... hence the blog post: 3.6m is a big number. <br><br>With regards to Quantcast and Comscore - Tweetmeme could be causing difficult because the apparent growth (if accurate) is so sudden. Agree… hence the blog post: 3.6m is a big number.

With regards to Quantcast and Comscore – Tweetmeme could be causing difficult because the apparent growth (if accurate) is so sudden.

]]> By: Chaz Yoon http://ryanspoon.com/blog/2009/06/08/tweetmemes-meteoric-rise-reveals-twitters-search-issue/comment-page-1/#comment-9571 Chaz Yoon Tue, 09 Jun 2009 03:46:31 +0000 http://ryanspoon.com/blog/?p=888#comment-9571 Something's weird about the Compete numbers. <a href="http://Tweetmeme.com" rel="nofollow">Tweetmeme.com</a> doesn't come up in either comScore or Nielsen as being sufficiently large to measure. Quantcast reports a less than a quarter million. I don't think it's in the millions.<br><br>Impressive growth in the past few months, regardless, and agree about the needs. Something's weird about the Compete numbers. Tweetmeme.com doesn't come up in either comScore or Nielsen as being sufficiently large to measure. Quantcast reports a less than a quarter million. I don't think it's in the millions.

Impressive growth in the past few months, regardless, and agree about the needs.

]]> By: Ryan Spoon http://ryanspoon.com/blog/2009/06/08/tweetmemes-meteoric-rise-reveals-twitters-search-issue/comment-page-1/#comment-9570 Ryan Spoon Tue, 09 Jun 2009 03:45:46 +0000 http://ryanspoon.com/blog/?p=888#comment-9570 Is that different than Digg though? Compete shouldn't be calculating those blog buttons in the calculations... unless a user clicks through.<br><br>You can certainly question the longevity of a user's visit (or the intent for that manner) - but that is also true of Digg, StumbleUpon, and so forth. Is that different than Digg though? Compete shouldn't be calculating those blog buttons in the calculations… unless a user clicks through.

You can certainly question the longevity of a user's visit (or the intent for that manner) – but that is also true of Digg, StumbleUpon, and so forth.

]]> By: OopsYouForgot http://ryanspoon.com/blog/2009/06/08/tweetmemes-meteoric-rise-reveals-twitters-search-issue/comment-page-1/#comment-9569 OopsYouForgot Tue, 09 Jun 2009 03:33:29 +0000 http://ryanspoon.com/blog/?p=888#comment-9569 Oops, you forgot that <a href="http://tweetmeme.com" rel="nofollow">tweetmeme.com</a> receives the combined traffic of thousands of blogs. Like yours. Because of that retweet button. People aren't actually visiting <a href="http://tweetmeme.com" rel="nofollow">tweetmeme.com</a>, their browsers just load javascript from that site. It's unproven whether people care about the filtering that Tweetmeme does. Oops, you forgot that tweetmeme.com receives the combined traffic of thousands of blogs. Like yours. Because of that retweet button. People aren't actually visiting tweetmeme.com, their browsers just load javascript from that site. It's unproven whether people care about the filtering that Tweetmeme does.

]]>