Feature Request: Remove Password Requirement to Enable Blocking

[OttScott]

It makes little sense to require a password in order to enable the service. In current form, a user would have to type in his password, potentially having to find it, or retrieve it from a password vault, in order to turn on the blocker.
I could potentially see some edge case where the current implementation would prevent pranks when a browser is left logged in. That aside, however, I would consider the default use case as:

1. User decides he/she needs to be uninterrupted
2. Clicks Distract-Me-Not
3. Clicks Enable

Attempting to Disable the blocker outside of schedule, or any configuration changes should continue to require a password.

[AXeL-dev]

Hum, i'm not sure to get what you mean 🤔, since the password is mainly there to protect your settings from being changed/accessed by someone else.

Actually, we have those too options (see the screenshots below), that let you bypass the password in some cases:

Still from what i understood, you're asking for a way to disable the password requirement in some other cases? like being able to enable/disable the extension without entering the password (even when pass-protection is enabled).

Edit: My bad.. you're only asking for a way to enable the extension without entering the password, the disable part should still ask for the password, right?

[AXeL-dev]

Actually, after thinking a little more about this, i'm wondering why not to add a "timer" mode:

Once you access the panel, you have a timer mode button, you click on it, you enter the amount of time for which you don't want to be disturbed, the timer starts counting & disallow you to disable the extension. Would that fit your needs?

Self-note: It would be interesting to add an option that displays a notification to the user once the timer ends.
Self-note 2: It would also be interesting to display a warning for the user, that the timer mode cannot be disabled until the session ends.
Self-note 3: Think to save the timer status somewhere in the local storage, to avoid bypassing it by restarting the browser (or would that be too much restricted? 🤔).

[OttScott]

Not quite what I mean. Say I'm sitting down to work on a project and I realize I'm getting distracted. I have ADHD so I have a password which makes it harder to turn off DMN impulsively. I sit down to work on my project and click the dimmed (off) DMN icon and am prompted to enter my password.

Then I have to open my password manager and find my password.

Now that I can unlock DMN, I can finally get in and turn on the don't distract me I'm hoping for.

What I'm suggesting is that password would only be required if DMN is Active or to open Config. Perhaps as you've designed it, changing modes would prompt also. But if it is not in block mode, please allow me to easily switch it on so I don't get distracted until I switch it on. 🤣

I do think your timer idea is also a great feature. You could enable timer and see the countdown (without password) from clicking the icon, but can't disable it or change config until you supply the password. Kind of like an 'Are you sure?' button...

[AXeL-dev]

How about this:

Edit: i made it optional for users that prefer to keep the previous behavior.

[OttScott]

Perfect!

[AXeL-dev]

Deployed in version 2.6.2 (might need to wait for few days until it gets published).