<?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: How to read your email</title>
	<atom:link href="http://www.hawkwings.net/2006/04/21/oldest-to-newest-email-or-vice-versa/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.hawkwings.net/2006/04/21/oldest-to-newest-email-or-vice-versa/</link>
	<description>Tips and add-ons to make Apple Mail / Mail.app even better</description>
	<lastBuildDate>Mon, 21 Nov 2011 18:23:54 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Jack P Toerson</title>
		<link>http://www.hawkwings.net/2006/04/21/oldest-to-newest-email-or-vice-versa/comment-page-1/#comment-3049</link>
		<dc:creator>Jack P Toerson</dc:creator>
		<pubDate>Tue, 25 Apr 2006 22:03:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.hawkwings.net/2006/04/21/oldest-to-newest-email-or-vice-versa/#comment-3049</guid>
		<description>I think the problem with a subject heading is that often their is no agreed upon or mutual understanding of what it may mean.  Unless the language is very staid.  Of course mailing lists often add square bracketed tags to their outgoing mail, but that&#039;s really an identifier of source rather than content; the mailing list may have been spammed.  If there were an agreed upon urgency weighting for various terms in subject headers it would be a different case.  

Although it&#039;s still pretty flawed because they rely on the user supplying the correct information.  The number of Viagra requests I get that are marked urgent is phenominal, and have no erectile problems.  I suppose someone could digitally sign a messages priority and the recipient were only to trust authenticated priorities the spam &#039;false-priority&#039; syndrome may be somewhat limited. However the  priority would have to be concatenated with a message digest prior to signing  to stop people cutting and pasting priorities from a authentic message to a forgery.

