John said:
That is certainly not my (and many others, I'm sure) understanding of
the Usenet network. It may have been a star network in the very early
days but it is now, and has for quite a while been described as a mesh
network.
Ok, first, the microsoft.public.* newsgroups are not usenet.
Second, call it what it want, it is still the same thing. A mesh is
just a form of a star network.
No matter what you can wish to call it, it requires coordination and
each node knowing who are their Uplinks and Downlinks which is what
experts in the mail distribution market, who still run the show, know
it as. Otherwise you will have redundancy (and hence duplicity).
An uplink is who you send data too, and downlink is who you get data from.
Now, in a mesh, redundancy may be part of the expectation with
duplicity considered a lower overhead operation then it was in other
days where hardware did did not allow for such low efficiency however
it still needed to be checked.
In a well coordinated network, to minimize duplicity, the nodes are
usually going to go to a more centralize hub (lets call it MAIN). If
the Nodes are going to also serve as HUBS for others, then they better
have dupe checking because they don't KNOW if their own nodes are also
using the MAIN hub.
In general, old and current, every node has a list of remote host they
will connect too to IMPORT and EXPORT information.
If you wish to see the PATH a messge takes from any server, see the
Path: header in a newsgroup article.
Viewing your message from the Microsoft NNTP server, I see:
Path: TK2MSFTNGP01.phx.gbl!TK2MSFTNGP06.phx.gbl
That means that it was posted at
TK2MSFTNGP06.phx.gbl
but it was also imported to:
TK2MSFTNGP01.phx.gbl
You can tell it was posted at TK2MSFTNGP06.phx.gbl because of the
message-ID: header:
Message-ID: <
[email protected]>
Now if I go to google groups and see your message from there, I see
(all one line)
Path: g2news1.google.com!
news1.google.com!
news.glorb.com!
feeder.erje.net!
weretis.net!
feeder1.news.weretis.net!
TK2MSFTNGP01.phx.gbl!
TK2MSFTNGP06.phx.gbl
Starting from the bottom, the feeder1.news.weretis.net! server it
pulled from Microsoft TK2MSFTNGP01.phx.gbl! and it was gated thru a
number of 5 additional servers.
Well, #1 once the MS servers goes down, Google will not be able to
pull from TK2MSFTNGP01.phx.gbl! It will have find some thing else.
#2, you won't have MS server to post, and if you found another, you
don't know if Google will be pulling from it or that your Serer will
be posting to GOOGLE.
So no matter want you wish to call it, there is is a "backbone"
concept where there is a main hub who is normally known as the OWNER
of the newsgroup.
In regards to USENET, this is different issue. This is in industry
sponsored backbone. Not one company ones it. Its like a DNS.
Everyone has it access to add and remove from it. As long as you have
have primary uplink you can act as a primary server as well.
Anyway, with usenet, long ago, we requested an alt.* group for usenet,
It still exist:
alt.bbs.wildcat
We abandoned it long ago around 1997 when it became a high volume of
spam for us and the anonymous dirt was not something we wanted to
bother with our customers with when it was gated into our support
avenues.
The only reason we had no problem abandoning it was because it wasn't
our NEWSGROUP. We were not the main hub for it.
Thats not the case here with Microsoft.* newsgroup. These are not
usenet groups. The main hub was Microsoft where others pulled from.
Now, if someone were to migrate all the microsoft.public.* groups into
usenet groups, then you and Jochen would be correct, it wouldn't
matter if the Microsoft NNTP servers goes down because they would be
just a node off the backbone, not the main hub for it.
Hey, who knows, Maybe Google's answer to this Microsoft dropping of
their NNTP server would be to announce their own services to be
available. But they don't want people off the web for the same reason
Microsoft wants people to use the web.