<?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: How to Write Good Blog Post Disclaimers</title>
	<atom:link href="http://usabilityworks.org/2007/02/02/how-to-write-good-blog-post-disclaimers/feed/" rel="self" type="application/rss+xml" />
	<link>http://usabilityworks.org/2007/02/02/how-to-write-good-blog-post-disclaimers/</link>
	<description>Making next year's Human-Computer family reunion a lot less uncomfortable.</description>
	<pubDate>Thu, 20 Nov 2008 00:13:41 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: Matthew Oliphant</title>
		<link>http://usabilityworks.org/2007/02/02/how-to-write-good-blog-post-disclaimers/#comment-14676</link>
		<dc:creator>Matthew Oliphant</dc:creator>
		<pubDate>Sat, 03 Feb 2007 01:28:54 +0000</pubDate>
		<guid isPermaLink="false">http://usabilityworks.org/2007/02/02/how-to-write-good-blog-post-disclaimers/#comment-14676</guid>
		<description>More disclosureness...  &lt;a href="http://scobleizer.com/2007/02/02/payperspeech-disclosure/" rel="nofollow"&gt;Scoble discloses being paid by PayPerPost&lt;/a&gt;.

I honestly think this makes a bigger deal out of things than is necessary.  Should he tell?  Yes.  Should it be the point of the post?  I don't think so.

