From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: Gnus Cloud
Date: Thu, 10 Feb 2011 11:56:32 -0600 [thread overview]
Message-ID: <87ipwrzsbz.fsf@lifelogs.com> (raw)
In-Reply-To: <87r5bgwdhk.fsf@keller.adm.naquadah.org>
On Thu, 10 Feb 2011 08:33:11 +0100 Julien Danjou <julien@danjou.info> wrote:
JD> A NoSQL database like CouchDB, but replacing JSON with Lisp?
Yes, that was my original idea but with custom merge logic. Lars'
proposal to just stack changes is probably better for the server but
definitely more expensive for the user. Membase seems like a better fit
to me as the backend, though. CouchDB is miserably slow under heavy
load.
(Yes, I know Membase and Couch* merged, but any actual results from that
union will take a while.)
I would really like to serve and accept JSON as an alternate format.
Then others can share this facility so it's not just a Gnus thing.
On Thu, 10 Feb 2011 11:58:53 +0100 Philipp Haselwarter <philipp.haselwarter@gmx.de> wrote:
PH> "TZ" == Ted Zlatanov <tzz@lifelogs.com> writes:
TZ> Right. So I'd allow for a generic "save a file to the cloud"
TZ> facility that doesn't have any of the deltas.
PH> I'm not sure that's a very good idea; there's no guarantee a
PH> .authinfo.gpg file is encrypted or anything.
PH> But I'd want to run the cloud on my own server anyways. After all, the
PH> emacs does let you shoot yourself in the foot if you insist, so, go for
PH> it.
Let's put it this way: if you choose to call an unencrypted file x.gpg
and save it on a server, why should the server stop you?
I think running the sync server on your own is a basic requirement,
yes. The target user base for Gnus tends to be a bit paranoid[1] :)
Ted
[1] Including myself, of course.
next prev parent reply other threads:[~2011-02-10 17:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-09 19:24 Lars Ingebrigtsen
2011-02-09 20:22 ` Julien Danjou
2011-02-10 0:58 ` Lars Ingebrigtsen
2011-02-10 7:35 ` Julien Danjou
2011-02-10 18:30 ` Lars Ingebrigtsen
2011-02-10 11:21 ` Steinar Bang
2011-02-11 16:27 ` Sivaram Neelakantan
2011-02-11 16:32 ` Richard Riley
2011-02-09 22:01 ` Ted Zlatanov
2011-02-10 1:02 ` Lars Ingebrigtsen
2011-02-10 3:25 ` Ted Zlatanov
2011-02-10 10:58 ` Philipp Haselwarter
2011-02-10 18:29 ` Lars Ingebrigtsen
2011-02-10 18:27 ` Lars Ingebrigtsen
2011-02-10 7:33 ` Julien Danjou
2011-02-10 17:56 ` Ted Zlatanov [this message]
2011-02-10 18:33 ` Lars Ingebrigtsen
2011-02-10 19:47 ` Ted Zlatanov
2011-02-14 2:12 ` Lars Ingebrigtsen
2011-02-18 16:04 ` Greg Troxel
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=87ipwrzsbz.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@gnus.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;
as well as URLs for NNTP newsgroup(s).