🚀 go-pugleaf

jtbell@cs1.presby.edu (Jon Bell) writes:

> How about this:  in addition to the above, convert the current can.* (for
> example) to can.natl.* or something like that; i.e. put all the existing
> "national" can.* groups in a sub-hierarchy of can.  That way, sites that
> currently get can.* can simply switch to can.natl.*, and not receive any
> of the local sub-hierarchies.

in some ways, that _does_ look cleanest -- at every hiearchy, where you
have n _geographical_ options, you put n+1 _newsgroup_ options -- one
for each geographical unit (province/territory, city) and one that covers
them all.

can.misc.general, can.misc.politics
can.ab.misc.general, can.ab.misc.politics
can.ab.edm.general, can.ab.edm.politics

but who would accept them?  we're not being flooded with random
crossposts to edm.general (well, not often) -- if we were uw.*
we might have more incentive.

not to _mention_ changing it to ca.ab.edm.* -- to _much_ more closely
resemble the FQDN structure.

of course, California would have to move first.  us.ca.ba.sbay.waffle
-- 
Russell Schulz  russell@alpha3.ersys.edmonton.ab.ca  ersys!rschulz  Shad 86c