<?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: 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>
	<lastBuildDate>Fri, 12 Mar 2010 12:15:54 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Wordpress SEO (Search engine optimization) (Arama motoru optimizasyonu) &#124; Wordpress &#124; rooteto.com - Ertuğrul SAĞLAM</title>
		<link>http://www.hm2k.com/articles/yes-www/comment-page-1#comment-194931</link>
		<dc:creator>Wordpress SEO (Search engine optimization) (Arama motoru optimizasyonu) &#124; Wordpress &#124; rooteto.com - Ertuğrul SAĞLAM</dc:creator>
		<pubDate>Sun, 24 Jan 2010 14:36:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.hm2k.com/articles/yes-www/#comment-194931</guid>
		<description>[...] geçemeyeceğim internette yes-www ve no-www savaşı yapılıyor. Herkezin haklı tarafı var benim şahsen www kullandığım site [...]</description>
		<content:encoded><![CDATA[<p>[...] geçemeyeceğim internette yes-www ve no-www savaşı yapılıyor. Herkezin haklı tarafı var benim şahsen www kullandığım site [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jack Aviado</title>
		<link>http://www.hm2k.com/articles/yes-www/comment-page-1#comment-178929</link>
		<dc:creator>Jack Aviado</dc:creator>
		<pubDate>Mon, 21 Sep 2009 01:58:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.hm2k.com/articles/yes-www/#comment-178929</guid>
		<description>I work in tech support. I work with the sort of people who will be most affected by cessation of the www subdomain. 

This is how the beginning of most calls will go:

&quot;Blah blah hello thank you for calling blah blah etc., to get started let&#039;s open Internet Explorer&quot;

. . .

&quot;Now go to sub.example.com&quot;

Besides typing it into the search bar, the most common error is going to www.sub.example.com. I have to remind the customer at this point that I said sub.example.com, not www.sub.example.com. www.sub.example.com redirects to a page nowhere near where we are trying to go. This happens regularly. 

In this most significant portion of my experience, unquestioning reliance on the validity of any web address with www in front of it causes nothing but trouble. I find myself agreeing with the no-www position: That we should preserve www subdomains for those who end up typing them, but teach the general internet user base that it is unnecessary and does not go arbitrarily at the beginning of every web address. To this end I will be redirecting www.jack.is to jack.is.</description>
		<content:encoded><![CDATA[<p>I work in tech support. I work with the sort of people who will be most affected by cessation of the www subdomain. </p>
<p>This is how the beginning of most calls will go:</p>
<p>&#8220;Blah blah hello thank you for calling blah blah etc., to get started let&#8217;s open Internet Explorer&#8221;</p>
<p>. . .</p>
<p>&#8220;Now go to sub.example.com&#8221;</p>
<p>Besides typing it into the search bar, the most common error is going to <a href="http://www.sub.example.com" rel="nofollow">http://www.sub.example.com</a>. I have to remind the customer at this point that I said sub.example.com, not <a href="http://www.sub.example.com" rel="nofollow">http://www.sub.example.com</a>. <a href="http://www.sub.example.com" rel="nofollow">http://www.sub.example.com</a> redirects to a page nowhere near where we are trying to go. This happens regularly. </p>
<p>In this most significant portion of my experience, unquestioning reliance on the validity of any web address with www in front of it causes nothing but trouble. I find myself agreeing with the no-www position: That we should preserve www subdomains for those who end up typing them, but teach the general internet user base that it is unnecessary and does not go arbitrarily at the beginning of every web address. To this end I will be redirecting <a href="http://www.jack.is" rel="nofollow">http://www.jack.is</a> to jack.is.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: raphidae</title>
		<link>http://www.hm2k.com/articles/yes-www/comment-page-1#comment-175290</link>
		<dc:creator>raphidae</dc:creator>
		<pubDate>Thu, 20 Aug 2009 18:11:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.hm2k.com/articles/yes-www/#comment-175290</guid>
		<description>I don&#039;t like not using www. for a website. Hostnames like &#039;irc&#039;, &#039;mail&#039; and also &#039;www&#039; are key elements in a proper and logical URI. Screwing with that is stupid and creates only confusion.

The www host is a way to tell strangers that if they want general information, they should look on the machine where it is CNAME&#039;d to. CNAMEs are really handy and that&#039;s why lots of people use them. But because it is new and exciting to leave the www. out nowadays there are enough idiots that copy the CNAME into @. Which works about 80% of the time because as I remember it putting a CNAME into @ will give different results depending on the client querying, and can so go unnoticed for a long time.

All this bullshit is screwing up DNS. If it is a webserver: label it as such, lazy bastards. You all know the internet is well over 98% complete idiots, so why propose something that is likely to confuse &gt;5% of those 98%  at one point or another, screws up DNS in the process and also creates a political discussion about it worldwide? I must now use at least a couple hundered non-www hosts to compensate for the time I took to write this comment, otherwise I don&#039;t even win time!

Basically if you want .www to go you are an idiot and should get off the internet and step away from the computer. Step away sir!</description>
		<content:encoded><![CDATA[<p>I don&#8217;t like not using www. for a website. Hostnames like &#8216;irc&#8217;, &#8216;mail&#8217; and also &#8216;www&#8217; are key elements in a proper and logical URI. Screwing with that is stupid and creates only confusion.</p>
<p>The www host is a way to tell strangers that if they want general information, they should look on the machine where it is CNAME&#8217;d to. CNAMEs are really handy and that&#8217;s why lots of people use them. But because it is new and exciting to leave the www. out nowadays there are enough idiots that copy the CNAME into @. Which works about 80% of the time because as I remember it putting a CNAME into @ will give different results depending on the client querying, and can so go unnoticed for a long time.</p>
<p>All this bullshit is screwing up DNS. If it is a webserver: label it as such, lazy bastards. You all know the internet is well over 98% complete idiots, so why propose something that is likely to confuse &gt;5% of those 98%  at one point or another, screws up DNS in the process and also creates a political discussion about it worldwide? I must now use at least a couple hundered non-www hosts to compensate for the time I took to write this comment, otherwise I don&#8217;t even win time!</p>
<p>Basically if you want .www to go you are an idiot and should get off the internet and step away from the computer. Step away sir!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: GadgetViper</title>
		<link>http://www.hm2k.com/articles/yes-www/comment-page-1#comment-174895</link>
		<dc:creator>GadgetViper</dc:creator>
		<pubDate>Tue, 18 Aug 2009 12:59:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.hm2k.com/articles/yes-www/#comment-174895</guid>
		<description>Rene said - &quot;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.&quot;

That&#039;s not true is it?

I have 10 sub-domain and only 1 has a SSL, I was I could only have 1 per IP address?</description>
		<content:encoded><![CDATA[<p>Rene said &#8211; &#8220;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.&#8221;</p>
<p>That&#8217;s not true is it?</p>
<p>I have 10 sub-domain and only 1 has a SSL, I was I could only have 1 per IP address?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: javex.org</title>
		<link>http://www.hm2k.com/articles/yes-www/comment-page-1#comment-164270</link>
		<dc:creator>javex.org</dc:creator>
		<pubDate>Sat, 30 May 2009 05:34:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.hm2k.com/articles/yes-www/#comment-164270</guid>
		<description>Nowadays having &#039;www&#039; or not is purely a preference, &#039;www&#039; is in fact depreciated. 

&#039;www&#039; used to depict an internet server, while without &#039;www&#039; would be an intranet server. 

&#039;www&#039; is defined by:
&#039;[i]The complete set of documents residing on all Internet servers that use the HTTP protocol, accessible to users via 

a simple point-and-click system.[/i]&#039;

Web browsers nowadays automatically prepend &#039;http://&#039; onto the requested URL. &#039;www&#039; is now just a useless subdomain. 

&#039;www&#039; can be for offline advertising, when someone hears &#039;double-you-double-you-double-you&#039; they immediately know 

you&#039;re talking about a website. This is fine, as you can 301 redirect all requests for www.example.com to example.com.

Other than that, the only reason to keep www dot is if you have a large established site with a high pagerank. Your 

backlinks may become invalid if you go from with-www to without-www, or vice versa.</description>
		<content:encoded><![CDATA[<p>Nowadays having &#8216;www&#8217; or not is purely a preference, &#8216;www&#8217; is in fact depreciated. </p>
<p>&#8216;www&#8217; used to depict an internet server, while without &#8216;www&#8217; would be an intranet server. </p>
<p>&#8216;www&#8217; is defined by:<br />
&#8216;[i]The complete set of documents residing on all Internet servers that use the HTTP protocol, accessible to users via </p>
<p>a simple point-and-click system.[/i]&#8216;</p>
<p>Web browsers nowadays automatically prepend &#8216;http://&#8217; onto the requested URL. &#8216;www&#8217; is now just a useless subdomain. </p>
<p>&#8216;www&#8217; can be for offline advertising, when someone hears &#8216;double-you-double-you-double-you&#8217; they immediately know </p>
<p>you&#8217;re talking about a website. This is fine, as you can 301 redirect all requests for <a href="http://www.example.com" rel="nofollow">http://www.example.com</a> to example.com.</p>
<p>Other than that, the only reason to keep www dot is if you have a large established site with a high pagerank. Your </p>
<p>backlinks may become invalid if you go from with-www to without-www, or vice versa.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris</title>
		<link>http://www.hm2k.com/articles/yes-www/comment-page-1#comment-157886</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Thu, 23 Apr 2009 05:24:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.hm2k.com/articles/yes-www/#comment-157886</guid>
		<description>If you dont need www, dont put it up. If you do, do! My site will accept both, but google only displays one. I think it is necessity... I also think that if people go no-www compliant, they should still have the www subdomain work, for people who still try and use it.... just my thoughts...</description>
		<content:encoded><![CDATA[<p>If you dont need www, dont put it up. If you do, do! My site will accept both, but google only displays one. I think it is necessity&#8230; I also think that if people go no-www compliant, they should still have the www subdomain work, for people who still try and use it&#8230;. just my thoughts&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: thelaw.com</title>
		<link>http://www.hm2k.com/articles/yes-www/comment-page-1#comment-130906</link>
		<dc:creator>thelaw.com</dc:creator>
		<pubDate>Sun, 28 Dec 2008 06:54:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.hm2k.com/articles/yes-www/#comment-130906</guid>
		<description>Regardless of whether people want to prevent the early onset of carpal tunnel syndrome and claim that the www has no use, so long as a significant number of people and computers find a need for the www, it&#039;s here to stay. I was shocked to find out that the folks at Wordpress had removed the www entirely from usage, which I found absurd. As someone else pointed out, search engines view http://www.domain.com and http://domain.com as two completely different sites. Now if your site has been running for a long time using a &quot;www&quot; and you&#039;ve set pathways for your site to use it, e.g. src=http://www.domain.com&quot; then you&#039;ve got a heck of a task in trying to find all those instances to &quot;correct&quot; them. Then you&#039;ve got the stand in typed text like you do here -- www.domain.com is automatically hyperlinked in text in many blogs, such as Wordpress. Simple domain.com entries are NOT hyperlinked. By that feature alone, Wordpress contradicts itself in forcing you to use the &quot;no-www&quot; method because they are telling you to NOT use it yet they have a plugin recognizing that people will use it and it is useful. We haven&#039;t even talked about the other search engines which will continue to look at www and non-www sites as separate sites... You got the point. The no-www people are self-righteous and just ought to give it up already and deal with typing the characters.</description>
		<content:encoded><![CDATA[<p>Regardless of whether people want to prevent the early onset of carpal tunnel syndrome and claim that the www has no use, so long as a significant number of people and computers find a need for the www, it&#8217;s here to stay. I was shocked to find out that the folks at Wordpress had removed the www entirely from usage, which I found absurd. As someone else pointed out, search engines view <a href="http://www.domain.com" rel="nofollow">http://www.domain.com</a> and <a href="http://domain.com" rel="nofollow">http://domain.com</a> as two completely different sites. Now if your site has been running for a long time using a &#8220;www&#8221; and you&#8217;ve set pathways for your site to use it, e.g. src=http://www.domain.com&#8221; then you&#8217;ve got a heck of a task in trying to find all those instances to &#8220;correct&#8221; them. Then you&#8217;ve got the stand in typed text like you do here &#8212; <a href="http://www.domain.com" rel="nofollow">http://www.domain.com</a> is automatically hyperlinked in text in many blogs, such as Wordpress. Simple domain.com entries are NOT hyperlinked. By that feature alone, Wordpress contradicts itself in forcing you to use the &#8220;no-www&#8221; method because they are telling you to NOT use it yet they have a plugin recognizing that people will use it and it is useful. We haven&#8217;t even talked about the other search engines which will continue to look at www and non-www sites as separate sites&#8230; You got the point. The no-www people are self-righteous and just ought to give it up already and deal with typing the characters.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SB</title>
		<link>http://www.hm2k.com/articles/yes-www/comment-page-1#comment-116602</link>
		<dc:creator>SB</dc:creator>
		<pubDate>Mon, 03 Nov 2008 15:54:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.hm2k.com/articles/yes-www/#comment-116602</guid>
		<description>Being a lazy surfer I prefer to type omit the www and just type the domain name. However, I am also of the opinion that this should just be a shortcut to the website and that the server should instruct the browser to redirect to the www subdomain.  Further, it is my opinion that the file should also be included, as, technically, the page you are viewing is a resource and not a domain/subdomain. Therefore, typing in &quot;example.com&quot; would resolve to &quot;www.example.com/index.html&quot;. This also has the advantage of ensuring that search engines crawl a single resource, as each variation (ie example.com, example.com/index.html, www.example.com and www.example.com/index.html) is regarded as a unique URL and, thereby, reduces the pages rankings (if accessed using multiple variations).</description>
		<content:encoded><![CDATA[<p>Being a lazy surfer I prefer to type omit the www and just type the domain name. However, I am also of the opinion that this should just be a shortcut to the website and that the server should instruct the browser to redirect to the www subdomain.  Further, it is my opinion that the file should also be included, as, technically, the page you are viewing is a resource and not a domain/subdomain. Therefore, typing in &#8220;example.com&#8221; would resolve to &#8220;www.example.com/index.html&#8221;. This also has the advantage of ensuring that search engines crawl a single resource, as each variation (ie example.com, example.com/index.html, <a href="http://www.example.com" rel="nofollow">http://www.example.com</a> and <a href="http://www.example.com/index.html" rel="nofollow">http://www.example.com/index.html</a>) is regarded as a unique URL and, thereby, reduces the pages rankings (if accessed using multiple variations).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: noox bloggt! &#187; Blog Archive &#187; Domainname mit oder ohne www.</title>
		<link>http://www.hm2k.com/articles/yes-www/comment-page-1#comment-104956</link>
		<dc:creator>noox bloggt! &#187; Blog Archive &#187; Domainname mit oder ohne www.</dc:creator>
		<pubDate>Mon, 29 Sep 2008 23:30:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.hm2k.com/articles/yes-www/#comment-104956</guid>
		<description>[...] das ist die große Frage. Im Web gibt es dazu einige Kontroversen. Es gibt eigene Seiten pro www aber auch kontra www. Und manchen gefällt das www so sehr, dass sie sogar für zwei www, also [...]</description>
		<content:encoded><![CDATA[<p>[...] das ist die große Frage. Im Web gibt es dazu einige Kontroversen. Es gibt eigene Seiten pro www aber auch kontra www. Und manchen gefällt das www so sehr, dass sie sogar für zwei www, also [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Uncle Che</title>
		<link>http://www.hm2k.com/articles/yes-www/comment-page-1#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&#039;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">http://www.theworldahead.com</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
