That would stop mashup services from working easily, for example embedded maps, which I work on: openspace

You are not being bayesian enough.

You need the probability someone is telling the truth given the evidence of being dumb enough to say "I've got a bomb".

If the Hypothesis is 'got a bomb' and the Evidence is 'said bomb', here are my estimates:

p(E) = 10**-7 proportion of travellers who are dumb enough to say bomb (one in ten million)
p(H) = 10**-13 proportion of travellers who have had a bomb so far (one in ten million million)
p(E|H) = well, ZERO so far, but let's say 10**-3 bombers who mention the word bomb (one in a thousand)

Then p(H|E) = proportion of people who say bomb who have a bomb = P(H) * P(E|H) / P(E) = 10**(-13-3+7) = 10**-9

One in one billion people who mention the word bomb will have a bomb.

So if we close the airport each time for two hours, our losses for an actual bomb need to exceed the damages for closing an airport for two billion hours before it is worth it. That's over 200,000 lifetimes of waiting in the departure lounge.

Just.

Any comments on my maths / approach happily received.

That theory (alcohol in the morning for 'withdrawal') is completely wrong. The chemistry is well known.

Hangovers are partially caused by dehydrogenation of alcohols leading to poisonous chemicals. Ethyl alcohol turns to acetaldehyde, but we can deal with this one (thank you evolution).

Methyl alcohol (wood alcohol impurities, present in most drinks to greater or lesser degree) turns to formaldehyde. This is very bad for you and makes you feel like hell. The process of creating formaldehyde is linear (because the total present must be limited due to toxicity), not power based, so there is never too much made unless the amount of methyl alcohol is even more toxic.

However, the conversion process is negatively catalysed (slowed down) in the presence of ethyl alcohol. So, a little beer can reduce the amount present enough to effectively remove the hangover.

Sorry about too many brackets (not really sorry).

Just.

I used to do this with a friend: peered ftp servers. Everything under /home and /etc was tarred, zipped, encrypted and ftp'd onto his server at midnight, while his did the same to mine. Can't remember where I put the decrypt key, probably on a floppy that is still in my bureau.

Of course, data volumes were lower then, and the sun was warmer, and girls prettier.

Just.

If he was in a coma, I'd think that'd be the part he missed.

Looks like they added Ethernet. Doesn't say what speed, though.

You still can. Just use proper cable hiding tools and techniques. Like whatever they use to make power cables running across floors OSHA-safe. :)

My chief complaint was that in the original announcement, they were only going to support wifi for networking, yet it was supposed to be useful for gaming and streaming video.

The problem is that wifi is terrible for both of those use cases. It's bad on its own for latency purposes, and then there's spectrum contention. I raised these points in response to their Kickstarter drive, and it looks like they turned around and added those features. If I'd known they would, I would have donated on the Kickstarter.

Then they added both my suggestions. Rock on!

I'll definitely have to get one, now.

When their Kickstarter began, I sent them a message (along with many other folks, I'm sure) that it needed _some_ means of getting a wired internet connection and/or access to by-wire accessories. USB was one of the possibilities I offered.

Now devs for Ouya can turn around and leverage that USB port to allow the Ouya device to latch on to a PC's network connection. Excellent.

(Page doesn't seem to show if it's USB2 or 3. At this point, I sure hope it's USB 3...)

And now we're back to a familiar analogy: "The door was open, so anything inside should have been mine to take!"