<?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 or NO-WWW?</title>
	<atom:link href="http://www.sitepoint.com/blogs/2008/02/19/www-or-no-www/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sitepoint.com/blogs/2008/02/19/www-or-no-www/</link>
	<description>News, opinion, and fresh thinking for web developers and designers. The official podcast of sitepoint.com.</description>
	<pubDate>Tue, 02 Dec 2008 04:02:44 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: Alan Haggai Alavi</title>
		<link>http://www.sitepoint.com/blogs/2008/02/19/www-or-no-www/#comment-804164</link>
		<dc:creator>Alan Haggai Alavi</dc:creator>
		<pubDate>Mon, 06 Oct 2008 05:49:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/2008/02/19/www-or-no-www/#comment-804164</guid>
		<description>I do not like prefixing &lt;code&gt;www&lt;/code&gt; to websites unless they do not work without it being present. It's high time that &lt;code&gt;www&lt;/code&gt; is declared `&lt;em&gt;officially deprecated&lt;/em&gt;'. I redirect &lt;code&gt;www&lt;/code&gt; to just the domain for my all my websites.</description>
		<content:encoded><![CDATA[<p>I do not like prefixing <code>www</code> to websites unless they do not work without it being present. It&#8217;s high time that <code>www</code> is declared `<em>officially deprecated</em>&#8216;. I redirect <code>www</code> to just the domain for my all my websites.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: busy</title>
		<link>http://www.sitepoint.com/blogs/2008/02/19/www-or-no-www/#comment-790868</link>
		<dc:creator>busy</dc:creator>
		<pubDate>Wed, 03 Sep 2008 15:31:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/2008/02/19/www-or-no-www/#comment-790868</guid>
		<description>Oh, look at that. http://no-www.org actually posted something new to the site. I thought it was dead for good.</description>
		<content:encoded><![CDATA[<p>Oh, look at that. <a href="http://no-www.org" rel="nofollow">http://no-www.org</a> actually posted something new to the site. I thought it was dead for good.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: msquared.id.au</title>
		<link>http://www.sitepoint.com/blogs/2008/02/19/www-or-no-www/#comment-790742</link>
		<dc:creator>msquared.id.au</dc:creator>
		<pubDate>Wed, 03 Sep 2008 06:29:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/2008/02/19/www-or-no-www/#comment-790742</guid>
		<description>I agree with ParkinT: it's frustrating when you say "subdomain.mydomain.com" and they end up trying "www.subdomain.mydomain.com".

My solution is tell them "http://subdomain.mydomain.com".</description>
		<content:encoded><![CDATA[<p>I agree with ParkinT: it&#8217;s frustrating when you say &#8220;subdomain.mydomain.com&#8221; and they end up trying &#8220;www.subdomain.mydomain.com&#8221;.</p>
<p>My solution is tell them &#8220;http://subdomain.mydomain.com&#8221;.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: DangerMouse1981</title>
		<link>http://www.sitepoint.com/blogs/2008/02/19/www-or-no-www/#comment-722343</link>
		<dc:creator>DangerMouse1981</dc:creator>
		<pubDate>Wed, 14 May 2008 19:31:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/2008/02/19/www-or-no-www/#comment-722343</guid>
		<description>The www. subdomain has the benefit of allowing you to maintain brand whilst quickly switching out against any penalities the SEs may impose.</description>
		<content:encoded><![CDATA[<p>The <a href="http://www" rel="nofollow">http://www</a>. subdomain has the benefit of allowing you to maintain brand whilst quickly switching out against any penalities the SEs may impose.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Ates Goral</title>
		<link>http://www.sitepoint.com/blogs/2008/02/19/www-or-no-www/#comment-712485</link>
		<dc:creator>Ates Goral</dc:creator>
		<pubDate>Thu, 01 May 2008 19:59:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/2008/02/19/www-or-no-www/#comment-712485</guid>
		<description>&lt;blockquote&gt;In the past, it was expected that companies would have different servers (and thus different hostnames) for each of the Internet services they would provide. www.example.com for their web sites, ftp.example.com for their file transfer services, and mail.example.com for their email services.

As things turned out, many small companies can’t afford to have a separate server for each of their services, so they run many of them on the same box. As a result, the above naming convention doesn’t really make much sense in most cases.&lt;/blockquote&gt;

I think it still makes sense to follow the convention of multiple subdomains even if all the services are running on the same box and on the same IP. It's a preparation for when a company can eventually afford to host their services on their own dedicated servers, on their own dedicated IPs. Instead of creating the need to alert the users to start using mail.example.com instead of www.example.com when accessing the POP3 server or ftp.example.com instead of www.example.com when accessing the FTP server, you pave the way properly once and never have to worry about it again.

Besides, I personally find it odd and unintuitive to access a www subdomain for any purpose other than WWW.</description>
		<content:encoded><![CDATA[<blockquote><p>In the past, it was expected that companies would have different servers (and thus different hostnames) for each of the Internet services they would provide. <a href="http://www.example.com" rel="nofollow">http://www.example.com</a> for their web sites, <a href="http://ftp.example.com" rel="nofollow">http://ftp.example.com</a> for their file transfer services, and mail.example.com for their email services.</p>
<p>As things turned out, many small companies can’t afford to have a separate server for each of their services, so they run many of them on the same box. As a result, the above naming convention doesn’t really make much sense in most cases.</p></blockquote>
<p>I think it still makes sense to follow the convention of multiple subdomains even if all the services are running on the same box and on the same IP. It&#8217;s a preparation for when a company can eventually afford to host their services on their own dedicated servers, on their own dedicated IPs. Instead of creating the need to alert the users to start using mail.example.com instead of <a href="http://www.example.com" rel="nofollow">http://www.example.com</a> when accessing the POP3 server or <a href="http://ftp.example.com" rel="nofollow">http://ftp.example.com</a> instead of <a href="http://www.example.com" rel="nofollow">http://www.example.com</a> when accessing the FTP server, you pave the way properly once and never have to worry about it again.</p>
<p>Besides, I personally find it odd and unintuitive to access a www subdomain for any purpose other than <a href="http://WWW" rel="nofollow">http://WWW</a>.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: jonas-e</title>
		<link>http://www.sitepoint.com/blogs/2008/02/19/www-or-no-www/#comment-657405</link>
		<dc:creator>jonas-e</dc:creator>
		<pubDate>Wed, 19 Mar 2008 06:48:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/2008/02/19/www-or-no-www/#comment-657405</guid>
		<description>HEAR HEAR, bschilt!
Let's  get rid of the "http://" ..!
(although that might be more up to the client software ..?)</description>
		<content:encoded><![CDATA[<p>HEAR HEAR, bschilt!<br />
Let&#8217;s  get rid of the &#8220;http://&#8221; ..!<br />
(although that might be more up to the client software ..?)</p>]]></content:encoded>
	</item>
	<item>
		<title>By: busy</title>
		<link>http://www.sitepoint.com/blogs/2008/02/19/www-or-no-www/#comment-644098</link>
		<dc:creator>busy</dc:creator>
		<pubDate>Wed, 27 Feb 2008 16:48:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/2008/02/19/www-or-no-www/#comment-644098</guid>
		<description>&lt;blockquote&gt;A google search item would normally be for a name or a service rather than a URL&lt;/blockquote&gt;
Are you kidding??? Yes, I know that's how it's intended to be used, but non-technical people type urls into google all the time to find a site. Don't forget about the little people :)

&lt;blockquote&gt;If you know the order of things “downunder”, that’s like saying the USA should do things the way Canada does, or the English should speak French!!&lt;/blockquote&gt;

You got my point backwards, and you're trying to put the American stereotype on me (that's a cheap shot BTW). You were talking about how advertisers in NZ play on the Ws and using that as a reason for keeping them. I was just pointing out that maybe that's just a NZ thing, so it's not a strong argument for an issue that would affect the whole world.

&lt;blockquote&gt;Oh, and BTW http://www.99designs.com also works.&lt;/blockquote&gt;

Yes, it redirects to the non W version, which is what the anti-W people are suggesting to do until it fades from the collective memory.

&lt;blockquote&gt;...and obvious that it is 99 Designs - who’s going to care about what’s in the browser address bar.&lt;/blockquote&gt;

Exactly :)</description>
		<content:encoded><![CDATA[<blockquote><p>A google search item would normally be for a name or a service rather than a URL</p></blockquote>
<p>Are you kidding??? Yes, I know that&#8217;s how it&#8217;s intended to be used, but non-technical people type urls into google all the time to find a site. Don&#8217;t forget about the little people :)</p>
<blockquote><p>If you know the order of things “downunder”, that’s like saying the USA should do things the way Canada does, or the English should speak French!!</p></blockquote>
<p>You got my point backwards, and you&#8217;re trying to put the American stereotype on me (that&#8217;s a cheap shot BTW). You were talking about how advertisers in NZ play on the Ws and using that as a reason for keeping them. I was just pointing out that maybe that&#8217;s just a NZ thing, so it&#8217;s not a strong argument for an issue that would affect the whole world.</p>
<blockquote><p>Oh, and BTW <a href="http://www.99designs.com" rel="nofollow">http://www.99designs.com</a> also works.</p></blockquote>
<p>Yes, it redirects to the non W version, which is what the anti-W people are suggesting to do until it fades from the collective memory.</p>
<blockquote><p>&#8230;and obvious that it is 99 Designs - who’s going to care about what’s in the browser address bar.</p></blockquote>
<p>Exactly :)</p>]]></content:encoded>
	</item>
	<item>
		<title>By: bennerg</title>
		<link>http://www.sitepoint.com/blogs/2008/02/19/www-or-no-www/#comment-643706</link>
		<dc:creator>bennerg</dc:creator>
		<pubDate>Tue, 26 Feb 2008 23:01:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/2008/02/19/www-or-no-www/#comment-643706</guid>
		<description>&lt;blockquote&gt;Check your webstats to see how many people googled you by searchig “domain.com” vs “www.domain.com”&lt;/blockquote&gt;

A google search item would normally be for a name or a service rather than a URL. A more relevant value would be the "referrer" (for internal links) or other value that returns the actual URL the site visitor enters into their browser address bar. What you use depends on your website statistics package. FYI with our larger sites our web application(s) keep these stats.

&lt;blockquote&gt;But then again I think I remember hearing that an Australian site called 99designs thought it was a good idea to launch without them…&lt;/blockquote&gt;

If you know the order of things "downunder", that's like saying the USA should do things the way Canada does, or the English should speak French!!  

Oh, and BTW www.99designs.com also works. And once you get to the site, it looks so beautiful - and obvious that it is 99 Designs - who's going to care about what's in the browser address bar.

Gary</description>
		<content:encoded><![CDATA[<blockquote><p>Check your webstats to see how many people googled you by searchig “domain.com” vs “www.domain.com”</p></blockquote>
<p>A google search item would normally be for a name or a service rather than a URL. A more relevant value would be the &#8220;referrer&#8221; (for internal links) or other value that returns the actual URL the site visitor enters into their browser address bar. What you use depends on your website statistics package. FYI with our larger sites our web application(s) keep these stats.</p>
<blockquote><p>But then again I think I remember hearing that an Australian site called 99designs thought it was a good idea to launch without them…</p></blockquote>
<p>If you know the order of things &#8220;downunder&#8221;, that&#8217;s like saying the USA should do things the way Canada does, or the English should speak French!!  </p>
<p>Oh, and BTW <a href="http://www.99designs.com" rel="nofollow">http://www.99designs.com</a> also works. And once you get to the site, it looks so beautiful - and obvious that it is 99 Designs - who&#8217;s going to care about what&#8217;s in the browser address bar.</p>
<p>Gary</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Busy</title>
		<link>http://www.sitepoint.com/blogs/2008/02/19/www-or-no-www/#comment-643296</link>
		<dc:creator>Busy</dc:creator>
		<pubDate>Tue, 26 Feb 2008 07:00:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/2008/02/19/www-or-no-www/#comment-643296</guid>
		<description>Another easy experiment to see how the non-technical users think:

Check your webstats to see how many people googled you by searchig "domain.com" vs "www.domain.com"

I'll also recognize that the Ws might by played on by advertising more heavily on your side of the world, I haven't noticed that here in the US. But then again I think I remember hearing that an Australian site called 99designs thought it was a good idea to launch without them... :P</description>
		<content:encoded><![CDATA[<p>Another easy experiment to see how the non-technical users think:</p>
<p>Check your webstats to see how many people googled you by searchig &#8220;domain.com&#8221; vs &#8220;www.domain.com&#8221;</p>
<p>I&#8217;ll also recognize that the Ws might by played on by advertising more heavily on your side of the world, I haven&#8217;t noticed that here in the US. But then again I think I remember hearing that an Australian site called 99designs thought it was a good idea to launch without them&#8230; :P</p>]]></content:encoded>
	</item>
	<item>
		<title>By: bennerg</title>
		<link>http://www.sitepoint.com/blogs/2008/02/19/www-or-no-www/#comment-643246</link>
		<dc:creator>bennerg</dc:creator>
		<pubDate>Tue, 26 Feb 2008 04:47:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/2008/02/19/www-or-no-www/#comment-643246</guid>
		<description>&lt;blockquote&gt;I can see some sense in the pattern recognition argument, except that it ignores the more well established “.com” “.net”, etc pattern that is much more consistant.
&lt;/blockquote&gt;

From my personal experience I don't think one is more prevalent than the other.

&lt;blockquote&gt;From my experience with non-technical people, they couldn’t care less about stuff like this.
&lt;/blockquote&gt;

Of course they don't - it is us technical types who "worry". My point is that the masses already recognise the "www" pattern ( as evidenced here in NZ that advertising types exploit the "dub dub dub" term all the time ) and to change a well established convention for mainstream websites seems a little pointless and confusing. 

Gary</description>
		<content:encoded><![CDATA[<blockquote><p>I can see some sense in the pattern recognition argument, except that it ignores the more well established “.com” “.net”, etc pattern that is much more consistant.
</p></blockquote>
<p>From my personal experience I don&#8217;t think one is more prevalent than the other.</p>
<blockquote><p>From my experience with non-technical people, they couldn’t care less about stuff like this.
</p></blockquote>
<p>Of course they don&#8217;t - it is us technical types who &#8220;worry&#8221;. My point is that the masses already recognise the &#8220;www&#8221; pattern ( as evidenced here in NZ that advertising types exploit the &#8220;dub dub dub&#8221; term all the time ) and to change a well established convention for mainstream websites seems a little pointless and confusing. </p>
<p>Gary</p>]]></content:encoded>
	</item>
</channel>
</rss>
