<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title><![CDATA[Grist - Comment Feed for Gore backs idea for a new .eco domain name]]></title>
	<atom:link href="http://www.grist.org/rss/" rel="self" type="application/rss+xml" />
	<description>Grist Comment Feed</description>
	<language>en</language>
    
		<item>
            <title>Comment #1 by Ted Clayton</title>
			<link>http://www.grist.org/article/.Eco-chamber/</link>
			<pubDate>Thu, 05 Mar 2009 03:10:47 -0800</pubDate>
			<guid isPermaLink="false">http://www.grist.org/article/.Eco-chamber/1</guid>
			<description><![CDATA[
				<p><strong>A Double-edged Idea<p>Sure, .eco is a catchy domain-space. &nbsp;How about .gun? &nbsp;Or .nra?<p>
If we are going to open up domain-terms for groups that can show a constituency, there could obviously be two sides to the process.<p>
There is also the consideration of 'cross-staking'. &nbsp;Smart climate-skeptics have a shown a talent for picking 'eco-appealing' names. &nbsp;Nothing to stop 'bad guys' from homesteading nice .eco names.<p>
But my biggest concern is that we already have a 'domain-proliferation' problem. &nbsp;If one wants or needs to 'secure' or 'protect' a domain-name, it is necessary to buy up a growing flock of domain-types, most of which we may have no interest in (to prevent others from diluting or even exploiting our base-name).<p>
Exxon will be chagrined, if they don't snag <a href="http://www.exxon.eco" rel="nofollow">http://www.exxon.eco in time. &nbsp;Gristmill will be horrified if someone succeeds with <a href="http://www.gristmill.gun" rel="nofollow">http://www.gristmill.gun.<p>
Generally, I am neither wild about the proliferation-scene, nor impressed with the dubious efficacy of specialized domain-roots.</p></a></a></p></p></p></p></p></strong></p>
			]]></description>
			<content:encoded><![CDATA[
				<p><strong>A Double-edged Idea<p>Sure, .eco is a catchy domain-space. &nbsp;How about .gun? &nbsp;Or .nra?<p>
If we are going to open up domain-terms for groups that can show a constituency, there could obviously be two sides to the process.<p>
There is also the consideration of 'cross-staking'. &nbsp;Smart climate-skeptics have a shown a talent for picking 'eco-appealing' names. &nbsp;Nothing to stop 'bad guys' from homesteading nice .eco names.<p>
But my biggest concern is that we already have a 'domain-proliferation' problem. &nbsp;If one wants or needs to 'secure' or 'protect' a domain-name, it is necessary to buy up a growing flock of domain-types, most of which we may have no interest in (to prevent others from diluting or even exploiting our base-name).<p>
Exxon will be chagrined, if they don't snag <a href="http://www.exxon.eco" rel="nofollow">http://www.exxon.eco in time. &nbsp;Gristmill will be horrified if someone succeeds with <a href="http://www.gristmill.gun" rel="nofollow">http://www.gristmill.gun.<p>
Generally, I am neither wild about the proliferation-scene, nor impressed with the dubious efficacy of specialized domain-roots.</p></a></a></p></p></p></p></p></strong></p>
			]]></content:encoded>
		</item>
    
 </channel>
</rss>