At 11:28 AM 3/8/99 -0600, Jason L Tibbitts III wrote:
>Users of that site then go to other sites and use those aliases, which
>don't work. (But note that the supported aliases are part of the code;
>they aren't per-list or even to a specific virtual domain.) The idea is to
>not have a bunch of little Majordomos, all different, where you have to
>read the help file of every one at every different site to see what to do.
It's not my preference, but I can live with that as long as aliases are
added relatively liberally. (like you just did with 'sub' for 'subscribe')
The downside is that some site managers will add abbreviations as aliases
and the documentation won't address it - if we auto-abbreviate, then we
can spit out an error message pointing exactly what went wrong (as in
"you used a non-unique abbreviation"). If we only allow premeditated
abbreviation, and only implement the ones that everyone likes, there won't
be any useful message at the sites that do not have the extensions.
As I read your response, you are worried about the OTHER sites, not the
site that sticks in every possible abbreviation by modifying the %aliases
variable for their installation... and perhaps that is MORE likely to
happen if we don't automatically allow abbreviations. Time will tell.