I am intrigued by your statistics and wish to know of their sources.

Hiring 'hackers' is a media fiction - you wouldn't hire someone who was convicted of armed robbery to guard your local bank just because he was really good at it, would you? Hire a security professional who actually takes what they do for a living seriously, has credentials to prove it, and has a reputation for honesty and integrity they're not afraid to defend with references from previous employers and clients. Or contract the same. Or hire a consulting firm that specializes in security. A CISSP should be a minimum bar to get over.

Security is all about setting appropriate levels of trust on personnel. If you don't trust your security professionals (and by the way, the guy who sets up your firewall there should be one of them) then you can't trust the security they're putting in place. Audit the work they do. Trust, but verify. And for your size of network, you should have at least one full-time IT security person on staff.

And Cryptome is now saying that a Wired reporter contacted them after having spoken with a hacker claiming responsibility for the attack.

Which they responded to with a threat of a subpoena, and publishing news about it before the reporter, after they told the reporter they wouldn't? ... er. Way to burn bridges, guys? Seriously, I understand free speech and using reporters as sources, but I don't think reporters are going to be too gung-ho about reporting your findings later after this.

The TransX plugin can help you plan out the proper mission plan, too, with burn times, Delta-V requirements, et al. There's a bit of a learning curve involved, but nothing that taking a couple hours in the tutorials won't fix.

I don't think Orbiter models effects like solar sails or thermal thrust yet, though.

And here I am with an android phone that's running 1.5 because the vendor refuses to release any more updates for this 1-year old model of phone.

Oh, wait, that's right, I already rooted and upgraded to 2.2. Nevermind.

Same situation here - running a conference, needed to allow registrations by credit card. Our primary method of payment is Google Checkout. Main difference: A large percentage of our attendees insisted we support PayPal - so we have a PayPal account that we keep at a zero-dollar balance. When people send us money via PayPal, we immediately transfer it out of that account and to our bank. All of our actual money is held at our real, stable, brick-and-mortar bank.

For fear of precisely this reason. If I had enough support in our fanbase, I'd drop PayPal like a dead cat.

What he meant by 'not going to chase anyone out of their homes' is that we're not going to see sudden, dramatic raises in sea levels. If you think that people aren't capable of adapting to changes in their environment over a period of a hundred years, then, well... I guess I should break out my buggy whip.

Because of poorly written contracts. Most current contracts don't have a distinction between 'audiobook' and 'text-to-speech conversion'. If the authors don't defend their copyright on the text-to-speech conversion, it can be legally argued that they don't mind if the publisher has rights to produce audiobooks - or that they actually sold the right to the publisher in the first place, even if it wasn't explicitly stated in the contract. Considering that we're typically talking about significant amounts of money, that an author may have to live on for the next few years while they write their next work... yeah, it can hurt them, because the original contracts didn't take future technology into account.

I was looking for something like this last year - it looks like this just got released last month, so I don't feel too bad about not finding it.

It looks really interesting, but how accurate is it? I've got some old books that are falling apart I'd like to scan in and textify, but I'd like to know how much time I'm going to have to budget ahead of time fixing problems and proofing.

.... is pretty much DOA.

Speaking as a security professional, we could REALLY use multi-threaded support in our Snort deployments, and the last time I heard 'multi-threaded support is just around the corner' was in 2008.

Right now, the fact that one Snort instance runs as one process linked to one interface in your ethernet stack means that only one core can run it. And with us hitting the plateau in computing speed on a per-core basis, and traffic still increasing, multi-threaded support had better show up in the next couple of years at the latest or I'll have to find some other network-based IDS product, at least for some extreme instances.

No revenue stream now; no revenue stream until 2012.

This seems to be pretty much parallel to most of the business plans of dot-coms. "We have cool new technology! What, we also need sales?"

It really depends on how well they can market the roadsters... which they have not shown to be one of their strong suits yet. Time will tell. Opening day will not.