Subject:
|
Re: careful planning with newsgroup names (was: De Bouwsteen club)
|
Newsgroups:
|
lugnet.admin.general
|
Date:
|
Sat, 14 Aug 1999 06:56:21 GMT
|
Viewed:
|
158 times
|
| |
|
|
In lugnet.admin.general, Larry Pieniazek <lar@voyager.net> writes:
> [...]
> Your point about names (that I cut away) is well taken but to my way of
> thinking renaming jambalaya now (not that anyone is suggesting it) from
> lugnet.market.jambalaya to lugnet.market.fredhead is not as big of a
> change as if you moved it somewhere else but kept it the same last name,
> such as going with lugnet.random.box.jambalaya. (terrible example...)
It would be about the same amount of both headspace and data-finagling with
the server to change it to either of those names, but yeah, it would be less
work for people using it in the case of the second name. (For anyone
dropping in: we're not considering renaming it, just making meta-talk.)
> Distingushed names have meaning because of all the components and the
> last component in a lot of ways is the least important. I would have
> found .loc.us.mi.grr if you had called it .loc.us.mi.gr instead but if
> you had moved it to .loc.furniturecities.gr then no.
.loc.furniturecities.* => LOL! :)
How about:
.loc.coldcities.msp
.loc.hotcities.dfw
.loc.watercities.chi
;-)
> Do you see what I am driving at? You are (correctly) agonizing over
> whether lugnet.trains should become lugnet.lego.town.trains (well, not
> exactly) to organize it correctly. That has a comparatively huge impact.
> changing the name lugnet.trains to lugnet.train would not (except for
> all those articles you'd have to finagle, but that's data, not headspace)
Yup, grok. :)s
--Todd
|
|
Message is in Reply To:
2 Messages in This Thread:
  
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
