Bet you didn't know that when you reduce child mortality rates, population growth rates actually go down, not up.

Nope, and it won't until more devices have solid video encoding support. The Android MediaRecorder is still limited to encoding from the camera only, and I'm not sure if any MediaCodecs can be made to encode from an OpenGL buffer.

You'll have to stick to DLNA (wouldn't it be nice if Chromecast supported that), or hope that Koush et al persist in their efforts. Or just pay $40 for a generic Android stick and run a DLNA server on that.

Agree completely. Personally I was really hoping for the Chromecast stick to support DLNA rendering robustly (and maybe it will yet be hacked to do so).

In the meantime, while I sincerely hope Koush continues his efforts, it's no surprise that his little workaround got broken. Might even be deliberate like he claims, but the API warning is right there in black & red.

Let's see what's possible after the API is finalised; Google may not be willing to throw the content gates too widely open, but they've always been hacker-friendly for the two-brain-cell market.

Why, were you planning to use only Koush's Cast app? There are other ways to stream local content which still work fine, like tab casting from Chrome.

It didn't break tab casting from Chrome at all.

If you read the original post, it only breaks Koush's Cast app for Android, which worked around the whitelisting restrictions to cast content directly.

Hmm, semi-open $35 dongle from Google, vs 100% proprietary $200 box from Microsoft. Is that really a choice?

Read Koush's actual post - the update breaks his Cast app for Android, which works around the app whitelisting to stream directly. Nothing says anywhere that casting arbitrary content from Chrome tabs is broken.

From the paper:

Range is improved a little with slower bit-rates, or in the presence of stronger ambient RF.

It's in a low-pressure tube.

It's in a low-pressure tube.

It's in a low-pressure tube.

It seems to me that you have absolutely NO idea about what the paper actually says.

I have a similar NFC tag in my car. And yeah, I could get Tasker to use non-data charging as a trigger instead, but I also do non-data charging by my bedside. And since I have a different bluetooth radio there and don't want GPS or max brightness, I use a second NFC tag for that with silent profile, no notification lights and screen dimming instead.

NFC isn't the answer to everything, but it's occasionally quite handy, such as sharing youtube or map links with a quick tap, no app required.

Actually, there is a possible hardware fix. Palmer Luckey has been looking into it for some time. But it's something that has to be treated with caution, for fairly obvious reasons.

Some people may take longer, two or three weeks or whatever - but if you're feeling more than just a touch of queasiness, you're overdoing it. It should be fun, not a burden. If you push yourself too hard and feel too nauseated while in VR, you might set up a mental association that'll take even longer to break. Relax and take your time to enjoy it in small doses.

Oh, and make sure your Rift is set up carefully, use the correct FoV and IPD settings, avoid any sudden movements, and it'll go a lot easier on you.

You'll quickly build up a tolerance, if my own experience, and others I've heard from, is any guide. Don't overdo it, just 10-15 minutes a day for a week or so and you'll be fine in no time.

Your wife may even find that a few more controlled sessions on the Rift actually improves her motion sickness in other contexts too. Some people have reported curing their own car sickness that way.

Or have them synced automatically and securely with BitTorrent Sync for Android.

Finding it hard to follow your train of thought, but if I understand you right...

There are multiple factors, not one "root cause". Orbital precession isn't enough by itself, but when combined with orbital eccentricity and obliquity AND favourable topology, then you get an ice age. That's why they don't occur at *every* orbital cycle - and why they can sometimes occur between cycles (e.g. if intense volcanism causes enough cooling to trigger an ice age by itself).

If you want a specific example, try this paper, which describes how, 116,000 years ago, a pattern of ice sheet formation and melting every few thousand years was triggered by the Bering Strait being shallow enough that whenever sea levels lowered sufficiently through ice formation, the Strait closed, which changed the salinity mixing of the Pacific and Atlantic oceans. This intensified the Atlantic's meridional current, which warmed parts of Greenland and North America sufficiently to melt enough ice to re-open the Strait - and the pattern repeated.

This pattern was eventually broken 34,000 years ago when (yes) we reached a point in our orbital cycle that kept temperatures cool enough, and the Strait closed long enough, to stabilise the climate, so that when it opened once more 10,000 years ago, the climate remained stable enough to allow our civilisation. So as you see, it's not so simple that there's a single "root cause" we can pin it on, but that doesn't mean we don't know what did it - we can see (and simulate) how multiple factors combined and interacted to result the ice ages we can see in the ice core record, which gives us a pretty solid explanation as to the causes of all the ice ages over the last 116,000 years.