<?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: The Future of Email: From SMTP to XMPP</title>
	<atom:link href="http://anarchogeek.com/2008/06/20/the-future-of-email-from-smtp-to-xmpp/feed/" rel="self" type="application/rss+xml" />
	<link>http://anarchogeek.com/2008/06/20/the-future-of-email-from-smtp-to-xmpp/</link>
	<description></description>
	<lastBuildDate>Mon, 09 Jan 2012 17:51:16 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: xian</title>
		<link>http://anarchogeek.com/2008/06/20/the-future-of-email-from-smtp-to-xmpp/comment-page-1/#comment-1903</link>
		<dc:creator>xian</dc:creator>
		<pubDate>Fri, 20 Jun 2008 02:16:00 +0000</pubDate>
		<guid isPermaLink="false">http://anarchogeek.com/2008/06/20/the-future-of-email-from-smtp-to-xmpp#comment-1903</guid>
		<description>&lt;p&gt;Rabble, I love this idea, but how does a buddy list transate into an email white list?&lt;/p&gt;


	&lt;p&gt;At scale, won&#8217;t I be &#8220;spammed&#8221; constantly by permission reuqests?&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Rabble, I love this idea, but how does a buddy list transate into an email white list?</p>
<p>At scale, won&#8217;t I be &#8220;spammed&#8221; constantly by permission reuqests?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Charlie</title>
		<link>http://anarchogeek.com/2008/06/20/the-future-of-email-from-smtp-to-xmpp/comment-page-1/#comment-1904</link>
		<dc:creator>Charlie</dc:creator>
		<pubDate>Fri, 20 Jun 2008 02:16:00 +0000</pubDate>
		<guid isPermaLink="false">http://anarchogeek.com/2008/06/20/the-future-of-email-from-smtp-to-xmpp#comment-1904</guid>
		<description>&lt;p&gt;This is a cool idea. And &lt;span class=&quot;caps&quot;&gt;XMPP&lt;/span&gt; seems to be getting a lot of attention in another sphere now too &#8211; as a messaging protocol, say, in cloud computing applications.
http://brainspl.at/articles/2008/06/02/introducing-vertebra&lt;/p&gt;


	&lt;p&gt;What would also be cool is if someone like facebook did this, and supported xmpp for im and email, and &lt;span class=&quot;caps&quot;&gt;NOT&lt;/span&gt; smtp. Then everybody gets a soandso@facebook.com address, using just the shiny new stuff. That plus adoption from gmail/gtalk would get pretty much everybody&#8217;s attention :)&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>This is a cool idea. And <span class="caps">XMPP</span> seems to be getting a lot of attention in another sphere now too &#8211; as a messaging protocol, say, in cloud computing applications.<br />
