<?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: Editorial: Where Network Solutions Went Wrong</title>
	<atom:link href="http://domainnamewire.com/2008/01/09/editorial-where-network-solutions-went-wrong/feed/" rel="self" type="application/rss+xml" />
	<link>http://domainnamewire.com/2008/01/09/editorial-where-network-solutions-went-wrong/</link>
	<description>News and Views for the Domain Name Industry</description>
	<lastBuildDate>Sat, 21 Nov 2009 09:34:27 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: bruceb news &#187; Blog Archive &#187; FRONTRUNNING</title>
		<link>http://domainnamewire.com/2008/01/09/editorial-where-network-solutions-went-wrong/comment-page-1/#comment-489053</link>
		<dc:creator>bruceb news &#187; Blog Archive &#187; FRONTRUNNING</dc:creator>
		<pubDate>Mon, 05 Oct 2009 08:06:26 +0000</pubDate>
		<guid isPermaLink="false">http://domainnamewire.com/2008/01/09/editorial-where-network-solutions-went-wrong/#comment-489053</guid>
		<description>[...] getting lots of attention online &#8211; influential publication eWeek reported it a few days ago, here&#8217;s a particularly thorough editorial, and bloggers are jumping on here and here and here and many more places. The unanimous feeling is [...]</description>
		<content:encoded><![CDATA[<div style="background-color: #FFfbd0">
<p>[...] getting lots of attention online &#8211; influential publication eWeek reported it a few days ago, here&#8217;s a particularly thorough editorial, and bloggers are jumping on here and here and here and many more places. The unanimous feeling is [...]</p>
</div>
]]></content:encoded>
	</item>
	<item>
		<title>By: sitehell.com &#187; Blog Archive &#187; ICANN Fee Rule Change Won’t End Domain Tasting, Frontrunning</title>
		<link>http://domainnamewire.com/2008/01/09/editorial-where-network-solutions-went-wrong/comment-page-1/#comment-187969</link>
		<dc:creator>sitehell.com &#187; Blog Archive &#187; ICANN Fee Rule Change Won’t End Domain Tasting, Frontrunning</dc:creator>
		<pubDate>Mon, 30 Jun 2008 19:58:00 +0000</pubDate>
		<guid isPermaLink="false">http://domainnamewire.com/2008/01/09/editorial-where-network-solutions-went-wrong/#comment-187969</guid>
		<description>[...] Measure&#8221;. Network Solutions &#8220;protects&#8221; its customers from frontrunning by preemptively registering any domain searched for on its web site. Because NetSol takes advantage of the add grace period for this &#8220;service&#8221;, it will end [...]</description>
		<content:encoded><![CDATA[<div style="background-color: #FFfbd0">
<p>[...] Measure&#8221;. Network Solutions &#8220;protects&#8221; its customers from frontrunning by preemptively registering any domain searched for on its web site. Because NetSol takes advantage of the add grace period for this &#8220;service&#8221;, it will end [...]</p>
</div>
]]></content:encoded>
	</item>
	<item>
		<title>By: Domain Name Wire &#187; News &#187; ICANN Fee Rule Change Won&#8217;t End Domain Tasting, Frontrunning - The Domain Industry's News Source</title>
		<link>http://domainnamewire.com/2008/01/09/editorial-where-network-solutions-went-wrong/comment-page-1/#comment-187886</link>
		<dc:creator>Domain Name Wire &#187; News &#187; ICANN Fee Rule Change Won&#8217;t End Domain Tasting, Frontrunning - The Domain Industry's News Source</dc:creator>
		<pubDate>Mon, 30 Jun 2008 14:41:08 +0000</pubDate>
		<guid isPermaLink="false">http://domainnamewire.com/2008/01/09/editorial-where-network-solutions-went-wrong/#comment-187886</guid>
		<description>[...] Measure&#8221;. Network Solutions &#8220;protects&#8221; its customers from frontrunning by preemptively registering any domain searched for on its web site. Because NetSol takes advantage of the add grace period for this &#8220;service&#8221;, it will end [...]</description>
		<content:encoded><![CDATA[<div style="background-color: #FFfbd0">
<p>[...] Measure&#8221;. Network Solutions &#8220;protects&#8221; its customers from frontrunning by preemptively registering any domain searched for on its web site. Because NetSol takes advantage of the add grace period for this &#8220;service&#8221;, it will end [...]</p>
</div>
]]></content:encoded>
	</item>
	<item>
		<title>By: Technology latest news &#187; Blog Archive &#187; Network Solutions stands by controversial name policy (InfoWorld)</title>
		<link>http://domainnamewire.com/2008/01/09/editorial-where-network-solutions-went-wrong/comment-page-1/#comment-157130</link>
		<dc:creator>Technology latest news &#187; Blog Archive &#187; Network Solutions stands by controversial name policy (InfoWorld)</dc:creator>
		<pubDate>Mon, 03 Mar 2008 22:40:26 +0000</pubDate>
		<guid isPermaLink="false">http://domainnamewire.com/2008/01/09/editorial-where-network-solutions-went-wrong/#comment-157130</guid>
		<description>[...] should be fired over the implementation,&#8221; wrote Andrew Allemann, a blogger with Domain Name Wire [...]</description>
		<content:encoded><![CDATA[<div style="background-color: #FFfbd0">
<p>[...] should be fired over the implementation,&#8221; wrote Andrew Allemann, a blogger with Domain Name Wire [...]</p>
</div>
]]></content:encoded>
	</item>
	<item>
		<title>By: Domain Name Wire &#187; News &#187; Class Action Lawsuit Filed Against Network Solutions, ICANN - The Domain Industry's News Source</title>
		<link>http://domainnamewire.com/2008/01/09/editorial-where-network-solutions-went-wrong/comment-page-1/#comment-155289</link>
		<dc:creator>Domain Name Wire &#187; News &#187; Class Action Lawsuit Filed Against Network Solutions, ICANN - The Domain Industry's News Source</dc:creator>
		<pubDate>Mon, 25 Feb 2008 20:44:54 +0000</pubDate>
		<guid isPermaLink="false">http://domainnamewire.com/2008/01/09/editorial-where-network-solutions-went-wrong/#comment-155289</guid>
		<description>[...] For more on the Network Solutions fiasco, see Editorial: Where Network Solutions Went Wrong. [...]</description>
		<content:encoded><![CDATA[<div style="background-color: #FFfbd0">
<p>[...] For more on the Network Solutions fiasco, see Editorial: Where Network Solutions Went Wrong. [...]</p>
</div>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew</title>
		<link>http://domainnamewire.com/2008/01/09/editorial-where-network-solutions-went-wrong/comment-page-1/#comment-138706</link>
		<dc:creator>Andrew</dc:creator>
		<pubDate>Wed, 23 Jan 2008 19:58:00 +0000</pubDate>
		<guid isPermaLink="false">http://domainnamewire.com/2008/01/09/editorial-where-network-solutions-went-wrong/#comment-138706</guid>
		<description>Short follow up.  GoDaddy has registered the domain RegisteratGoDaddy.com.  Of course, it had to do it through Network Solutions.</description>
		<content:encoded><![CDATA[<p>Short follow up.  GoDaddy has registered the domain RegisteratGoDaddy.com.  Of course, it had to do it through Network Solutions.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Web Worker Daily &#187; Archive Open Thread: is Network Solutions Evil? &#171;</title>
		<link>http://domainnamewire.com/2008/01/09/editorial-where-network-solutions-went-wrong/comment-page-1/#comment-134675</link>
		<dc:creator>Web Worker Daily &#187; Archive Open Thread: is Network Solutions Evil? &#171;</dc:creator>
		<pubDate>Mon, 14 Jan 2008 22:35:44 +0000</pubDate>
		<guid isPermaLink="false">http://domainnamewire.com/2008/01/09/editorial-where-network-solutions-went-wrong/#comment-134675</guid>
		<description>[...] Solutions has run afoul of bloggers, domain registry industry watchers and others in the last few days when it became clear that using its popular domain registry [...]</description>
		<content:encoded><![CDATA[<div style="background-color: #FFfbd0">
<p>[...] Solutions has run afoul of bloggers, domain registry industry watchers and others in the last few days when it became clear that using its popular domain registry [...]</p>
</div>
]]></content:encoded>
	</item>
</channel>
</rss>
