Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: Gnus Cloud
Date: Wed, 09 Feb 2011 21:25:13 -0600	[thread overview]
Message-ID: <87y65omuzq.fsf@lifelogs.com> (raw)
In-Reply-To: <87k4h8hfb6.fsf@gnus.org>

On Wed, 09 Feb 2011 17:02:53 -0800 Lars Ingebrigtsen <larsi@gnus.org> wrote: 

LI> Ted Zlatanov <tzz@lifelogs.com> writes:

>> A .GPG file could be stored.  It wouldn't be synchronized, just set/get.

LI> Well, it should be updated when it's updated on one of the Gnus
LI> installations.

Right.  So I'd allow for a generic "save a file to the cloud" facility
that doesn't have any of the deltas.

LI> You might also envision totally storage-less Gnus installations, sort
LI> of.  That is, `M-x gnus-ephemeral-on-the-go' that would just get the
LI> data from the cloud, read a bit, and then exit without saving anything
LI> locally.  If you're afraid storing your secret .newsrc.eld/.authinfo.gpg
LI> files on your device.

Basically Google Reader.  I don't like that as much as just
synchronizing the configuration, although I'm sure some would like it.
It seems like an extreme compared to just synchronizing the things you
listed.

I would make a final Gnus release of the current series and start a new
"Cloudy" or "Cumulonimbus Gnus" whichever way you go.  FWIW I'd make it
flexible enough that people can sync just their marks or go all the way
up to 100% synchronized configuration.

Ted




  reply	other threads:[~2011-02-10  3:25 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 [this message]
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
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=87y65omuzq.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).