That post rendered in DejaVu Sans Mono for me too, because I don't have Courier New installed. (I missed the "over1ook", though, because although the 1 and l in DejaVu Sans Mono look very different, the 1 is passable as an l, even if the l isn't passable as a 1.)

Watts are the right unit to measure power.

What we really want to know, though, is how many joules of energy they wasted

The more sensible fix would be to charge Microsoft for a certain minimum amount of energy use regardless of how much was actually used, rather than making them actually burn the energy in order to keep costs down.

Doing the hash on the browser is mostly pointless, because then people can log in merely with the hash, rather than with the actual password. So you aren't making your own site any more secure. (You are making other people's sites more secure indirectly, though, because people using the same password at multiple sites won't be compromised at those sites if your site gets compromised.)

My workplace requires all computers used there to have anti-virus installed, which is why I have antivirus on this machine despite it running Linux. (It even found something, once: a decompression bomb that I was looking at for fun.)

Whenever I have something which naturally has a password prompt, but I want arbitrary people to be able to log in, I set the password equal to the username (especially as the username itself tends to be guessable). That's probably more common than using a default password like 123456.

Something similar to the summary happens to me occasionally (although it isn't obviously linked to suspend or lid closing).

I'm using a (custom-patched) Unity, so I fix the problem with control-alt-f1, log in, DISPLAY=:0 unity &. (The DISPLAY=:0 is required because most window managers don't know how to run in a terminal.) If you're using a different window manager, just swap out its name.)

You don't even lose any work, but all the windows do end up collapsing onto the same virtual desktop.

I'm not sure. I don't normally buy newspapers, but when I do, I often look for ones with an opposite bias to mine; it's more informative because it's easier to mentally allow for an opposite bias than for an agreeing bias.

For anyone interested reading this discussion, I may as well say what the proof actually is, because it's shorter than typical explanations of how easy it is.

Suppose there are only a finite number of prime numbers. That means you can produce a complete List Of All Primes. Multiply them all together, add 1. This number has no prime factors (by definition; none of the primes on our List Of All Primes divide into it), which means it must be prime itself, but it's way bigger than anything on the list so it can't be. This is a contradiction, so the assumption that there are only finitely many primes must be wrong.

(And indeed, this is used as a standard example of proof technique.)

Unlike OpenOffice.org, LibreOffice has been intentionally trying to reduce or remove Java dependencies. (I don't know whether it's because they're worried about Oracle too, or for some other reason, like "why would an office suite need Java anyway?".)

http://en.wikipedia.org/w/index.php?title=Main_Page&action=raw&ctype=text/plain
"You have chosen to open index.php which is a: text/x-wiki from: http://en.wikipedia.org/"

http://en.wikipedia.org/w/api.php?format=txt
"You have chosen to open api.php which is a: text/text from: http://en.wikipedia.org/"

It refuses to serve text/plain, even if you ask for it specifically. (Compare http://en.wikipedia.org/w/index.php?title=Main_Page&action=raw&ctype=text/css, which it'll serve quite happily.)

After seeing a demonstration of a successful XSS attack on a plaintext file (IE7 was the offending browser, incidentally), I find it hard to see what sort of validation could possibly help. After all, the offending code was a perfectly valid ASCII plain text file that didn't even look particularly like HTML, but happened to contain a few HTML tags. (Incidentally, for this reason, Wikipedia refuses to serve user-entered content as text/plain; it uses text/css instead, because it happens to render the same on all major browsers and doesn't have bizarre security issues with IE.)

Presumably, just because the sides asked for one.

It's just a mistake in genkernel's timeline. 2K is one of the alternating good releases; the bad release between it and XP is Windows ME, which genkernel seems to have edited out from his or her memory entirely. (And it's pretty universally considered to be absolutely awful.)

Meanwhile, Toshiba put the information about the existence of the Microsoft Tax and the fact that they didn't do refunds on the outside of the box, on a bright yellow label that was very visible, rather than hidden in an EULA or in small print. I was pretty impressed by that. (I'm in the UK, by the way, where there's some doubt about whether EULAs are enforceable unless they're shown pre-sale.)