Here is the "official" Mars One answer to bone issues (site seems to be down now so copy and paste from Google Cache):
Prolonged weightlessness causes osteoporosis, which can be reduced by exercise and medicine. Research onboard the International Space Station has led to even better and more effective training programs being drawn up, and new machines being made specifically for astronauts. Conjointly, there have been major leaps forward in medications capable of partially preventing declining calcium levels.

Recent study about 14 ISS astronauts, who were 4-6 month in space, showed a maximum bone loss of 1.5% / month in the most vulnerable (from bone loss point of view) region - the hip. Therefore the bone loss after arriving on Mars, after a 7 month flight, would be in the worst case scenario 10.5%.

When they arrive on a planet with 62% less gravity, they would have 100% more bone density compared to humans under earth gravity.

Google Cache link: http://webcache.googleusercontent.com/search?q=cache:YS4BxMBdYy4J:mars-one.com/en/faq-en/19-faq-health/193-will-the-astronauts-develop-osteoporosis+&cd=1&hl=en&ct=clnk&gl=au

Touches on the tendency for systems to be inherently more complex as time goes on http://www.ted.com/talks/david_christian_big_history.html

It may not be exactly what Gartner envisioned, but there's the RepRap project which aims to be able to fully self replicate. At least check it could print 50% of it's own parts, and they are working on being able to print electric circuitry next - http://www.reprapcentral.com/vmchk.html

Andy Rubin (Co-founder of Android before Google bought it, and current VP of Mobile) posted this a few months ago in relation to Aluyin OS. https://plus.google.com/112599748506977857728/posts/hRcCi5xgayg (which links to the official Android blog: http://officialandroid.blogspot.com.au/2012/09/the-benefits-importance-of-compatibility.html).

It sounds like this modification of the SDK might be another move toward Google defending against this Aluyin OS-style modification of Android. While Android is commonly cited as being "fragmented" due to the %'s of handsets that have older versions of Android on them (see the Development Dashboard); what these links talk about is a very serious, more dangerous style of fragmentation. Currently all Android apps are forward compatible with future versions and most are backward compatible (unless the develop chooses to use a new API and not include any graceful degradation in their app for older versions). But Google's flavor of Android is also sideways-compatible with the likes of Amazon such that if you write an app intended for the play store and later decide to distribute it to an Amazon-flavored device (via their app store or other various means), you can do this.

The implications of allowing such activities to continue are that Android could turn into a true wild-west of operating systems. From a technical standpoint, a budding Chinese developer modifies some core Android source code which work with the apps being developed by his company, but suddenly break every other app developed for their flavor of the Android OS -- and then suddenly developers for that hypothetical OS can no longer pick up their app and take it to Google's (/Amazon's) flavor of Android without resorting to hacks and workarounds. Suddenly that Android Development dashboard needs to represent that data in more than 2 dimensions - and Google's got a world of new problems to deal with.

See this Architecture Diagram for some further context. Basically the various Android OEM's and custom ROM developers such as Cyanogenmod should only really be modifying the blue bits and maybe some of the green (I'm sure ROM developers would argue on the red bits, but in a perfect world..). Seems like Google is trying to stop the messing with of the yellow "Android runtime" section.

Really, Android "copied" Apple's field of icons? I was using Nokia SmartPhones in 2006 which used the same style. Apple must have a time machine?

We agree that the Aliyun OS is not part of the Android ecosystem and you're under no requirement to be compatible.

However, the fact is, Aliyun uses the Android runtime, framework and tools. And your app store contains Android apps (including pirated Google apps). So there's really no disputing that Aliyun is based on the Android platform and takes advantage of all the hard work that's gone into that platform by the OHA.

So if you want to benefit from the Android ecosystem, then make the choice to be compatible. [It's] easy, free, and we'll even help you out. But if you don't want to be compatible, then don't expect help from OHA members that are all working to support and build a unified Android ecosystem.

Get yourself involved in some Corporate Performance Management stuff (specifically OLAP). This is the perfect intersection of IT and Business/Finance. Think Oracle Hyperion, IBM Cognos TM1, etc. Guys I work with (not me) are currently putting this stuff in at our clients - even the guys without the technical know-how (e.g. they still have finance/technical backgrounds but don't actually build it) have a role in navigating/deciphering and translating whatever bunch of Excel models and disparate systems into Functional Requirements, which get built into Multidimensional structures by the technical guys. I'd start by looking for companies that do this type of stuff - the role name could be anything from Solution Architect to Consultant. Good luck!

1. It would have to be cheap ($100-$150)
2. The screen should be touch.
3. Might the dock supplier need to be include their own Android launcher? Can't see the various different launchers and configurations all fitting perfectly. This would be a problem for people who want to take their phone home and use it but prefer their launcher of choice.
4. Google will have to get into gear for QuickOffice pretty quickly/merge it with Google Docs/pull together all the main bits of functionality missing from each program, make the blur between Google Drive and Google Docs less confusing and improve the overall user experience.
5. Docking/undocking: seamless, no funny business specific to certain handsets.

http://yro.slashdot.org/story/12/05/27/1917213/patent-troll-now-armed-with-thousands-of-nortel-patents?utm_source=feedburnerGoogle+International&utm_medium=feed&utm_campaign=Feed%3A+Slashdot%2Fslashdot+(Slashdot)&utm_content=Google+International

FYI Valve have dropped the "Defense of the Ancients" moniker and now more generically refer to it as Dota.

Perhaps Symantec are flagging it as malware because it is using permissions that the app clearly does not need, and it is just some rookie developer that has permission code copied in from some other site?

Since this article is about iiNet and people have been talking about SOPA, I thought it a good idea to post this article published on the official iiNet blog yesterday about SOPA: http://blog.iinet.net.au/sopa-internet-censorship-effort-beginning/

I agree with your notion for Wave - put out too early, cancelled way too early.

Australia is one of the least densely populated countries in the world, so the rollout of a network like this is nothing trivial. Europe is a different story..

Android's browser isn't "Chrome" per se, and is tracked by it's own user agent. So no figures in the wild should be counting it toward Chrome's market share.