<?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: Is Google Conjuring a &#8220;Magic Inbox&#8221; for Gmail?</title>
	<atom:link href="http://thenoisychannel.com/2009/05/21/is-google-conjuring-a-magic-inbox-for-gmail/feed/" rel="self" type="application/rss+xml" />
	<link>http://thenoisychannel.com/2009/05/21/is-google-conjuring-a-magic-inbox-for-gmail/</link>
	<description></description>
	<lastBuildDate>Mon, 21 May 2012 05:21:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Daniel Tunkelang</title>
		<link>http://thenoisychannel.com/2009/05/21/is-google-conjuring-a-magic-inbox-for-gmail/comment-page-1/#comment-3655</link>
		<dc:creator>Daniel Tunkelang</dc:creator>
		<pubDate>Fri, 22 May 2009 01:49:42 +0000</pubDate>
		<guid isPermaLink="false">http://thenoisychannel.com/?p=2121#comment-3655</guid>
		<description>One might argue that it can&#039;t hurt to prioritize some but not all high-priority emails. But to me that&#039;s completely useless. It&#039;s like using a spam filter with a significant amount of false positives--you end up having to check the spam folder frequently, thus defeating its purpose.

The sequence I want--which could be completely automated--looks like this.

You, a complete stranger, want to send me an email that you&#039;re sure I&#039;ll consider important. So you send it using your email client, annotated with that assurance. My email client responds that, given that I have no idea who you are, I probably won&#039;t get to it any time soon. Your client responds that it will &quot;bet&quot; $1 (or more, depending on my client&#039;s threshold and your level of assurance) that I&#039;ll appreciate it being bumped up in the queue. When I read it, I can either acknowledge the important (and you keep your money) or disagree (in which case I get it). It doesn&#039;t have to be cash, if some other currency will do the trick. And of course the negotiation has to be largely automated (and secure) to be usable.

Sound complicated? Fair enough. But I can&#039;t think of a better way to do prioritization than to let the two parties negotiate it. And I&#039;m assuming 99%+ of messages will use default settings. This only should kick in for people who are inundated by incoming traffic but don&#039;t want to hire someone to screen their messages.

Also, I like that this approach addresses the subjectivity of what constitutes spam.</description>
		<content:encoded><![CDATA[<p>One might argue that it can&#8217;t hurt to prioritize some but not all high-priority emails. But to me that&#8217;s completely useless. It&#8217;s like using a spam filter with a significant amount of false positives&#8211;you end up having to check the spam folder frequently, thus defeating its purpose.</p>
<p>The sequence I want&#8211;which could be completely automated&#8211;looks like this.</p>
<p>You, a complete stranger, want to send me an email that you&#8217;re sure I&#8217;ll consider important. So you send it using your email client, annotated with that assurance. My email client responds that, given that I have no idea who you are, I probably won&#8217;t get to it any time soon. Your client responds that it will &#8220;bet&#8221; $1 (or more, depending on my client&#8217;s threshold and your level of assurance) that I&#8217;ll appreciate it being bumped up in the queue. When I read it, I can either acknowledge the important (and you keep your money) or disagree (in which case I get it). It doesn&#8217;t have to be cash, if some other currency will do the trick. And of course the negotiation has to be largely automated (and secure) to be usable.</p>
<p>Sound complicated? Fair enough. But I can&#8217;t think of a better way to do prioritization than to let the two parties negotiate it. And I&#8217;m assuming 99%+ of messages will use default settings. This only should kick in for people who are inundated by incoming traffic but don&#8217;t want to hire someone to screen their messages.</p>
<p>Also, I like that this approach addresses the subjectivity of what constitutes spam.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jeremy</title>
		<link>http://thenoisychannel.com/2009/05/21/is-google-conjuring-a-magic-inbox-for-gmail/comment-page-1/#comment-3654</link>
		<dc:creator>jeremy</dc:creator>
		<pubDate>Thu, 21 May 2009 23:02:18 +0000</pubDate>
		<guid isPermaLink="false">http://thenoisychannel.com/?p=2121#comment-3654</guid>
		<description>&lt;i&gt;That wouldn’t be hard to implement for Google or any other email service / application that has access to your history, but I’m skeptical of the value of implementing prioritization this way. I can’t speak for others, but I personally have no reason to believe there is a correlation between frequency of contact and priority.&lt;/i&gt;

Case in point: I email many of my work colleagues much more often than I email my wife. 

But when that email from her arrives, oh my, it better be in my priority queue ;-)</description>
		<content:encoded><![CDATA[<p><i>That wouldn’t be hard to implement for Google or any other email service / application that has access to your history, but I’m skeptical of the value of implementing prioritization this way. I can’t speak for others, but I personally have no reason to believe there is a correlation between frequency of contact and priority.</i></p>
<p>Case in point: I email many of my work colleagues much more often than I email my wife. </p>
<p>But when that email from her arrives, oh my, it better be in my priority queue <img src='http://thenoisychannel.com/wordpress/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>

