<?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: Matt The Domain Guru Strikes Again</title>
	<atom:link href="http://www.wptavern.com/matt-the-domain-guru-strikes-again/feed" rel="self" type="application/rss+xml" />
	<link>http://www.wptavern.com/matt-the-domain-guru-strikes-again</link>
	<description>Where Every Drink Is On The House</description>
	<lastBuildDate>Wed, 08 Feb 2012 10:56:16 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Mark McWilliams</title>
		<link>http://www.wptavern.com/matt-the-domain-guru-strikes-again#comment-1022</link>
		<dc:creator>Mark McWilliams</dc:creator>
		<pubDate>Mon, 27 Apr 2009 23:00:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.wptavern.com/?p=1012#comment-1022</guid>
		<description>@&lt;a href=&quot;#comment-1010&quot; rel=&quot;nofollow&quot;&gt;Patrick D.&lt;/a&gt; - As Jeff says, it would be VERY hard to have a WordPress related domain if you couldn&#039;t include WP in the domain! However, as they have stated on their site, they are happy with that just not the full!

I personally don&#039;t think they could enforce people like that is because it could be something completely UNRELATED to WordPress, afterall, it&#039;s just 2 letters!

Just my honest opinion though, each to their own! :)

Thanks
Mark</description>
		<content:encoded><![CDATA[<p>@<a href="#comment-1010" rel="nofollow">Patrick D.</a> &#8211; As Jeff says, it would be VERY hard to have a WordPress related domain if you couldn&#8217;t include WP in the domain! However, as they have stated on their site, they are happy with that just not the full!</p>
<p>I personally don&#8217;t think they could enforce people like that is because it could be something completely UNRELATED to WordPress, afterall, it&#8217;s just 2 letters!</p>
<p>Just my honest opinion though, each to their own! :)</p>
<p>Thanks<br />
Mark</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeffro</title>
		<link>http://www.wptavern.com/matt-the-domain-guru-strikes-again#comment-1014</link>
		<dc:creator>Jeffro</dc:creator>
		<pubDate>Mon, 27 Apr 2009 19:36:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.wptavern.com/?p=1012#comment-1014</guid>
		<description>@&lt;a href=&quot;#comment-1006&quot; rel=&quot;reply&quot; rel=&quot;nofollow&quot;&gt;hd-J&lt;/a&gt; - Hmm valid point regarding branding but I could see them offering a choice to end users on which domain they would like to have as part of their URL. I bet the majority would pick WP.com. 

@&lt;a href=&quot;#comment-1007&quot; rel=&quot;reply&quot; rel=&quot;nofollow&quot;&gt;Edward Caissie&lt;/a&gt; - What do you mean by hosted blog service for the shortened URL? You mean create a new WordPress.com built on top of WP.com?

@&lt;a href=&quot;#comment-1010&quot; rel=&quot;reply&quot; rel=&quot;nofollow&quot;&gt;Patrick D.&lt;/a&gt; - I didn&#039;t think of that. Man, I hope not, that would make it a REAL PAIN to have a WordPress related domain if you could not have</description>
		<content:encoded><![CDATA[<p>@<a href="#comment-1006" rel="reply" rel="nofollow">hd-J</a> &#8211; Hmm valid point regarding branding but I could see them offering a choice to end users on which domain they would like to have as part of their URL. I bet the majority would pick WP.com. </p>
<p>@<a href="#comment-1007" rel="reply" rel="nofollow">Edward Caissie</a> &#8211; What do you mean by hosted blog service for the shortened URL? You mean create a new WordPress.com built on top of WP.com?</p>
<p>@<a href="#comment-1010" rel="reply" rel="nofollow">Patrick D.</a> &#8211; I didn&#8217;t think of that. Man, I hope not, that would make it a REAL PAIN to have a WordPress related domain if you could not have</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Patrick D.</title>
		<link>http://www.wptavern.com/matt-the-domain-guru-strikes-again#comment-1010</link>
		<dc:creator>Patrick D.</dc:creator>
		<pubDate>Mon, 27 Apr 2009 16:40:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.wptavern.com/?p=1012#comment-1010</guid>
		<description>If they did that, Jeff, wouldn&#039;t they haven&#039;t to shut down any site with &#039;wp&#039; in their domain to &#039;avoid confusion&#039;, for example, wptavern.com? Hmmmm...</description>
		<content:encoded><![CDATA[<p>If they did that, Jeff, wouldn&#8217;t they haven&#8217;t to shut down any site with &#8216;wp&#8217; in their domain to &#8216;avoid confusion&#8217;, for example, wptavern.com? Hmmmm&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Edward Caissie</title>
		<link>http://www.wptavern.com/matt-the-domain-guru-strikes-again#comment-1007</link>
		<dc:creator>Edward Caissie</dc:creator>
		<pubDate>Mon, 27 Apr 2009 15:32:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.wptavern.com/?p=1012#comment-1007</guid>
		<description>In order, I would go with the hosted blog service first for the shortened URL; then, with the URL shortening service.  It seems these ideas go hand-in-hand, perhaps Automattic can sort out a way to do both?!</description>
		<content:encoded><![CDATA[<p>In order, I would go with the hosted blog service first for the shortened URL; then, with the URL shortening service.  It seems these ideas go hand-in-hand, perhaps Automattic can sort out a way to do both?!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hd-J</title>
		<link>http://www.wptavern.com/matt-the-domain-guru-strikes-again#comment-1006</link>
		<dc:creator>hd-J</dc:creator>
		<pubDate>Mon, 27 Apr 2009 12:29:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.wptavern.com/?p=1012#comment-1006</guid>
		<description>imho WordPress.com has to stay the reference rather than WP.com. After all, it is a question of branding, and everybody knows WordPress now, and having it in the URL of many blogs is also part of the branding. Remove it and you destroy a part of the branding built arounf WordPress, don&#039;t you think? Unless Matt wants to rebuild completely the image of WordPress of course.

I would vote for the Mobile version of WordPress.com. There are already dozens of shortening services, Automattic just bought a good one so why bother? 

But like you, I am curious about the choices from WP team! You can be sure they had an idea before to buy the domain!!</description>
		<content:encoded><![CDATA[<p>imho WordPress.com has to stay the reference rather than WP.com. After all, it is a question of branding, and everybody knows WordPress now, and having it in the URL of many blogs is also part of the branding. Remove it and you destroy a part of the branding built arounf WordPress, don&#8217;t you think? Unless Matt wants to rebuild completely the image of WordPress of course.</p>
<p>I would vote for the Mobile version of WordPress.com. There are already dozens of shortening services, Automattic just bought a good one so why bother? </p>
<p>But like you, I am curious about the choices from WP team! You can be sure they had an idea before to buy the domain!!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

