🚀 go-pugleaf

In article <865465853snz@grempc.demon.co.uk>
   Graham@grempc.demon.co.uk (Graham E Kinns) writes:
>
>Maybe I should just put up a version as it is now (all the code added, 
>I've tested and I'm using it online) and see what the reaction is?

My reaction would be "Gimmegimmegimme".  I'd willingly help beta-test
such a wonderful new version.

As another thing for the "to-do" list, something I've long been toying
with is the idea of permitting multiple NNTP clients.  There are an
increasing number of private new heirarchies that are deliberately not
permitted on Demon or other public news servers.   At present you have
to manage multiple feeds manually, starting the next when the previous
one has finished - you can't, in all practicality, automate it.  I see
them as receiving concurrently into different batch files, probably
sharing other resources such as the history list to keep space down.

Another suggestion is adding an article-number NNTP client such as a
port of slurp, because Demon is one of only a few feeds that allow
NEWNEWS.  Retrieval by article numbers would further increase the
utility of KA9Q and let me take feeds that I can't at present do at
all, even if I manually manage the sessions.  I don't know how much
space this would actually require, but I envisage that the syntax could
become something like:

nntp addserver <hostname> [NEWNEWS|SLURP] [<batch-file>] <interval> [<groups>]

where the literal NEWNEWS or SLURP is obvious, and its presence or that
of the batch file name is detected by their not being numeric and hence
not a valid interval.

Nick