But then there&#039;s the problem of people who may not have public keys available or are malicious users who have public keys.  There&#039;s no way enough people signing each-others keys to rely on a sense of trust. Almost everything I think of in this regard leads to another question, and I&#039;m not very technical, and I haven&#039;t entirely thought it through.  I&#039;m just tossing ideas to the wind.  Thanks for the reply.</description>
		<content:encoded><![CDATA[<p>I think the problem with a subject heading is that often their is no agreed upon or mutual understanding of what it may mean.  Unless the language is very staid.  Of course mailing lists often add square bracketed tags to their outgoing mail, but that&#8217;s really an identifier of source rather than content; the mailing list may have been spammed.  If there were an agreed upon urgency weighting for various terms in subject headers it would be a different case.  </p>
<p>Although it&#8217;s still pretty flawed because they rely on the user supplying the correct information.  The number of Viagra requests I get that are marked urgent is phenominal, and have no erectile problems.  I suppose someone could digitally sign a messages priority and the recipient were only to trust authenticated priorities the spam &#8216;false-priority&#8217; syndrome may be somewhat limited. However the  priority would have to be concatenated with a message digest prior to signing  to stop people cutting and pasting priorities from a authentic message to a forgery.</p>
<p>But then there&#8217;s the problem of people who may not have public keys available or are malicious users who have public keys.  There&#8217;s no way enough people signing each-others keys to rely on a sense of trust. Almost everything I think of in this regard leads to another question, and I&#8217;m not very technical, and I haven&#8217;t entirely thought it through.  I&#8217;m just tossing ideas to the wind.  Thanks for the reply.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sjk</title>
		<link>http://www.hawkwings.net/2006/04/21/oldest-to-newest-email-or-vice-versa/comment-page-1/#comment-3040</link>
		<dc:creator>sjk</dc:creator>
		<pubDate>Tue, 25 Apr 2006 21:45:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.hawkwings.net/2006/04/21/oldest-to-newest-email-or-vice-versa/#comment-3040</guid>
		<description>Are you suggesting tags for outgoing messages, Jack?  I don&#039;t see how that really adds value beyond what you can already do by simply adding freeform tag-like info to the Subject header.</description>
		<content:encoded><![CDATA[<p>Are you suggesting tags for outgoing messages, Jack?  I don&#8217;t see how that really adds value beyond what you can already do by simply adding freeform tag-like info to the Subject header.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jack P Toerson</title>
		<link>http://www.hawkwings.net/2006/04/21/oldest-to-newest-email-or-vice-versa/comment-page-1/#comment-2998</link>
		<dc:creator>Jack P Toerson</dc:creator>
		<pubDate>Tue, 25 Apr 2006 15:40:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.hawkwings.net/2006/04/21/oldest-to-newest-email-or-vice-versa/#comment-2998</guid>
		<description>The simple answer would be to implement tags for email.  There could be a &#039;nasty surprise tag&#039;, an &#039;ebullient praise&#039; tag and a &#039;this isn&#039;t important&#039; tag.  The standard priority header isn&#039;t descriptive enough and is over-used.

Thanks for the link :-).

- Jack</description>
		<content:encoded><![CDATA[<p>The simple answer would be to implement tags for email.  There could be a &#8216;nasty surprise tag&#8217;, an &#8216;ebullient praise&#8217; tag and a &#8216;this isn&#8217;t important&#8217; tag.  The standard priority header isn&#8217;t descriptive enough and is over-used.</p>
<p>Thanks for the link :-).</p>
<p>- Jack</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim</title>
		<link>http://www.hawkwings.net/2006/04/21/oldest-to-newest-email-or-vice-versa/comment-page-1/#comment-2904</link>
		<dc:creator>Tim</dc:creator>
		<pubDate>Tue, 25 Apr 2006 07:55:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.hawkwings.net/2006/04/21/oldest-to-newest-email-or-vice-versa/#comment-2904</guid>
		<description>Well, you learn something every day. :)

I didn&#039;t know that.</description>
		<content:encoded><![CDATA[<p>Well, you learn something every day. :)</p>
<p>I didn&#8217;t know that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sjk</title>
		<link>http://www.hawkwings.net/2006/04/21/oldest-to-newest-email-or-vice-versa/comment-page-1/#comment-2878</link>
		<dc:creator>sjk</dc:creator>
		<pubDate>Tue, 25 Apr 2006 04:22:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.hawkwings.net/2006/04/21/oldest-to-newest-email-or-vice-versa/#comment-2878</guid>
		<description>Ahh, &#039;tis simply a difference in our &lt;a href=&quot;http://www.acronymfinder.com/acronym.aspx?rec={97C3BD3E-89E8-11D4-8351-00C04FC2C2BF}&quot; rel=&quot;nofollow&quot;&gt;FIFO&lt;/a&gt; (me) vs. &lt;a href=&quot;http://www.acronymfinder.com/acronym.aspx?rec={8DFA0945-89E8-11D4-8351-00C04FC2C2BF}&quot; rel=&quot;nofollow&quot;&gt;LIFO&lt;/a&gt; (you) preferences. :)</description>
		<content:encoded><![CDATA[<p>Ahh, &#8217;tis simply a difference in our <a href="http://www.acronymfinder.com/acronym.aspx?rec={97C3BD3E-89E8-11D4-8351-00C04FC2C2BF}" rel="nofollow">FIFO</a> (me) vs. <a href="http://www.acronymfinder.com/acronym.aspx?rec={8DFA0945-89E8-11D4-8351-00C04FC2C2BF}" rel="nofollow">LIFO</a> (you) preferences. :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim</title>
		<link>http://www.hawkwings.net/2006/04/21/oldest-to-newest-email-or-vice-versa/comment-page-1/#comment-2831</link>
		<dc:creator>Tim</dc:creator>
		<pubDate>Tue, 25 Apr 2006 00:29:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.hawkwings.net/2006/04/21/oldest-to-newest-email-or-vice-versa/#comment-2831</guid>
		<description>Naturally, being a top-poster, I am perverse about this too.

I like me newest at the top. It&#039;s like working through the in-tray from the top to the bottom.</description>
		<content:encoded><![CDATA[<p>Naturally, being a top-poster, I am perverse about this too.</p>
<p>I like me newest at the top. It&#8217;s like working through the in-tray from the top to the bottom.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sjk</title>
		<link>http://www.hawkwings.net/2006/04/21/oldest-to-newest-email-or-vice-versa/comment-page-1/#comment-2828</link>
		<dc:creator>sjk</dc:creator>
		<pubDate>Tue, 25 Apr 2006 00:12:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.hawkwings.net/2006/04/21/oldest-to-newest-email-or-vice-versa/#comment-2828</guid>
		<description>&lt;blockquote&gt;How do you know if the newer ones deserve more immediate attention unless you read them first?&lt;/blockquote&gt;

Intuition? :)
The sender/subject/date of newer messages can of course be a clue.  And priority depends on the content; you might be anticipating personal/business messages whereas mailing list traffic is typically unpredictable.  It&#039;s an ongoing readjustment of context-dependent attention focus.

&lt;blockquote&gt;I like newest messages to appear at the bottom.&lt;/blockquote&gt;
Same here.  Not possible with Gmail, being one of several key reasons I&#039;m not comfortable using that service.</description>
		<content:encoded><![CDATA[<blockquote><p>How do you know if the newer ones deserve more immediate attention unless you read them first?</p></blockquote>
<p>Intuition? :)<br />
The sender/subject/date of newer messages can of course be a clue.  And priority depends on the content; you might be anticipating personal/business messages whereas mailing list traffic is typically unpredictable.  It&#8217;s an ongoing readjustment of context-dependent attention focus.</p>
<blockquote><p>I like newest messages to appear at the bottom.</p></blockquote>
<p>Same here.  Not possible with Gmail, being one of several key reasons I&#8217;m not comfortable using that service.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hoby</title>
		<link>http://www.hawkwings.net/2006/04/21/oldest-to-newest-email-or-vice-versa/comment-page-1/#comment-2823</link>
		<dc:creator>Hoby</dc:creator>
		<pubDate>Mon, 24 Apr 2006 21:26:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.hawkwings.net/2006/04/21/oldest-to-newest-email-or-vice-versa/#comment-2823</guid>
		<description>I read oldest to newest most of the time. I don&#039;t run into dilemma because I see others in thread via the list view.

What I think is more of an interesting preference, is whether people like to have newer messages at the top of the list window or at the bottom.

I like newest messages to appear at the bottom.</description>
		<content:encoded><![CDATA[<p>I read oldest to newest most of the time. I don&#8217;t run into dilemma because I see others in thread via the list view.</p>
<p>What I think is more of an interesting preference, is whether people like to have newer messages at the top of the list window or at the bottom.</p>
<p>I like newest messages to appear at the bottom.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tony Meyer</title>
		<link>http://www.hawkwings.net/2006/04/21/oldest-to-newest-email-or-vice-versa/comment-page-1/#comment-2737</link>
		<dc:creator>Tony Meyer</dc:creator>
		<pubDate>Fri, 21 Apr 2006 23:03:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.hawkwings.net/2006/04/21/oldest-to-newest-email-or-vice-versa/#comment-2737</guid>
		<description>This is where a mailer that organises mail nicely by thread is so important, because you can at least see that there is later message (e.g. it&#039;s not 100 emails down the list).

I read oldest-to-newest, because that makes most sense, but complete reading (the thread) before replying/actioning.</description>
		<content:encoded><![CDATA[<p>This is where a mailer that organises mail nicely by thread is so important, because you can at least see that there is later message (e.g. it&#8217;s not 100 emails down the list).</p>
<p>I read oldest-to-newest, because that makes most sense, but complete reading (the thread) before replying/actioning.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim</title>
		<link>http://www.hawkwings.net/2006/04/21/oldest-to-newest-email-or-vice-versa/comment-page-1/#comment-2736</link>
		<dc:creator>Tim</dc:creator>
		<pubDate>Fri, 21 Apr 2006 22:38:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.hawkwings.net/2006/04/21/oldest-to-newest-email-or-vice-versa/#comment-2736</guid>
		<description>&lt;blockquote&gt;I normally read mail, news, etc. oldest-to-newest unless newer items deserve more immediate attention or clearly supersede older ones that can be skipped and/or deleted.&lt;/blockquote&gt;That&#039;s the bind, isn&#039;t it? 

How do you know if the newer ones deserve more immediate attention unless you read them first?</description>
		<content:encoded><![CDATA[<blockquote><p>I normally read mail, news, etc. oldest-to-newest unless newer items deserve more immediate attention or clearly supersede older ones that can be skipped and/or deleted.</p></blockquote>
<p>That&#8217;s the bind, isn&#8217;t it? </p>
<p>How do you know if the newer ones deserve more immediate attention unless you read them first?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

