<?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: A note on the blog format</title>
	<atom:link href="http://yankees.lhblogs.com/2007/05/19/a-note-on-the-blog-format/feed/" rel="self" type="application/rss+xml" />
	<link>http://yankees.lhblogs.com/2007/05/19/a-note-on-the-blog-format/</link>
	<description>A New York Yankees blog by Chad Jennings and the staff of The Journal News</description>
	<lastBuildDate>Fri, 10 Feb 2012 11:26:07 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Jenny</title>
		<link>http://yankees.lhblogs.com/2007/05/19/a-note-on-the-blog-format/comment-page-1/#comment-624222</link>
		<dc:creator>Jenny</dc:creator>
		<pubDate>Tue, 23 Dec 2008 10:34:32 +0000</pubDate>
		<guid isPermaLink="false">http://yankees.lhblogs.com/2007/05/19/a-note-on-the-blog-format/#comment-624222</guid>
		<description>Interesting article. I found some more information here</description>
		<content:encoded><![CDATA[<p>Interesting article. I found some more information here</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Phil Oye</title>
		<link>http://yankees.lhblogs.com/2007/05/19/a-note-on-the-blog-format/comment-page-1/#comment-47761</link>
		<dc:creator>Phil Oye</dc:creator>
		<pubDate>Mon, 21 May 2007 04:22:08 +0000</pubDate>
		<guid isPermaLink="false">http://yankees.lhblogs.com/2007/05/19/a-note-on-the-blog-format/#comment-47761</guid>
		<description>12to6, one more thing.

I do agree that updates at top are useful when you&#039;re about to say &quot;Hmm, I was totally wrong with this post&quot; or something. That alerts the user to read the post with the update in mind. But for multiple chronological updates that merely ADD information? No way.</description>
		<content:encoded><![CDATA[<p>12to6, one more thing.</p>
<p>I do agree that updates at top are useful when you&#8217;re about to say &#8220;Hmm, I was totally wrong with this post&#8221; or something. That alerts the user to read the post with the update in mind. But for multiple chronological updates that merely ADD information? No way.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Phil Oye</title>
		<link>http://yankees.lhblogs.com/2007/05/19/a-note-on-the-blog-format/comment-page-1/#comment-47759</link>
		<dc:creator>Phil Oye</dc:creator>
		<pubDate>Mon, 21 May 2007 04:13:46 +0000</pubDate>
		<guid isPermaLink="false">http://yankees.lhblogs.com/2007/05/19/a-note-on-the-blog-format/#comment-47759</guid>
		<description>Ghost of Yankees Past, I use NetNewsWire on the Mac.

12to6, I couldn&#039;t disagree with you more. Updates at the top is fine, if you saw every iteration of the post, but what happens when you come late? It is IMPOSSIBLE to follow along. For example, if you check out today&#039;s (Sunday&#039;s) game 42 link. There are NINE updates. I didn&#039;t bring up the page until just now. To read that page is impossible. You need to start in the MIDDLE, read down, then scroll up to the FIRST update, read down a few lines, then scroll up, remember where you were to find the SECOND update, etc. Maddening. Too hard. Not everyone reads these entries in real-time.</description>
		<content:encoded><![CDATA[<p>Ghost of Yankees Past, I use NetNewsWire on the Mac.</p>
<p>12to6, I couldn&#8217;t disagree with you more. Updates at the top is fine, if you saw every iteration of the post, but what happens when you come late? It is IMPOSSIBLE to follow along. For example, if you check out today&#8217;s (Sunday&#8217;s) game 42 link. There are NINE updates. I didn&#8217;t bring up the page until just now. To read that page is impossible. You need to start in the MIDDLE, read down, then scroll up to the FIRST update, read down a few lines, then scroll up, remember where you were to find the SECOND update, etc. Maddening. Too hard. Not everyone reads these entries in real-time.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bumblebee</title>
		<link>http://yankees.lhblogs.com/2007/05/19/a-note-on-the-blog-format/comment-page-1/#comment-47696</link>
		<dc:creator>bumblebee</dc:creator>
		<pubDate>Mon, 21 May 2007 02:58:29 +0000</pubDate>
		<guid isPermaLink="false">http://yankees.lhblogs.com/2007/05/19/a-note-on-the-blog-format/#comment-47696</guid>
		<description>test</description>
		<content:encoded><![CDATA[<p>test</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 12to6</title>
		<link>http://yankees.lhblogs.com/2007/05/19/a-note-on-the-blog-format/comment-page-1/#comment-47377</link>
		<dc:creator>12to6</dc:creator>
		<pubDate>Sun, 20 May 2007 22:26:27 +0000</pubDate>
		<guid isPermaLink="false">http://yankees.lhblogs.com/2007/05/19/a-note-on-the-blog-format/#comment-47377</guid>
		<description>The person with the comment about RSS feeds has a valid point. Feedreaders won&#039;t pick up an &quot;updated&quot; post, so if that&#039;s the only way you read a blog, you&#039;ll miss the updates (and more and more people are now reading via RSS readers).

Secondly, the updates always go at the TOP of a post (take a look around the blogosphere), which is how someone knows that there actually IS an update to a post. If the update is at the bottom, they&#039;re more likely to miss the fact that an update has been posted.</description>
		<content:encoded><![CDATA[<p>The person with the comment about RSS feeds has a valid point. Feedreaders won&#8217;t pick up an &#8220;updated&#8221; post, so if that&#8217;s the only way you read a blog, you&#8217;ll miss the updates (and more and more people are now reading via RSS readers).</p>
<p>Secondly, the updates always go at the TOP of a post (take a look around the blogosphere), which is how someone knows that there actually IS an update to a post. If the update is at the bottom, they&#8217;re more likely to miss the fact that an update has been posted.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bryans</title>
		<link>http://yankees.lhblogs.com/2007/05/19/a-note-on-the-blog-format/comment-page-1/#comment-47150</link>
		<dc:creator>Bryans</dc:creator>
		<pubDate>Sun, 20 May 2007 14:50:31 +0000</pubDate>
		<guid isPermaLink="false">http://yankees.lhblogs.com/2007/05/19/a-note-on-the-blog-format/#comment-47150</guid>
		<description>I am going to go with the updates on the bottom.  That way I can miss one and follow along going down and not hit a &quot;spoiler&quot; if you post the updates at the top of the post...

Keep up the great work!  Thanks!</description>
		<content:encoded><![CDATA[<p>I am going to go with the updates on the bottom.  That way I can miss one and follow along going down and not hit a &#8220;spoiler&#8221; if you post the updates at the top of the post&#8230;</p>
<p>Keep up the great work!  Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin</title>
		<link>http://yankees.lhblogs.com/2007/05/19/a-note-on-the-blog-format/comment-page-1/#comment-47130</link>
		<dc:creator>Justin</dc:creator>
		<pubDate>Sun, 20 May 2007 13:45:31 +0000</pubDate>
		<guid isPermaLink="false">http://yankees.lhblogs.com/2007/05/19/a-note-on-the-blog-format/#comment-47130</guid>
		<description>Thanks for all your updates. I&#039;m down in Texas, so getting news like this can only come from a few sources. You have proven to be the most accurate and the quickest to update. Thanks for adopting the blogging feature!!!</description>
		<content:encoded><![CDATA[<p>Thanks for all your updates. I&#8217;m down in Texas, so getting news like this can only come from a few sources. You have proven to be the most accurate and the quickest to update. Thanks for adopting the blogging feature!!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jimmy</title>
		<link>http://yankees.lhblogs.com/2007/05/19/a-note-on-the-blog-format/comment-page-1/#comment-47097</link>
		<dc:creator>Jimmy</dc:creator>
		<pubDate>Sun, 20 May 2007 05:41:29 +0000</pubDate>
		<guid isPermaLink="false">http://yankees.lhblogs.com/2007/05/19/a-note-on-the-blog-format/#comment-47097</guid>
		<description>Pete,

I love the updates posted on the front page.  I prefer not having to wade through 95% of idiotic comments to get to the meat of what I&#039;m looking for.

Also, I like the newer updates at the bottom.  It just reads better.</description>
		<content:encoded><![CDATA[<p>Pete,</p>
<p>I love the updates posted on the front page.  I prefer not having to wade through 95% of idiotic comments to get to the meat of what I&#8217;m looking for.</p>
<p>Also, I like the newer updates at the bottom.  It just reads better.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ghost of Yankees Past</title>
		<link>http://yankees.lhblogs.com/2007/05/19/a-note-on-the-blog-format/comment-page-1/#comment-47078</link>
		<dc:creator>Ghost of Yankees Past</dc:creator>
		<pubDate>Sun, 20 May 2007 03:16:49 +0000</pubDate>
		<guid isPermaLink="false">http://yankees.lhblogs.com/2007/05/19/a-note-on-the-blog-format/#comment-47078</guid>
		<description>Phil Oye-0

what rss feeder/reader do you use/recommend??</description>
		<content:encoded><![CDATA[<p>Phil Oye-0</p>
<p>what rss feeder/reader do you use/recommend??</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Phil Oye</title>
		<link>http://yankees.lhblogs.com/2007/05/19/a-note-on-the-blog-format/comment-page-1/#comment-47054</link>
		<dc:creator>Phil Oye</dc:creator>
		<pubDate>Sun, 20 May 2007 02:22:02 +0000</pubDate>
		<guid isPermaLink="false">http://yankees.lhblogs.com/2007/05/19/a-note-on-the-blog-format/#comment-47054</guid>
		<description>Putting update on the lineup post itself is great. However, I would strongly recommend that you put newer updates at the bottom, rather than the top. That way, if you read the post late you won&#039;t get confused by the updates, especially when updates contradict an earlier (&quot;he&#039;s injured!&quot; to &quot;Err, never mind!&quot;, if the latter was first that would be bad).

Also, as long as the post is properly updated in WordPress or whatever you&#039;re using, the RSS feed will update the entry so us RSS readers won&#039;t miss anything.</description>
		<content:encoded><![CDATA[<p>Putting update on the lineup post itself is great. However, I would strongly recommend that you put newer updates at the bottom, rather than the top. That way, if you read the post late you won&#8217;t get confused by the updates, especially when updates contradict an earlier (&#8220;he&#8217;s injured!&#8221; to &#8220;Err, never mind!&#8221;, if the latter was first that would be bad).</p>
<p>Also, as long as the post is properly updated in WordPress or whatever you&#8217;re using, the RSS feed will update the entry so us RSS readers won&#8217;t miss anything.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

