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

Use data to match functionality of StayFocusd and Freedom #126

Closed
ErikBjare opened this Issue Oct 26, 2017 · 2 comments

Comments

Projects
None yet
1 participant
@ErikBjare
Copy link
Member

ErikBjare commented Oct 26, 2017

It's a neat idea, but StayFocusd does it so well that it should hardly be a priority. I'm just creating this issue so that we have one. I've been thinking about it for a long time.

@ErikBjare

This comment has been minimized.

Copy link
Member

ErikBjare commented Oct 27, 2017

One issue I have with StayFocusd is that it's all or nothing. Sometimes I need to check e.g. Facebook during the day, or want to take a short break. StayFocusd is great and all, but perhaps there is a middle way?

An idea

Instead of blocking all blacklisted sites once a timer runs out, we give ourselves a timelimit before opening such a site. What we really want with things like StayFocusd is to get in control of time, not to limit what we can do with it. By nudging the user to estimate how much time they plan to spend on a site before they do, we help them adopt better behavior.

ActivityWatch data isn't needed for something like this, but it can be of great help. An example would be that whenever you open a blacklisted site you'd first get shown how much time you've already spent there during the past day. With that figure, the user would become aware of the time already spent there the past day/week/month/year. With that in mind we can learn when we need to restrain ourselves. and be a better judge of how much additional time, if any, we should let ourselves spend there for our intended visit.

@ErikBjare

This comment has been minimized.

@ErikBjare ErikBjare closed this Nov 6, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment