<?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"
	>
<channel>
	<title>Comments on: Top-level decision made on domain names</title>
	<atom:link href="http://www.dusteddesign.com/blog/top-level-domain-names/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.dusteddesign.com/blog/top-level-domain-names/</link>
	<description>The Blog for Dusted Design Partners Limited</description>
	<pubDate>Thu, 08 Jan 2009 10:53:27 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: DNEdition</title>
		<link>http://www.dusteddesign.com/blog/top-level-domain-names/#comment-6049</link>
		<dc:creator>DNEdition</dc:creator>
		<pubDate>Sat, 27 Sep 2008 19:28:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.dusteddesign.com/blog/?p=364#comment-6049</guid>
		<description>The new .PRO extension seems to be a good idea. Not exactly sure how it will benefit branding but I like the aspect of providing domain extension for certain business professionals.</description>
		<content:encoded><![CDATA[<p>The new .PRO extension seems to be a good idea. Not exactly sure how it will benefit branding but I like the aspect of providing domain extension for certain business professionals.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SEO</title>
		<link>http://www.dusteddesign.com/blog/top-level-domain-names/#comment-6048</link>
		<dc:creator>SEO</dc:creator>
		<pubDate>Sat, 27 Sep 2008 19:14:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.dusteddesign.com/blog/?p=364#comment-6048</guid>
		<description>I think they have gone to far with the "extension boom"  newbies are getting more and more confused. If they would have stayed with the original 5 we would have been ok, but in the long run the  new ones will fall and well be back to a less confusing dimension</description>
		<content:encoded><![CDATA[<p>I think they have gone to far with the &#8220;extension boom&#8221;  newbies are getting more and more confused. If they would have stayed with the original 5 we would have been ok, but in the long run the  new ones will fall and well be back to a less confusing dimension</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Epic Urls</title>
		<link>http://www.dusteddesign.com/blog/top-level-domain-names/#comment-6047</link>
		<dc:creator>Epic Urls</dc:creator>
		<pubDate>Sat, 27 Sep 2008 19:05:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.dusteddesign.com/blog/?p=364#comment-6047</guid>
		<description>I agree with Matt. I think as long as search engines do not discriminate the extension but give equally to each extension then we may see a slight balance of power with .coms. Unfortunately, the coms are regarded as the only extension worthy of businesses.</description>
		<content:encoded><![CDATA[<p>I agree with Matt. I think as long as search engines do not discriminate the extension but give equally to each extension then we may see a slight balance of power with .coms. Unfortunately, the coms are regarded as the only extension worthy of businesses.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sharlene</title>
		<link>http://www.dusteddesign.com/blog/top-level-domain-names/#comment-5844</link>
		<dc:creator>sharlene</dc:creator>
		<pubDate>Sun, 21 Sep 2008 12:37:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.dusteddesign.com/blog/?p=364#comment-5844</guid>
		<description>yeah agreed....some things are just meant to be kept simple</description>
		<content:encoded><![CDATA[<p>yeah agreed&#8230;.some things are just meant to be kept simple</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt</title>
		<link>http://www.dusteddesign.com/blog/top-level-domain-names/#comment-5179</link>
		<dc:creator>Matt</dc:creator>
		<pubDate>Tue, 02 Sep 2008 11:02:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.dusteddesign.com/blog/?p=364#comment-5179</guid>
		<description>I think the last thing we need is overcomplicated domain names. Simple is best. Currently you can pretty much guess a company’s web address by taking their name and sticking ‘.com’ on the end.

Complicated &lt;acronym title="Universal Resource Identifier"&gt;URI&lt;/acronym&gt;s have already proved to be a miss with users. An example of this is the social bookmarking site Delicious. Their URI used to be &lt;del datetime="2008-09-02T11:17:05+00:00"&gt;de.licio.us&lt;/del&gt; &lt;a href="http://del.icio.us" rel="nofollow"&gt;del.icio.us&lt;/a&gt; (Had to edit this to get it right... case in point!). When they recently re-designed their site, they also took the opportunity to change their URI to &lt;a href="http://delicious.com" rel="nofollow"&gt;delicious.com&lt;/a&gt; as users would frequently mis-type the old one.</description>
		<content:encoded><![CDATA[<p>I think the last thing we need is overcomplicated domain names. Simple is best. Currently you can pretty much guess a company’s web address by taking their name and sticking ‘.com’ on the end.</p>
<p>Complicated <acronym title="Universal Resource Identifier">URI</acronym>s have already proved to be a miss with users. An example of this is the social bookmarking site Delicious. Their URI used to be <del datetime="2008-09-02T11:17:05+00:00">de.licio.us</del> <a href="http://del.icio.us" rel="nofollow">del.icio.us</a> (Had to edit this to get it right&#8230; case in point!). When they recently re-designed their site, they also took the opportunity to change their URI to <a href="http://delicious.com" rel="nofollow">delicious.com</a> as users would frequently mis-type the old one.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