Though for someone like Scoble, perhaps this is an easier way to deal with it than answering any queries as to his motivation in the comments.</description>
		<content:encoded><![CDATA[<p>More disclosureness&#8230;  <a href="http://scobleizer.com/2007/02/02/payperspeech-disclosure/" rel="nofollow">Scoble discloses being paid by PayPerPost</a>.</p>
<p>I honestly think this makes a bigger deal out of things than is necessary.  Should he tell?  Yes.  Should it be the point of the post?  I don&#8217;t think so.</p>
<p>Though for someone like Scoble, perhaps this is an easier way to deal with it than answering any queries as to his motivation in the comments.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matthew Oliphant</title>
		<link>http://usabilityworks.org/2007/02/02/how-to-write-good-blog-post-disclaimers/#comment-14670</link>
		<dc:creator>Matthew Oliphant</dc:creator>
		<pubDate>Sat, 03 Feb 2007 00:44:46 +0000</pubDate>
		<guid isPermaLink="false">http://usabilityworks.org/2007/02/02/how-to-write-good-blog-post-disclaimers/#comment-14670</guid>
		<description>Admittedly, this entire post started with the stray thoughtage of, "Hm, wonder why he wrote that disclaimer... Shouldn't that be claimer... I need more coffee... I need to write a post..."

I highly recommend you delete the disclaimer.  Also, I recommend you leave it.  Yeah, one of those. :)

And that's a good idea: call it what it is!

Brag: Scott Berkun commented on my blog.</description>
		<content:encoded><![CDATA[<p>Admittedly, this entire post started with the stray thoughtage of, &#8220;Hm, wonder why he wrote that disclaimer&#8230; Shouldn&#8217;t that be claimer&#8230; I need more coffee&#8230; I need to write a post&#8230;&#8221;</p>
<p>I highly recommend you delete the disclaimer.  Also, I recommend you leave it.  Yeah, one of those. :)</p>
<p>And that&#8217;s a good idea: call it what it is!</p>
<p>Brag: Scott Berkun commented on my blog.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Natalie Jost</title>
		<link>http://usabilityworks.org/2007/02/02/how-to-write-good-blog-post-disclaimers/#comment-14665</link>
		<dc:creator>Natalie Jost</dc:creator>
		<pubDate>Sat, 03 Feb 2007 00:16:56 +0000</pubDate>
		<guid isPermaLink="false">http://usabilityworks.org/2007/02/02/how-to-write-good-blog-post-disclaimers/#comment-14665</guid>
		<description>Hey Scott, for changes made, you can use the &#60;ins&#62; tag to "insert" new information. Likewise &#60;del&#62; is used to strike out text which no longer applies. I should use those both more than I do. :)

</description>
		<content:encoded><![CDATA[<p>Hey Scott, for changes made, you can use the &lt;ins&gt; tag to &#8220;insert&#8221; new information. Likewise &lt;del&gt; is used to strike out text which no longer applies. I should use those both more than I do. :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Berkun</title>
		<link>http://usabilityworks.org/2007/02/02/how-to-write-good-blog-post-disclaimers/#comment-14656</link>
		<dc:creator>Scott Berkun</dc:creator>
		<pubDate>Fri, 02 Feb 2007 22:55:06 +0000</pubDate>
		<guid isPermaLink="false">http://usabilityworks.org/2007/02/02/how-to-write-good-blog-post-disclaimers/#comment-14656</guid>
		<description>Guilty as charged. If I promise to do better next time, can I get a suspended sentence, or early parole? 

I think I've been annoyed when I discover, midway through a piece, that the writer owns stock in / is married to / or is under magic spells from / the subject of the article.  Tucking it away does have its elegance, and I'm all for flow, but it also seems like hiding broccoli in the mashed potatoes. 

In this case I really don't know why I even mentioned it. I met Bill once 5 years ago and who would care to know that? Or would think that would impact the objectivity of my review? I think now I was probably bragging.

And now an additional dilemma: now that I'm writing all this, is the proper etiquette to go back and strip that lead disclaimer out? Or is removing it worse that leaving it in, as it would break your example in your essay. I wish there were a standard, simple way to notate that changes have been made to live posts but I don't know of one.</description>
		<content:encoded><![CDATA[<p>Guilty as charged. If I promise to do better next time, can I get a suspended sentence, or early parole? </p>
<p>I think I&#8217;ve been annoyed when I discover, midway through a piece, that the writer owns stock in / is married to / or is under magic spells from / the subject of the article.  Tucking it away does have its elegance, and I&#8217;m all for flow, but it also seems like hiding broccoli in the mashed potatoes. </p>
<p>In this case I really don&#8217;t know why I even mentioned it. I met Bill once 5 years ago and who would care to know that? Or would think that would impact the objectivity of my review? I think now I was probably bragging.</p>
<p>And now an additional dilemma: now that I&#8217;m writing all this, is the proper etiquette to go back and strip that lead disclaimer out? Or is removing it worse that leaving it in, as it would break your example in your essay. I wish there were a standard, simple way to notate that changes have been made to live posts but I don&#8217;t know of one.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matthew Oliphant</title>
		<link>http://usabilityworks.org/2007/02/02/how-to-write-good-blog-post-disclaimers/#comment-14623</link>
		<dc:creator>Matthew Oliphant</dc:creator>
		<pubDate>Fri, 02 Feb 2007 20:14:31 +0000</pubDate>
		<guid isPermaLink="false">http://usabilityworks.org/2007/02/02/how-to-write-good-blog-post-disclaimers/#comment-14623</guid>
		<description>I constantly editorialize my writing (look at all those parentheticals and statements between commas up there!)

(disclosure: I can't help it.) :)  

Just like you, random thoughtage.  It's a word now.</description>
		<content:encoded><![CDATA[<p>I constantly editorialize my writing (look at all those parentheticals and statements between commas up there!)</p>
<p>(disclosure: I can&#8217;t help it.) :)  </p>
<p>Just like you, random thoughtage.  It&#8217;s a word now.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Natalie Jost</title>
		<link>http://usabilityworks.org/2007/02/02/how-to-write-good-blog-post-disclaimers/#comment-14597</link>
		<dc:creator>Natalie Jost</dc:creator>
		<pubDate>Fri, 02 Feb 2007 16:48:24 +0000</pubDate>
		<guid isPermaLink="false">http://usabilityworks.org/2007/02/02/how-to-write-good-blog-post-disclaimers/#comment-14597</guid>
		<description>As a person who uses a lot of "by the ways" in her writing, I laughed and laughed at this. You're right, of course, though in my case, I have to say, it's not so much disclaimer or disclosure but simply random thoughts that come to mind after the fact and I feel I must include them right then and there without forethought (or morethought may be a better word). See, no disclosure, just random toughtage (thoughtage? um, ok, thoughtage). :)</description>
		<content:encoded><![CDATA[<p>As a person who uses a lot of &#8220;by the ways&#8221; in her writing, I laughed and laughed at this. You&#8217;re right, of course, though in my case, I have to say, it&#8217;s not so much disclaimer or disclosure but simply random thoughts that come to mind after the fact and I feel I must include them right then and there without forethought (or morethought may be a better word). See, no disclosure, just random toughtage (thoughtage? um, ok, thoughtage). :)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
