Thread View: list.netnws-l
1 messages
1 total messages
Started by David Herron -- NonResident E-Ma...
Tue, 13 Feb 1990 15:03
Re: Unix folks unhappy about bit groups
Author: David Herron -- NonResident E-Ma...
Date: Tue, 13 Feb 1990 15:03
Date: Tue, 13 Feb 1990 15:03
54 lines
3247 bytes
3247 bytes
>> == Ed Vielmetti (sp?)
> == Laura Littleton <lrl@psuvm.psu.edu>
> >Another problem with the gatewaying as it's set up now is that
> >there doesn't seem to be a current list of all of the bit groups,
> >information on them, and where messages to the group need to be
> >sent to.
>
> I have a such a list. It is available from LISTSERV at PSUVM with
> GET NETNEWS MODERATO and GET NETNEWS DESCRIBE. I could post a checkgroups
> if that would help. I don't see anything in the RFC on how moderators
> should be listed in the checkgroups, though.
NNTP-people ... the NETNWS-L people have started talking about gatewaying
problems 'tween "us" and "them" because Erik contacted Laura recently.
Part of the problem with the co-existance of Usenet & the bit.all
sub-culture is that a lot of the Usenet practices simply are not
documented in the RFC. Instead they are passed around `verbally'.
Other pieces of the arcane lore of running Usenet are in Gene's
Postings which appear in various news.all groups.
But then the bit.all people have their own practices which aren't
well enough advertised ...
I suggest more interaction between the two groups. Neither group
fully understands what the other does .. I wish I had more time to help
improve the understanding on each side of the fence but I just don't.
BTW, Laura, "handling a Message-ID: properly" means
****NO**** mangling of the contents
and DO ****NOT**** lose the contents
You should treat the Message-ID: as a *string* whose contents are
inviolate and uninterpreted. Pass the Message-ID: along in any
instance of the message you are handling. Use it as a "key" for
finding the message in a database. Use it however you like. But do
not do anything to the contents -- that string is what should be used
to uniquely identify **THAT** message, if it were changed or lost then
that message is **NO**LONGER** identifiable as being itself.
--
<- David Herron; an MMDF guy <david@ms.uky.edu>
<- ska: David le casse\*' {rutgers,uunet}!ukma!david, david@UKMA.BITNET
<- Coming to a nameserver near you --SOON--: david@davids.mmdf.com
<- (until then, david%davids.mmdf.com@rutgers.edu will work)
--
<- David Herron; an MMDF guy <david@ms.uky.edu>
<- ska: David le casse\*' {rutgers,uunet}!ukma!david, david@UKMA.BITNET
<- Coming to a nameserver near you --SOON--: david@davids.mmdf.com
<- (until then, david%davids.mmdf.com@rutgers.edu will work)
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads