First off, I fixed another issue with processing whitelists. So update for that if nothing else.
Second, up until now, you couldn’t blacklist or whitelist any preceding or trailing spaces around the search strings in your definitions files. These wrapping spaces were trimmed off of the string, so a careless space on its own line in the definitions didn’t trigger uninstalling every app with a space in it!! But now you can have wrapping spaces without this happening, as I have some additional error checking code in place for the the dangerous part..
So for example, now you can whitelist “hp ” with wrapping spaces (no quotes!) and it will probably never uninstall HP software, but it would not affect just anything with “HPinthename” only “HP ” (with a space on the end) would get flagged by the whitelist check.
Also up until now, you couldn’t have comments. These are now possible following the PIPE character | in your definitions. Example for “hp ” with the space on the end, when you add a comment it would look like “hp | this is printer software” or without a space on the end of the search string “toolbar| I don’t like toolbars” would flag just “toolbar” as the term and everything after the pipe is commented. Again, no double/wrapping quotes should be present in the defs I’m just including them here to clarify the example.
I know I know. Auto-updating functionality should follow soon.