= 27d567bc2d48d9f40e9ccc20ea370b15)
rhollerith_dot_com comments on Anti-akrasia remote monitoring experiment - Less Wrong
You are viewing a comment permalink. View the original post to see all comments and the full post content.
= 783df68a0f980790206b9ea87794c5b6)
Loading…= b715d02e85f7b3b4ae65ca3d3e450868)
Subscribe to RSS Feed
Powered by Reddit
= f037147d6e6c911a85753b9abdedda8d)
You are viewing a comment permalink. View the original post to see all comments and the full post content.
Comments (114)
Here's a recipe for a bigger trivial inconvenience. If you're running Windows, you can edit the WINDOWS/SYSTEM32/DRIVERS/ETC/hosts file to include some lines like this:
This way, the domains you listed will force-resolve to 127.0.0.1 (a.k.a. localhost). Once done, this will introduce a pretty big trivial inconvenience between you and your favorite timesinks -- hosts is a system file, so you'll have to deal with OS warnings and prompts every time you want to edit it.
Oh, I've been doing that for years.
To increase the size of the obstacle it represents, I once modified the command I am in the habit of using to open files for editing so that any request to open /etc/hosts got changed to a request to open the file containing my to-do list.
But the next time it wanted to go to one of the sites on my blocklist, it took my brain about 5 seconds to realize that if it requested the opening of /:/etc/hosts (the /: being a quoting convention in Emacs) rather than /etc/hosts, it could get around my obstacle.
Some small software changes have proved effective obstacles for months, but the above was not one of them.
I will continue to maintain a blocklist in /etc/hosts because it causes my brain to observe my policy on work and procrastination more than it would without it, but the reason I am involved in remote-monitoring experiments is because it is a more powerful anti-akrasia technique.