From: Lars Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: I can haz cloud idea
Date: Thu, 16 Feb 2012 06:03:47 +0100 [thread overview]
Message-ID: <87fwebnzd8.fsf@gnus.org> (raw)
The main problems with going all cloudy is that you have to have yet
another server out there somewhere. Whether you use Dropbox/sshfs/a yet
to be determined Gnus-specific server, that's not very sexy.
But how about if we just cheat and put all the information on the IMAP
server?
That is: Gnus would create and maintain a special group on one of your
IMAP servers that would contain all the data Gnus needs.
You'd set this up by setting, er, something, like:
(setq gnus-cloud-server '(nnimap "imap.gmail.com"))
This would make Gnus save all the data on that server whenever you exit
Gnus. (Or on certain intervals.) It could gzip and encrypt the data
before uploading, I guess.
So when you go to your other machine, you'd say `M-x gnus-cloud', and it
would prompt you for the server and password(s), download the data, and
then start up more or less as normal.
And it would upload the data on exit, as well, so you'd be all cloudy.
What would be stored on the server? Well, the .newsrc.eld file, for
one. And the SCORE files, I guess. And... well, whatever else you
want. It could be a simple archive "file" type, and Gnus could just
decrypt, uncompress and unpack the files. Some sanity check about
overwriting newer files with older files, I guess.
How much data would this be? Here's my .newsrc.eld file:
larsi@rusty:~/mgnus$ ls -l ~/.newsrc.eld
-rw-r--r-- 1 larsi larsi 502770 2012-02-16 05:46 /home/larsi/.newsrc.eld
larsi@rusty:~/mgnus$ gzip -9 -c /home/larsi/.newsrc.eld | wc
441 2222 117577
larsi@rusty:~/mgnus$ xz -c /home/larsi/.newsrc.eld | wc
258 1440 65288
A 65K download isn't too bad. Well. You'd have to base64 it before
uploading, I guess.
Does Emacs have xz compression built in? And built-in encryption would
also be nice, but that's already planned for Emacs 24.2, I guess...
--
(domestic pets only, the antidote for overdose, milk.)
http://lars.ingebrigtsen.no * Sent from my Rome
next reply other threads:[~2012-02-16 5:03 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-16 5:03 Lars Ingebrigtsen [this message]
2012-02-16 6:49 ` Lars Ingebrigtsen
2012-02-16 8:19 ` Antoine Levitt
2012-02-16 9:27 ` Steinar Bang
2012-02-16 9:35 ` Lars Ingebrigtsen
2012-02-16 7:00 ` Vegard Vesterheim
2012-02-17 17:49 ` Richard Riley
2012-02-19 15:21 ` Lars Ingebrigtsen
2012-02-19 18:04 ` Andy Moreton
2012-02-19 22:15 ` Dan Christensen
2012-02-20 7:41 ` Lars Ingebrigtsen
2012-02-20 19:20 ` Dan Christensen
2012-03-10 1:18 ` Lars Magne Ingebrigtsen
2012-02-20 7:37 ` Lars Ingebrigtsen
2012-02-20 7:51 ` Lars Ingebrigtsen
2012-02-19 19:03 ` Adam Sjøgren
2012-02-21 21:23 ` Ted Zlatanov
2012-03-10 1:12 ` Lars Magne Ingebrigtsen
2012-03-10 12:43 ` Reiner Steib
2012-03-10 13:06 ` Ted Zlatanov
2012-07-18 14:31 ` Ted Zlatanov
2012-07-18 20:52 ` Steinar Bang
2012-02-16 8:25 ` David Engster
2012-02-16 9:12 ` Lars Ingebrigtsen
2012-02-16 9:23 ` David Engster
2012-02-16 9:29 ` Steinar Bang
2012-02-16 9:25 ` Steinar Bang
2012-02-16 11:55 ` Greg Troxel
2012-02-16 12:23 ` David Engster
2012-02-16 12:54 ` Ted Zlatanov
2012-02-16 12:51 ` Ted Zlatanov
2012-02-16 13:07 ` Ted Zlatanov
2012-02-20 7:48 ` Lars Ingebrigtsen
2012-02-25 9:46 ` Steinar Bang
2012-03-10 1:07 ` Lars Magne Ingebrigtsen
2012-03-03 3:20 ` TSUCHIYA Masatoshi
2012-03-10 1:06 ` Lars Magne Ingebrigtsen
2014-10-15 23:31 ` TSUCHIYA Masatoshi
2014-10-16 8:34 ` Steinar Bang
2014-10-16 12:38 ` Ted Zlatanov
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=87fwebnzd8.fsf@gnus.org \
--to=larsi@gnus.org \
--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).