Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ability to revert rules. #5

Open
revident opened this issue Nov 16, 2016 · 2 comments
Open

Ability to revert rules. #5

revident opened this issue Nov 16, 2016 · 2 comments

Comments

@revident
Copy link

revident commented Nov 16, 2016

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.

  1. Registry Keys
  2. Windows Services
  3. 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.

@devio
Copy link
Member

devio commented Nov 24, 2016

Today i pushed a new release that implements backup/restore for being able to revert all changes that have been made. This is the first step into the direction you mentioned above, though. Next goal is to have the possibility to selectively revert changes and disable rules/group of rules. I'm working on it, but it will probably take some time due to regular business... :)

@ygorlazaro
Copy link

@devio Nice, but this is gonna work with someone who used the previous version?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants