Publishing headlines such as these typically get reactions that range from "Hell, no! We're still pirating up in dis!" to "I knew it! It's the pirate kiddies who're to blame for music industry losses". Does anyone ever wonder whether publishing numbers like these could be, for the RIAA and associates, a graceful way out of the anti-piracy business? As long as they can indicate that they have made an impact on the P2P music piracy going on they can then look the other way while reaping the word-of-mouth publicity benefits (and others) of this same P2P music piracy. Do you think they've learned from their ongoing 10 year old battle with the P2P industry?

is this even news?

Let me know if you get that bluetooth remote working. It's funky at best last I tried. I was even at the point where I started dabbling in bluetooth socket programming but realized it wasn't worth it after spending countless hours getting it to work. I ended up buying a microsoft mceusb2 remote with a usb receiver (and room to plugin to irblasters) and have been happy ever since.

controlling your TV might not be one of them. It typically uses your TV as an output device and that's the extent of control it has on it. You could look into using an irblaster in conjunction with your frontend to exert more control via scripts that can be tied to your remote control using lirc but that's something you'll have to build yourself. It's more common to use an irblaster for channel changing a cable box for which mythbackend already has support.

I'd say pick whatever TV works for you and ensure your frontend can handle decoding and playing full HD content. Add a universal remote to the mix and you have the makings of a killer mythfrontend. If you'll have a separate backend (which is what it seems like based on your description) you won't have to touch the backend at all.

While this is true, there's no reason that future input paradigms will conform to the ones you're used to.

So kind of like the optimus tactus? http://www.artlebedev.com/everything/optimus-tactus/

So... is this a good time to ask you to return your Man card?

And by code commenting skills AC doesn't mean add a comment for each line of code. In my experience good commenting would be to add a brief comment for each block of code. If you've written a particularly obscure one-liner or something that might also deserve a quote and perhaps a reference of where you picked it up but that should be rare: I hope you're writing functional and legible code before you start optimizing it.

So when *would* a linked list be more appropriate than a hash table?

Google's last foray into all-inclusive communications (Voice) resulted in lots of voicemails being made publicly searchable. I wonder if the same fate awaits all your documents. It hasn't happened for the documents that exist already on Google docs but what of the ones that are not created by Google docs and don't have the same rights data associated with them?

doesn't necessarily mean you should. This might just be a case of that. What's the usability of OSX on this? For that matter what about the resource hungry Vista and 7? XP was probably as far as it needed to go. That and perhaps Linux.

I've been using Ubuntu since 8.04 and have always upgraded using the "Upgrade" button without any issues. Upgrading to Karmic Koala was just as simple. I'm sure there's some crud left over from Jaunty but I did run apt-get autoremove so most of that should be gone.

George R. R. Martin as well. He's taking forever and a decade finishing a dance with dragons.

As an actual lazy slacker even I put in a little bit of work before asking my peers for help. That way I can maximize the benefit I get from asking my peers by making sure they don't give me the same answer I could get frmo Google. That just makes good sense. It also helps me determine who else is a lazy slacker :)

AVERAGE isn't the only archiving function you can use with rrdtool. For your purposes, you should create an additional RRA with an archiving function of MAX. http://oss.oetiker.ch/rrdtool/doc/rrdcreate.en.html#IRRA_CF_cf_arguments