triangle
Hi Adam,
triangle
This used to be a local hierarchy for the triangle area of NC (Raleigh
Durham chapel hill).
-- > (private)[...]
KA[...]
ULM
Adam H. Kerman schrieb:
-- > (private)[...]
KA[...]
ULM
Those are regional hierarchies for the cities of Karlsruhe and Ulm
(and the neighbouring areas).
ka.* has a peering policy demanding that each peer has to peer with a
"core site", but that policy has never really been enforced, and the >hierarchy is mostly available in the same way as any other regional >hierarchies. According to your specification, it's "regional" for all
intents and purposes.
ulm.* is a bit different; it's "private" as in "mostly [1] only
carried by news.in-ulm.de", so mostly fits the "private" description.
-thh
[1] Many servers seem to carry the groups, but I'm not sure if they
are really peering with the "home" server.
MICROSOFT (defunct)
Thank you. I'll take it off the institutional list. It's a defunct
regional hierarchy?
Thomas Hochstein <thh@thh.name> wrote:
Adam H. Kerman schrieb:
-- > (private)[...]
KA[...]
ULM
Those are regional hierarchies for the cities of Karlsruhe and Ulm
(and the neighbouring areas).
ka.* has a peering policy demanding that each peer has to peer with a
"core site", but that policy has never really been enforced, and the
hierarchy is mostly available in the same way as any other regional
hierarchies. According to your specification, it's "regional" for all
intents and purposes.
ulm.* is a bit different; it's "private" as in "mostly [1] only
carried by news.in-ulm.de", so mostly fits the "private" description.
-thh
[1] Many servers seem to carry the groups, but I'm not sure if they
are really peering with the "home" server.
Thank you. As no special permission is required, then they should not be listed as private. Regional sounds like a better designation.
Op 1-7-2021 om 20:49 schreef Adam H. Kerman:
Thomas Hochstein <thh@thh.name> wrote:
Adam H. Kerman schrieb:
-- > (private)[...]
KA[...]
ULM
Those are regional hierarchies for the cities of Karlsruhe and Ulm
(and the neighbouring areas).
ka.* has a peering policy demanding that each peer has to peer with a
"core site", but that policy has never really been enforced, and the
hierarchy is mostly available in the same way as any other regional
hierarchies. According to your specification, it's "regional" for all
intents and purposes.
ulm.* is a bit different; it's "private" as in "mostly [1] only
carried by news.in-ulm.de", so mostly fits the "private" description.
-thh
[1] Many servers seem to carry the groups, but I'm not sure if they
are really peering with the "home" server.
Thank you. As no special permission is required, then they should not be
listed as private. Regional sounds like a better designation.
12 ulm.* groups are available on eternal-september
8 of them are empty,
two *.misc groups with the last message in 2012 (going back to 2008)
and two *.test groups with only test messages in 2021.
So these 12 newsgroups are not alive...
No ulm.* groups on aioe and neodome
These three newsservers have no newsgroups of ka.*
I see a lot of regional hierarchies from Germany.
(bln.* = Berlin, hamburg.*, muenster.*, hannover.*. kassel.*, kiel.*,
muc.* = München, nrw.* = Nordrhein-Westfalen, rhein.*, ruhr.*,
saar.*, braunschweig.*, luebeck.*, wolfsburg.*, and so on).
But only a few newsgroups are alive (I haven't checked them all).
The only newsgroup I follow is bln.verkehr, because there are
also messages about trains and other public transport.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 293 |
Nodes: | 16 (2 / 14) |
Uptime: | 232:36:04 |
Calls: | 6,624 |
Files: | 12,171 |
Messages: | 5,319,537 |