<?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: Spam and comments &#8211; 32,000+ spams in 3 months</title>
	<atom:link href="http://www.teleread.org/2009/04/05/spam-and-comments-3200-spams-in-3-months/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.teleread.org/2009/04/05/spam-and-comments-3200-spams-in-3-months/</link>
	<description>News &#38; views on e-books, libraries, publishing and related topics</description>
	<lastBuildDate>Sat, 21 Nov 2009 20:01:59 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: David Rothman</title>
		<link>http://www.teleread.org/2009/04/05/spam-and-comments-3200-spams-in-3-months/comment-page-1/#comment-1032951</link>
		<dc:creator>David Rothman</dc:creator>
		<pubDate>Mon, 06 Apr 2009 16:43:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.teleread.org/?p=19937#comment-1032951</guid>
		<description>Hey, Steve, I hope you persist. You&#039;re among the last people in the world we&#039;d want to block--why, you&#039;re practically my neighbor geographically. Beyond which your comments have an excellent signal-to-noise ratio.

Please show this message to the Askimet people and tell &#039;em they will get lots of negative PR in the TeleBlog if the company does not solve your problem. Akismet&#039;s accusing us of blocking you is a big mistake. We&#039;re eager to cooperate with Akismet. I&#039;ve complained directly and am baffled why no solution is at hand. It is both lazy and sleazy for Akismet to accuse us of blocking you, unless they mean unwittingly---in which case Akismet should say so. The bastards need a lesson in customer service. WordPress should drop Akismet as a partner if customer service remains at this level. Or can they? I&#039;m trying to recall if WordPress people have a role in the company, in which case maybe that&#039;s how Akismet gets away with the current end-user abuse.

Thanks,
David</description>
		<content:encoded><![CDATA[<p>Hey, Steve, I hope you persist. You&#8217;re among the last people in the world we&#8217;d want to block&#8211;why, you&#8217;re practically my neighbor geographically. Beyond which your comments have an excellent signal-to-noise ratio.</p>
<p>Please show this message to the Askimet people and tell &#8216;em they will get lots of negative PR in the TeleBlog if the company does not solve your problem. Akismet&#8217;s accusing us of blocking you is a big mistake. We&#8217;re eager to cooperate with Akismet. I&#8217;ve complained directly and am baffled why no solution is at hand. It is both lazy and sleazy for Akismet to accuse us of blocking you, unless they mean unwittingly&#8212;in which case Akismet should say so. The bastards need a lesson in customer service. WordPress should drop Akismet as a partner if customer service remains at this level. Or can they? I&#8217;m trying to recall if WordPress people have a role in the company, in which case maybe that&#8217;s how Akismet gets away with the current end-user abuse.</p>
<p>Thanks,<br />
David</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve Jordan</title>
		<link>http://www.teleread.org/2009/04/05/spam-and-comments-3200-spams-in-3-months/comment-page-1/#comment-1032918</link>
		<dc:creator>Steve Jordan</dc:creator>
		<pubDate>Mon, 06 Apr 2009 15:34:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.teleread.org/?p=19937#comment-1032918</guid>
		<description>Unfortunately, I&#039;ve tried contacting Akismet through their form, and after a bit of back-and-forth, they blamed TeleRead for doing the blocking (in fact, I hope you see this)...</description>
		<content:encoded><![CDATA[<p>Unfortunately, I&#8217;ve tried contacting Akismet through their form, and after a bit of back-and-forth, they blamed TeleRead for doing the blocking (in fact, I hope you see this)&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
