Thank you for your suggestions. I'm not planning architectural changes to leafnode-1.X.Y.
Your assertion that local users cannot post is false, the postings are unaffected, but will only appear after the next fetchnews run. This is a deliberate design decision and allows leafnode-1 to work without the slightest clue of which groups are moderated and which aren't. Leafnode-2 should lend itself more to such changes as you suggest, but I'm not sure if this will find its way into Debian as a separate package, and I'm not inclined to fix leafnode-2 in order to support binary group, as long as high-traffic/high-volume text groups work well; leafnode is not designed in situations where fetchnews takes more than a day to run, and I am willing to carry this shortcoming on into future versions, as fixing this requires a major effort. Leafnode-1 is not meant to be a binary server and is not very good at handling binary groups, in that it has no optimization for large numbers of articles or articles with large bodies, and tosses everything through several places in userspace, rather than storing articles in "wire format" and using sendfile(). Besides that, my sympathy for abusing NNTP to transport binaries is near zero. There are other protocols that are suited better to transport binaries, among them HTTP/1.1, FTP, SFTP, BitTorrent, Gnutella, to name the first that come to mind. Consider this a "wontfix". -- Matthias Andree -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