<a href="http://brainspl.at/articles/2008/06/02/introducing-vertebra" rel="nofollow">http://brainspl.at/articles/2008/06/02/introducing-vertebra</a></p>
<p>What would also be cool is if someone like facebook did this, and supported xmpp for im and email, and <span class="caps">NOT</span> smtp. Then everybody gets a <a href="mailto:soandso@facebook.com">soandso@facebook.com</a> address, using just the shiny new stuff. That plus adoption from gmail/gtalk would get pretty much everybody&#8217;s attention <img src='http://anarchogeek.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Caleb Cushing (xenoterracide)</title>
		<link>http://anarchogeek.com/2008/06/20/the-future-of-email-from-smtp-to-xmpp/comment-page-1/#comment-1905</link>
		<dc:creator>Caleb Cushing (xenoterracide)</dc:creator>
		<pubDate>Fri, 20 Jun 2008 02:16:00 +0000</pubDate>
		<guid isPermaLink="false">http://anarchogeek.com/2008/06/20/the-future-of-email-from-smtp-to-xmpp#comment-1905</guid>
		<description>&lt;p&gt;Email can already do what you are asking for, the problem is the interface that email providers give you to there spam filtering technology plus mail server white/blacklists.&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Email can already do what you are asking for, the problem is the interface that email providers give you to there spam filtering technology plus mail server white/blacklists.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shannon</title>
		<link>http://anarchogeek.com/2008/06/20/the-future-of-email-from-smtp-to-xmpp/comment-page-1/#comment-1906</link>
		<dc:creator>Shannon</dc:creator>
		<pubDate>Fri, 20 Jun 2008 02:16:00 +0000</pubDate>
		<guid isPermaLink="false">http://anarchogeek.com/2008/06/20/the-future-of-email-from-smtp-to-xmpp#comment-1906</guid>
		<description>&lt;p&gt;Looking at this another way, by automatically adding your gmail contacts to your gtalk buddylist, does google make it&#8217;s own version of IM more spammy?&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Looking at this another way, by automatically adding your gmail contacts to your gtalk buddylist, does google make it&#8217;s own version of IM more spammy?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Lane</title>
		<link>http://anarchogeek.com/2008/06/20/the-future-of-email-from-smtp-to-xmpp/comment-page-1/#comment-1907</link>
		<dc:creator>Dan Lane</dc:creator>
		<pubDate>Fri, 20 Jun 2008 02:16:00 +0000</pubDate>
		<guid isPermaLink="false">http://anarchogeek.com/2008/06/20/the-future-of-email-from-smtp-to-xmpp#comment-1907</guid>
		<description>&lt;p&gt;Wait, EX-employer? where are you now?&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Wait, EX-employer? where are you now?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ian Parker</title>
		<link>http://anarchogeek.com/2008/06/20/the-future-of-email-from-smtp-to-xmpp/comment-page-1/#comment-1908</link>
		<dc:creator>Ian Parker</dc:creator>
		<pubDate>Fri, 20 Jun 2008 02:16:00 +0000</pubDate>
		<guid isPermaLink="false">http://anarchogeek.com/2008/06/20/the-future-of-email-from-smtp-to-xmpp#comment-1908</guid>
		<description>&lt;p&gt;I think leveraging social networks for this is a bad idea because they are insular and are not considered to be viable or particularly productive by all. If GMail/GTalk could manage to push the envelope here, that would be great, but older users and non-tech users tend to shy away from IM technology. Not to say that IM is inherently bad, on the contrary, there are studies suggesting that IM makes people more productive. I would argue that with the point that e-mail is almost identical, but that&#8217;s another story.&lt;/p&gt;


	&lt;p&gt;If it&#8217;s just a matter of the underlying protocol, then the change could be made easily and most easily by Google and &lt;span class=&quot;caps&quot;&gt;AOL&lt;/span&gt; as you suggested. Why? Because it would be transparent to users as they both control the server and client software that users are accessing. As for the spam issue, there are some good points that arise. How do we allow new people onto the whitelist? Can people request to be added in the manner of social networks, or do we bring our own friends? Do I as a user then need to add a contact every time I want to receive e-mail from a new sender or source? That would be rather painful and not acceptable. Administering a firewall is bad enough without having to micromanage e-mail. Technology is supposed to make lives easier, not more complex. I&#8217;ve rambled on enough. Interesting idea, you have.&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>I think leveraging social networks for this is a bad idea because they are insular and are not considered to be viable or particularly productive by all. If GMail/GTalk could manage to push the envelope here, that would be great, but older users and non-tech users tend to shy away from IM technology. Not to say that IM is inherently bad, on the contrary, there are studies suggesting that IM makes people more productive. I would argue that with the point that e-mail is almost identical, but that&#8217;s another story.</p>
<p>If it&#8217;s just a matter of the underlying protocol, then the change could be made easily and most easily by Google and <span class="caps">AOL</span> as you suggested. Why? Because it would be transparent to users as they both control the server and client software that users are accessing. As for the spam issue, there are some good points that arise. How do we allow new people onto the whitelist? Can people request to be added in the manner of social networks, or do we bring our own friends? Do I as a user then need to add a contact every time I want to receive e-mail from a new sender or source? That would be rather painful and not acceptable. Administering a firewall is bad enough without having to micromanage e-mail. Technology is supposed to make lives easier, not more complex. I&#8217;ve rambled on enough. Interesting idea, you have.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: david koblas</title>
		<link>http://anarchogeek.com/2008/06/20/the-future-of-email-from-smtp-to-xmpp/comment-page-1/#comment-1909</link>
		<dc:creator>david koblas</dc:creator>
		<pubDate>Fri, 20 Jun 2008 02:16:00 +0000</pubDate>
		<guid isPermaLink="false">http://anarchogeek.com/2008/06/20/the-future-of-email-from-smtp-to-xmpp#comment-1909</guid>
		<description>&lt;p&gt;Let&#8217;s see if I&#8217;ve got this right&#8230;  The idea is to switch the transport of messages from &lt;span class=&quot;caps&quot;&gt;SMTP&lt;/span&gt; =&gt; &lt;span class=&quot;caps&quot;&gt;XMPP&lt;/span&gt;.  Fine at the core that&#8217;s like saying I wan&#8217;t &lt;span class=&quot;caps&quot;&gt;JSON&lt;/span&gt; formatted data not &lt;span class=&quot;caps&quot;&gt;XML&lt;/span&gt;.  It&#8217;s just wire format.&lt;/p&gt;


	&lt;p&gt;The problem becomes that while you can transport a message, who do you receive messages from?&lt;/p&gt;


	&lt;p&gt;If you only accept email from people in your address book (which hotmail supports) then you&#8217;re back to needing a way for anonymous communications.   The &#8220;biggest&#8221; user of this is that order confirmation from &lt;span class=&quot;caps&quot;&gt;XYZ&lt;/span&gt; corp that&#8217;s going to show up in your mailbox, do you first need to add them as a buddy before a message is accepted?  That new website that isn&#8217;t OpenID compatible sends you a confirmation message, where did it go?&lt;/p&gt;


	&lt;p&gt;At the end of the day you still need that anonymous communications channel, but adding more and more structure to the display of messages makes a huge difference.&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Let&#8217;s see if I&#8217;ve got this right&#8230;  The idea is to switch the transport of messages from <span class="caps">SMTP</span> =&gt; <span class="caps">XMPP</span>.  Fine at the core that&#8217;s like saying I wan&#8217;t <span class="caps">JSON</span> formatted data not <span class="caps">XML</span>.  It&#8217;s just wire format.</p>
