Apologies for not responding Mr. Gentry'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.
DGentry
· 11 months ago
I'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'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's page at http://www.postrank.com/feed/2bee36818fb4b9bdcf... 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's built-in commenting system. We'll see what happens.
Melanie
· 11 months ago
Alrighty, I think we'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's issue getting swallowed up within someone else's larger issue, which, when that got fixed, we chalked up as taken care of. My bad on that one.
DGentry
· 11 months ago
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 "digg/slashdot filter" 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've added capacity to mitigate delays in processing the metrics. Thats good! I'll cross my fingers and we'll move forward.
All Comments
Thanks for being transparent and following up with a post.
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's page at http://www.postrank.com/feed/2bee36818fb4b9bdcf... 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's built-in commenting system. We'll see what happens.
The Get Satisfaction problem appears to have been an issue of Mr. Gentry's issue getting swallowed up within someone else's larger issue, which, when that got fixed, we chalked up as taken care of. My bad on that one.
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've added capacity to mitigate delays in processing the metrics. Thats good! I'll cross my fingers and we'll move forward.