* Some sort of scripting interface?

* Should  doarticle_show_multi be an option? (always/auto(default)/never) (longness/shortness optional too?)

* Some sort of hierarchical organization for .ngetrc, so that you could set some options for abunch of hosts or a bunch of groups at once...

* A "connectiongroup" or something so that you can set a maxconnections within a certain set of servers

should uu_msg(1) (Note) be a decode error?
This should be handled:
uu_msg(1):Note: No encoded data found in ec3317e3-71cf792d.011
 1 decoding errors occured, keeping temp files.

*create .ngetrc on first run from NNTPSERVER or -h if specified instead.  (and add new servers not seen before when used with -h?  need to keep comments somehow though...)

*derr on uulib messages - file already exists derr.. is the current hack good enough?


*redo byte lenience?
*store d/l path in -w files (for -W)
*make -W switch to read in -w files and decode it all. (also if downloading any, update the file )

definataly gonna do:
*make MID_INFO_MIN_KEEP, etc config options
*fix EINTR (should try read again, not err (also should keep the same timeout within multiple tries?))
*add log output ability
*fix tempfiledir mixup where -w to write doesn't use the tempfile dir and such misses parts we already have


might do eventually:

 * cross post detection/mark downloaded in all groups somehow??
   Hm, actually it might not be that hard.. since mids are globally unique, it
   could just use the same midinfo for _all_ groups?  sound good/bad?
 * ditch/fix uulib?   Are there any alternatives?
 * per group (.ngetrc) config setting for "base directory", then -p/-P could be
   relative of that.  (maybe if you put / or ./ in front, it would be
   relative to root/current instead of base)
 * allow searching based upon date/author/lines etc.  ideally, something like:
   nget -r (date > 03/04/1999 && (author = bob && subject = file\.) || (subject
   = blah)).. DONE, but uses postfix method.. might be nice to add infix type.
 * threaded (background) decoding

only considering:

 * should the midinfo files only store the mid for the first part, like now, 
   or the mid of all parts of the post?

not gonna do:
 
 * test libc5/old gcc (forget it.  ngetlite is their only hope. upgrade.)

Misc info:
rfc977	"Network News Transfer Protocol"
rfc1036	"Standard for Interchange of USENET Messages"
various other rfcs/drafts: http://www.tin.org/docs.html