<?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: Blog posts vs. web pages</title>
	<atom:link href="http://boredzo.org/blog/archives/2010-01-25/blog-posts-vs-web-pages/feed" rel="self" type="application/rss+xml" />
	<link>http://boredzo.org/blog/archives/2010-01-25/blog-posts-vs-web-pages</link>
	<description>The personal weblog of Peter Hosey.</description>
	<lastBuildDate>Tue, 17 Jan 2012 18:19:08 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
	<item>
		<title>By: Peter Hosey</title>
		<link>http://boredzo.org/blog/archives/2010-01-25/blog-posts-vs-web-pages/comment-page-1#comment-300624</link>
		<dc:creator>Peter Hosey</dc:creator>
		<pubDate>Mon, 25 Jan 2010 20:41:21 +0000</pubDate>
		<guid isPermaLink="false">http://boredzo.org/blog/?p=1224#comment-300624</guid>
		<description>Justin Williams:

&lt;blockquote&gt;… if I find a blog post that dates back to 2007 or earlier, I immediately dismiss it from the start. I may still read it, but I feel the content is already dated just by looking at its URL.&lt;/blockquote&gt;

Yup. This is related to (possibly the cause of) what I mentioned in relation to the ASL posts: They&#039;re old, so people expect inaccuracy, so people don&#039;t report them.

&lt;blockquote&gt;So instead of having a tutorial on NSGradient at /2008/05/12/nsgradient_tutorial/ it would instead be at /article/nsgradient_tutorial/, which seems more future proof.&lt;/blockquote&gt;

I&#039;ve wanted to do that since the beginning of this journal (“blog”), but didn&#039;t because there could be duplicate permalinks. Nowadays, WordPress enforces that all stubs must be unique, so I can do that. I&#039;d just have to make sure to redirect existing links.</description>
		<content:encoded><![CDATA[<p>Justin Williams:</p>
<blockquote cite="http://boredzo.org/blog/archives/2010-01-25/blog-posts-vs-web-pages#comment-"><p>… if I find a blog post that dates back to 2007 or earlier, I immediately dismiss it from the start. I may still read it, but I feel the content is already dated just by looking at its URL.</p>
</blockquote>
<p>Yup. This is related to (possibly the cause of) what I mentioned in relation to the ASL posts: They&#8217;re old, so people expect inaccuracy, so people don&#8217;t report them.</p>
<blockquote cite="http://boredzo.org/blog/archives/2010-01-25/blog-posts-vs-web-pages#comment-"><p>So instead of having a tutorial on NSGradient at /2008/05/12/nsgradient_tutorial/ it would instead be at /article/nsgradient_tutorial/, which seems more future proof.</p>
</blockquote>
<p>I&#8217;ve wanted to do that since the beginning of this journal (“blog”), but didn&#8217;t because there could be duplicate permalinks. Nowadays, WordPress enforces that all stubs must be unique, so I can do that. I&#8217;d just have to make sure to redirect existing links.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin Williams</title>
		<link>http://boredzo.org/blog/archives/2010-01-25/blog-posts-vs-web-pages/comment-page-1#comment-300621</link>
		<dc:creator>Justin Williams</dc:creator>
		<pubDate>Mon, 25 Jan 2010 19:55:35 +0000</pubDate>
		<guid isPermaLink="false">http://boredzo.org/blog/?p=1224#comment-300621</guid>
		<description>I&#039;ve thought about this in passing as well as my blog musings have gone from being more long-form, and less time sensitive.  The problem I find with date-based posts is that if I find a blog post that dates back to 2007 or earlier, I immediately dismiss it from the start.  I may still read it, but I feel the content is already dated just by looking at its URL. 

So instead of having a tutorial on NSGradient at /2008/05/12/nsgradient_tutorial/ it would instead be at /article/nsgradient_tutorial/, which seems more future proof.  

Having said that, it&#039;s not something that has bugged me enough to update my URL scheme and deal with the hassle of redirecting content.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve thought about this in passing as well as my blog musings have gone from being more long-form, and less time sensitive.  The problem I find with date-based posts is that if I find a blog post that dates back to 2007 or earlier, I immediately dismiss it from the start.  I may still read it, but I feel the content is already dated just by looking at its URL. </p>
<p>So instead of having a tutorial on NSGradient at /2008/05/12/nsgradient_tutorial/ it would instead be at /article/nsgradient_tutorial/, which seems more future proof.  </p>
<p>Having said that, it&#8217;s not something that has bugged me enough to update my URL scheme and deal with the hassle of redirecting content.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ssp</title>
		<link>http://boredzo.org/blog/archives/2010-01-25/blog-posts-vs-web-pages/comment-page-1#comment-300585</link>
		<dc:creator>ssp</dc:creator>
		<pubDate>Mon, 25 Jan 2010 11:44:24 +0000</pubDate>
		<guid isPermaLink="false">http://boredzo.org/blog/?p=1224#comment-300585</guid>
		<description>I agree with the sentiment. Yet, the &#039;argument&#039; isn&#039;t quite convincing to me. There&#039;s nothing that keeps you from editing and improving blog posts. _If_ there is a problem it&#039;s that search engines seem to prefer the &#039;new&#039; and that the whole &#039;feed&#039; scene does as well, which may mean that changes to &#039;historic&#039; material are lost.

On the other hand the great thing about blogging software, as you will be well aware, is that it&#039;s _easy_. You click new entry, you type, you click post, you&#039;re done. Setting up a specific web page may require a lot more work and mean that you won&#039;t make the effort as a consequence.

Perhaps it&#039;d be enough if blogging software could provide a way of specially &#039;staging&#039; certain posts, by giving them special URLs and using a different design. I suspect you can actually achieve just that with standard blogging software (say by using categories) I haven&#039;t tried doing it because I thought a blog post is just &#039;good enough&#039;. If the search engines are too stupid to find it _they_ should improve…</description>
		<content:encoded><![CDATA[<p>I agree with the sentiment. Yet, the &#8216;argument&#8217; isn&#8217;t quite convincing to me. There&#8217;s nothing that keeps you from editing and improving blog posts. _If_ there is a problem it&#8217;s that search engines seem to prefer the &#8216;new&#8217; and that the whole &#8216;feed&#8217; scene does as well, which may mean that changes to &#8216;historic&#8217; material are lost.</p>
<p>On the other hand the great thing about blogging software, as you will be well aware, is that it&#8217;s _easy_. You click new entry, you type, you click post, you&#8217;re done. Setting up a specific web page may require a lot more work and mean that you won&#8217;t make the effort as a consequence.</p>
<p>Perhaps it&#8217;d be enough if blogging software could provide a way of specially &#8216;staging&#8217; certain posts, by giving them special URLs and using a different design. I suspect you can actually achieve just that with standard blogging software (say by using categories) I haven&#8217;t tried doing it because I thought a blog post is just &#8216;good enough&#8217;. If the search engines are too stupid to find it _they_ should improve…</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.134 seconds -->

