Keeping in mind they can't possibly have humans listening to all that, the only way to flag human-worthy content is voice recognition and transcription to plain text files. If you keep voice only on the 0.1% that are "likely" to be interesting, and simply voice-recognize the rest after a month and compress the plain text, the storage problem drops by orders of magnitude.

Nobody ever wants to go on strike, any more than employers want a lockout. It's the nuclear option, used as a last resort.

Oh, right, I thought that JavaScript sucked because I was under the impression that it was dynamically typed, allowed monkey-patching, had a lame set of numeric types, poor support for sequential I/O, etc., etc., etc. Oh, wait... those things are true? But Douglas Crockford says it's Lisp-y, so that gives us license to sweep all those problems under the rug.

You're a little behind the times, that stopped eighteen years ago when PWORA was passed and AFDC abolished.

These days slaves are made with "right to work" laws and strict limits on the extent of the safety net.

I gained my freedom this past February. YAY! Free at last! Free at last! Thank God almighty, I'm free at last!

Indeed, B&N is cheaper and ships faster and carries more books. And your public library is free.

And if you're going to buy a book, buy one of mine!

Don't piss on Javascript. Sure, the standard library is terrible and poor cross compatibility makes it impossible to do anything interesting in a browser without shims, but

Maybe it's just me, but I find this hilarious. "but"...

I dread being handed someone else's Javascript code. It's nearly always faster for me to refactor it than to try and resolve a subtle bug.

From what I read here on Slashdot, I thank the gods that I don't do Perl. And many of the complaints I read about PHP are surely valid, but I like it and use it anyway, and so far I have not shot myself in the foot.

If you're doing Javascript in Visual Studio, then you have no excuse not to check out TypeScript. Likewise, in IDEA, you should check out Scala.js. It's surprisingly mature for something that just got off the ground. Javascript needs to die.

My concern is how Google handles removing things accurately. This isn't the white pages-- there isn't some person assembling these indices. They've generated by learning algorithms, and those algorithms themselves misclassify information. So how do you get all of your references removed without inflicting collateral damage? What about people with the same name? Furthermore, how does Google know that requests are legitimate? You can imagine political candidates requesting that Google remove their opponents.

Whatever algorithm Google is using to do this, I think its details are in the public interest. I'd like to see them publish its details.

javascript:void(open('//web.archive.org/save/'+encodeURI(document.location)))

Using the above bookmarklet will archive the entire page in the Internet Archive immediately (timestamped by the Internet Archive). The Internet Archive crawler respects robots.txt, but it doesn't appear the Flickr robots.txt file will prevent you from using this method.

Remember when we had a Debian system on the biosciences mission? They scrubbed the whole mission after they were already in space due to a fuel-cell issue that I think turned out to be a faulty sensor, and flew the entire mission a second time.