<p>The problem becomes that while you can transport a message, who do you receive messages from?</p>
<p>If you only accept email from people in your address book (which hotmail supports) then you&#8217;re back to needing a way for anonymous communications.   The &#8220;biggest&#8221; user of this is that order confirmation from <span class="caps">XYZ</span> corp that&#8217;s going to show up in your mailbox, do you first need to add them as a buddy before a message is accepted?  That new website that isn&#8217;t OpenID compatible sends you a confirmation message, where did it go?</p>
<p>At the end of the day you still need that anonymous communications channel, but adding more and more structure to the display of messages makes a huge difference.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ideamonk</title>
		<link>http://anarchogeek.com/2008/06/20/the-future-of-email-from-smtp-to-xmpp/comment-page-1/#comment-1910</link>
		<dc:creator>ideamonk</dc:creator>
		<pubDate>Fri, 20 Jun 2008 02:16:00 +0000</pubDate>
		<guid isPermaLink="false">http://anarchogeek.com/2008/06/20/the-future-of-email-from-smtp-to-xmpp#comment-1910</guid>
		<description>&lt;p&gt;great idea&#8230; thinking if spam would cause any problem&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>great idea&#8230; thinking if spam would cause any problem</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ideamonk</title>
		<link>http://anarchogeek.com/2008/06/20/the-future-of-email-from-smtp-to-xmpp/comment-page-1/#comment-1911</link>
		<dc:creator>ideamonk</dc:creator>
		<pubDate>Fri, 20 Jun 2008 02:16:00 +0000</pubDate>
		<guid isPermaLink="false">http://anarchogeek.com/2008/06/20/the-future-of-email-from-smtp-to-xmpp#comment-1911</guid>
		<description>&lt;p&gt;great idea&#8230; thinking if spam would cause any problem&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>great idea&#8230; thinking if spam would cause any problem</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: byr0n</title>
		<link>http://anarchogeek.com/2008/06/20/the-future-of-email-from-smtp-to-xmpp/comment-page-1/#comment-1912</link>
		<dc:creator>byr0n</dc:creator>
		<pubDate>Fri, 20 Jun 2008 02:16:00 +0000</pubDate>
		<guid isPermaLink="false">http://anarchogeek.com/2008/06/20/the-future-of-email-from-smtp-to-xmpp#comment-1912</guid>
		<description>&lt;p&gt;I think there are actually a couple of good alternatives to the current mail problems we all have, however I see the bigger problem being the backbone providers, core hardware providers and the carriers. Spam is bad for us, but good for someone selling bandwidth. I see that being the problem with the lack of wider adoption of &lt;span class=&quot;caps&quot;&gt;IPV6&lt;/span&gt; at a carrier level as well, because less private address  space means less spoofing and in turn spamming but this would cost the bandwidth providers precious revenue in spam traffic. I think the barrier in adoption of something like &lt;span class=&quot;caps&quot;&gt;XMPP&lt;/span&gt; is the loss of revenue rather from the problem it will help to solve rather than the know-how or adoption process&#8230;&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>I think there are actually a couple of good alternatives to the current mail problems we all have, however I see the bigger problem being the backbone providers, core hardware providers and the carriers. Spam is bad for us, but good for someone selling bandwidth. I see that being the problem with the lack of wider adoption of <span class="caps">IPV6</span> at a carrier level as well, because less private address  space means less spoofing and in turn spamming but this would cost the bandwidth providers precious revenue in spam traffic. I think the barrier in adoption of something like <span class="caps">XMPP</span> is the loss of revenue rather from the problem it will help to solve rather than the know-how or adoption process&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

