Xref: utzoo news.admin:12327 news.software.b:6895 Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!crdgw1!rpi!tale From: tale@rpi.edu (David C Lawrence) Newsgroups: news.admin,news.software.b Subject: Cross-posting with moderated groups Message-ID: <6!=&*T_@rpi.edu> Date: 17 Feb 91 21:18:16 GMT References: <1991Feb14.031551.2993@ddsw1.MCS.COM> <40991@ucbvax.BERKELEY.EDU> <91371964@bfmny0.BFM.COM> Followup-To: news.software.b Organization: Rensselaer Polytechnic Institute Computer Science, Troy NY Lines: 28 Nntp-Posting-Host: cs.rpi.edu In article <91371964@bfmny0.BFM.COM> tneff@bfmny0.BFM.COM (Tom Neff) writes: Yet there are instances, such as my offered example of an announcement crossposted to ny.events (unmoderated) and comp.ai.whatever (assume moderated) where it might make sense to propagate two separate articles. First, because the newsgroup readerships are orthogonal although probably not mutually exclusive, Uh, hmm? If the article is truly appropriate for both groups, then, as you say, their readerships are probably not mutually exclusive. Many of those people who would want to see an AI conference announcement in ny.events are probably also reading comp.ai.whatever. Handling cross-posts by linking only one copy of an article everywhere it appears has always been, from the user side, for the benefit of the people who are reading more than one of the groups. and second, quite simply because the comp.ai.whatever, who could be a hermit in New Zealand, might not support a ny.* crossposting! When you can put forth evidence that there is some statistically meaningful set of moderators who really have this problem, then please let us know again and I would reconsider supporting your desire for change. Moderators at B News and C News sites should not have this problem. I can't speak knowingly of posting interfaces on other systems, but as long as sites support RFC 1036 handling of Newsgroups:, their software should not have a problem with unknown groups. -- (setq mail '("tale@rpi.edu" "uupsi!rpi!tale" "tale@rpitsmts.bitnet"))