<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: FeedBurner May Suffer Glitches, But PostRank is Not the Answer to Our Prayers</title>
	<atom:link href="http://www.marketingpilgrim.com/2009/01/feedburner-may-suffer-glitches-but-postrank-is-not-the-answer-to-our-prayers.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.marketingpilgrim.com/2009/01/feedburner-may-suffer-glitches-but-postrank-is-not-the-answer-to-our-prayers.html</link>
	<description>Internet Marketing News</description>
	<lastBuildDate>Fri, 10 Feb 2012 17:00:40 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Trending Upward &#124; Recent Talk About PostRank</title>
		<link>http://www.marketingpilgrim.com/2009/01/feedburner-may-suffer-glitches-but-postrank-is-not-the-answer-to-our-prayers.html/comment-page-1#comment-67033</link>
		<dc:creator>Trending Upward &#124; Recent Talk About PostRank</dc:creator>
		<pubDate>Sat, 31 Jan 2009 05:26:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.marketingpilgrim.com/2009/01/feedburner-may-suffer-glitches-but-postrank-is-not-the-answer-to-our-prayers.html#comment-67033</guid>
		<description>[...] are also other concerns with how it ranks posts, but I do think that they&#8217;re headed in the right direction. I can say that I am very excited [...]</description>
		<content:encoded><![CDATA[<p>[...] are also other concerns with how it ranks posts, but I do think that they&#8217;re headed in the right direction. I can say that I am very excited [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PostRank: l&#8217;erede di FeedBurner? &#124; DelfinsBlog (Guido Arata)</title>
		<link>http://www.marketingpilgrim.com/2009/01/feedburner-may-suffer-glitches-but-postrank-is-not-the-answer-to-our-prayers.html/comment-page-1#comment-66838</link>
		<dc:creator>PostRank: l&#8217;erede di FeedBurner? &#124; DelfinsBlog (Guido Arata)</dc:creator>
		<pubDate>Wed, 28 Jan 2009 10:23:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.marketingpilgrim.com/2009/01/feedburner-may-suffer-glitches-but-postrank-is-not-the-answer-to-our-prayers.html#comment-66838</guid>
		<description>[...] PostRank a sconfiggere il servizio che google ha reso incelebre? Qualcuno avanza i propri dubbi. Ironia della sorte, PostRank sembra scimmiottare il nome del famoso algoritmo [...]</description>
		<content:encoded><![CDATA[<p>[...] PostRank a sconfiggere il servizio che google ha reso incelebre? Qualcuno avanza i propri dubbi. Ironia della sorte, PostRank sembra scimmiottare il nome del famoso algoritmo [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Melanie Baker</title>
		<link>http://www.marketingpilgrim.com/2009/01/feedburner-may-suffer-glitches-but-postrank-is-not-the-answer-to-our-prayers.html/comment-page-1#comment-66800</link>
		<dc:creator>Melanie Baker</dc:creator>
		<pubDate>Tue, 27 Jan 2009 19:35:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.marketingpilgrim.com/2009/01/feedburner-may-suffer-glitches-but-postrank-is-not-the-answer-to-our-prayers.html#comment-66800</guid>
		<description>Hi Andy,

I can definitely see the value of comparing the performance of a current post against a post from a year ago if they&#039;re on the same topic, for example. That would actually be really cool. Unfortunately, there really isn&#039;t a way to isolate the reasons for the engagement those posts get. For example, in a year your blog could have a lot bigger reach, and you might get more comments and diggs and tweets on every post, so the engagement wouldn&#039;t necessarily reflect your handling of a particular topic. 

The Top Posts calculation isn&#039;t quite that simplified or specific, nor is it specifically based on time frame, though that&#039;s certainly the default assumption people make (myself included, initially, because it makes the most sense at a glance). The intent of the widget also isn&#039;t really as a snapshot of recent posts. It certainly &lt;em&gt;could&lt;/em&gt; be, but ideally it brings up content that&#039;s a bit deeper than that and, ideally, gets readers into publishers&#039; archives.

It&#039;s been really interesting seeing how people approach PostRank. We get the whole gamut, really, from folks who don&#039;t care in the least how it works -- they&#039;re just happy to trust the algorithms and have less to read -- to folks who want to completely dismantle and understand the entire system and who aren&#039;t willing to trust anything. Sometimes they get comfortable with how we do things, sometimes not.

Really, though, the skeptics, like yourself, make the most interesting people to talk to. They often have perspectives and questions we haven&#039;t seen before, which sparks great conversations and ideas about new ways to handle features. (So thank you!) 

It&#039;s certainly one of the motivations behind launching the &lt;a href=&quot;http://www.postrank.com/publishers/analytics&quot; rel=&quot;nofollow&quot;&gt;Analytics Beta&lt;/a&gt; -- to get input from people from all over the adoption spectrum.

&lt;em&gt;Melanie Baker&#039;s last blog post..&lt;a href=&#039;http://blog.postrank.com/2009/01/27/a-response-on-how-postrank-works/&#039; rel=&quot;nofollow&quot;&gt;A response on how PostRank works&lt;/a&gt;&lt;/em&gt;</description>
		<content:encoded><![CDATA[<p>Hi Andy,</p>
<p>I can definitely see the value of comparing the performance of a current post against a post from a year ago if they&#8217;re on the same topic, for example. That would actually be really cool. Unfortunately, there really isn&#8217;t a way to isolate the reasons for the engagement those posts get. For example, in a year your blog could have a lot bigger reach, and you might get more comments and diggs and tweets on every post, so the engagement wouldn&#8217;t necessarily reflect your handling of a particular topic. </p>
<p>The Top Posts calculation isn&#8217;t quite that simplified or specific, nor is it specifically based on time frame, though that&#8217;s certainly the default assumption people make (myself included, initially, because it makes the most sense at a glance). The intent of the widget also isn&#8217;t really as a snapshot of recent posts. It certainly <em>could</em> be, but ideally it brings up content that&#8217;s a bit deeper than that and, ideally, gets readers into publishers&#8217; archives.</p>
<p>It&#8217;s been really interesting seeing how people approach PostRank. We get the whole gamut, really, from folks who don&#8217;t care in the least how it works &#8212; they&#8217;re just happy to trust the algorithms and have less to read &#8212; to folks who want to completely dismantle and understand the entire system and who aren&#8217;t willing to trust anything. Sometimes they get comfortable with how we do things, sometimes not.</p>
<p>Really, though, the skeptics, like yourself, make the most interesting people to talk to. They often have perspectives and questions we haven&#8217;t seen before, which sparks great conversations and ideas about new ways to handle features. (So thank you!) </p>
<p>It&#8217;s certainly one of the motivations behind launching the <a href="http://www.postrank.com/publishers/analytics" rel="nofollow">Analytics Beta</a> &#8212; to get input from people from all over the adoption spectrum.</p>
<p><em>Melanie Baker&#8217;s last blog post..<a href='http://blog.postrank.com/2009/01/27/a-response-on-how-postrank-works/' rel="nofollow">A response on how PostRank works</a></em></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy Beal</title>
		<link>http://www.marketingpilgrim.com/2009/01/feedburner-may-suffer-glitches-but-postrank-is-not-the-answer-to-our-prayers.html/comment-page-1#comment-66797</link>
		<dc:creator>Andy Beal</dc:creator>
		<pubDate>Tue, 27 Jan 2009 18:36:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.marketingpilgrim.com/2009/01/feedburner-may-suffer-glitches-but-postrank-is-not-the-answer-to-our-prayers.html#comment-66797</guid>
		<description>Hi Melanie,

I appreciate you stopping by and sharing some additional insight.

While I understand the explanation given, it doesn&#039;t make PostRank a tool that I can use. Why would I want to know the PostRank of an old post at the time of publication? Surely it&#039;s more valuable for me to know how a post I wrote a year ago, stacks up against a post I wrote this week, no?

Then, you flip the system with the widget. Now, you do look at how the post stacks up against the history of the site. Yet, the &quot;Top Posts&quot; are not really a definitive list but just a snapshot of recent published posts. What&#039;s strange is that the &quot;7.5&quot; appears to be calculated against posts published within a 2 week period--the exact same period that the 6.5 should have been calculated against.

It&#039;s your system, and your algo, but I can tell you that with these apparent inconsistencies, you&#039;re not going to get many folks feeling comfortable they understand what they heck they are looking at--I know I don&#039;t understand it. :-(</description>
		<content:encoded><![CDATA[<p>Hi Melanie,</p>
<p>I appreciate you stopping by and sharing some additional insight.</p>
<p>While I understand the explanation given, it doesn&#8217;t make PostRank a tool that I can use. Why would I want to know the PostRank of an old post at the time of publication? Surely it&#8217;s more valuable for me to know how a post I wrote a year ago, stacks up against a post I wrote this week, no?</p>
<p>Then, you flip the system with the widget. Now, you do look at how the post stacks up against the history of the site. Yet, the &#8220;Top Posts&#8221; are not really a definitive list but just a snapshot of recent published posts. What&#8217;s strange is that the &#8220;7.5&#8243; appears to be calculated against posts published within a 2 week period&#8211;the exact same period that the 6.5 should have been calculated against.</p>
<p>It&#8217;s your system, and your algo, but I can tell you that with these apparent inconsistencies, you&#8217;re not going to get many folks feeling comfortable they understand what they heck they are looking at&#8211;I know I don&#8217;t understand it. <img src='http://www.marketingpilgrim.com/wp-includes/images/smilies/icon_sad.gif' alt=':-(' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Melanie Baker</title>
		<link>http://www.marketingpilgrim.com/2009/01/feedburner-may-suffer-glitches-but-postrank-is-not-the-answer-to-our-prayers.html/comment-page-1#comment-66793</link>
		<dc:creator>Melanie Baker</dc:creator>
		<pubDate>Tue, 27 Jan 2009 16:36:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.marketingpilgrim.com/2009/01/feedburner-may-suffer-glitches-but-postrank-is-not-the-answer-to-our-prayers.html#comment-66793</guid>
		<description>Hi Andy,

Actually, none of those examples are errors. (Whew!) I&#039;ll try and explain what you&#039;re actually seeing there.

In the first example you list, I can&#039;t fully see the two dates those posts were published, but I suspect those two posts you reference were published quite a while apart? We don&#039;t compare each new post to every post you&#039;ve published that&#039;s in our system, for a number of reasons, so comparing the PostRank scores and metrics of two posts published a year apart, for example, wouldn&#039;t be applicable.

If the two posts you reference had been published in the same week, for example, the second one would definitely have gotten a higher PostRank score. However, the second example post, ranked 4.1 was published after a number of posts that had gotten even more engagement -- more than 5 comments, 2 tweets, etc. When the post ranked 7.0 was published, however, the preceding posts weren&#039;t getting as much engagement, so 4 comments was pretty good performance at that time.

Regarding the second example, the short answer is that PostRank scores in the widget and PostRank scores on the website are calculated slightly differently. A more in-depth explanation of that is here: http://blog.postrank.com/2009/01/07/postranks-website-vs-widget/.

Hope that helps clear things up. Any additional or outstanding questions, please feel free to give me a holler any time. :)

&lt;em&gt;Melanie Baker&#039;s last blog post..&lt;a href=&#039;http://blog.postrank.com/2009/01/26/feed-analytics-beta/&#039; rel=&quot;nofollow&quot;&gt;Feed Analytics Beta&lt;/a&gt;&lt;/em&gt;</description>
		<content:encoded><![CDATA[<p>Hi Andy,</p>
<p>Actually, none of those examples are errors. (Whew!) I&#8217;ll try and explain what you&#8217;re actually seeing there.</p>
<p>In the first example you list, I can&#8217;t fully see the two dates those posts were published, but I suspect those two posts you reference were published quite a while apart? We don&#8217;t compare each new post to every post you&#8217;ve published that&#8217;s in our system, for a number of reasons, so comparing the PostRank scores and metrics of two posts published a year apart, for example, wouldn&#8217;t be applicable.</p>
<p>If the two posts you reference had been published in the same week, for example, the second one would definitely have gotten a higher PostRank score. However, the second example post, ranked 4.1 was published after a number of posts that had gotten even more engagement &#8212; more than 5 comments, 2 tweets, etc. When the post ranked 7.0 was published, however, the preceding posts weren&#8217;t getting as much engagement, so 4 comments was pretty good performance at that time.</p>
<p>Regarding the second example, the short answer is that PostRank scores in the widget and PostRank scores on the website are calculated slightly differently. A more in-depth explanation of that is here: http://blog.postrank.com/2009/01/07/postranks-website-vs-widget/.</p>
<p>Hope that helps clear things up. Any additional or outstanding questions, please feel free to give me a holler any time. <img src='http://www.marketingpilgrim.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p><em>Melanie Baker&#8217;s last blog post..<a href='http://blog.postrank.com/2009/01/26/feed-analytics-beta/' rel="nofollow">Feed Analytics Beta</a></em></p>
]]></content:encoded>
	</item>
</channel>
</rss>

