Hacker News new | past | comments | ask | show | jobs | submit login

> One thing I do is put sites I want to spend less time on into my hosts file. That way I have to edit a file, which means leaving the context of my web browser, before I can access the site.

I use the LeeckBlock extension in Firefox. I have it set to block a bunch of sites 24/7. It has an override option; I have it set to override the block for 2 minutes when I activate it. As I'm typing these words, I have ~20 seconds left before HN is blocked again, so I'll probably have to override again before I submit this comment.

It adds enough friction that I don't spend as much time as I otherwise might on the blocked sites. I think the fact that it auto-blocks again helps over having to manually re-enable the block in a hosts file. Of course that could be automated.

It also has a bunch of related features that I don't use much, in case anyone is interested.

(Override, OK, reply)




Leechblock is good, but it's too easy to get around. I have several browsers installed since I do web dev, so it's an easy matter to just open a different one, or use private browsing, or disable the extension.


Well sure; but isn't editing the hosts file easy as well? Unless you lock yourself out of root and would have to boot from a live image. :D

LeechBlock has been enough for me, because I mostly just need a reminder to get in the way of my autopilot, not something that strongly prevents access. If my autopilot gets smarter, I can turn up the friction. LeechBlock has an option that requires you to enter a password to override it or get into the settings; either a user-specified password, or even worse/better, a 32/64/128 character random password.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: