Happened a few times today (tonight for you yanks).

Been happening all day for me

Me too. I thought it was because I'm a neolib.

Same for me minutes ago-had to re-submit a post after a refresh.

The sift hasn't been running so well recently. Maybe it's time for another fundraiser...?

Comment hidden because you are ignoring dag. (show it anyway)

We may be having some server issues ... we're looking into it.

>> ^dag:
We may be having some server issues ... we're looking into it.


I saw it again on the home page about five minutes ago.

I blame the Military-Industrial Complex.

Again a few minutes ago!

It's probably all the socialism.

And another one a few minutes ago.

Yeah it's been happening to me fairly regularly over the last 2-3 days. You usually know it's about to happen as when you click a link, it proceeds to take a while before displaying the error.

We've discovered it appears to be thanks to Googlebot. It seems angry and out to destroy Siftbot for some reason.

It's been hitting old sifty from many dozens of different IP addresses repeatedly every second and every once in a while siftbot gets knocked down for a minute and that's when the dreaded "An internal server error occurred" message appears.

We're not sure of the reason or exactly how to stop Googlebot at the moment, but we're working on it. If any electro-whiz gurus have any ideas, feel free to toss them in our direction.

So it's a fucking bot-war then!?! I say we retaliate with everything we have.

What do we have?

>> ^lucky760:
We've discovered it appears to be thanks to Googlebot. It seems angry and out to destroy Siftbot for some reason.
It's been hitting old sifty from many dozens of different IP addresses repeatedly every second and every once in a while siftbot gets knocked down for a minute and that's when the dreaded "An internal server error occurred" message appears.
We're not sure of the reason or exactly how to stop Googlebot at the moment, but we're working on it. If any electro-whiz gurus have any ideas, feel free to toss them in our direction.


Robots.txt but then VS won't be indexed. Can you contact Googlebot about this issue?

Us. DDoS!

Turns out it was a combination of several factors, but the bottom line is it should be behind us now.

until next time.

>> ^lucky760:
Turns out it was a combination of several factors, but the bottom line is it should be behind us now.
until next time.


Aww. I wanted a war against Google.

Good thing you got it fixed, lucky. Here's to ya. *drinks malt liquor*

Well, robots.txt doesn't mean Google won't crawl VS, ant, it just lets you define stuff for it not to scan, etc.

A better way to go at Googlebot is through the Webmaster Tools that let you define how often Googlebot will scan your site, and also submit sitemaps, etc.