🚀 go-pugleaf

Brian {Hamilton Kelly} (bhk@dsl.co.uk) wrote:
: In article <4nokrk$qe4@panix2.panix.com> tgold@panix.com "Anthony Gold" writes:

: > Unless you have a very small number of newsgroups, your nntp client will
: > issue many NEWNEWS commands, each with a separate list of newsgroups.  I
: > believe that any newsborg change is unlikely to prevent duplicates and
: > would urge Demon to allocate their scarce development resources elsewhere. 

: I think you'll find that KA9Q issues a NEWNEWS command with a list of a
: dozen or so newsgroups at a time.  It's *within* these downloads that the
: trouble appears, when quasi-adjacent groups have the same article.  This
: is because of the ring-buffering used by KA9Q between the fetches.  I
: think it's already been stated that within the longer time cycle of
: multiple NEWNEWS commands, KA9Q will have added the new articles'
: Message-IDs to its history file, and won't bother to get the later
: duplicates.  The problem never arose until the quite recent past; I
: believe it actually post-dates the official introduction of the
: distributed servers: it certainly happened after their unofficial launch.

: It's not just affecting KA9Q users either, from the impressions I gain.

If indeed the history file is only updated between NEWNEWS commands, might
I suggest that the NNTP.DAT file is rearranged out of the alphabetical
sequence that DIS prefers and that one attempts to separate groups which
are frequently cross-posted.  Tuning faq? 

Regards,
-- 
   Tony - G3SKR / AA2PM                  email: tgold@panix.com
                                                tgold@microvst.demon.co.uk
                                        packet: g3skr@n0ary.#nocal.ca.usa.na