<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>contentious.com &#187; Real World Writing</title>
	<atom:link href="http://www.contentious.com/category/real-world-writing/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.contentious.com</link>
	<description>Amy Gahran's news and musings on how we communicate in the online age.</description>
	<lastBuildDate>Thu, 19 Jan 2012 17:13:24 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
		<item>
		<title>Transparency vs. Payola: Weighing Risks</title>
		<link>http://www.contentious.com/2006/10/11/transparency-vs-payola-weighing-risks/</link>
		<comments>http://www.contentious.com/2006/10/11/transparency-vs-payola-weighing-risks/#comments</comments>
		<pubDate>Wed, 11 Oct 2006 19:50:03 +0000</pubDate>
		<dc:creator>Amy Gahran</dc:creator>
				<category><![CDATA[Conversations]]></category>
		<category><![CDATA[Media Musings]]></category>
		<category><![CDATA[Net Effects on Society]]></category>
		<category><![CDATA[Real World Writing]]></category>
		<category><![CDATA[Voices: Blogs, etc.]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[Ppp PayPerPost: Worth the risk? Over at the Center for Citizen Media blog, I&#8217;ve joined an interesting conversation concerning the thorny issue of payola in online media. See: PayPerPost: A Cancer on the Blogosphere, or Merely Semi-Sleazy? by Dan Gillmor. Background: The controversial online advertising service PayPerPost attracted considerable blog and media attention after it [...]]]></description>
			<content:encoded><![CDATA[<table width="208" cellpadding="5" align="left">
<tbody>
<tr>
<td><div class="img " style="width:203px;">
	<img src="http://agahran.typepad.com/photos/uncategorized/ppp.jpg" alt="Ppp" width="203" height="70" />
	<div>Ppp</div>
</div></td>
</tr>
<tr>
<td><strong><span style="color: #cc0033;">PayPerPost: Worth the risk?</span></strong></td>
</tr>
</tbody>
</table>
<p>Over at the Center for Citizen Media blog, I&#8217;ve joined an interesting conversation concerning the thorny issue of <a href="http://en.wikipedia.org/wiki/Payola">payola</a> in online media. See: <a href="http://citmedia.org/blog/2006/10/09/payperpost-a-cancer-on-the-blogosphere-or-merely-semi-sleazy/">PayPerPost: A Cancer on the Blogosphere, or Merely Semi-Sleazy?</a> by <strong>Dan Gillmor</strong>.</p>
<p><em>Background: </em>The controversial online advertising service <a href="http://payperpost.com/">PayPerPost</a> attracted considerable blog and media attention after it recently got <a href="http://charlotte.bizjournals.com/orlando/stories/2006/10/02/daily24.html">$3 million in venture funding</a>. In a nutshell, PayPerPost is an automated system where companies can advertise their sites, products, services, or brands through a network of approved bloggers who get paid $2 per qualifying post. That is, bloggers who sign on to PayPerPost agree to write about those advertisers.</p>
<p>PayPerPost reviews and approves those posts, which can be required to be positive. Although PayPerPost urges its bloggers to be &quot;honest,&quot; it <a href="http://blog.payperpost.com/2006/07/deal-with-disclosure.html">discourages</a> them from disclosing their relationship with PayPerPost. So, ethically, everyone involved appears to be on thin ice &#8212; but when did ethics ever have much to do with the advertising business?</p>
<p>&#8230;Anyway, Dan Gillmor&#8217;s post on the PayPerPost flap nudged me to consider the issue of payola more closely. Here are a couple of comments I contributed to that discussion&#8230;</p>
<p><b>READ THE REST OF THIS ARTICLE over at my other blog, <a href="http://www.rightconversation.com/2006/10/transparency_vs.html">The Right Conversation</a>&#8230;</b><br />
&#8211; If you wish to leave a comment on this post, you can do so there.</p></p>
<div name="googleone_share_1" style="position:relative;z-index:5;float: right; margin-left: 10px;"><g:plusone size="tall" count="1" href="http://www.contentious.com/2006/10/11/transparency-vs-payola-weighing-risks/"></g:plusone></div>]]></content:encoded>
			<wfw:commentRss>http://www.contentious.com/2006/10/11/transparency-vs-payola-weighing-risks/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Blogging Gets Bumpy, and that\&#8217;s OK</title>
		<link>http://www.contentious.com/2006/10/08/blogging-gets-bumpy-and-thats-ok/</link>
		<comments>http://www.contentious.com/2006/10/08/blogging-gets-bumpy-and-thats-ok/#comments</comments>
		<pubDate>Mon, 09 Oct 2006 02:38:02 +0000</pubDate>
		<dc:creator>Amy Gahran</dc:creator>
				<category><![CDATA[Content Style & Business]]></category>
		<category><![CDATA[Conversations]]></category>
		<category><![CDATA[Real World Writing]]></category>
		<category><![CDATA[Voices: Blogs, etc.]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[Recently, PR blogger Kami Huyse published an interesting article: 5 Tips to Avoid Comment Hell: Dealing with Trolls. There, she posed a crucial question for new bloggers who are nervous about allowing comments on their blogs: &#34;I have had many clients ask me about the risks of blogging. How do you keep competitors and arch [...]]]></description>
			<content:encoded><![CDATA[<p>Recently, PR blogger <strong>Kami Huyse</strong> published an interesting article: <a href="http://overtonecomm.blogspot.com/2006/10/5-tips-to-avoid-comment-hell-dealing.html">5 Tips to Avoid Comment Hell: Dealing with Trolls</a>. There, she posed a crucial question for new bloggers who are nervous about allowing comments on their blogs:</p>
<blockquote>
<p><em>&quot;I have had many clients ask me about the risks of blogging. How do you keep competitors and arch enemies from taking over the conversation and dissolving the &#8216;conversation&#8217; into a shouting match?&quot;</em>
</p>
</blockquote>
<p>Her answers:
</p>
<ol>
<li>Moderate comments.
</li>
<li>Have a written comment policy to manage expectations.
</li>
<li>Be in it for the long haul.
</li>
<li>Ban grossly abusive comments, but let most negative comments ride.
</li>
<li>Turn comments off if necessary, preferably temporarily.
</li>
</ol>
<p>A few quibbles notwithstanding, I mostly agree with Kami&#8217;s advice.</p>
<p>That said, I also believe it&#8217;s important for everyone who chooses to participate in conversational media to learn how to handle the inevitable unpleasant bumps of conflict and even flames.That&#8217;s not something you can learn theoretically. Personally I think you need to live through it. Only then can you put Kami&#8217;s advice into balanced practice. Otherwise, you might be tempted to protect yourself into total vulnerability.</p>
<p>Of course, surviving public conversational conflicts is not fun &#8212; but it&#8217;s crucial. If there&#8217;s one thing you learn fast in conversational media, it&#8217;s that <strong>you can never really control the conversation</strong>. Most of it happens in venues that are beyond your control, anyway The best you can do is influence it. </p>
<p>I raised that issue in this comment to Kami&#8217;s post&#8230;</p>
<p><b>READ THE REST of this article</b> over at my other blog, <a href="http://www.rightconversation.com/2006/10/blogging_gets_b.html#more">The Right Conversation</a>&#8230;</p></p>
<div name="googleone_share_1" style="position:relative;z-index:5;float: right; margin-left: 10px;"><g:plusone size="tall" count="1" href="http://www.contentious.com/2006/10/08/blogging-gets-bumpy-and-thats-ok/"></g:plusone></div>]]></content:encoded>
			<wfw:commentRss>http://www.contentious.com/2006/10/08/blogging-gets-bumpy-and-thats-ok/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Apologizing: Good for Your Reputation</title>
		<link>http://www.contentious.com/2006/09/29/apologizing-good-for-your-reputation/</link>
		<comments>http://www.contentious.com/2006/09/29/apologizing-good-for-your-reputation/#comments</comments>
		<pubDate>Fri, 29 Sep 2006 16:37:09 +0000</pubDate>
		<dc:creator>Amy Gahran</dc:creator>
				<category><![CDATA[Content Style & Business]]></category>
		<category><![CDATA[Conversations]]></category>
		<category><![CDATA[Net Effects on Society]]></category>
		<category><![CDATA[Real World Writing]]></category>
		<category><![CDATA[Voices: Blogs, etc.]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[Often I&#8217;m amazed at how the universe conspires to hit me over the head with a theme, yelling &#8220;You MUST blog this!&#8221; That&#8217;s just happened this morning on the theme of apologies. Particularly, how crucial apologies are to public discourse &#8212; and to re-establishing broken trust with your core community and the general public. Everyone [...]]]></description>
			<content:encoded><![CDATA[<p>Often I&#8217;m amazed at how the universe conspires to hit me over the head with a theme, yelling &#8220;You MUST blog this!&#8221; That&#8217;s just happened this morning on the theme of apologies. Particularly, how crucial apologies are to public discourse &#8212; and to re-establishing broken trust with your core community and the general public.</p>
<p>Everyone messes up sometime. However, acknowledging your role in a problem, apologizing for it, and making amends is not a sign of weakness. In fact, it&#8217;s often the bravest, strongest, smartest, and most constructive thing an individual, publisher, or organization can do. Especially because conversational media has a way of amplifying any failure to apologize, thus making the consequences of your original screw-up much worse in the long run.</p>
<p>Here are all the hints on this theme that fate has handed me in the last 24 hours&#8230;</p>
<p><strong><a href="http://www.rightconversation.com/2006/09/apologizing_goo.html#more">READ MORE</a> at my other blog, The Right Conversation&#8230;</strong></p>
<div name="googleone_share_1" style="position:relative;z-index:5;float: right; margin-left: 10px;"><g:plusone size="tall" count="1" href="http://www.contentious.com/2006/09/29/apologizing-good-for-your-reputation/"></g:plusone></div>]]></content:encoded>
			<wfw:commentRss>http://www.contentious.com/2006/09/29/apologizing-good-for-your-reputation/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Explaining Substantive Edits: Good Idea (Rewriting Blog History, Part 2)</title>
		<link>http://www.contentious.com/2006/08/03/explaining-substantive-edits-good-idea-rewriting-blog-history-part-2/</link>
		<comments>http://www.contentious.com/2006/08/03/explaining-substantive-edits-good-idea-rewriting-blog-history-part-2/#comments</comments>
		<pubDate>Thu, 03 Aug 2006 17:41:20 +0000</pubDate>
		<dc:creator>Amy Gahran</dc:creator>
				<category><![CDATA[Content Style & Business]]></category>
		<category><![CDATA[Conversations]]></category>
		<category><![CDATA[Real World Writing]]></category>
		<category><![CDATA[Voices: Blogs, etc.]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[<p>Yesterday's post, <a href="http://contentious.com/archives/2006/08/01/rewriting-blog-history-bad-idea">Rewriting blog history: Bad idea</a>, sparked some interesting discussion in its <a href="http://contentious.com/archives/2006/08/01/rewriting-blog-history-bad-idea#comments">comments thread</a> and in other weblogs (by <a href="http://www.intuitive.com/blog/should_you_ever_edit_or_delete_blog_entries.html">Dave Taylor</a>, <a href="http://webfeed.wordpress.com/2006/08/01/dave-winers-disapearing-posts/">Tom Simpson</a>, and <a href="http://www.newsome.org/2006/08/itchy-fingers-in-blogosphere.shtml">Kent Newsome</a>). 

<p>I realized through this conversation that I hadn't expressed my thoughts clearly enough, so here's a second go at it.

<p>From my perspective, <b>it's perfectly fine to change your mind and revise, retract, or clarify your statements</b>, whether on a blog or elsewhere. In fact, I'm writing this post for exactly that purpose. 

<p>I also think it's a good idea to revisit postings to fix typos, tighten up sentences, etc. -- and if those nit-fixes don't substantially alter your meaning, no need to point them out.

<p>That said, in my experience it <i>is</i> indeed almost always a bad move to delete statements or postings <i>without acknowledgment or explanation</i>. I'm not talking about minor edits -- I'm talking about trying to make content "disappear" and then acting like it never existed. 

<p>That strategy is almost certain to backfire -- causing a bigger fuss than a simple explanation would have done, and possibly damaging your reputation or credibility in the process.

<p>In short, ethical conduct online means <b>owning up to what you publish</b> -- even if you have to remove it. And there may well be good reasons to remove it (legal, factual, ethical, social, and so on).

<p>Here's a fairly recent example from my own experience...</p></p></p></p></p></p></p></p>]]></description>
			<content:encoded><![CDATA[<p>Yesterday&#8217;s post, <a href="http://contentious.com/archives/2006/08/01/rewriting-blog-history-bad-idea">Rewriting blog history: Bad idea</a>, sparked some interesting discussion in its <a href="http://contentious.com/archives/2006/08/01/rewriting-blog-history-bad-idea#comments">comments thread</a> and in other weblogs (by <a href="http://www.intuitive.com/blog/should_you_ever_edit_or_delete_blog_entries.html">Dave Taylor</a>, <a href="http://webfeed.wordpress.com/2006/08/01/dave-winers-disapearing-posts/">Tom Simpson</a>, and <a href="http://www.newsome.org/2006/08/itchy-fingers-in-blogosphere.shtml">Kent Newsome</a>). </p>
<p>I realized through this conversation that I hadn&#8217;t expressed my thoughts clearly enough, so here&#8217;s a second go at it.</p>
<p>From my perspective, <b>it&#8217;s perfectly fine to change your mind and revise, retract, or clarify your statements</b>, whether on a blog or elsewhere. In fact, I&#8217;m writing this post for exactly that purpose. </p>
<p>I also think it&#8217;s a good idea to revisit postings to fix typos, tighten up sentences, etc. &#8212; and if those nit-fixes don&#8217;t substantially alter your meaning, no need to point them out.</p>
<p>That said, in my experience it <i>is</i> indeed almost always a bad move to delete statements or postings <i>without acknowledgment or explanation</i>. I&#8217;m not talking about minor edits &#8212; I&#8217;m talking about trying to make content &#8220;disappear&#8221; and then acting like it never existed. </p>
<p>That strategy is almost certain to backfire &#8212; causing a bigger fuss than a simple explanation would have done, and possibly damaging your reputation or credibility in the process.</p>
<p>In short, ethical conduct online means <b>owning up to what you publish</b> &#8212; even if you have to remove it. And there may well be good reasons to remove it (legal, factual, ethical, social, and so on).</p>
<p>Here&#8217;s a fairly recent example from my own experience&#8230;</p>
<p><span id="more-893"></span></p>
<p>On March 12, 2006, I published a posting originally titled <i>&#8220;Alexa&#8217;s &#8216;reach&#8217; stats: More like &#8216;stretch&#8217;.&#8221;</i> Within hours of my posting, several people pointed out to me that my interpretation of a statistical graph was completely mistaken. They were right, I was wrong &#8212; and I was mortified. (I know, this happens to every blogger sometime.)</p>
<p>At that point I assumed there were already some inbound links to my article, gleefully noting my blatant error. And I knew the original version went out into feed readers and elsewhere. I never considered deleting the posting, but if I had it probably would have made me look much worse.</p>
<p>So I owned up to it, immediately. I replaced the posting title with: <a href="http://contentious.com/archives/2006/03/12/alexas-reach-stats-more-like-stretch"><b>Egg on my face about Alexa stats</b></a>. I wrote a disclaimer at the beginning acknowledging and apologizing for my error, and then left the original text in place so people could see to what I was referring. The historical record was left in place, but the correction was made in an un-missable way at the original location.</p>
<p>That strategy worked well for me in that instance, and the minor flap blew over almost immediately.</p>
<p><b>But what about times when you really <i>do</i> need to delete content or postings? </b>Stuff happens. </p>
<p>Say you launched into a public personal attack you now regret, or you disclosed information forbidden by SEC or other rules or laws, or you libeled someone. Those statements need to come down, immediately. What do you do?</p>
<p>Here&#8217;s my advice: </p>
<ul>
<li>At the URL where the original posting or statement appeared, <b>change the headline</b> to indicate there&#8217;s been a correction. This will help with headline-only aggregation views.</li>
<li>Then, <b>delete the necessary text</b>, and replace it with a <b>simple acknowledgment</b>. You could say something as simple as, &#8220;I originally posted some statements here I shouldn&#8217;t have, so I&#8217;ve deleted them. I apologize for my error and any confusion or damage that may have resulted.&#8221;</li>
</ul>
<p>Yes, of course, some people will still squawk. If you make a mistake or go seriously overboard, you&#8217;ve got to expect some heat for it. But believe me, you&#8217;ll look much better in to long run if you own up to errors than if you try to cover them up. Removing published content without explanation <i>always</i> looks like a coverup &#8212; or that you&#8217;re a hothead or thin-skinned.</p>
<p>Some people don&#8217;t really care how it looks or what people say if they remove content. If you&#8217;re one of them, more power to you. Just be aware that it can be a significant tradeoff.</p>
<p>I hope that clarifies my thinking on this topic. I realize that not everyone agrees with me on this, so as always take this as one person&#8217;s perspective. I&#8217;d love to hear more reactions to this. </p>
<p><b>How do <i>you</i> handle missteps on your blog or site?</b> And why do you handle them that way? Please comment below, and offer specific examples if possible.</p>
</p>
</p>
</p>
</p></p>
<div name="googleone_share_1" style="position:relative;z-index:5;float: right; margin-left: 10px;"><g:plusone size="tall" count="1" href="http://www.contentious.com/2006/08/03/explaining-substantive-edits-good-idea-rewriting-blog-history-part-2/"></g:plusone></div>]]></content:encoded>
			<wfw:commentRss>http://www.contentious.com/2006/08/03/explaining-substantive-edits-good-idea-rewriting-blog-history-part-2/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Rewriting blog history: Bad idea</title>
		<link>http://www.contentious.com/2006/08/01/rewriting-blog-history-bad-idea/</link>
		<comments>http://www.contentious.com/2006/08/01/rewriting-blog-history-bad-idea/#comments</comments>
		<pubDate>Wed, 02 Aug 2006 04:36:30 +0000</pubDate>
		<dc:creator>Amy Gahran</dc:creator>
				<category><![CDATA[Real World Writing]]></category>
		<category><![CDATA[Voices: Blogs, etc.]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[<em>(UPDATE AUG. 2:  This post sparked intriguing followup and conversation by <a href="http://www.intuitive.com/blog/should_you_ever_edit_or_delete_blog_entries.html">Dave Taylor</a>, <a href="http://webfeed.wordpress.com/2006/08/01/dave-winers-disapearing-posts/">Tom Simpson</a>, and <a href="http://www.newsome.org/2006/08/itchy-fingers-in-blogosphere.shtml">Kent Newsome.</a> I realize I needed to clarify something about the point I'm making here, which I did in this <a href="http://contentious.com/archives/2006/08/03/explaining-substantive-edits-good-idea-rewriting-blog-history-part-2">followup posting</a>.)</em>

I've seen this happen many times: Someone posts something in haste to a weblog. He later regrets it, recognizes an error or embarrassment, or is criticized for it -- and then deletes the post in equal haste, hoping that erases the event and no one noticed.

While that may seem like a safe strategy (as long as you delete the post quickly, before it gets indexed by search engines), it's actually a very bad idea. In my experience, it's wisest to assume that anything you post online will live forever, regardless of whether you delete it from it's original location.

Here's why that's so...
]]></description>
			<content:encoded><![CDATA[<p><em>(UPDATE AUG. 2:  This post sparked intriguing followup and conversation by <a href="http://www.intuitive.com/blog/should_you_ever_edit_or_delete_blog_entries.html">Dave Taylor</a>, <a href="http://webfeed.wordpress.com/2006/08/01/dave-winers-disapearing-posts/">Tom Simpson</a>, and <a href="http://www.newsome.org/2006/08/itchy-fingers-in-blogosphere.shtml">Kent Newsome.</a> I realize I needed to clarify something about the point I&#8217;m making here, which I did in this <a href="http://contentious.com/archives/2006/08/03/explaining-substantive-edits-good-idea-rewriting-blog-history-part-2">followup posting</a>.)</em></p>
<p>I&#8217;ve seen this happen many times: Someone posts something in haste to a weblog. He later regrets it, recognizes an error or embarrassment, or is criticized for it &#8212; and then deletes the post in equal haste, hoping that erases the event and no one noticed.</p>
<p>While that may seem like a safe strategy (as long as you delete the post quickly, before it gets indexed by search engines), it&#8217;s actually a very bad idea. In my experience, it&#8217;s wisest to assume that anything you post online will live forever, regardless of whether you delete it from its original location. <i>(Note: I fixed a typo in that sentence. Thanks for spotting it, <a href="http://www.intuitive.com/blog/should_you_ever_edit_or_delete_blog_entries.html">Dave Taylor</a>.)</i></p>
<p>Here&#8217;s why that&#8217;s so&#8230;</p>
<p><span id="more-892"></span></p>
<p>As soon as you post something to a weblog, an announcement of that item goes out on the blog&#8217;s feed. This means your feed subscribers will potentially read it &#8212; and also that the text of your posting is <strong>stored in their feed readers</strong>, whether they read it or not. Once they&#8217;ve downloaded the latest content from your feed, you can&#8217;t pull it back. It&#8217;s beyond your control.</p>
<p>Similarly, once your posting is on the web, anyone can use a web archiving tool like <a href="http://furl.net">Furl</a> to save a copy of your page as it appeared. They can do that in just a couple of seconds. So if your page is online for one minute and it intrigues a Furl user who passes by 15 seconds after you posted it, your posting is then stored beyond your control and you can&#8217;t take it back.</p>
<p>Or, another blogger can simply grab and repost your text, photos, etc. That&#8217;s what happened recently to <strong>Dave Winer</strong> when <strong>Ian Bettridge</strong> spotted Winer&#8217;s snarky retort to <a href="http://technovia.typepad.com/technovia/2006/07/sorry_which_cen.html">Bettridge&#8217;s criticism</a> of some <a href="http://www.scripting.com/2006/07/31.html#postblogherThoughts">remarks Winer made about BlogHer</a>. It looks like that criticism pushed Winer&#8217;s buttons and he replied in haste, then quickly deleted that reply &#8212; but not before Bettridge&#8217;s feed reader downloaded the posting. So Bettridge was able to post <a href="http://technovia.typepad.com/technovia/2006/08/thanks_dave_win.html">a copy of Winer&#8217;s retort</a>, and point out that Winer had removed it without explanation.</p>
<p>Which then allowed Bettridge to escalate the conflict by beginning a new posting this way:</p>
<blockquote><p>
&#8220;I&#8217;m sure glad that Dave Winer invented RSS. After all, if he hadn&#8217;t, I might not have spotted the completely missing-the-point response that he posted to my questioning of his comments on BlogHer. Why might I not have spotted it? Because, as he commonly does when he gets things wrong, he removed the post without any explanation.&#8221;
</p></blockquote>
<p>Ouch, that&#8217;s gotta hurt. But that&#8217;s what can happen with weblogs. You can never really shove a published posting entirely down the memory hole. </p>
<p><strong>The bottom line: Think twice &#8212; even thrice &#8212; before you post,</strong> especially if you&#8217;re ticked off at someone who&#8217;s likely trying to bait you into losing your temper.</p>
<p>And if you do make an unfortunate post (either by the tone of your remark, or by the inclusion of errors or embarrassing misunderstandings) <strong>don&#8217;t try to erase your misstep</strong> &#8212; because you probably can&#8217;t. A better approach is to acknowledge what you said, and clarify with a note that you&#8217;ve regretted your hasty response, learned your facts were wrong, etc. Then move on as gracefully as possible.</p>
<p>You&#8217;ll probably still take some heat for that posting, but that&#8217;s life. It&#8217;s better to take heat when owning up to a misjudgement than to be caught trying to pretend it never happened. Which is why it&#8217;s crucial to understand how easy it is to get caught. Weblogs are interconnected, and that connection starts the instant you hit &#8220;publish.&#8221; </p>
<p>There is no grace period in the blogosphere.</p>
<div name="googleone_share_1" style="position:relative;z-index:5;float: right; margin-left: 10px;"><g:plusone size="tall" count="1" href="http://www.contentious.com/2006/08/01/rewriting-blog-history-bad-idea/"></g:plusone></div>]]></content:encoded>
			<wfw:commentRss>http://www.contentious.com/2006/08/01/rewriting-blog-history-bad-idea/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Blogging a book</title>
		<link>http://www.contentious.com/2006/07/10/blogging-a-book/</link>
		<comments>http://www.contentious.com/2006/07/10/blogging-a-book/#comments</comments>
		<pubDate>Mon, 10 Jul 2006 21:53:29 +0000</pubDate>
		<dc:creator>Amy Gahran</dc:creator>
				<category><![CDATA[Amy's Adventures]]></category>
		<category><![CDATA[Conversations]]></category>
		<category><![CDATA[Media Musings]]></category>
		<category><![CDATA[Real World Writing]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[As I mentioned yesterday, on July 9 the San Diego Union-Tribune published an article by Bruce Bigelow called "Dr. Beyster's book (Or: How SAIC's founder stopped worrying about publicity and learned to love the blog)."

No kidding, that's the actual title. Being a die-hard Dr. Strangelove fan, I adore it. And I don't just like the article because I'm quoted in it. (But thanks, Bruce!)

Anyway, this is an example of someone who, like me, is blogging a book...]]></description>
			<content:encoded><![CDATA[<p>As <a href="http://www.rightconversation.com/2006/07/links_for_20060_3.html">I mentioned yesterday</a>, on July 9 the San Diego Union-Tribune published an article by <strong>Bruce Bigelow </strong>called <a href="http://www.signonsandiego.com/uniontrib/20060709/news_lz1b9drbeyste.html"><span class="sansmediumhead">Dr. Beyster&#8217;s book</span></a> <em>(Or: </em><span class="drophead"><em>How SAIC&#8217;s founder stopped worrying about publicity and learned to love the blog).</em></p>
<p>No kidding, that&#8217;s the actual title. Being a die-hard <a href="http://www.indelibleinc.com/kubrick/films/strangelove/audio/icanwalk.wav">Dr. Strangelove</a> fan, I adore it. And I don&#8217;t just like the article because I&#8217;m quoted in it. (But thanks, Bruce!)</p>
<p>Anyway, this article is about how </span><span class="newstext"><strong>J. Robert Beyster</strong>,</span><span class="drophead"> founder of one of the major super-spooky defense/intelligence contractors, <a href="http://www.saic.com/">SAIC</a>, is using a <a href="http://www.beyster.com/blog/">blog</a> to support/enhance the process of writing a book about the evolution of that employee-owned company. This is rather like what what <strong>Robert Scoble</strong> and <strong>Shel Israel</strong> did for <a href="http://www.bestwebbuys.com/Naked_Conversations-ISBN_047174719X.html?isrc=b-search">Naked Conversations</a>, and what I&#8217;m doing for my book on <a href="http://www.rightconversation.com/2006/07/how_do_you_star.html">conversational media</a>. But it&#8217;s very nice to see someone from outside the tight, incestuous community of online-media professionals trying this strategy.</p>
<p>But it makes a lot of sense&#8230;</span></p>
<p><i>(Read the full story at my other blog, <a href="http://www.rightconversation.com/2006/07/blogging_a_book.html#more">The Right Conversation</a>&#8230;)<br />
</i></p>
<div name="googleone_share_1" style="position:relative;z-index:5;float: right; margin-left: 10px;"><g:plusone size="tall" count="1" href="http://www.contentious.com/2006/07/10/blogging-a-book/"></g:plusone></div>]]></content:encoded>
			<wfw:commentRss>http://www.contentious.com/2006/07/10/blogging-a-book/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Links for my URMA talk</title>
		<link>http://www.contentious.com/2006/05/16/links-for-my-urma-talk/</link>
		<comments>http://www.contentious.com/2006/05/16/links-for-my-urma-talk/#comments</comments>
		<pubDate>Tue, 16 May 2006 05:12:24 +0000</pubDate>
		<dc:creator>Amy Gahran</dc:creator>
				<category><![CDATA[Amy's Adventures]]></category>
		<category><![CDATA[Content Style & Business]]></category>
		<category><![CDATA[Feeds (RSS)]]></category>
		<category><![CDATA[Media Musings]]></category>
		<category><![CDATA[Real World Writing]]></category>
		<category><![CDATA[Resources]]></category>
		<category><![CDATA[Voices: Blogs, etc.]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[On Wednesday, May 17, I'll be giving a talk at the annual conference of the <a href="http://www.urma.org/" target="new"><strong>University Reseach Magazine Association</strong></a> (URMA). They seem like a fun group of media professionals. (Seriously -- their <a href="http://www.urma.org/forms/06agend.pdf" target="new">conference agenda</a> even features the Creature from the Black Lagoon!)

The topic of my talk is: <strong>Invasion of the bloggin’ pods: The new media – ready or not, they’re here! (So whatta we do with ‘em?)</strong>...]]></description>
			<content:encoded><![CDATA[<p>On Wednesday, May 17, I&#8217;ll be giving a talk at the annual conference of the <a href="http://www.urma.org/" target="new"><strong>University Reseach Magazine Association</strong></a> (URMA). They seem like a fun group of media professionals. (Seriously &#8212; their <a href="http://www.urma.org/forms/06agend.pdf" target="new">conference agenda</a> even features the Creature from the Black Lagoon!)</p>
<p>The topic of my talk is: <strong>Invasion of the bloggin’ pods: The new media – ready or not, they’re here! (So whatta we do with ‘em?)</strong></p>
<p>I already warned URMA: I don&#8217;t do lectures, so the people attending this session had better be ready to get involved.</p>
<p>Here are some links I plan to mention in my session&#8230;</p>
<p><i>(Read the full article at <a href="http://www.rightconversation.com/2006/05/links_for_my_ur.html#more">The Right Conversation&#8230;</a>)</i></p>
<div name="googleone_share_1" style="position:relative;z-index:5;float: right; margin-left: 10px;"><g:plusone size="tall" count="1" href="http://www.contentious.com/2006/05/16/links-for-my-urma-talk/"></g:plusone></div>]]></content:encoded>
			<wfw:commentRss>http://www.contentious.com/2006/05/16/links-for-my-urma-talk/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>In online writing, little things mean a lot</title>
		<link>http://www.contentious.com/2006/03/14/in-online-writing-little-things-mean-a-lot/</link>
		<comments>http://www.contentious.com/2006/03/14/in-online-writing-little-things-mean-a-lot/#comments</comments>
		<pubDate>Tue, 14 Mar 2006 22:19:42 +0000</pubDate>
		<dc:creator>Amy Gahran</dc:creator>
				<category><![CDATA[Content Style & Business]]></category>
		<category><![CDATA[Real World Writing]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[<i>(NOTE: I originally published this article in Spring 2000 in my former venture Content Exchange, which is now defunct. But it's still useful information, so I've decided to republish it.)</i>

Good writing is good writing no matter where you find it. However, each medium has its own unique considerations. One of the key points to consider about the text on your web site is <b>microcontent</b>.

Microcontent is all the short bits of text that help guide the user or provide an "at-a-glance" overview of what a given page is about. The basic categories of microcontent are...]]></description>
			<content:encoded><![CDATA[<p><i>(NOTE: I originally published this article in Spring 2000 in my former venture Content Exchange, which is now defunct. But it&#8217;s still useful information, so I&#8217;ve decided to republish it.)</i></p>
<p>Good writing is good writing no matter where you find it. However, each medium has its own unique considerations. One of the key points to consider about the text on your web site is <b>microcontent</b>.</p>
<p>Microcontent is all the short bits of text that help guide the user or provide an &#8220;at-a-glance&#8221; overview of what a given page is about. The basic categories of microcontent are&#8230;</p>
<p><span id="more-853"></span></p>
<ul>
<li>page titles</li>
<li>headlines and subheads</li>
<li>&#8220;in-page&#8221; indexes</li>
<li>navigation bar links</li>
<li>other links</li>
<li>bold text</li>
<li>alt text</li>
<li>captions </li>
</ul>
<p>Microcontent is especially important in online writing for three reasons:</p>
<ul>
<li>Web users tend to scan pages, rather than read them.</li>
<li>A user can arrive at virtually any page in your site from just about anywhere on the web.</li>
<li>Web users tend to be impatient and fickle. If they can&#8217;t figure out a site or page in a few seconds, they&#8217;ll probably move on.</li>
</ul>
<p>Therefore, every page in your site should provide near-instant orientation and context. You can accomplish some of this with design and branding, but ultimately text is your user&#8217;s most important guide.</p>
<p>There are a few <strong>general principles for writing any kind of microcontent:<br />
</strong></p>
<ul>
<li><b>Make it explanatory.</b> Each element of your microcontent should quickly communicate the substance or significance of the associated content, ideally from the perspective of your target audience. Avoid cute, clever, or generic wording. A good test is to imagine that the microcontent is the only thing visible on your page &#8211; could your users guess with reasonable accuracy what kind of information your page would contain?</li>
<li><b>Make it work out of context.</b> Online, some key pieces of your microcontent will get passed around, displayed, and linked to in all sorts of ways you can&#8217;t control, or even predict. Therefore, your should create page titles, headlines, and subheads that make a reasonable amount of sense if viewed totally on their own, beyond the context of your site. This principle also applies to your link text. Visually, links stand out from a page like roadsigns. If your page is full of links that say &#8220;click here&#8221; or other such vague terms, your users will feel stranded.</li>
<li><b>Keep it short.</b> There&#8217;s a reason they call it <em>micro</em>content. It has to work fast, so it has to be short. The trick is to make it as short as possible without obscuring its meaning or making it awkward. Headlines and subheads should be no more than 40-50 characters. Other links ideally should be 1-3 words long.</li>
<li><b>Don&#8217;t overdo it.</b> Good microcontent clarifies and directs. Pages with too many microcontent elements are like a busy intersection with too many roadsigns. As much as possible, limit the number of links, subheads, etc. that you present on a single page. Organize your information so you can easily break it up easily. If you must present a long list of links or large piece of text content, break it up into sections with brief, intuitive subheads. However, avoid breaking sections into subsections &#8211; that works well in print, poorly on the web. In most cases, text content should be broken into sections of about 300-400 words each, with no more than about 5 or 6 sections per page, and no more than 2-3 emphasized items (links or highlighted keywords) per section.</li>
</ul>
<p>In addition, each category of microcontent has unique considerations.</p>
<ul>
<li><b>Page titles:</b> The text you put between the <em>&lsaquo;title&rsaquo; &lsaquo;/title&rsaquo; </em>tags on your pages is what users see in their &#8220;bookmark&#8221; or &#8220;favorite&#8221; lists. It&#8217;s also what displays in some search engine results. Your page titles should summarize &#8220;the point&#8221; of the page and identify your company or site, in no more than 40-50 characters. It&#8217;s best not to have every page title start with the same text, so put your site or company name at the end.</li>
<li><b>Headlines and subheads:</b> The headline is the main heading at the top of the page, and it should address the overall content of the page. It can be nearly the same as the page title. Subheads address specific sections within the page. Organize your content so that all the subheads on a given page are of roughly equal significance.</li>
<li><b>&#8220;In-page&#8221; indexes:</b> If you have more than two sections of content on a single page, it&#8217;s a good idea to present an index to those sections at the top of the page (a simple list of links). This functions as an executive summary for the page, with no scrolling required. Each index item should link directly to the relevant section. If your subheads are all 2-3 words long, then your index can repeat them verbatim. If a particular subhead is longer, you might want to edit the corresponding index item down to a 2- to 3-word synopsis of that section&#8217;s key concept.</li>
<li><b>Navigation bar links:</b> These point to the various sections of your  site. Try to limit them to 1-2 words each. Organize and name your site sections so they make sense from the user&#8217;s perspective. Avoid clever, cryptic, or internally focused language.</li>
<li><b>Other links:</b> Crafting your link text can take a lot of work. It must not only direct, but also inform. One useful trick is to first figure out the most obvious and concise way to word the link you wish to create, and then structure your sentences and other content to support that wording. The best link text indicates:
<ul>
<li>Where users will be taken if they click that link, as well as what kind of content they&#8217;ll find there. (For instance, &#8220;this recent <u>Industry Standard article</u>,&#8221; rather than just &#8220;<u>article</u>.&#8221;)</li>
<li>Why you chose to direct your readers to that page. (For instance, &#8220;It helps to understand what happened in <u>13th-century Kosovo</u>.&#8221;)</li>
</ul>
<li><b>Bold text (highlighted keywords):</b> Often, online writers use bold text to emphasize an important word or phrase. Since this stands out visually about as much as a link, it can be effective &#8211; as long as you don&#8217;t overdo it, and as long as the bold text conveys meaning. Ideally, you should be able to get a rough idea of what a page covers just by scanning the links and bold text.</li>
<li><b>Alt text:</b> Images often are a key part of online content. However, if a user cannot or does not view your images, or mouses over an image in most browsers, the &#8220;alt&#8221; text will display. For every image on your site that has a content purpose, specify corresponding alt text &#8211; ideally, no more than 40 characters. This text should convey the meaning or significance of the image, not describe what it looks like. Conversely, make sure that you do not specify alt text for images that are strictly design or decorative elements.</li>
<li><b>Captions:</b> If an image is an important piece of your content, but simply looking at it may not convey its full meaning, write a caption. Web caption text usually is small or otherwise hard to read, so keep it very short &#8211; ideally 10 words or less. Answer the user&#8217;s natural questions: &#8220;What am I looking at?&#8221; and &#8220;Why are you showing me this?&#8221;</li>
</li>
</ul>
<p>If you follow these guidelines, the chances are good that your users will be able to follow you &#8211; and your site &#8211; pretty easily.</p>
<div name="googleone_share_1" style="position:relative;z-index:5;float: right; margin-left: 10px;"><g:plusone size="tall" count="1" href="http://www.contentious.com/2006/03/14/in-online-writing-little-things-mean-a-lot/"></g:plusone></div>]]></content:encoded>
			<wfw:commentRss>http://www.contentious.com/2006/03/14/in-online-writing-little-things-mean-a-lot/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Brilliant headline from Koan Bremner</title>
		<link>http://www.contentious.com/2006/03/14/brilliant-headline-from-koan-bremner/</link>
		<comments>http://www.contentious.com/2006/03/14/brilliant-headline-from-koan-bremner/#comments</comments>
		<pubDate>Tue, 14 Mar 2006 05:01:32 +0000</pubDate>
		<dc:creator>Amy Gahran</dc:creator>
				<category><![CDATA[Real World Writing]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[Usually, I advise people that when writing headlines or titles for online content, it helps to not be too "cute" or "cryptic." This is because headlines are often viewed out of context online (in search engine results or feed readers, etc.). They generally need to speak for themselves.

That said, I love a good pun. And sometimes, depending on the author, topic, and target audience, a good pun is just what's needed. This morning, my friend and fellow blogger <b>Koan Bremner</b> pulled off a magnificently punnish headline: "<b>Ctrl-Alt-Delete</b>."

Now that might not sound like much of a pun &#8211; you need to read the article to see why it works so well. Normally I would consider that a problem, too. 

However, here's why I think it's a great headline, even though it's geeky and superficially cryptic &#8211; and what other bloggers can learn from this example...]]></description>
			<content:encoded><![CDATA[<p>Usually, I advise people that when writing headlines or titles for online content, it helps to not be too &#8220;cute&#8221; or &#8220;cryptic.&#8221; This is because headlines are often viewed out of context online (in search engine results or feed readers, etc.). They generally need to speak for themselves.</p>
<p>That said, I love a good pun. And sometimes, depending on the author, topic, and target audience, a good pun is just what&#8217;s needed. This morning, my friend and fellow blogger <b>Koan Bremner</b> pulled off a magnificently punnish headline: &#8220;<b>Ctrl-Alt-Delete</b>.&#8221;</p>
<p>Now that might not sound like much of a pun &#8211; you need to read the article to see why it works so well. Normally I would consider that a problem, too. </p>
<p>However, here&#8217;s why I think it&#8217;s a great headline, even though it&#8217;s geeky and superficially cryptic &#8211; and what other bloggers can learn from this example&#8230;</p>
<p><span id="more-850"></span></p>
<p>First of all, <b>Koan&#8217;s blog is mostly personal</b>, which means that it&#8217;s entirely fitting for her writing to strongly reflect her personality &#8211; including her wry, lighthearted sense of humor.  It also means her blog is strongly about building a relationship with her target audience. That audience mainly includes people who are interested in her, or in the issues she discusses (gender, technology, music, society, UK life, and more.)</p>
<p>Given that closeness with her audience, occasional in-joke headlines work well &#8211; definitely better than in a blog or other venue that actively courts a broader audience and less personal connection.</p>
<p>This week, Koan has gone through a major transformation &#8211; the culmination of years of effort, preparation, and planning. <a href="http://www.multidimensional.me.uk/2006/03/13.html#a379">Read her posting</a> to get the full story. <b>Be prepared: It&#8217;s very frank</b>, as it deals with surgical and post-surgical matters related to gender reassignment. But she tells it well.</p>
<p>The final element that makes this otherwise mysterious headline a success is that Koan doesn&#8217;t leave her readers guessing long. The lead of her posting delivers the &#8220;punchline&#8221;:</p>
<blockquote><p>
&#8220;Those of you running Windows (any flavour) will recognise the title of this post as the keystroke for a reboot &#8211; those of you running OS X&#8230; won&#8217;t &#8211; because, of course, you don&#8217;t need to keep rebooting a Mac in the way you do a crashed PC&#8230; <img src='http://www.contentious.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
<p>&#8220;Anyway&#8230; my personal reboot is now completed &#8211; and my operating system is now running on its shiny, upgraded hardware, and all the diagnostic tests are showing record-breaking performance.&#8221;
</p></blockquote>
<p>If you do on rare occasions decide to go with a cryptic or cute headline that requires explanation, make sure to offer that explanation <i>immediately</i>. Most web users will only give you a second or two to grab their attention. If you manage to intrigue them in the first second with your headline, you&#8217;d better clue them in before they click away in the next sentence.</p>
<p>The way Koan uses humor in this piece is more than fun. She&#8217;s recounting a very personal and serious story &#8211; which could have seemed heavy or daunting had she not deftly gotten people laughing right from the start. This is a positive, optimistic time for her, and she communicates that energy to her audience with humor.</p>
<p>She&#8217;s definitely better at using humor than I am. I could learn from her on that.</p>
<p>Well done, Koan, in every sense!</p>
<div name="googleone_share_1" style="position:relative;z-index:5;float: right; margin-left: 10px;"><g:plusone size="tall" count="1" href="http://www.contentious.com/2006/03/14/brilliant-headline-from-koan-bremner/"></g:plusone></div>]]></content:encoded>
			<wfw:commentRss>http://www.contentious.com/2006/03/14/brilliant-headline-from-koan-bremner/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Link blog pros &amp; cons</title>
		<link>http://www.contentious.com/2006/03/13/linkblog-pros-cons/</link>
		<comments>http://www.contentious.com/2006/03/13/linkblog-pros-cons/#comments</comments>
		<pubDate>Mon, 13 Mar 2006 22:34:38 +0000</pubDate>
		<dc:creator>Amy Gahran</dc:creator>
				<category><![CDATA[Content Style & Business]]></category>
		<category><![CDATA[Conversations]]></category>
		<category><![CDATA[Feeds (RSS)]]></category>
		<category><![CDATA[Real World Writing]]></category>
		<category><![CDATA[Resources]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[My friend, colleague, and fellow blogger <strong>Dave Taylor </strong>wrote on March 7 about how he's finally "<a href="http://www.intuitive.com/blog/ive_succumbed_i_now_have_a_link_blog.html" target="new"><strong>succumbed</strong></a>" and created a link blog: <a href="http://www.bloglines.com/blog/d1taylor" target="new"><strong>Dave Taylor's blog clippings</strong></a>

...A <em>link blog</em> is a way to use a weblog to share interesting links. There are lots of different ways to do it...]]></description>
			<content:encoded><![CDATA[<p>My friend, colleague, and fellow blogger <strong>Dave Taylor </strong>wrote on March 7 about how he&#8217;s finally &#8220;<a href="http://www.intuitive.com/blog/ive_succumbed_i_now_have_a_link_blog.html" target="new"><strong>succumbed</strong></a>&#8221; and created a link blog: <a href="http://www.bloglines.com/blog/d1taylor" target="new"><strong>Dave Taylor&#8217;s blog clippings</strong></a></p>
<p>&#8230;A <em>link blog</em> is a way to use a weblog to share interesting links. There are lots of different ways to do it. I use the free social bookmarking service <a href="http://del.icio.us" target="new">del.icio.us</a> to create link-related content for all of my main weblogs. In this weblog, that&#8217;s what generates my &#8220;Latest Recommended Links&#8221; content in the right-hand sidebar.</p>
<p>For my other weblog, <a href="http://rightconversation.com">The Right Conversation</a>, I save links (with relevant excerpts or comments) in <a href="http://del.icio.us/rightconversation" target="new">del.icio.us</a> and then use an automated system to compile and post a daily roundup of links. (For instance, here&#8217;s <a href="http://www.rightconversation.com/2006/03/links_for_20060_8.html">yesterday&#8217;s link posting</a> from The Right Conversation.)</p>
<p>Dave points out that while having a linkblog fulfills some needs (for him and, presumably, his audience), it&#8217;s not exactly conversational &#8211; especially in his case, since the tool he&#8217;s chosen does not allow comments.</p>
<p>I shared my thoughts on linkblogs with Dave, and asked him to explain his linkblog rationale further&#8230;.</p>
<p><em>(Read the rest of this article on <a href="http://www.rightconversation.com/2006/03/linkblog_pros_c.html#more">The Right Conversation</a>&#8230;)</em></p>
<div name="googleone_share_1" style="position:relative;z-index:5;float: right; margin-left: 10px;"><g:plusone size="tall" count="1" href="http://www.contentious.com/2006/03/13/linkblog-pros-cons/"></g:plusone></div>]]></content:encoded>
			<wfw:commentRss>http://www.contentious.com/2006/03/13/linkblog-pros-cons/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

