06-18-2018, 06:00 AM
I've been using FocusMe for a few months now, and I've run into a consistent problem. I do simulations and programming work for my job and, while I don't use Terminal too often in my day-to-day, I do need to have it available on a moment's notice. I certainly can't afford to have it locked away behind the stringent requirement that all my plans be inactive - at least not if I expect them to be at all useful.
The problem, of course, is that killing a process from the command line is super easy. That's something you definitely can't "fix" directly. What I think you could possibly do, however, is allow blocking of Terminal as part of a plan (as part of applications? or separately). Even just being able to pause Terminal blocking would be valuable for me.
Of course, if I allow myself any access to the Terminal at any point, I will be able to kill FocusMe regardless, but if anyone knows the value of artificially increasing complexity as a defense against procrastination, it's your team.
The problem, of course, is that killing a process from the command line is super easy. That's something you definitely can't "fix" directly. What I think you could possibly do, however, is allow blocking of Terminal as part of a plan (as part of applications? or separately). Even just being able to pause Terminal blocking would be valuable for me.
Of course, if I allow myself any access to the Terminal at any point, I will be able to kill FocusMe regardless, but if anyone knows the value of artificially increasing complexity as a defense against procrastination, it's your team.