OneAndOneIs2

Yup. 30,000 hits yesterday. And that's not counting the multitudes that couldn't even access the page because the server had melted.

And it was the same page that's been dugg at least 3 times before, so it's not like there was anything new.

So. Stuff it. I've blocked Digg. I did it the simple way: Through an .htaccess file.

B2evolution, which is what powers this blog, has a .htaccess file in its main directory. Your blog or website will quite likely have one too.

RewriteEngine on
# Options +FollowSymlinks
RewriteCond %{HTTP_REFERER} digg\.com [NC]
RewriteRule .* - [F]

So I put that little lot into it. And now, if you go to the digg page that caused all the trouble and try to follow the link, you'll get a 403 error.

If you try to access the web page directly, you'll get the page no problem. So a Digg user who really wants to get to the page can do so easily, but not with a simple click as was the case before. Hopefully, that'll be enough. If not, I'll set it up to redirect to a much less CPU-intensive page.

That says "Bugger off"