slowmover

For the purposes of this article, it is assumed the air-gapped computer is already running the malware, having been infected by some other means (ex. thumbdrive). The ultrasound communications provide a continuous (albeit slow) link between two infected computers.

It would be quite impressive, though, if a vulnerability in an audio driver allowed an uninfected computer to be infected simply by "hearing" the exploit sound!

What made you decide to leave?

Your link to Rosetta Code reminded me how much I love Inform. http://rosettacode.org/wiki/Towers_of_Hanoi#Inform_7

I would buy this in an instant if it had Android support. Are mobile devices on the roadmap?

Huh, first time I've seen this one, very interesting. Any idea what kind of volume they handle and whether or not they're profitable?

It just hangs on the "building your Hutt" page for me. Either it's swamped, or my company is blocking WebRTC somehow. Is there any way to verify WebRTC availability?

Specifically, there are both short-term and long-term disability insurances. Both pay some percentage of your base pay (often 60%-80%, or even 100% for short-term) at the time of the qualifying event. Short-term kicks in first, but eventually runs out and the long-term insurance kicks in. Long-term insurance often covers the individual to retirement age.

Take it from me, you really want to make sure you've got both, because shit happens.

Was this written in javascript directly, or compiled to javascript from another language?

The list of lists page[1] is a great place to dive in for a nice long Wikipedia binge.

[1]http://en.wikipedia.org/wiki/List_of_lists

I still score geek points when I demonstrate this function to other Emacs users. I wonder if the word list is still maintained. Last time I checked it was getting a little dated.

Also, please bring back M-x yow. (I know, copyright this and that, etc.)

Yet a Ruby-Throated Hummingbird can fly 450 miles (20 hours) nonstop over water when migrating, which I've always found amazing.

http://www.worldofhummingbirds.com/migration.php

Agreed, and clear won't help if you accidentally cat some binary code and put the terminal into "goofy symbols mode". In that case it's important to remember the reset command, especially if there's something vital running in that terminal and you can't just kill it.

But ctrl-r in bash starts a reverse history search, which is also very useful. It doesn't clear the screen, at least not the way it's configured on my linux machines.

See: http://www.talug.org/events/20030709/cmdline_history.html

This is way better than downloading a random executable and running it. (I assume you mean running it as root.) With this, you can grab the install script and see exactly what it uses root for. It only takes a couple minutes. You could even modify the install script to comply to whatever installation scheme you wanted, and probably even make a version that runs without root privs if you're willing to do a few things manually. This mechanism is WAY better than a binary executable installer.

As for the product, it looks really good to me. No mention of encryption of stored data in the privacy statement, which might be a concern for some.

Also it wouldn't hurt to make checksums available for the installer and downloaded tar, for more paranoid folks like me.

No, this technology is still far from a "bridge the gap" solution to paralysis that would return both function and sensation to the body below the SCI. Still, natural brain control of a robotic prosthesis is a [pun ahead] big step in the right direction.

>>I don't know how to say this delicately, so I won't: I'm having trouble distinguishing this book from the disjointed ramblings of a mad man. The RANDOM capitalization of VERY IMPORTANT WORDS!

Madmen do tend to emphasize random words: http://zippythepinhead.com/Merchant2/merchant.mv?Screen=PROD...

(M-x yow, how I miss you.)

Back in my heady startup days, I'd occasionally take my programmers to a local pub for afternoon chat and coding sessions. Code produced during these sessions often contained comments like:

  /* First pint begins here */

  /* Starting a second pint */

The idea being to keep track of code written during increasing states of inebriation. Interestingly, later analysis of that code showed no relationship between number of drinks and number of defects. (Of course none of us would ever get really smashed.)