Subject:
|
Re: Todd, can we have an Arctic posting group?
|
Newsgroups:
|
lugnet.admin.general
|
Date:
|
Wed, 5 Jan 2000 13:48:14 GMT
|
Viewed:
|
2154 times
|
| |
| |
On Tue, 4 Jan 2000 18:30:56 GMT, lehman@javanet.com (Todd Lehman)
wrote:
> In lugnet.admin.general, mattdm@mattdm.org (Matthew Miller) writes:
> > Jasper Janssen <jasper@janssen.dynip.com> wrote:
> Hmmm, seems pretty messy to me, especially for deep hierarchies where there
> are many nested umbrealla groups. In that scenario, aren't you saying that
> if someone posted to lugnet.loc.us.ma.bos, the message would actually have
> to be crossposted (either automatically or manually) as this?--
>
> Newsgroups: lugnet.loc.us.ma.bos,lugnet.loc.us.ma,lugnet.loc.us,
> lugnet.loc,lugnet
I'd leave off the lugnet, but yeah, that's the idea. I'm still not
entirely convinced it wouldbe a good thing, though.
> It would also mean that anytime a group were split, it would have to die and
> be moved to a .general subgroup so that it could be reborn as an umbrella
> group. For practical reasons, it's extremely difficult (next to impossible
> in an automated way) to move messages out of a non-empty newsgroup and into
> a new one, and it's not reasonable simply to throw them away.
Hmm. Which would mean that you would have to create every single group
as a .general. Bad.
> The client side is really the appropriate place for that, IMHO. I wonder
> why the popular newsreaders don't have an option to coalesce groups down a
> hierarchy (or some set of specified groups). I've never seen that feature
> in a newsreader except in the LUGNET web interface.
I'd like it. Does slrn do it? ;)
>
> Alternatively, on the server side, an nntpd doesn't actually know (or care)
> what group an article _actually_ is in (as specified by it's 'Newsgroups:'
> header) when it transmits the article's header and body. Normally, they
> match, but they wouldn't have to. Thus a virtual group consisting of a
Good point.
> collection of other group's messages could actually contain hard or symbolic
> links to the article files in the other groups without even having to mess
> with crossposting. In other words, a group foo.bar could theoretically
> contain a collection of messages with Newsgroups headers like this:
>
> Newsgroups: foo.bar
> Newsgroups: foo.bar.bletch
> Newsgroups: foo.bar.blat
> Newsgroups: foo.bar.bletch
> Newsgroups: foo.bar.gork.splat
> etc.
>
> and when the client composes a reply, the reply actually goes into the
> proper groups (rather than into foo.bar) and then is echoed back into
> foo.bar as if it had actually appeared there. Some newsreaders may have
> problems with a layout like that, though, if they checked the newsgroup line
> against the current group that someone was in and gave an error if there was
> a mismatch.
How easu would it be for you to set up a test group on one of the test
ports containing, say, some of lugnet.general into
lugnet.off-topic.test.something?
Bets to get this out of the way for as many newsreaders as possible,
if we'd actually want this.
If it can be done, I think it'd be a great addition.
You still have to deal with non-follow-ups that get posted in the
umbrella groups, though. A rejection with a simple URL explaining the
problem would probably be best.
Jasper
|
|
Message has 1 Reply: | | Re: Todd, can we have an Arctic posting group?
|
| (...) I looked around a bit in the newsserver code last night and I was thinking of setting up a virtual newsgroup called _lugnet as a test case, and just filling it manually with some stuff, and seeing what happened with a few newsreaders. Before I (...) (25 years ago, 5-Jan-00, to lugnet.admin.general)
|
Message is in Reply To:
| | Re: Todd, can we have an Arctic posting group?
|
| (...) Hmmm, seems pretty messy to me, especially for deep hierarchies where there are many nested umbrealla groups. In that scenario, aren't you saying that if someone posted to lugnet.loc.us.ma.bos, the message would actually have to be crossposted (...) (25 years ago, 4-Jan-00, to lugnet.admin.general)
|
44 Messages in This Thread:
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|