= 27d567bc2d48d9f40e9ccc20ea370b15)
wedrifid 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.
For which versions of Windows does this happen? I'm running Windows XP and I also use my hosts file to block time-wasting websites, but I don't ever get any warnings when I edit my hosts file in Notepad. This makes the hosts file not so inconvenient, because all you have to do is (Windows key) + R > type in "cmd" and hit enter, and in command line type: "edit c:\windows\system32\drivers\etc\hosts" and you're done.
This can be done in about 15 seconds, unfortunately, and having the line "#127.0.0.1 www.facebook.com" in my current hosts file is a testament to that fact ("#" comments everything out after it on that line).
I've actually got mine pinned on the taskbar. ;)
Useful for web development... I redirect to my linux VM.