On Oct 20, 2010, at 22:04:58, Christopher Forsythe wrote: > Long and short of it, is I meant more along the lines of some kind of kill > switch.
I have been thinking of implementing an internal, hard-coded banlist. Any application on the list would be disabled by default when it registers. It would appear in the Growl prefpane (with the Enabled checkbox unchecked), so that the user could enable the application if they want. If the user enables the application, Growl adds its name to a list of banned applications so enabled. Ideally, we'd make it as difficult as possible for an application to add itself to the enabled list. Suggestions on this are welcome (but remember that it's impossible to fully solve, since there's no secure per-application storage and permissions are by user, so any process running under the same account Growl runs under can write to anything Growl can write to). This could only benefit on-purpose users, though (I mainly thought of it as an answer to applications like Adobe's that use Growl to display ads). The CS5 installer and Dropbox both install a old version (1.2), which wouldn't know about the banlist. -- You received this message because you are subscribed to the Google Groups "Growl Discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/growldiscuss?hl=en.
