<?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 for www. is not deprecated</title>
	<atom:link href="http://www.yes-www.org/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.yes-www.org</link>
	<description>really</description>
	<lastBuildDate>Sat, 30 Jan 2010 18:48:10 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=3.0-alpha</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on www. is not deprecated by kersurk</title>
		<link>http://www.yes-www.org/www-is-not-deprecated/comment-page-2/#comment-1213</link>
		<dc:creator>kersurk</dc:creator>
		<pubDate>Sat, 30 Jan 2010 18:48:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.yes-www.org/www-is-not-deprecated/#comment-1213</guid>
		<description>Hi,
http protocol IS www, so www is just a leftover, so no-www.org ftw!</description>
		<content:encoded><![CDATA[<p>Hi,<br />
http protocol IS www, so www is just a leftover, so no-www.org ftw!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on www. is not deprecated by Lucas</title>
		<link>http://www.yes-www.org/www-is-not-deprecated/comment-page-2/#comment-1209</link>
		<dc:creator>Lucas</dc:creator>
		<pubDate>Wed, 20 Jan 2010 07:17:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.yes-www.org/www-is-not-deprecated/#comment-1209</guid>
		<description>I&#039;m tired or people who argue that typing URI into the search engine is wrong! I do it for sites I have never been to for this reasons: typo, I can barely spell in any language and I don&#039;t want to land in a phishing site. Google will rank first the correct domain for sure, even if I made a mistake. I do it for a prophylactic purpose, so should you. With the sites I have regularly encounters with, I don&#039;t, I just use the bookmarks ;)
NOTE: Also, you can check if the site has been flagged if you have McAfee Site Advisor.</description>
		<content:encoded><![CDATA[<p>I&#8217;m tired or people who argue that typing URI into the search engine is wrong! I do it for sites I have never been to for this reasons: typo, I can barely spell in any language and I don&#8217;t want to land in a phishing site. Google will rank first the correct domain for sure, even if I made a mistake. I do it for a prophylactic purpose, so should you. With the sites I have regularly encounters with, I don&#8217;t, I just use the bookmarks <img src='http://www.yes-www.org/wordpress/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /><br />
NOTE: Also, you can check if the site has been flagged if you have McAfee Site Advisor.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on www. is not deprecated by Chris</title>
		<link>http://www.yes-www.org/www-is-not-deprecated/comment-page-1/#comment-1200</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Mon, 14 Dec 2009 01:20:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.yes-www.org/www-is-not-deprecated/#comment-1200</guid>
		<description>I prefer the non-www.  I don&#039;t like seeing duplicate entries in the SERP with www and non-www links to the same page.  I do use a 301 redirect for all www to go to non-www on all my domains.  I&#039;m hoping this will help clean up the duplicate entries in the search engines the next time the spiders come to my websites.</description>
		<content:encoded><![CDATA[<p>I prefer the non-www.  I don&#8217;t like seeing duplicate entries in the SERP with www and non-www links to the same page.  I do use a 301 redirect for all www to go to non-www on all my domains.  I&#8217;m hoping this will help clean up the duplicate entries in the search engines the next time the spiders come to my websites.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on www. is not deprecated by Richard Joh</title>
		<link>http://www.yes-www.org/www-is-not-deprecated/comment-page-1/#comment-1199</link>
		<dc:creator>Richard Joh</dc:creator>
		<pubDate>Mon, 07 Dec 2009 15:23:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.yes-www.org/www-is-not-deprecated/#comment-1199</guid>
		<description>Protocol understanding fail.</description>
		<content:encoded><![CDATA[<p>Protocol understanding fail.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on www. is not deprecated by Eric</title>
		<link>http://www.yes-www.org/www-is-not-deprecated/comment-page-1/#comment-1197</link>
		<dc:creator>Eric</dc:creator>
		<pubDate>Fri, 27 Nov 2009 02:33:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.yes-www.org/www-is-not-deprecated/#comment-1197</guid>
		<description>I believe in yes-www, but seriously, a gentle reminder?
www misleads to world wide web...
To remind people there are other protocols, shouldn&#039;t it be http://http.example.com/.

I use www since I use subdomains. If I had a site without any subdomains, then I would go no-www. I think it is useful since I have gs1.example.com, forum.example.com, svn.example.com, etc... I just think that www.example.com while meshed in there is a lot cleaner than just example.com</description>
		<content:encoded><![CDATA[<p>I believe in yes-www, but seriously, a gentle reminder?<br />
www misleads to world wide web&#8230;<br />
To remind people there are other protocols, shouldn&#8217;t it be <a href="http://http.example.com/">http://http.example.com/</a>.</p>
<p>I use www since I use subdomains. If I had a site without any subdomains, then I would go no-www. I think it is useful since I have gs1.example.com, forum.example.com, svn.example.com, etc&#8230; I just think that <a href="http://www.example.com">http://www.example.com</a> while meshed in there is a lot cleaner than just example.com</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on www. is not deprecated by Kevin Jennings</title>
		<link>http://www.yes-www.org/www-is-not-deprecated/comment-page-1/#comment-1196</link>
		<dc:creator>Kevin Jennings</dc:creator>
		<pubDate>Sat, 21 Nov 2009 03:32:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.yes-www.org/www-is-not-deprecated/#comment-1196</guid>
		<description>As the General Manager of Search Engine Optimization company, this issue is a real one.  Having duplicate content on both http://www.example.com and http://example.com is a horror for the commercial value of the site.  You end up with competing sites in the search engines.  To maximize ranking you need to choose either http://www.example.com or http://example.com as the target of you link building. Consequently, a webmaster needs to decide, www. or not www.  

Given any history of a site, choosing NOT www. is usually a major mistake.  If you get natural links, the ones the search engines want you to have, most will be www. today so even for a new site it is a better choice. Next you need to redirect to one version of your site.  Choosing both options is just stupid for any commercial site or any site that wants people to visit the site. Of course if you do not want people to visit your site, the site should not exist as it does not serve anyone other than perhaps some stupid algorithm developed by Google to promote adwords and increase barriers to entry to competitors.</description>
		<content:encoded><![CDATA[<p>As the General Manager of Search Engine Optimization company, this issue is a real one.  Having duplicate content on both <a href="http://www.example.com">http://www.example.com</a> and <a href="http://example.com">http://example.com</a> is a horror for the commercial value of the site.  You end up with competing sites in the search engines.  To maximize ranking you need to choose either <a href="http://www.example.com">http://www.example.com</a> or <a href="http://example.com">http://example.com</a> as the target of you link building. Consequently, a webmaster needs to decide, www. or not www.  </p>
<p>Given any history of a site, choosing NOT www. is usually a major mistake.  If you get natural links, the ones the search engines want you to have, most will be www. today so even for a new site it is a better choice. Next you need to redirect to one version of your site.  Choosing both options is just stupid for any commercial site or any site that wants people to visit the site. Of course if you do not want people to visit your site, the site should not exist as it does not serve anyone other than perhaps some stupid algorithm developed by Google to promote adwords and increase barriers to entry to competitors.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on www. is not deprecated by Dave</title>
		<link>http://www.yes-www.org/www-is-not-deprecated/comment-page-1/#comment-1192</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Wed, 30 Sep 2009 04:03:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.yes-www.org/www-is-not-deprecated/#comment-1192</guid>
		<description>Here&#039;s my take on this whole business:
http://www.bigfatdave.com/to_www_or_not_to_www.html
If you&#039;d like to have some fun, try doing this:
http://bigfatdave.com/
or this:
http://bigfatdave.com/blog.php

BTW - IO Error: in case you&#039;re wondering where all your visitors have
gone, they&#039;re all seeing server not found errors, because you&#039;ve got a
DNS error.

Peace,
 - Dave</description>
		<content:encoded><![CDATA[<p>Here&#8217;s my take on this whole business:<br />
<a href="http://www.bigfatdave.com/to_www_or_not_to_www.html">http://www.bigfatdave.com/to_www_or_not_to_www.html</a><br />
If you&#8217;d like to have some fun, try doing this:<br />
<a href="http://bigfatdave.com/">http://bigfatdave.com/</a><br />
or this:<br />
<a href="http://bigfatdave.com/blog.php">http://bigfatdave.com/blog.php</a></p>
<p>BTW &#8211; IO Error: in case you&#8217;re wondering where all your visitors have<br />
gone, they&#8217;re all seeing server not found errors, because you&#8217;ve got a<br />
DNS error.</p>
<p>Peace,<br />
 &#8211; Dave</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on www. is not deprecated by Sorceror</title>
		<link>http://www.yes-www.org/www-is-not-deprecated/comment-page-1/#comment-1189</link>
		<dc:creator>Sorceror</dc:creator>
		<pubDate>Tue, 16 Sep 2008 23:19:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.yes-www.org/www-is-not-deprecated/#comment-1189</guid>
		<description>I see a lot of people complaining that ftp://example.com and http://example.com would have to be hosted on the same physical machine.

My modem has at least 9 different computers connected to it via ethernet switches and wireless routers. Obviously, all traffic directed to my modem&#039;s IP gets routed to all boxes on the LAN, right? Wrong. There are mechanisms in place in TCP/IP and ethernet protocols to avoid this.

What about serving? The magical solution to the one-IP-many-serving-boxes problem is called NAT. Even with a residential-class modem, I&#039;ve been able to direct access from port A to local IP X, and port B to local IP Y. So I could have http://example.com and ftp://example.com sharing the same WAN IP but being physically different boxes with different LAN IPs. And in fact, that is what I do. And it works.

What you wouldn&#039;t be able to do with NAT is separate http://example.com from ftp://example.com:80, but I think most people will agree using the HTTP port for FTP is silly :)</description>
		<content:encoded><![CDATA[<p>I see a lot of people complaining that <a href="ftp://example.com">ftp://example.com</a> and <a href="http://example.com">http://example.com</a> would have to be hosted on the same physical machine.</p>
<p>My modem has at least 9 different computers connected to it via ethernet switches and wireless routers. Obviously, all traffic directed to my modem&#8217;s IP gets routed to all boxes on the LAN, right? Wrong. There are mechanisms in place in TCP/IP and ethernet protocols to avoid this.</p>
<p>What about serving? The magical solution to the one-IP-many-serving-boxes problem is called NAT. Even with a residential-class modem, I&#8217;ve been able to direct access from port A to local IP X, and port B to local IP Y. So I could have <a href="http://example.com">http://example.com</a> and <a href="ftp://example.com">ftp://example.com</a> sharing the same WAN IP but being physically different boxes with different LAN IPs. And in fact, that is what I do. And it works.</p>
<p>What you wouldn&#8217;t be able to do with NAT is separate <a href="http://example.com">http://example.com</a> from <a href="ftp://example.com:80">ftp://example.com:80</a>, but I think most people will agree using the HTTP port for FTP is silly <img src='http://www.yes-www.org/wordpress/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on www. is not deprecated by qhutz</title>
		<link>http://www.yes-www.org/www-is-not-deprecated/comment-page-1/#comment-1186</link>
		<dc:creator>qhutz</dc:creator>
		<pubDate>Thu, 04 Sep 2008 20:34:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.yes-www.org/www-is-not-deprecated/#comment-1186</guid>
		<description>while I disagree with you about the www. being preferred, I am completely agree that both www.example.com and example.com should resolve to the intended page, and that it should redirect to one or the other, making the page&#039;s url unique.</description>
		<content:encoded><![CDATA[<p>while I disagree with you about the www. being preferred, I am completely agree that both <a href="http://www.example.com">http://www.example.com</a> and example.com should resolve to the intended page, and that it should redirect to one or the other, making the page&#8217;s url unique.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on www. is not deprecated by www.www.extra-www.org &#8212; omglog</title>
		<link>http://www.yes-www.org/www-is-not-deprecated/comment-page-1/#comment-1182</link>
		<dc:creator>www.www.extra-www.org &#8212; omglog</dc:creator>
		<pubDate>Tue, 19 Aug 2008 21:01:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.yes-www.org/www-is-not-deprecated/#comment-1182</guid>
		<description>[...] is presumably parody aimed at the two sídes of the anti-www/pro-www [...]</description>
		<content:encoded><![CDATA[<p>[...] is presumably parody aimed at the two sídes of the anti-www/pro-www [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
