Oddly enough, I was just thinking about that. I'm working on buying a house with a pool, and the pool house (the pump room) seems to be the best place for my servers anyway. Was just pondering if there was an easy way to sink the heat from the servers into the water pool water lines =P Course I know nothing about how to approach said project, so they'll probably just be air cooled with some fans.

Has anyone verified that this microcode update actually fixes the issue in question?

Only way I figured out it was X.org is clicking the link.

I just think of the bible as a book explaining things that are to people who don't have the foundation of knowledge to understand things at a higher level. Sort of like how we'd explain Linux to the average Windows user. I am not very religious, but I have a fascination with religion and make it a point to visit as many denomination's services as allowed without lying to them about my beliefs. It's very interesting to see how everyone interprets things differently.

Stop suggesting they save their DRM cash and lower prices. We all know this won't happen. Prices are set to what the market will bear, this has little to do with how much it costs to produce things. I would be happy to see the DRM removed, and the prices stay the same. Let them keep the cash of their failing product, and instead invest it in the next new thing. It sounds like the Cash Cow phase of this product is going to be shorter than some, it's time to cut your losses, and just make the maximum amount of money possible from the technology.

While it's possible to find one device that supports multiple carriers, it generally only supports one carrier well due to frequency differences. If you're looking for a device that'll work with multiple carriers, look for "unlocked". I'm not entirely sure there is a way to unlock the mifi things.

3M SelfCheck System (BCS-Series) is what I've seen some libraries use. May not fit your situation cost wise, and definitally isn't FOSS.

The difference here, is if this is like any other beta, you signed a non-disclosure agreement when you were handed beta. While you may not care about that, reputable news sources generally don't break those kinds of things, because they will get sued for it. That's if they even agreed to it in the first place, which I doubt any did.

While that might work for bank logins or sites you visit regularly, but for normal e-commerce, that tactic is useless. You have to be able to quickly decide if you trust that this site is who they say they are (if you're smart, you look at the cert, where at least some validation took place), so that if there is a problem, you can at least identify who the culprit was. If I'm doing business with Amazon for the first time, I need to know that I'm talking with Amazon, not some proxy setup at my ISP to collect credit card info. I know based on the name their reputable, but I may only order there once a year, at which time there should be a new certificate each time I go.

No it doesn't, with ssh you're generally not logging into a system and expecting to trust the security of a system based on it's name. SSH trust is based on have you been there before, and it having the same identity as before.

I remember the days when Perl was considered the language that attracted the crappy coders. Oh the security wonders I went through back with those CGI form mailers. I don't use Linux on my desktop because it attracts less idiots, I use Linux on my desktop because I like how it works. I use PHP in most websites because it's cheap to host, C or Python in desktop applications (C because I can code it extremely light on memory, Python because it has excellent support for gui libraries), and Java for certain enterprise pieces of my applications. Use a programming language because it's strengths fit your project and team, not because there are idiots who code with it. I hope you filter out the idiots long before you program it, or no matter the language, you'll have issues.