<?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: Email message threading is broken</title>
	<atom:link href="http://stealthisidea.com/articles/tweaking-email-message-threading/feed/" rel="self" type="application/rss+xml" />
	<link>http://stealthisidea.com/articles/tweaking-email-message-threading/</link>
	<description>Philip Haine&#039;s articles on Product Vision, Innovation and Design</description>
	<lastBuildDate>Tue, 06 Dec 2011 23:38:16 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: CL</title>
		<link>http://stealthisidea.com/articles/tweaking-email-message-threading/comment-page-1/#comment-2946</link>
		<dc:creator>CL</dc:creator>
		<pubDate>Mon, 05 Oct 2009 21:15:55 +0000</pubDate>
		<guid isPermaLink="false">http://stealthisidea.com/?p=640#comment-2946</guid>
		<description>The same problem appears in Gmail (or at least I&#039;ve seen it in Gmail)... I don&#039;t know if this is a &quot;fancy&quot; solution as David suggests or simply a conservative solution.

I recently read an article explaining how people are much more satisfied with wrong results if they understand how the results were reached than wrong results from a process they don&#039;t understand.  If we assume even a modest 5% false positive with Philip&#039;s suggestion, it might create more frustration than twice as many false positives in something I understand (i.e., just using the subject line).

On the other hand, it might simply be the easy thing to do from an engineering perspective.  I&#039;d imagine the subject line is pretty well indexed in any email client, so it should be relatively simple to correlate when organizing thousands of messages for a view (not everybody subscribes to zero inbox after all).</description>
		<content:encoded><![CDATA[<p>The same problem appears in Gmail (or at least I&#8217;ve seen it in Gmail)&#8230; I don&#8217;t know if this is a &#8220;fancy&#8221; solution as David suggests or simply a conservative solution.</p>
<p>I recently read an article explaining how people are much more satisfied with wrong results if they understand how the results were reached than wrong results from a process they don&#8217;t understand.  If we assume even a modest 5% false positive with Philip&#8217;s suggestion, it might create more frustration than twice as many false positives in something I understand (i.e., just using the subject line).</p>
<p>On the other hand, it might simply be the easy thing to do from an engineering perspective.  I&#8217;d imagine the subject line is pretty well indexed in any email client, so it should be relatively simple to correlate when organizing thousands of messages for a view (not everybody subscribes to zero inbox after all).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Josh</title>
		<link>http://stealthisidea.com/articles/tweaking-email-message-threading/comment-page-1/#comment-2518</link>
		<dc:creator>Josh</dc:creator>
		<pubDate>Wed, 03 Jun 2009 17:51:51 +0000</pubDate>
		<guid isPermaLink="false">http://stealthisidea.com/?p=640#comment-2518</guid>
		<description>The same problem appears in Gmail (or at least I&#039;ve seen it in Gmail)... I don&#039;t know if this is a &quot;fancy&quot; solution as David suggests or simply a conservative solution.

I recently read an article explaining how people are much more satisfied with wrong results if they understand how the results were reached than wrong results from a process they don&#039;t understand.  If we assume even a modest 5% false positive with Philip&#039;s suggestion, it might create more frustration than twice as many false positives in something I understand (i.e., just using the subject line).

On the other hand, it might simply be the easy thing to do from an engineering perspective.  I&#039;d imagine the subject line is pretty well indexed in any email client, so it should be relatively simple to correlate when organizing thousands of messages for a view (not everybody subscribes to zero inbox after all).</description>
		<content:encoded><![CDATA[<p>The same problem appears in Gmail (or at least I&#8217;ve seen it in Gmail)&#8230; I don&#8217;t know if this is a &#8220;fancy&#8221; solution as David suggests or simply a conservative solution.</p>
<p>I recently read an article explaining how people are much more satisfied with wrong results if they understand how the results were reached than wrong results from a process they don&#8217;t understand.  If we assume even a modest 5% false positive with Philip&#8217;s suggestion, it might create more frustration than twice as many false positives in something I understand (i.e., just using the subject line).</p>
<p>On the other hand, it might simply be the easy thing to do from an engineering perspective.  I&#8217;d imagine the subject line is pretty well indexed in any email client, so it should be relatively simple to correlate when organizing thousands of messages for a view (not everybody subscribes to zero inbox after all).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Creemer</title>
		<link>http://stealthisidea.com/articles/tweaking-email-message-threading/comment-page-1/#comment-2502</link>
		<dc:creator>David Creemer</dc:creator>
		<pubDate>Wed, 27 May 2009 16:17:46 +0000</pubDate>
		<guid isPermaLink="false">http://stealthisidea.com/?p=640#comment-2502</guid>
		<description>This is a problem with Apple Mail.app being a bit aggressive with threading.

There is actually a standard header for this (&quot;In-Reply-To&quot; -- for example, &quot;In-Reply-To: &quot;).

Unfortunately not every mailer in the world adds this header so mail application developers try to get fancy. Like so many other design choices, Apple always shoot for fancy over basic.</description>
		<content:encoded><![CDATA[<p>This is a problem with Apple Mail.app being a bit aggressive with threading.</p>
<p>There is actually a standard header for this (&#8220;In-Reply-To&#8221; &#8212; for example, &#8220;In-Reply-To: &#8220;).</p>
<p>Unfortunately not every mailer in the world adds this header so mail application developers try to get fancy. Like so many other design choices, Apple always shoot for fancy over basic.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

