<?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: www. is NOT deprecated</title>
	<atom:link href="http://www.hm2k.com/articles/yes-www/feed" rel="self" type="application/rss+xml" />
	<link>http://www.hm2k.com</link>
	<description>The research of an internet entrepreneur and IT consultant</description>
	<pubDate>Wed, 20 Aug 2008 02:23:57 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Uncle Che</title>
		<link>http://www.hm2k.com/articles/yes-www#comment-62288</link>
		<dc:creator>Uncle Che</dc:creator>
		<pubDate>Sat, 19 Apr 2008 20:51:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.hm2k.com/articles/yes-www/#comment-62288</guid>
		<description>I am not a techie, so i don't understand most of the terms you guys use here. All I know is www is a subdomain and i will not set a subdomain as the prefered url of my site. I rather use theworldahead.com than www.theworldahead.com</description>
		<content:encoded><![CDATA[<p>I am not a techie, so i don&#8217;t understand most of the terms you guys use here. All I know is www is a subdomain and i will not set a subdomain as the prefered url of my site. I rather use theworldahead.com than <a href="http://www.theworldahead.com" rel="nofollow" onclick="javascript:urchinTracker ('/outbound/comment/www.theworldahead.com');">http://www.theworldahead.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hm2k</title>
		<link>http://www.hm2k.com/articles/yes-www#comment-60948</link>
		<dc:creator>hm2k</dc:creator>
		<pubDate>Wed, 16 Apr 2008 16:37:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.hm2k.com/articles/yes-www/#comment-60948</guid>
		<description>The argument for has more weight than the argument against, that's for sure.</description>
		<content:encoded><![CDATA[<p>The argument for has more weight than the argument against, that&#8217;s for sure.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Columbus Search Marketing</title>
		<link>http://www.hm2k.com/articles/yes-www#comment-60505</link>
		<dc:creator>Columbus Search Marketing</dc:creator>
		<pubDate>Mon, 14 Apr 2008 19:41:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.hm2k.com/articles/yes-www/#comment-60505</guid>
		<description>This is a pretty weak argument for keeping the www.  There are no real valid points to be found here.  Simply redirecting any www traffic to the regular domain name addresses any concerns or issues (people can still access the site that way) but we can stop using it for any other purposes.  Eventually, it will go away due to natural selection just like many other things that have outlived their purposes. Simply saying "keep it because we've always had it" is not an argument.  Many worthless things that had always been are gone today, and the world is a better place because of it.</description>
		<content:encoded><![CDATA[<p>This is a pretty weak argument for keeping the <a href="http://www" rel="nofollow" onclick="javascript:urchinTracker ('/outbound/comment/www');">http://www</a>.  There are no real valid points to be found here.  Simply redirecting any www traffic to the regular domain name addresses any concerns or issues (people can still access the site that way) but we can stop using it for any other purposes.  Eventually, it will go away due to natural selection just like many other things that have outlived their purposes. Simply saying &#8220;keep it because we&#8217;ve always had it&#8221; is not an argument.  Many worthless things that had always been are gone today, and the world is a better place because of it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roberto Bermejo Blog. &#187; WWW sí o no?</title>
		<link>http://www.hm2k.com/articles/yes-www#comment-58876</link>
		<dc:creator>Roberto Bermejo Blog. &#187; WWW sí o no?</dc:creator>
		<pubDate>Wed, 09 Apr 2008 07:31:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.hm2k.com/articles/yes-www/#comment-58876</guid>
		<description>[...] Si a las www [...]</description>
		<content:encoded><![CDATA[<p>[...] Si a las www [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Basalt</title>
		<link>http://www.hm2k.com/articles/yes-www#comment-27374</link>
		<dc:creator>Basalt</dc:creator>
		<pubDate>Tue, 04 Dec 2007 03:15:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.hm2k.com/articles/yes-www/#comment-27374</guid>
		<description>"Removing the “www.” because you think it’s “hip and trendy” or because you think “it’s no longer needed” or even “the mass media are doing it” is plain stupid."

You claim it's stupid to get rid of something that is no longer needed? And how do you support that argument? What? With your personal opinion? Oh, then it must be the truth.

"It’s a bit like “breaking the back button” (see: http://www.useit.com/alertbox/990530.html), it confuses people."

Althought I disagree it will cause mass hysteria amongst the masses: breaking the back button is just plain annoying, deprecating www is new. Everything new confuses. It's still no reason to not move to better.

"You say this but how many times have I seen addresses such as: “http://www@example.com” on company stationary and signage, too many. For them it still works in their browser, and it looks right, but we know it’s not."

So we get rid of one element and people have smaller possibility to go wrong.

"example.com is often not detected as a URL, however www.example.com is."

You don't really give a bunch of numbers to someone without informing the person it's a phone number. We have lived with those for quite some time, I think we can handle URL's without www too (and most companies already are advertising without it,)

"People need to stop being so ignorant about this."

It's not such a big deal. I think we can safely agree that only thing that really matters is using either www or no-www, and direct the traffic to the other one. It's no use forcing people to the other.</description>
		<content:encoded><![CDATA[<p>&#8220;Removing the “www.” because you think it’s “hip and trendy” or because you think “it’s no longer needed” or even “the mass media are doing it” is plain stupid.&#8221;</p>
<p>You claim it&#8217;s stupid to get rid of something that is no longer needed? And how do you support that argument? What? With your personal opinion? Oh, then it must be the truth.</p>
<p>&#8220;It’s a bit like “breaking the back button” (see: <a href="http://www.useit.com/alertbox/990530.html" rel="nofollow" onclick="javascript:urchinTracker ('/outbound/comment/www.useit.com');">http://www.useit.com/alertbox/990530.html</a>), it confuses people.&#8221;</p>
<p>Althought I disagree it will cause mass hysteria amongst the masses: breaking the back button is just plain annoying, deprecating www is new. Everything new confuses. It&#8217;s still no reason to not move to better.</p>
<p>&#8220;You say this but how many times have I seen addresses such as: “http://www@example.com” on company stationary and signage, too many. For them it still works in their browser, and it looks right, but we know it’s not.&#8221;</p>
<p>So we get rid of one element and people have smaller possibility to go wrong.</p>
<p>&#8220;example.com is often not detected as a URL, however <a href="http://www.example.com" rel="nofollow" onclick="javascript:urchinTracker ('/outbound/comment/www.example.com');">http://www.example.com</a> is.&#8221;</p>
<p>You don&#8217;t really give a bunch of numbers to someone without informing the person it&#8217;s a phone number. We have lived with those for quite some time, I think we can handle URL&#8217;s without www too (and most companies already are advertising without it,)</p>
<p>&#8220;People need to stop being so ignorant about this.&#8221;</p>
<p>It&#8217;s not such a big deal. I think we can safely agree that only thing that really matters is using either www or no-www, and direct the traffic to the other one. It&#8217;s no use forcing people to the other.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: URL con o sin WWW, esa es la cuestión en PHPBSD.net</title>
		<link>http://www.hm2k.com/articles/yes-www#comment-20866</link>
		<dc:creator>URL con o sin WWW, esa es la cuestión en PHPBSD.net</dc:creator>
		<pubDate>Mon, 05 Nov 2007 19:42:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.hm2k.com/articles/yes-www/#comment-20866</guid>
		<description>[...] Actualmente podríamos decir que es una cuestión de gustos usar o no la WWW para nuestras URL, te encuentras con partidarios del NO, como la iniciativa no-www.org, y otros que exponen interesantes motivos de porque SÍ, como en HM2K. [...]</description>
		<content:encoded><![CDATA[<p>[...] Actualmente podríamos decir que es una cuestión de gustos usar o no la WWW para nuestras URL, te encuentras con partidarios del NO, como la iniciativa no-www.org, y otros que exponen interesantes motivos de porque SÍ, como en HM2K. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Elektronik Forum</title>
		<link>http://www.hm2k.com/articles/yes-www#comment-20403</link>
		<dc:creator>Elektronik Forum</dc:creator>
		<pubDate>Sat, 03 Nov 2007 12:28:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.hm2k.com/articles/yes-www/#comment-20403</guid>
		<description>Speacial Thanks for the mod_rewrite method, it works (see http://www.stshome.de also http://stshome.de ) greate...

Thanks from Münster Germany

Gerald</description>
		<content:encoded><![CDATA[<p>Speacial Thanks for the mod_rewrite method, it works (see <a href="http://www.stshome.de" rel="nofollow" onclick="javascript:urchinTracker ('/outbound/comment/www.stshome.de');">http://www.stshome.de</a> also <a href="http://stshome.de" rel="nofollow" onclick="javascript:urchinTracker ('/outbound/comment/stshome.de');">http://stshome.de</a> ) greate&#8230;</p>
<p>Thanks from Münster Germany</p>
<p>Gerald</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hm2k</title>
		<link>http://www.hm2k.com/articles/yes-www#comment-18980</link>
		<dc:creator>hm2k</dc:creator>
		<pubDate>Wed, 24 Oct 2007 11:00:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.hm2k.com/articles/yes-www/#comment-18980</guid>
		<description>Removing the "www." because you think it's "hip and trendy" or because you think "it's no longer needed" or even "the mass media are doing it" is plain stupid.

It's a bit like "breaking the back button" (see: http://www.useit.com/alertbox/990530.html), it confuses people.

You say this but how many times have I seen addresses such as: "http://www@example.com" on company stationary and signage, too many. For them it still works in their browser, and it looks right, but we know it's not.

People need to stop being so ignorant about this.</description>
		<content:encoded><![CDATA[<p>Removing the &#8220;www.&#8221; because you think it&#8217;s &#8220;hip and trendy&#8221; or because you think &#8220;it&#8217;s no longer needed&#8221; or even &#8220;the mass media are doing it&#8221; is plain stupid.</p>
<p>It&#8217;s a bit like &#8220;breaking the back button&#8221; (see: <a href="http://www.useit.com/alertbox/990530.html" rel="nofollow" onclick="javascript:urchinTracker ('/outbound/comment/www.useit.com');">http://www.useit.com/alertbox/990530.html</a>), it confuses people.</p>
<p>You say this but how many times have I seen addresses such as: &#8220;http://www@example.com&#8221; on company stationary and signage, too many. For them it still works in their browser, and it looks right, but we know it&#8217;s not.</p>
<p>People need to stop being so ignorant about this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon</title>
		<link>http://www.hm2k.com/articles/yes-www#comment-18930</link>
		<dc:creator>Jon</dc:creator>
		<pubDate>Tue, 23 Oct 2007 18:47:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.hm2k.com/articles/yes-www/#comment-18930</guid>
		<description>Anyone who doesn't realize that "example.com" is a URI just because they don't see "www" is an idiot! Lots of big companies are advertising their domains now without it, and they don't use a "web icon." And if you're trying to get customers, you probably don't want the business of some numbskull that doesn't know "something.com" is a URI! "www" is outdated, takes extra space to print, and extra time to *say* when you are telling somebody a URI to go to. So, it's a waste of time and space. I prefer to drop it. It's not the 90's anymore people! Just my 2 cents -j</description>
		<content:encoded><![CDATA[<p>Anyone who doesn&#8217;t realize that &#8220;example.com&#8221; is a URI just because they don&#8217;t see &#8220;www&#8221; is an idiot! Lots of big companies are advertising their domains now without it, and they don&#8217;t use a &#8220;web icon.&#8221; And if you&#8217;re trying to get customers, you probably don&#8217;t want the business of some numbskull that doesn&#8217;t know &#8220;something.com&#8221; is a URI! &#8220;www&#8221; is outdated, takes extra space to print, and extra time to *say* when you are telling somebody a URI to go to. So, it&#8217;s a waste of time and space. I prefer to drop it. It&#8217;s not the 90&#8217;s anymore people! Just my 2 cents -j</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: René</title>
		<link>http://www.hm2k.com/articles/yes-www#comment-17623</link>
		<dc:creator>René</dc:creator>
		<pubDate>Mon, 08 Oct 2007 06:17:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.hm2k.com/articles/yes-www/#comment-17623</guid>
		<description>Another reason you might want to use a subdomain is SSL. If you host several subdomains on one IP address, you can use a wildcard like *.example.org in your SSL certificate, and the certificate will be valid for all of them. If you use example.org  as the CN in your SSL certificate, the certificate will not be valid for e.g. someuser.example.org.</description>
		<content:encoded><![CDATA[<p>Another reason you might want to use a subdomain is SSL. If you host several subdomains on one IP address, you can use a wildcard like *.example.org in your SSL certificate, and the certificate will be valid for all of them. If you use example.org  as the CN in your SSL certificate, the certificate will not be valid for e.g. someuser.example.org.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
