@justheretoask yeah I agree - I have tried building this, and you need a way to disable it sometimes. At this stage, the main way we seem to confuse people is by adding hard-to-see toggles that people forget they turned on, and then they want to turn them off but don't know how to do it.
You'd be surprised, but because f.lux is running in the background, we have a dozen people who forgot they set a thing for every user who is really invested in controlling how the app works. For an example, lots of people get stuck with f.lux "disabled for Chrome" and don't know how to disable it. So I guess this has taught us a few rules about adding stateful features.
The simple way around this is that we should sweep up a bunch of persistent things like this and put them in a "pro" version (where the state is "complex" and you have to be kind of involved to undo it). But for the "main" f.lux here is how we think about it:
We will add a "demo" feature that resets automatically - on restart, or after a day - a lot of things are in this category
For every persistent feature/state: it has to be visible, and easy to turn off. you don't want a new user turning on a feature and then being frustrated about how to turn it off
Things you might need to turn off intermittently (even as an advanced user) might need a hotkey or some way to interact, and the space of global hotkeys is kind of limited - we do in fact reserve one for grayscale, so that's not an issue here
So I guess I have to say "f.lux pro" is probably something I must finish up - I have an internal version where I develop new features and try them in-house, it's just not shipping yet!
