<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Ideas? Plenty of ideas!</title>
	<link>http://pvanhoof.be/blog/index.php/2008/03/04/ideas-plenty-of-ideas</link>
	<description>From the mind of Philip</description>
	<pubDate>Sat, 13 Mar 2010 16:07:10 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.2</generator>

	<item>
		<title>by: pvanhoof</title>
		<link>http://pvanhoof.be/blog/index.php/2008/03/04/ideas-plenty-of-ideas#comment-24244</link>
		<pubDate>Sat, 08 Mar 2008 14:56:14 +0000</pubDate>
		<guid>http://pvanhoof.be/blog/index.php/2008/03/04/ideas-plenty-of-ideas#comment-24244</guid>
					<description>Peter: I agree. But how do we get there? It's not only a technical problem to tackle. Also a social one. But I for example frequently meet the guys doing Telepathy. I really hope to find some sort of synergy ... For me future is also guesswork, of course.

DJ: Right now I will of course start this contract with this new customer. But after that, sure ... Doing Steve's E-mail client's network layer sounds fun :)

They never contacted me, though. I never met any of the iPhone guys at the Lemonade interops nor on the Lemonade mailing lists. So I kinda fear they are not aware of what we are trying to achieve with IMAP's future.</description>
		<content:encoded><![CDATA[<p>Peter: I agree. But how do we get there? It&#8217;s not only a technical problem to tackle. Also a social one. But I for example frequently meet the guys doing Telepathy. I really hope to find some sort of synergy &#8230; For me future is also guesswork, of course.</p>
<p>DJ: Right now I will of course start this contract with this new customer. But after that, sure &#8230; Doing Steve&#8217;s E-mail client&#8217;s network layer sounds fun :)</p>
<p>They never contacted me, though. I never met any of the iPhone guys at the Lemonade interops nor on the Lemonade mailing lists. So I kinda fear they are not aware of what we are trying to achieve with IMAP&#8217;s future.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: DJ Saltarelli</title>
		<link>http://pvanhoof.be/blog/index.php/2008/03/04/ideas-plenty-of-ideas#comment-24201</link>
		<pubDate>Fri, 07 Mar 2008 00:43:36 +0000</pubDate>
		<guid>http://pvanhoof.be/blog/index.php/2008/03/04/ideas-plenty-of-ideas#comment-24201</guid>
					<description>Philip-  It's always a pleasure to catch up on what you're doing with Tinymail and just your thoughts on things.  Anyway, it seems of utmost importance to tinymail that we get you hired by someone interesting and soon.

Besides Novell, who are always working on Evo and their groupware suites, there's Apple and the iPhone's e-mail client backend.  They seem like a great candidate employer for your work since anywhere they can free up memory or add features without using more is a win that will pay off in other areas on the device.

On the opposite side, Yahoo might be a good candidate, since they purchased Zimbra.  You never know when they might want to start working on custom mobile device clients for their IMAP services (think for Blackberry phones or for the non-PDA type of devices).

I wish I knew some people at those organizations.  Good luck man.

/djs</description>
		<content:encoded><![CDATA[<p>Philip-  It&#8217;s always a pleasure to catch up on what you&#8217;re doing with Tinymail and just your thoughts on things.  Anyway, it seems of utmost importance to tinymail that we get you hired by someone interesting and soon.</p>
<p>Besides Novell, who are always working on Evo and their groupware suites, there&#8217;s Apple and the iPhone&#8217;s e-mail client backend.  They seem like a great candidate employer for your work since anywhere they can free up memory or add features without using more is a win that will pay off in other areas on the device.</p>
<p>On the opposite side, Yahoo might be a good candidate, since they purchased Zimbra.  You never know when they might want to start working on custom mobile device clients for their IMAP services (think for Blackberry phones or for the non-PDA type of devices).</p>
<p>I wish I knew some people at those organizations.  Good luck man.</p>
<p>/djs
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Peter Stradinger</title>
		<link>http://pvanhoof.be/blog/index.php/2008/03/04/ideas-plenty-of-ideas#comment-24166</link>
		<pubDate>Wed, 05 Mar 2008 15:09:46 +0000</pubDate>
		<guid>http://pvanhoof.be/blog/index.php/2008/03/04/ideas-plenty-of-ideas#comment-24166</guid>
					<description>Hi,

I've been thinking about messaging for a while now, but haven't been able to get out from under other projects to tackle it.  I think my main issue with e-mail is not client-related, but storage related.  Wouldn't it make a lot of sense (and save a lot of space) to store messages in a relational database?  And, given that database, to make the messages client-agnostic?  I don't see why we couldn't have a message server that treats threaded messages from email, IM, sms and web forums identically.  Email threads could be subscribed to and browsed.  You could invite people to access a thread in its entirety, or partially without needing to CC them on every message.  The benefits of even slightly more uniformity in storage are enormous.

Peter</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>I&#8217;ve been thinking about messaging for a while now, but haven&#8217;t been able to get out from under other projects to tackle it.  I think my main issue with e-mail is not client-related, but storage related.  Wouldn&#8217;t it make a lot of sense (and save a lot of space) to store messages in a relational database?  And, given that database, to make the messages client-agnostic?  I don&#8217;t see why we couldn&#8217;t have a message server that treats threaded messages from email, IM, sms and web forums identically.  Email threads could be subscribed to and browsed.  You could invite people to access a thread in its entirety, or partially without needing to CC them on every message.  The benefits of even slightly more uniformity in storage are enormous.</p>
<p>Peter
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: timsamoff</title>
		<link>http://pvanhoof.be/blog/index.php/2008/03/04/ideas-plenty-of-ideas#comment-24125</link>
		<pubDate>Tue, 04 Mar 2008 14:22:39 +0000</pubDate>
		<guid>http://pvanhoof.be/blog/index.php/2008/03/04/ideas-plenty-of-ideas#comment-24125</guid>
					<description>Philip ~ In my world of &quot;dead passion&quot; (i.e., the corporate smothering of good ideas), I just wanted to thank you for your obvious passion. I look forward to reading your email posts about the work you're doing with Modest, etc.</description>
		<content:encoded><![CDATA[<p>Philip ~ In my world of &#8220;dead passion&#8221; (i.e., the corporate smothering of good ideas), I just wanted to thank you for your obvious passion. I look forward to reading your email posts about the work you&#8217;re doing with Modest, etc.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: pvanhoof</title>
		<link>http://pvanhoof.be/blog/index.php/2008/03/04/ideas-plenty-of-ideas#comment-24124</link>
		<pubDate>Tue, 04 Mar 2008 14:09:51 +0000</pubDate>
		<guid>http://pvanhoof.be/blog/index.php/2008/03/04/ideas-plenty-of-ideas#comment-24124</guid>
					<description>You could use Sieve on IMAP (Cyrus, for example, supports Sieve) to do serverside filtering to redirect important E-mails to different folders?</description>
		<content:encoded><![CDATA[<p>You could use Sieve on IMAP (Cyrus, for example, supports Sieve) to do serverside filtering to redirect important E-mails to different folders?
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Gaël Varoquaux</title>
		<link>http://pvanhoof.be/blog/index.php/2008/03/04/ideas-plenty-of-ideas#comment-24118</link>
		<pubDate>Tue, 04 Mar 2008 07:09:13 +0000</pubDate>
		<guid>http://pvanhoof.be/blog/index.php/2008/03/04/ideas-plenty-of-ideas#comment-24118</guid>
					<description>Hi Philip,

As you keep blogging about the future of e-mail I would like to have your opinion on how to deal with heaps of mail. I have about 100 non-spam e-mail that arrive per dail in my mailbox. They are not all of similar importance, and I keep losing the important info into the noise. Recently friends introduced me to popfile (http://popfile.sourceforge.net/) and POP proxy that does bayesian classification of incoming e-mail. This seems like a great idea, but lacks integration in mail user agents. I leave all my e-mail on the server and I don't want to set up a secondary mail server.

In general, what do you think can help us classifying e-mail, sorting it out to find the important info? IMHO, this can range from clever Bayesian techniques to flat/non-flat views of several mailboxes, and good keyboard shortcuts for dealing with e-mail quickly. This is for me an incredibly important issue, and I would be strongly in depth to a mail user agent that helped me deal with my e-mail.

Cheers</description>
		<content:encoded><![CDATA[<p>Hi Philip,</p>
<p>As you keep blogging about the future of e-mail I would like to have your opinion on how to deal with heaps of mail. I have about 100 non-spam e-mail that arrive per dail in my mailbox. They are not all of similar importance, and I keep losing the important info into the noise. Recently friends introduced me to popfile (http://popfile.sourceforge.net/) and POP proxy that does bayesian classification of incoming e-mail. This seems like a great idea, but lacks integration in mail user agents. I leave all my e-mail on the server and I don&#8217;t want to set up a secondary mail server.</p>
<p>In general, what do you think can help us classifying e-mail, sorting it out to find the important info? IMHO, this can range from clever Bayesian techniques to flat/non-flat views of several mailboxes, and good keyboard shortcuts for dealing with e-mail quickly. This is for me an incredibly important issue, and I would be strongly in depth to a mail user agent that helped me deal with my e-mail.</p>
<p>Cheers
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
