🚀 go-pugleaf

In article <91267.113259DOUG@ysub.ysu.edu>, Doug Sewell <DOUG@ysub.ysu.edu>
writes:
>I receive 'biz' on my primary newsfeed via NNTP.
>
>I rarely receive anything in it, other than what's cross-posted
>to other hierarchies.
>
>If I 'nntpxfer' from several geographically-remote sites, I receive
>a completely different set of articles.
>
>I suspect the biz hierarchy's quite fragmented, distribution-wise.

I get a fair bit of stuff in biz.*. For instance, biz.dec (DEC press releases)
is fairly active. I suspect that the site that is feeding biz to you is not
itself receiving a feed (or the site feeding it, etc.) In other words, it is a
"local" problem. Of course, lots of those sorts of local problems would indicate
that the distribution is highly fragmented, but based on what I see, I think
there is a core distribution in place that is fairly solid (though you seem to
be disconnected from it).

If you have the stomach for it, you could send either a version or sendsys
message in biz.config to see what sites make up your subnet of biz, and see if
you can link that to the outside. Of course, if your subnet feeds out (but not
in), you'll get a mass of replies which will be basically useless, since they
won't identify the bounds of your subnet.

Based on the philosophy that problems should be solved by those who see them,
you could arrange a regular feed to your site from one of those hosts you did an
nntpxfer from, which would connect your subnet to theirs (and hopefully everyone
elses). Getting a hierarchy connected is much like getting a regional
distribution connected. One of those that I'm in is perennially disconnected,
the ks distribution. So it goes...
--
Terry Poot <tp@mccall.com>                   The McCall Pattern Company
(uucp: ...!rutgers!ksuvax1!deimos!mccall!tp) 615 McCall Road
(800)255-2762, in KS (913)776-4041           Manhattan, KS 66502, USA