<?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: Context, please!</title>
	<atom:link href="http://emergentchaos.com/archives/2008/03/context-please.html/feed" rel="self" type="application/rss+xml" />
	<link>http://emergentchaos.com/archives/2008/03/context-please.html</link>
	<description>The Emergent Chaos Jazz Combo</description>
	<lastBuildDate>Wed, 01 Feb 2012 19:20:40 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Tiffany</title>
		<link>http://emergentchaos.com/archives/2008/03/context-please.html/comment-page-1#comment-4487</link>
		<dc:creator>Tiffany</dc:creator>
		<pubDate>Tue, 01 Apr 2008 21:09:15 +0000</pubDate>
		<guid isPermaLink="false">http://emergentchaos.com/?p=2693#comment-4487</guid>
		<description>procuring the rude produce annually required for the use and consumption of &lt;a href=&quot;http://idisk.mac.com/defaultlandscapemysp/Public/0/white-and-pink-flower-myspace-layouts.html&quot; rel=&quot;nofollow&quot;&gt;http://idisk.mac.com/defaultlandscapemysp/Public/0/white-and-pink-flower-myspace-layouts.html&lt;/a&gt; &gt;white and pink flower myspace layouts    The accumulated treasures of the prince have in former times
</description>
		<content:encoded><![CDATA[<p>procuring the rude produce annually required for the use and consumption of <a href="http://idisk.mac.com/defaultlandscapemysp/Public/0/white-and-pink-flower-myspace-layouts.html" rel="nofollow">http://idisk.mac.com/defaultlandscapemysp/Public/0/white-and-pink-flower-myspace-layouts.html</a> >white and pink flower myspace layouts    The accumulated treasures of the prince have in former times</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Timothy Knox</title>
		<link>http://emergentchaos.com/archives/2008/03/context-please.html/comment-page-1#comment-4486</link>
		<dc:creator>Timothy Knox</dc:creator>
		<pubDate>Sun, 23 Mar 2008 18:34:14 +0000</pubDate>
		<guid isPermaLink="false">http://emergentchaos.com/?p=2693#comment-4486</guid>
		<description>Top-posting will not go away so long as Outlook (the dominant email client) makes that not only the default, but practically impossible to avoid. The best criticism I ever saw on the subject was one man&#039;s .sig quote:
A: Because it disrupts the normal flow of conversation.
Q: Why is top-posting a bad idea.
</description>
		<content:encoded><![CDATA[<p>Top-posting will not go away so long as Outlook (the dominant email client) makes that not only the default, but practically impossible to avoid. The best criticism I ever saw on the subject was one man&#8217;s .sig quote:<br />
A: Because it disrupts the normal flow of conversation.<br />
Q: Why is top-posting a bad idea.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard Veryard</title>
		<link>http://emergentchaos.com/archives/2008/03/context-please.html/comment-page-1#comment-4485</link>
		<dc:creator>Richard Veryard</dc:creator>
		<pubDate>Fri, 21 Mar 2008 08:50:36 +0000</pubDate>
		<guid isPermaLink="false">http://emergentchaos.com/?p=2693#comment-4485</guid>
		<description>You are right that excessive pruning may kill the exchange, but that doesn&#039;t mean you should never prune. Long emails often contain embarrasing stuff at the end, which leak internal discussions to other departments or companies, because people are too lazy to prune. The correct answer is to replace email with proper collaboration software.
</description>
		<content:encoded><![CDATA[<p>You are right that excessive pruning may kill the exchange, but that doesn&#8217;t mean you should never prune. Long emails often contain embarrasing stuff at the end, which leak internal discussions to other departments or companies, because people are too lazy to prune. The correct answer is to replace email with proper collaboration software.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lyger</title>
		<link>http://emergentchaos.com/archives/2008/03/context-please.html/comment-page-1#comment-4484</link>
		<dc:creator>Lyger</dc:creator>
		<pubDate>Thu, 20 Mar 2008 18:00:59 +0000</pubDate>
		<guid isPermaLink="false">http://emergentchaos.com/?p=2693#comment-4484</guid>
		<description>I don&#039;t mind quoting full context when needed, but MAN, people should at least trim off excessive sig files, disclaimers, and email list footers... ;)
p.s. post approved!
</description>
		<content:encoded><![CDATA[<p>I don&#8217;t mind quoting full context when needed, but MAN, people should at least trim off excessive sig files, disclaimers, and email list footers&#8230; ;)<br />
p.s. post approved!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rich Kulawiec</title>
		<link>http://emergentchaos.com/archives/2008/03/context-please.html/comment-page-1#comment-4483</link>
		<dc:creator>Rich Kulawiec</dc:creator>
		<pubDate>Thu, 20 Mar 2008 03:56:40 +0000</pubDate>
		<guid isPermaLink="false">http://emergentchaos.com/?p=2693#comment-4483</guid>
		<description>Top-posting, like full-quoting or HTML markup, is used only by rude, ignorant newbies.  Anyone using a quality mail reader and observing basic standards of netiquette should be able to read and write email that is concise, automatically threaded, and contains enough in-line context to be comprehensible -- but no more.  Not only is excessive quoting wasteful of system and network resources, but it wastes human resources -- and it shows disrespect for the recipient(s).
</description>
		<content:encoded><![CDATA[<p>Top-posting, like full-quoting or HTML markup, is used only by rude, ignorant newbies.  Anyone using a quality mail reader and observing basic standards of netiquette should be able to read and write email that is concise, automatically threaded, and contains enough in-line context to be comprehensible &#8212; but no more.  Not only is excessive quoting wasteful of system and network resources, but it wastes human resources &#8212; and it shows disrespect for the recipient(s).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Walter</title>
		<link>http://emergentchaos.com/archives/2008/03/context-please.html/comment-page-1#comment-4482</link>
		<dc:creator>Walter</dc:creator>
		<pubDate>Wed, 19 Mar 2008 16:37:37 +0000</pubDate>
		<guid isPermaLink="false">http://emergentchaos.com/?p=2693#comment-4482</guid>
		<description>Snipping context, however, does add to the chaos.
</description>
		<content:encoded><![CDATA[<p>Snipping context, however, does add to the chaos.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kurt wismer</title>
		<link>http://emergentchaos.com/archives/2008/03/context-please.html/comment-page-1#comment-4481</link>
		<dc:creator>kurt wismer</dc:creator>
		<pubDate>Tue, 18 Mar 2008 15:26:33 +0000</pubDate>
		<guid isPermaLink="false">http://emergentchaos.com/?p=2693#comment-4481</guid>
		<description>your chess master analogy doesn&#039;t really do your plea justice, as one could easily say that the chess master doesn&#039;t care about what the board looked like before, he only cares about what it looks like right now - so in email you shouldn&#039;t care about what was being discussed before but only about what is being discussed right now...
if i don&#039;t use a piece of information sent to me when it&#039;s originally sent then i fully expect to have to data-mine my mail archive to get it and i&#039;m ok with that...
it probably comes down to personal taste, but there are those of us who follow RFC1855 (more or less), and then there are those who think top posting is ok or that quoting should be more liberal... as much as i can&#039;t stand top posting and excessive quoting, though, i won&#039;t be holding my breath waiting for other people to stop doing it...
</description>
		<content:encoded><![CDATA[<p>your chess master analogy doesn&#8217;t really do your plea justice, as one could easily say that the chess master doesn&#8217;t care about what the board looked like before, he only cares about what it looks like right now &#8211; so in email you shouldn&#8217;t care about what was being discussed before but only about what is being discussed right now&#8230;<br />
if i don&#8217;t use a piece of information sent to me when it&#8217;s originally sent then i fully expect to have to data-mine my mail archive to get it and i&#8217;m ok with that&#8230;<br />
it probably comes down to personal taste, but there are those of us who follow RFC1855 (more or less), and then there are those who think top posting is ok or that quoting should be more liberal&#8230; as much as i can&#8217;t stand top posting and excessive quoting, though, i won&#8217;t be holding my breath waiting for other people to stop doing it&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

