By all means ignore IE6 compatibility and even display messages informing your users that things probably won't work quite right. But intentionally shutting them out is just silly.

I agree about not shutting IE6 users out though. If broken rendering and warning messages aren't enough to get them to upgrade, blocking them from the site isn't going to accomplish anything except reducing the number of visitors to your site.

http://i.imgur.com/MvmB9.png

http://i.imgur.com/pdyqV.png

I think it's tasteful on your alphabet clock. But it bothers me on the cooking blog. For instance, I'm at work. I'm excited, because I'm going to get a recipe from chocochichi.com and pick up ingredients on the way home. But because work has very old computers, the site is blocked! I become sad and stop by McDonalds on the way home.

AlphabetClock: http://imgur.com/92qW4.png

Chocochichi: http://imgur.com/O5rNv.png

and don't do anything else for compatibility, then put a little notice. They probably won't pay attention either way, but you won't be needlessly cutting people off either.

And one day, I'll be visiting someone's house and remember a great chocolate recipe from your wife's blog, will sit down at a computer running IE6 and try to visit your site, and your messages will have me shouting "It's none of your business what browser this is, I didn't choose it; just show me the site so I can copy some text out. I don't care how badly rendered and mangled it is, that's my problem not yours. If you want to serve it up picture perfect then make it a freaking PDF, that's what PDF is there for, it's not what HTML is there for".