What to do when servers are down...

[Jalathea]

...apply abberant aggression to all around...
...be bored enough to begin bloodshed...
...consume capricious amounts of chocolate...
...craft chants concerning charismatic coliseum-champions...
...do some daring deeds...
...flaunder furious and fuming files...
...fight the fury with fantasies of fabulous feats...
...imagine insane insects eating evil egamers...
...meditate about menacing measures...
...pray the punishment will pass...
...ramblingly retell the story of roaring raids ...
...sing silly songs...
...wrangle some wails (or was it: whales?) out of those waiting...
...

[Ghost_of_Ames]

I sat around thinking of ways to blame this on Shekka

[DoyleDD]

I sat around thinking of ways to blame this on Shekka

Bahahaha !

[Bj_Knows]

...play Space Miner: Space ORE Bust...
...discover the Bee jay sector of space...
...discover the remains of a future-generation AI laboratory that turned on its human creators...
...discover rumors the AI was called Superior. Heuristic. Electronic. Kinetic. Knowledge. Array. ...
...ask AI for its Inquisitor 1h rotation...

[_Raiden]

I sat around thinking of ways to blame this on Shekka

We can blame shekka for the servers too? Cool!

Well i still blame him for the fact that he got all justi nerf!

[dragondreamer]

I sat and twitched lol

[Shekka]

I sat around thinking of ways to blame this on Shekka

We can blame shekka for the servers too? Cool!

Well i still blame him for the fact that he got all justi nerf!

Sadly I can't control Amazon servers for reliability!

[Bbbb]

Sadly I can't control Amazon servers for reliability!

The official cause "According to Amazon, the trouble began Tuesday morning when an employee, who was conducting routine maintenance, mistakenly entered the wrong command while trying to take "a small number of servers" offline."

They didn't give out the name but I think we all know who it was!

[Gary_]

George Bush?

[Shekka]

Sadly I can't control Amazon servers for reliability!

The official cause "According to Amazon, the trouble began Tuesday morning when an employee, who was conducting routine maintenance, mistakenly entered the wrong command while trying to take "a small number of servers" offline."

They didn't give out the name but I think we all know who it was!