It does. When Grrl Power’s author put a link to Superbitch, everybody going there and archive diving caused her server to bog down and crash. A denial-of-service attack with legitimate traffic. This case is not as severe (sadly, a lot less of us – get the word out, vote on TWC!), but it can still be overwhelming.
While websites certainly do struggle under unusually high loads, I would not consider error 500 a likely result. On the other hand, in software everything is possible – especially weird bugs. But when also given that an immediate press of the refresh button generally makes the error go away I’m fairly sure it is not related to load, at least not closely enough to be a clue as to what the problem is.
I could be wrong though. I’m like 80% sure, I may know computers but I haven’t tried webservers yet.
Yay! It is soo good to binge reading this! But the 500 is showing up more frequently now…
Looks like we’re at the half way point here,hopefully the current comic arc will be reloaded soon.
I’m hoping the rest of Lock(e)down next week, then all of Things That Matter… then away we go!
I did not notice the bug on Brainspike’s back before. Nice touch.
I didn’t notice until you pointed it out! Very nice, stealthy surprises in the art!
Okay, its good to refresh my memory of the comic, but the server’s struggling to keep up; the constant 500 errors are definitely increasing
There usually aren’t so many people all going through the archives at once.
I dunno enough about how computers work to say so for sure, but that seems like something that could cause strain.
It does. When Grrl Power’s author put a link to Superbitch, everybody going there and archive diving caused her server to bog down and crash. A denial-of-service attack with legitimate traffic. This case is not as severe (sadly, a lot less of us – get the word out, vote on TWC!), but it can still be overwhelming.
While websites certainly do struggle under unusually high loads, I would not consider error 500 a likely result. On the other hand, in software everything is possible – especially weird bugs. But when also given that an immediate press of the refresh button generally makes the error go away I’m fairly sure it is not related to load, at least not closely enough to be a clue as to what the problem is.
I could be wrong though. I’m like 80% sure, I may know computers but I haven’t tried webservers yet.
Wow…was this comic really 4 years ago? It certainly doesn’t seem that long..
And then your comment was another 3 years ago . . .
…
COME BACK, MY YOUTH! I’m not ready to be this old yet!