>> a pref for everything. The more we have, the more conditional forks in
>> the code there are, and the greater its complexity and the greater the

   So you have to pick and choose which you have because, obviously, 
the other extreme of having NO prefs also won't work.  I'm just saying 
that the override ability here is one which should not be left out.

>increases its offensiveness.) But I'd rather have the salting always
>happen, than present users with an inevitably incomprehensible pref for
>it when they create a new profile.

   There isn't even a need for the user to be presented with a pref.  
There could be a simple change needed to a config file, which is 
documented but not presented in the GUI.  That way, only the people 
who really don't like it and are looking for a solution will see it.  
(Similar to the method of editing the prefs.js file to prevent popup 
windows.  That's not a UI pref, so it doesn't confuse anybody, but it 
is behaviour you can modify if you know how.)

      Jason.

Reply via email to