frognibble

The server is running on EC2. As far as I can tell, EC2 does not have a virtual console interface or any other way to rescue a server that blocks all network connections with a firewall.

There's something to be said for relatively simple tool like make. It can be a lot easier to understand what's going on with Make because it eliminates the layers of stuff between the build script and the actual commands that are run. That's not to say that it's possible to write inscrutable Makefiles.

I recommend the book "Parasite Rex" by Carl Zimmer for those who are fascinated by this sort of thing. The book discusses several interesting and creepy parasites.

I heard that acquisitions often involve a merger with a shell company because of a tax or liability advantage. I searched for info on this, but couldn't find anything. Can somebody please comment on how this works?

What part of lzw's logic is twisted?

It is not obvious that the bulk of the resources come from the idled workers. Resources are needed to pay the workers. Resources are needed to buy the steel, concreate and other materials used in the projects.

It is also an error to assume that disallowing GET for updates adds any security. I recommend reading about cross site request forgery. CSRF is the type of attack used on Twitter today.

Seriously. Search the web for documents on "cross site request forgery". Most of the documents discuss the POST issue. Some documents don't mention GET because GET should not be used when the request has side effects.

The resources used in the stimulus come from someplace in the economy. The resources do not magically appear out of thin air when the Fed buys government debt.

No, it's not entirely the fault of GET. The browser does not prevent script from triggering POSTs to third party sites.