<?xml version="1.0" encoding="utf-8"?><!-- generator="wordpress/2.0.4" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: ICANN Kills Domain Tasting?</title>
	<link>http://blog.whoisireland.com/2008/06/26/icann-kills-domain-tasting/</link>
	<description>Search Engines, Domains, Statistics and Analysis</description>
	<pubDate>Sun, 21 Mar 2010 13:52:26 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.4</generator>

	<item>
		<title>by: nev</title>
		<link>http://blog.whoisireland.com/2008/06/26/icann-kills-domain-tasting/#comment-177112</link>
		<pubDate>Sun, 27 Jul 2008 00:02:45 +0000</pubDate>
		<guid>http://blog.whoisireland.com/2008/06/26/icann-kills-domain-tasting/#comment-177112</guid>
					<description>a welcome step, but the problem should have been acted upon sooner, and companies like godaddy currently employ people specifically for domain tasting, and godaddy aren't just going to lay them off without seeking another way around it...</description>
		<content:encoded><![CDATA[<p>a welcome step, but the problem should have been acted upon sooner, and companies like godaddy currently employ people specifically for domain tasting, and godaddy aren&#8217;t just going to lay them off without seeking another way around it&#8230;
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Michele</title>
		<link>http://blog.whoisireland.com/2008/06/26/icann-kills-domain-tasting/#comment-163499</link>
		<pubDate>Sat, 28 Jun 2008 10:21:16 +0000</pubDate>
		<guid>http://blog.whoisireland.com/2008/06/26/icann-kills-domain-tasting/#comment-163499</guid>
					<description>From talking to a couple of "tasters" I get the impression that they won't be seriously affected overall, but they will have to cutback on their activities.</description>
		<content:encoded><![CDATA[<p>From talking to a couple of &#8220;tasters&#8221; I get the impression that they won&#8217;t be seriously affected overall, but they will have to cutback on their activities.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
