Surprising, because I'd totally forgotten about it and really wanted to see what this was all about (after reading some of the comments here).
So I thought to myself 'ok, this once' knowing I'd be sticking my head out. It took me a minute or two to realize the cause and I thought that was a nice side-effect of solving this at the DNS layer, even when you're momentarily stupid this will still create enough of a barrier that you'll stop to think a bit longer.
I didn't know about the ghostery extension, so thanks to the person that posted that, that's another good solution.
FB has had its use for me (it found a bunch of long lost people), I haven't been back since.
i'm guessing that you actually have a bunch of other sites blocked in your hosts file, as well. on the assumption that you do, do you ever see any network performance issues related to this? i used to maintain a rather large hosts file for this purpose, but eventually gave it up because i suspected that it had started doing more harm than good.
Some of these hostnames are quite arcane to me (peace.facebook.com); did you get them from a list somewhere or did you identify each one of them yourself?
Good point. I'm pretty old school so the hosts file was my first line of defense. I didn't know about ghostery until this thread so that's installed now as well.
We'll see how my s.o. reacts to it, but on my machine it does absolutely nothing.
In case you're wondering what is in my hosts file:
A nice side-effect of this seems to be that the web has become a lot more responsive. No more 'like' buttons popping up all over the place.edit: regarding my s.o. it's been an interesting morning, this app seems to have opened her eyes to facebook in a different way. No more apps.