Ability to revert rules. #5
Description
For these Privacy Fixes, I feel there are three categories in which a 'fix' applies.
- Want
- Do Not Want
- Do Not Know
This issue is to examine the Third category. (The second is addressed in issue 1, and the app as a whole attempts to address the first).
For example, "Let apps access/control my Camera". This likely does what I think it does and makes the camera complete useless, but then I wouldn't be able to use google hangouts.
For a regular user, they may see Privacy == Good, run this software blindly and suddenly find that Privacy == Nuanced. Being left with no channel back, quickly sours the idea of privacy as being not worth the hassle.
As such, being able to test out, and revert rules as they are discovered to conflict with users specific needs is critical. It also let's them build up a mental understand of what each change entails.
For the benefit of others, and head off a whole lot of +1 replies, I will state that I understand this a rather complex request. Reverting some of these changes may not be as simple as running operation in reverse order, or binary on/off.
At this point I see 3 class of privacy changes.
- Registry Keys
- Windows Services
- Application Specific Configuration Tweaks
Class 1 and 2 are all that is currently in this application. For most cases I believe can be handled with a generic mechanism for saving and restoring specific original values at the time of change. Note that I say original values instead of default, as some of these may have already been changed, and reverting them to defaults would create a third state instead of returning to the first.
Class 3 can be horrible complex and specific and may simple be out of scope for this application.