🚀 go-pugleaf

In article <rmal.814462873@gen-off-3> rmal@jet.uk (Richard Lucock) writes:
> 
> >One problem with sophisticated clients is that they are slow. In
> >most cases it is faster to copy all articles and remove crossposts
> >later.
> 
> It depends on how sophisticated the program structure is, I suppose. I
> can imagine a program that downloads a news header while a separate
> task is examining the previous header to decide whether to take the
> rest of the previous article. Then when the current header is
> finished, the transfer program can download the article from the
> previous header if required. This way the download task is busy all of
> the time, but unwanted article bodies are not transferred.

   The way I'd do it is even simpler to implement: use an XOVER command, which
gives a 'digest' of the articles in the group, including the Message-ID field.
Since Message-ID fields are unique in practice, any duplicated IDs must be
cross-posted articles.
   Of course, if your server isn't modern enough to support XOVER, you're
screwed anyway....

-- 
Jonathan Gapen (jagapen@students.wisc.edu)