Re: Emacs Cloud (coverage and killed groups)

[Lars Ingebrigtsen <larsi@gnus.org>]

The file duplication thingies are basically done now, so I'm starting in
on the newsrc replication.

(Things are taking a lot longer than I expected because of Stuff.)

I had originally planned to just say "all network based servers should
be covered by default", but I think that's not really the common use
case.  I have a gazillion servers in my .newsrc.eld at home, but I
really just want to have news.gmane.org, news.gnus.org and one of my
IMAP servers while travelling.

So I think a new server mode command would be the thing -- to mark
server explicitly for coverage.

The other thing I'm wondering about what to do with is
`gnus-killed-list' and killed groups in general.

First of all, the list tends to be long:

(length gnus-killed-list)
=> 9138

So it would be nice not to carry that around all the time.  But if we
don't, then backends that don't support "give me new groups since DATE"
will pop up new groups that we have already killed off in one of the
other instances.

The other question is whether to replicate killing groups at all.  If
I'm on holiday, and I kill off 30 work-related groups, do I really want
the same to happen at home?  I think the answer is...  perhaps...

Any thoughts?

-- 
(domestic pets only, the antidote for overdose, milk.)
  bloggy blog http://lars.ingebrigtsen.no/