From: Rich Lane <rlane@club.cc.cmu.edu>
To: Andrei Thorp <garoth@gmail.com>
Cc: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] sup-server
Date: Tue, 08 Dec 2009 21:33:29 -0500 [thread overview]
Message-ID: <1260323222-sup-1616@zyrg.net> (raw)
In-Reply-To: <80055d7c0912081412h483bc6dt8493b08dfab1d23b@mail.gmail.com>
Excerpts from Andrei Thorp's message of Tue Dec 08 17:12:05 -0500 2009:
> This really seems like it's in direct competition with the Wave
> system... but Wave has a lot more support. And yes, Wave doesn't have
> e-mail federation at the moment, but I think they plan to do that in
> the future. So yes, I like the idea of a Sup server, I like being able
> to access my (sup) mail from multiple computers, I like the idea of
> having multiple UIs to the Sup Service... but I think that in the long
> run, I'd feel just as good about a couple good open source UIs to
> Google's Wave instead.
I actually didn't think about this as being competition to Wave. The
current implementation is much more narrowly scoped, but the grand
generic document store vision does bear a resemblance. I don't know how
far down that road the project will go. I don't want to lose mail client
functionality for the sake of being as generic as Wave (I haven't seen
any information on the subject, but I assume the translation to/from
email is lossy).
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2009-12-09 2:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-08 18:56 Rich Lane
2009-12-08 22:12 ` Andrei Thorp
2009-12-09 2:33 ` Rich Lane [this message]
2009-12-09 13:45 ` Andrei Thorp
2009-12-19 19:16 ` William Morgan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1260323222-sup-1616@zyrg.net \
--to=rlane@club.cc.cmu.edu \
--cc=garoth@gmail.com \
--cc=sup-talk@rubyforge.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox