From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: Current state of gnus-cloud?
Date: Thu, 11 Oct 2018 20:59:24 +0000 [thread overview]
Message-ID: <k1moxkr7.fsf@lifelogs.com> (raw)
In-Reply-To: <877eis2wz0.fsf@ericabrahamsen.net>
On Mon, 08 Oct 2018 10:02:11 -0700 Eric Abrahamsen <eric@ericabrahamsen.net> wrote:
EA> Ted Zlatanov <tzz@lifelogs.com> writes:
>> I use it to upload my newsrc and it works all right.
EA> Out of curiosity -- I'd always thought it was a bad idea to share
EA> newsrc.eld files between machines, as the article numbers aren't
EA> guaranteed to be the same between them. Is that not an issue for you?
Across NNTP servers it works. You can choose backends to synchronize, so
NNTP makes sense but nnrss nnml etc. probably wouldn't.
(The gnus-cloud format is like a multipart message, and the article sync
is just one use case. You can sync files and any kind of data through it.)
Ted
next prev parent reply other threads:[~2018-10-11 20:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-05 16:42 Jason L Tibbitts III
2018-10-08 0:48 ` Ted Zlatanov
2018-10-08 17:02 ` Eric Abrahamsen
2018-10-11 20:59 ` Ted Zlatanov [this message]
2018-10-11 22:10 ` Eric Abrahamsen
2018-10-29 16:14 ` Steinar Bang
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=k1moxkr7.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).