<?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: Troubleshooting user issues</title>
	<atom:link href="http://blog.postrank.com/2008/11/troubleshooting-user-issues/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.postrank.com/2008/11/troubleshooting-user-issues/</link>
	<description>Read what matters</description>
	<lastBuildDate>Fri, 19 Mar 2010 03:09:15 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: 英文家教</title>
		<link>http://blog.postrank.com/2008/11/troubleshooting-user-issues/comment-page-1/#comment-13368</link>
		<dc:creator>英文家教</dc:creator>
		<pubDate>Thu, 01 Oct 2009 14:07:55 +0000</pubDate>
		<guid isPermaLink="false">http://blog.postrank.com/?p=553#comment-13368</guid>
		<description>Interesting post. I have stumbled this for my friends. Hope others find it as interesting as I did.</description>
		<content:encoded><![CDATA[<p>Interesting post. I have stumbled this for my friends. Hope others find it as interesting as I did.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DGentry</title>
		<link>http://blog.postrank.com/2008/11/troubleshooting-user-issues/comment-page-1/#comment-1398</link>
		<dc:creator>DGentry</dc:creator>
		<pubDate>Tue, 18 Nov 2008 15:18:32 +0000</pubDate>
		<guid isPermaLink="false">http://blog.postrank.com/?p=553#comment-1398</guid>
		<description>That one wildly inflated article now shows the correct count. As you said, correcting that post did not have much impact on the PostRank of subsequent posts. Presumably your &quot;digg/slashdot filter&quot; had already discounted its impact.

The main point of my comment on louisgray.com was the impact of the long delays of the PostRank metrics. If an article has a PostRank of 1.0 for its first several days, then even if the metrics are subsequently corrected the damage has already been done: people that pay attention to the PostRank have already marked the article as read.

You said you&#039;ve added capacity to mitigate delays in processing the metrics. Thats good! I&#039;ll cross my fingers and we&#039;ll move forward.</description>
		<content:encoded><![CDATA[<p>That one wildly inflated article now shows the correct count. As you said, correcting that post did not have much impact on the PostRank of subsequent posts. Presumably your &#8220;digg/slashdot filter&#8221; had already discounted its impact.</p>
<p>The main point of my comment on louisgray.com was the impact of the long delays of the PostRank metrics. If an article has a PostRank of 1.0 for its first several days, then even if the metrics are subsequently corrected the damage has already been done: people that pay attention to the PostRank have already marked the article as read.</p>
<p>You said you&#8217;ve added capacity to mitigate delays in processing the metrics. Thats good! I&#8217;ll cross my fingers and we&#8217;ll move forward.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Melanie</title>
		<link>http://blog.postrank.com/2008/11/troubleshooting-user-issues/comment-page-1/#comment-1308</link>
		<dc:creator>Melanie</dc:creator>
		<pubDate>Mon, 17 Nov 2008 21:45:51 +0000</pubDate>
		<guid isPermaLink="false">http://blog.postrank.com/?p=553#comment-1308</guid>
		<description>Alrighty, I think we&#039;ve got this sorted out now. For those watching at home, it appears to have been a comments detection issue. Cross your fingers! :)

The Get Satisfaction problem appears to have been an issue of Mr. Gentry&#039;s issue getting swallowed up within someone else&#039;s larger issue, which, when that got fixed, we chalked up as taken care of. My bad on that one.</description>
		<content:encoded><![CDATA[<p>Alrighty, I think we&#8217;ve got this sorted out now. For those watching at home, it appears to have been a comments detection issue. Cross your fingers! <img src='http://blog.postrank.com/wordpress/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>The Get Satisfaction problem appears to have been an issue of Mr. Gentry&#8217;s issue getting swallowed up within someone else&#8217;s larger issue, which, when that got fixed, we chalked up as taken care of. My bad on that one.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DGentry</title>
		<link>http://blog.postrank.com/2008/11/troubleshooting-user-issues/comment-page-1/#comment-1302</link>
		<dc:creator>DGentry</dc:creator>
		<pubDate>Mon, 17 Nov 2008 20:42:21 +0000</pubDate>
		<guid isPermaLink="false">http://blog.postrank.com/?p=553#comment-1302</guid>
		<description>I&#039;m the Mr Gentry referenced in the article. I do appreciate the effort put into the response. I hope you understand that, having already sent email and posted to the GetSatisfaction page, I&#039;d simply given up on AideRSS. When Louis Gray posted a followup article about the rechristened PostRank service it piqued my interest again, and I responded there.

This morning I sent Melanie Baker links to the aforementioned GetSatisfaction posting and to my blog at http://codingrelic.geekhold.com/, and will watch my feed&#039;s page at http://www.postrank.com/feed/2bee36818fb4b9bdcf0aba7437a267b1?level=all to see the outcome. It should be interesting: I switched to disqus for comments in July, but the older articles still have comments from blogger.com&#039;s built-in commenting system. We&#039;ll see what happens.</description>
		<content:encoded><![CDATA[<p>I&#8217;m the Mr Gentry referenced in the article. I do appreciate the effort put into the response. I hope you understand that, having already sent email and posted to the GetSatisfaction page, I&#8217;d simply given up on AideRSS. When Louis Gray posted a followup article about the rechristened PostRank service it piqued my interest again, and I responded there.</p>
<p>This morning I sent Melanie Baker links to the aforementioned GetSatisfaction posting and to my blog at <a href="http://codingrelic.geekhold.com/" rel="nofollow">http://codingrelic.geekhold.com/</a>, and will watch my feed&#8217;s page at <a href="http://www.postrank.com/feed/2bee36818fb4b9bdcf0aba7437a267b1?level=all" rel="nofollow">http://www.postrank.com/feed/2bee36818fb4b9bdcf0aba7437a267b1?level=all</a> to see the outcome. It should be interesting: I switched to disqus for comments in July, but the older articles still have comments from blogger.com&#8217;s built-in commenting system. We&#8217;ll see what happens.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Louis Gray</title>
		<link>http://blog.postrank.com/2008/11/troubleshooting-user-issues/comment-page-1/#comment-1280</link>
		<dc:creator>Louis Gray</dc:creator>
		<pubDate>Mon, 17 Nov 2008 16:38:58 +0000</pubDate>
		<guid isPermaLink="false">http://blog.postrank.com/?p=553#comment-1280</guid>
		<description>Apologies for not responding Mr. Gentry&#039;s first e-mail. I remember seeing it and thinking I would get back to it, but obviously, I failed.

Thanks for being transparent and following up with a post.</description>
		<content:encoded><![CDATA[<p>Apologies for not responding Mr. Gentry&#8217;s first e-mail. I remember seeing it and thinking I would get back to it, but obviously, I failed.</p>
<p>Thanks for being transparent and following up with a post.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
