From: Luke S. <lsc...@us...> - 2005-03-02 19:11:18
|
On Wed, Mar 02, 2005 at 01:44:30PM -0500, Ethan Blanton wrote: > Accounts should default to "Allow All" at creation (I don't think anyone > can reasonably disagree with this), and only subsequent manipulations > will cause this to change. Set management and closure is a relatively > well understood topic in Computer Science, I'm sure we can work this > out. ;-) exactly, I did not mean to imply there was any question about at what state we should *start* on account creation. > > I don't think we'll be able to get around having a _few_ knobs to tweak > (for example, some people will want a "Block All" button), but I agree > completely with Sean that users should not have to decide what set oper- > ations to apply to their privacy preferences, Gaim should Just Handle > It. This is what computers are for. you highlighted the question I intended to be asking here nicely, some people will want a "block all," we need to add something to the UI to handle that, and, having blocked all, some way to return from it to "allow all" or "deny below" (which correspond to each other) we should further remember the "deny below" list even when "block all" or "allow below" (which also correspond) are active, to allow for seemless migration back and forth from these basic policies. luke > > Ethan > > -- > The laws that forbid the carrying of arms are laws [that have no remedy > for evils]. They disarm only those who are neither inclined nor > determined to commit crimes. > -- Cesare Beccaria, "On Crimes and Punishments", 1764 |