<?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: Updating Your Blog Posts</title>
	<atom:link href="http://www.blogherald.com/2007/12/10/updating-your-blog-posts/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.blogherald.com/2007/12/10/updating-your-blog-posts/</link>
	<description>The leading source of news covering social media and the blogosphere.</description>
	<lastBuildDate>Mon, 13 Feb 2012 02:30:55 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Alta Sowl</title>
		<link>http://www.blogherald.com/2007/12/10/updating-your-blog-posts/comment-page-1/#comment-1128286</link>
		<dc:creator>Alta Sowl</dc:creator>
		<pubDate>Thu, 15 Dec 2011 02:36:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.blogherald.com/2007/12/10/updating-your-blog-posts/#comment-1128286</guid>
		<description>Great post!</description>
		<content:encoded><![CDATA[<p>Great post!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: See Justin and Selina nude Video</title>
		<link>http://www.blogherald.com/2007/12/10/updating-your-blog-posts/comment-page-1/#comment-1126173</link>
		<dc:creator>See Justin and Selina nude Video</dc:creator>
		<pubDate>Tue, 13 Dec 2011 19:08:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.blogherald.com/2007/12/10/updating-your-blog-posts/#comment-1126173</guid>
		<description>Zune and iPod: Most people compare the Zune to the Touch, but after seeing how slim and surprisingly small and light it is, I consider it to be a rather unique hybrid that combines qualities of both the Touch and the Nano. It&#039;s very colorful and lovely OLED screen is slightly smaller than the touch screen, but the player itself feels quite a bit smaller and lighter. It weighs about 2/3 as much, and is noticeably smaller in width and height, while being just a hair thicker.</description>
		<content:encoded><![CDATA[<p>Zune and iPod: Most people compare the Zune to the Touch, but after seeing how slim and surprisingly small and light it is, I consider it to be a rather unique hybrid that combines qualities of both the Touch and the Nano. It&#8217;s very colorful and lovely OLED screen is slightly smaller than the touch screen, but the player itself feels quite a bit smaller and lighter. It weighs about 2/3 as much, and is noticeably smaller in width and height, while being just a hair thicker.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ajay</title>
		<link>http://www.blogherald.com/2007/12/10/updating-your-blog-posts/comment-page-1/#comment-1105619</link>
		<dc:creator>ajay</dc:creator>
		<pubDate>Sat, 17 Oct 2009 04:38:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.blogherald.com/2007/12/10/updating-your-blog-posts/#comment-1105619</guid>
		<description>hi i wold like to do edit and update the post with strike through features how will possible this can any one help meeeeeeee?</description>
		<content:encoded><![CDATA[<p>hi i wold like to do edit and update the post with strike through features how will possible this can any one help meeeeeeee?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anne Helmond</title>
		<link>http://www.blogherald.com/2007/12/10/updating-your-blog-posts/comment-page-1/#comment-289124</link>
		<dc:creator>Anne Helmond</dc:creator>
		<pubDate>Thu, 13 Dec 2007 11:11:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.blogherald.com/2007/12/10/updating-your-blog-posts/#comment-289124</guid>
		<description>Thank you all for sharing updating insights. I think the preferred method depends on the context and the type of blog. As a news blog thrives on news and thus constantly receives new insights, a new post would make most sense. But for a personal blog an update in the &#039;old&#039; post might be preferred, taking into account that readers might not be aware of these updates.

It&#039;s great to hear everyone&#039;s different methods and reasons for updating a post. It actually made me reconsider my own method. If it was a minor update I would post a comment to my old post and if it was a major update I would write a new post.

I think that from now on I will use a new post for every kind of update because, as Candice pointed out, a blog evolves. And a small update notice in bold at the end of the old post because not everyone will notice the pingback to the new post.</description>
		<content:encoded><![CDATA[<p>Thank you all for sharing updating insights. I think the preferred method depends on the context and the type of blog. As a news blog thrives on news and thus constantly receives new insights, a new post would make most sense. But for a personal blog an update in the &#8216;old&#8217; post might be preferred, taking into account that readers might not be aware of these updates.</p>
<p>It&#8217;s great to hear everyone&#8217;s different methods and reasons for updating a post. It actually made me reconsider my own method. If it was a minor update I would post a comment to my old post and if it was a major update I would write a new post.</p>
<p>I think that from now on I will use a new post for every kind of update because, as Candice pointed out, a blog evolves. And a small update notice in bold at the end of the old post because not everyone will notice the pingback to the new post.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marco</title>
		<link>http://www.blogherald.com/2007/12/10/updating-your-blog-posts/comment-page-1/#comment-287525</link>
		<dc:creator>Marco</dc:creator>
		<pubDate>Tue, 11 Dec 2007 21:43:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.blogherald.com/2007/12/10/updating-your-blog-posts/#comment-287525</guid>
		<description>I update posts quite a lot. I tend to put UPDATE: within a strong tag to indicate this.

When new insights come in I feel it would be stupid to not reflect those in the post. I know RSS people might not see it but the post will last for a long time so I think it&#039;s still worth it.</description>
		<content:encoded><![CDATA[<p>I update posts quite a lot. I tend to put UPDATE: within a strong tag to indicate this.</p>
<p>When new insights come in I feel it would be stupid to not reflect those in the post. I know RSS people might not see it but the post will last for a long time so I think it&#8217;s still worth it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Angel</title>
		<link>http://www.blogherald.com/2007/12/10/updating-your-blog-posts/comment-page-1/#comment-287520</link>
		<dc:creator>Angel</dc:creator>
		<pubDate>Tue, 11 Dec 2007 21:33:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.blogherald.com/2007/12/10/updating-your-blog-posts/#comment-287520</guid>
		<description>For me, and I am nowhere near being a prominent blogger, it depends. A small detail usually means I just do an &quot;update note&quot; at the end of the post. I bold the &quot;Update Note&quot; text and put in parenthesis a date (and time if it is in the same day), then type whatever the new information is. For something more substantial, I would likely write a new post and link to the previous one. 

Best, and keep on blogging.</description>
		<content:encoded><![CDATA[<p>For me, and I am nowhere near being a prominent blogger, it depends. A small detail usually means I just do an &#8220;update note&#8221; at the end of the post. I bold the &#8220;Update Note&#8221; text and put in parenthesis a date (and time if it is in the same day), then type whatever the new information is. For something more substantial, I would likely write a new post and link to the previous one. </p>
<p>Best, and keep on blogging.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Zach</title>
		<link>http://www.blogherald.com/2007/12/10/updating-your-blog-posts/comment-page-1/#comment-287227</link>
		<dc:creator>Zach</dc:creator>
		<pubDate>Tue, 11 Dec 2007 13:21:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.blogherald.com/2007/12/10/updating-your-blog-posts/#comment-287227</guid>
		<description>My blog is built all around breaking news and the like.  It just makes more sense for me to make a new post.</description>
		<content:encoded><![CDATA[<p>My blog is built all around breaking news and the like.  It just makes more sense for me to make a new post.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rupert</title>
		<link>http://www.blogherald.com/2007/12/10/updating-your-blog-posts/comment-page-1/#comment-286878</link>
		<dc:creator>Rupert</dc:creator>
		<pubDate>Tue, 11 Dec 2007 03:56:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.blogherald.com/2007/12/10/updating-your-blog-posts/#comment-286878</guid>
		<description>I am constantly doing this, sometimes I may write something in the morning with a &quot;This post will grow&quot; statement for my readers to come back later on to see what I have updated, often at times three or four times during the day - once I actually had a fellow Blogger comment that she had been sitting, checking back every fifteen minutes or so as I updated.

Rupert</description>
		<content:encoded><![CDATA[<p>I am constantly doing this, sometimes I may write something in the morning with a &#8220;This post will grow&#8221; statement for my readers to come back later on to see what I have updated, often at times three or four times during the day &#8211; once I actually had a fellow Blogger comment that she had been sitting, checking back every fifteen minutes or so as I updated.</p>
<p>Rupert</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anne Helmond</title>
		<link>http://www.blogherald.com/2007/12/10/updating-your-blog-posts/comment-page-1/#comment-286841</link>
		<dc:creator>Anne Helmond</dc:creator>
		<pubDate>Tue, 11 Dec 2007 02:24:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.blogherald.com/2007/12/10/updating-your-blog-posts/#comment-286841</guid>
		<description>@Sue Thank you for sharing your insights. Your remark regarding using the comment section for updates is really valuable. I sometimes write a comment so it won&#039;t interfere with the original post, but the fact that most readers will not be informed of this update is a really important issue to keep in mind.

@ia Yes indeed, that&#039;s why I mentioned &lt;strike&gt; is deprecated. Maybe I should have explicitly stated that &lt;strike&gt; is not a structural element and that &lt;del&gt; is the preferred option but I&#039;m not going to use &lt;ins&gt; in my post because it would simply be too confusing ;)</description>
		<content:encoded><![CDATA[<p>@Sue Thank you for sharing your insights. Your remark regarding using the comment section for updates is really valuable. I sometimes write a comment so it won&#8217;t interfere with the original post, but the fact that most readers will not be informed of this update is a really important issue to keep in mind.</p>
<p>@ia Yes indeed, that&#8217;s why I mentioned &lt;strike&gt; is deprecated. Maybe I should have explicitly stated that &lt;strike&gt; is not a structural element and that &lt;del&gt; is the preferred option but I&#8217;m not going to use &lt;ins&gt; in my post because it would simply be too confusing ;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Candice</title>
		<link>http://www.blogherald.com/2007/12/10/updating-your-blog-posts/comment-page-1/#comment-286839</link>
		<dc:creator>Candice</dc:creator>
		<pubDate>Tue, 11 Dec 2007 02:15:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.blogherald.com/2007/12/10/updating-your-blog-posts/#comment-286839</guid>
		<description>I never edit posts for anything other than spelling, grammar, or awkward phrases. And I never would. I wouldn&#039;t say that a blog evolves, I&#039;d say that it grows. The contents generally don&#039;t change much -- they are added to. If I wanted something else out of my website, I wouldn&#039;t organize it primarily chronologically.

Most likely, I would add a new entry, and if I was feeling helpful, add a link to it from the old one.

Plus, it irritates me when people make significant changes to their posts, for several reasons. One of the main ones being that if they add anything of interest, I most likely will never see it, since I do most of my reading through RSS. The only edits I usually see are those that happen to be made before Google pulls the feed.</description>
		<content:encoded><![CDATA[<p>I never edit posts for anything other than spelling, grammar, or awkward phrases. And I never would. I wouldn&#8217;t say that a blog evolves, I&#8217;d say that it grows. The contents generally don&#8217;t change much &#8212; they are added to. If I wanted something else out of my website, I wouldn&#8217;t organize it primarily chronologically.</p>
<p>Most likely, I would add a new entry, and if I was feeling helpful, add a link to it from the old one.</p>
<p>Plus, it irritates me when people make significant changes to their posts, for several reasons. One of the main ones being that if they add anything of interest, I most likely will never see it, since I do most of my reading through RSS. The only edits I usually see are those that happen to be made before Google pulls the feed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Quandary</title>
		<link>http://www.blogherald.com/2007/12/10/updating-your-blog-posts/comment-page-1/#comment-286797</link>
		<dc:creator>Quandary</dc:creator>
		<pubDate>Tue, 11 Dec 2007 01:14:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.blogherald.com/2007/12/10/updating-your-blog-posts/#comment-286797</guid>
		<description>I tend to prefer a combination of &lt;del&gt;, &lt;ins&gt;, and &lt;em&gt;. I&#039;ll generally use the former two for minor updates/corrections, and reserve &lt;em&gt; for use with a paragraph at the start of the post, to indicate huge situation changes that void the post&#039;s original content. I generally use In Series only ongoing sagas, not really &quot;updates&quot; -- but I do appreciate the mention in any case. :)</description>
		<content:encoded><![CDATA[<p>I tend to prefer a combination of &lt;del&gt;, &lt;ins&gt;, and &lt;em&gt;. I&#8217;ll generally use the former two for minor updates/corrections, and reserve &lt;em&gt; for use with a paragraph at the start of the post, to indicate huge situation changes that void the post&#8217;s original content. I generally use In Series only ongoing sagas, not really &#8220;updates&#8221; &#8212; but I do appreciate the mention in any case. :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ia</title>
		<link>http://www.blogherald.com/2007/12/10/updating-your-blog-posts/comment-page-1/#comment-286785</link>
		<dc:creator>ia</dc:creator>
		<pubDate>Tue, 11 Dec 2007 00:57:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.blogherald.com/2007/12/10/updating-your-blog-posts/#comment-286785</guid>
		<description>&lt;strike&gt; is a purely decorative element and has no semantic value, while &lt;del&gt; is preferred. It&#039;s even available in the WP editor toolbar (along with &lt;ins&gt;), so it&#039;s a better choice whether it&#039;s indicating deleted text or sarcasm. :)</description>
		<content:encoded><![CDATA[<p>&lt;strike&gt; is a purely decorative element and has no semantic value, while &lt;del&gt; is preferred. It&#8217;s even available in the WP editor toolbar (along with &lt;ins&gt;), so it&#8217;s a better choice whether it&#8217;s indicating deleted text or sarcasm. :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sue</title>
		<link>http://www.blogherald.com/2007/12/10/updating-your-blog-posts/comment-page-1/#comment-286779</link>
		<dc:creator>Sue</dc:creator>
		<pubDate>Tue, 11 Dec 2007 00:44:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.blogherald.com/2007/12/10/updating-your-blog-posts/#comment-286779</guid>
		<description>I&#039;d always wondered which way to go when doing an update. If there&#039;s enough information that has changed, I&#039;ll do a whole new post on the subject. If it&#039;s just a little addendum, I&#039;ll write at the bottom of the post) in bold, Edit: and add what is updated. I rarely leave a comment to update, as that way, those reading in feed readers or via email will not get the benefit of the updated information. 
I also use a sideblog, for updates and corrections. That works well in most cases. It&#039;s just the right size for a mini-post. 
I think the use of strikethrough is rarely justified. That tactic is more for legal documents, and it strikes me as improper usage and is kind of irritating when I see it overdone.</description>
		<content:encoded><![CDATA[<p>I&#8217;d always wondered which way to go when doing an update. If there&#8217;s enough information that has changed, I&#8217;ll do a whole new post on the subject. If it&#8217;s just a little addendum, I&#8217;ll write at the bottom of the post) in bold, Edit: and add what is updated. I rarely leave a comment to update, as that way, those reading in feed readers or via email will not get the benefit of the updated information.<br />
I also use a sideblog, for updates and corrections. That works well in most cases. It&#8217;s just the right size for a mini-post.<br />
I think the use of strikethrough is rarely justified. That tactic is more for legal documents, and it strikes me as improper usage and is kind of irritating when I see it overdone.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

