From mboxrd@z Thu Jan  1 00:00:00 1970
From: marcus-sup@bar-coded.net (Marcus Williams)
Date: Thu, 07 Feb 2008 21:09:05 +0000
Subject: [sup-talk] Persistence between IMAP clients
In-Reply-To: <1202407800-sup-6982@south>
References: <20080204151221.GA29477@manheim.library.drexel.edu>
	<1202229600-sup-4858@south> <1202248916-sup-1460@south>
	<1202373660-sup-5293@tomsk> <1202407800-sup-6982@south>
Message-ID: <1202417630-sup-9601@tomsk>

On 7.2.2008, William Morgan wrote:
> If you can run a sup server somewhere, surely you can run sshd there
> instead. The only difference would be UI lag on slow connections. Is
> that the big win?

Man, your throw away suggestions should come with "warning, bear trap
ahead" notices :)

For me, the biggest draw of having it as a service is multi-app usage.
I treat sup as a view upon my email but I use my email for a whole lot
of things and sup doesnt (yet) give me views of this data if you see
what I mean. For instance - I might mark emails as todos via the
message hooks so I can email myself todos. I dont need to see who
these are from or the date of these email, just the snippet. Also I
dont really want to go into sup to get these I'd rather have them
available via http. I can do this read only now, but if I want to do
any interactions with this "view" I need to go via sup really. Also I
cant do this when sup is open on my machine as its got the index open
and I'm not sure ferret lets you do multi-user access to the index.

Console access is great when you've got it, but its not so good on a
phone/pda (I am determined to get it running locally on my n800
though!) - so accessing the index through other ways would be useful
here.

Also, sup *is already* a client/server console tool - you're accessing
imap or maildir-over-ssh as a client. The beauty of IMAP (_not_ the
protocol which I have to agree sucks) is the fact I can use any client
I want *locally* and have the same view upon my email anywhere. I dont
have to save an attachment to a disk on my imap server, open winscp to
go to that server pick up the attachment and save locally to view it
on my machine at work or battle with x11 auth and install x11/gnome
packages on my server so I can view it over X11 over ssh.

Dont get me wrong, for my biggest usage sup doesnt need to use the
index over a networked service, I could write most stuff as ruby cgis
or RoR that access the ferret index because most of the time sup wont
be running so wont care. Its just I wouldnt have to worry about it if
it was networked :) and I think it would open up more possibilities of
the use of the index (again, I'm thinking "views" upon my data not
necessarily sup's usage).

Marcus