<?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: Google Mapspam now a Global Phenom</title>
	<atom:link href="http://blumenthals.com/blog/2008/06/04/google-mapspam-now-a-global-phenom/feed/" rel="self" type="application/rss+xml" />
	<link>http://blumenthals.com/blog/2008/06/04/google-mapspam-now-a-global-phenom/</link>
	<description>Developing Knowledge about Local Search</description>
	<lastBuildDate>Sat, 25 May 2013 19:40:51 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Mike Blumenthal</title>
		<link>http://blumenthals.com/blog/2008/06/04/google-mapspam-now-a-global-phenom/comment-page-1/#comment-247399</link>
		<dc:creator>Mike Blumenthal</dc:creator>
		<pubDate>Thu, 05 Jun 2008 15:28:59 +0000</pubDate>
		<guid isPermaLink="false">http://blumenthals.com/blog/?p=686#comment-247399</guid>
		<description><![CDATA[Hey Brick, thanks for posting. 

Yes abuse of the &quot;commons&quot; does seem to spread quickly when money is involved.

Certainly Google is concerned about Mapspam and I am glad that they are taking a proactive role in fighting it. 

But the caveats I see are:
1)Google&#039;s response has been erratic and slow. Sometimes they respond immediately, sometimes they don&#039;t respond at all. Sometimes they remove by hand, sometimes not. So it leaves a hanging feeling about what and why...

2)it is not clear what is mapspam from their perspective and they have left things up for months that I believe should have been removed. 

3)Are they in fact working towards the standard of truth or is relevance still their benchmark. Because long haul I fear that the standard of relevance will  be goal rather than truthfulness. I am hoping otherwise but only by speaking up now can we have even a small influence on the product of tomorrow.

I for one am hoping that local turns out not to be just an alternative avenue for shucksterism.

Mike]]></description>
		<content:encoded><![CDATA[<p>Hey Brick, thanks for posting. </p>
<p>Yes abuse of the &#8220;commons&#8221; does seem to spread quickly when money is involved.</p>
<p>Certainly Google is concerned about Mapspam and I am glad that they are taking a proactive role in fighting it. </p>
<p>But the caveats I see are:<br />
1)Google&#8217;s response has been erratic and slow. Sometimes they respond immediately, sometimes they don&#8217;t respond at all. Sometimes they remove by hand, sometimes not. So it leaves a hanging feeling about what and why&#8230;</p>
<p>2)it is not clear what is mapspam from their perspective and they have left things up for months that I believe should have been removed. </p>
<p>3)Are they in fact working towards the standard of truth or is relevance still their benchmark. Because long haul I fear that the standard of relevance will  be goal rather than truthfulness. I am hoping otherwise but only by speaking up now can we have even a small influence on the product of tomorrow.</p>
<p>I for one am hoping that local turns out not to be just an alternative avenue for shucksterism.</p>
<p>Mike</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brick Marketing Local</title>
		<link>http://blumenthals.com/blog/2008/06/04/google-mapspam-now-a-global-phenom/comment-page-1/#comment-247397</link>
		<dc:creator>Brick Marketing Local</dc:creator>
		<pubDate>Thu, 05 Jun 2008 14:36:55 +0000</pubDate>
		<guid isPermaLink="false">http://blumenthals.com/blog/?p=686#comment-247397</guid>
		<description><![CDATA[Seems something bad always has to ruin something good and when this little devious trick occurs, it spreads like wildfire!  We commend Google for fighting back though!]]></description>
		<content:encoded><![CDATA[<p>Seems something bad always has to ruin something good and when this little devious trick occurs, it spreads like wildfire!  We commend Google for fighting back though!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
