Google didn't pull the plug on Wave because it didn't work, it just didn't fit into their business model. The wave protocol is federated, while all other Google services are centralized, Google relies upon all traffic coming through them for skimming revenue from their users. This is why they killed wave and even when it was style in hype mode refused to release a user installable client (free or otherwise). However, the ideas behind wave, most importantly that it allows rich real-time communication with automatic archiving of history make it a powerful evolution of email/instant messaging. Rot in your capitalist filth Google, long live Wave!

That's not the best evidence. The most appropriate literature for this exposure is that pertaining to nuclear industry workers. This is how the guidelines of 20mSv per year were derived. See this study for instance: http://www.ncbi.nlm.nih.gov/pubmed/17388693 there's no need to reinvent the wheel here, there is ample evidence that nuclear workers have higher risks of cancer and a population exposed to fallout from a reactor could reasonably be expected to have similar or worse outcomes (due to increased ingestion of isotopes)

I recently had a similar issue and now use: Local: 3x 3TB Hitachi high end drives RAID 5 in external enclosure. Remote: Data that is really critical gets synced using rsnapshot (incrementally) to 'my own cloud', a dedicated server running Debian that I pay about $60 per month for (Fasthosts). It also runs a web/email/WebDAV server which is handy to access the incremental backups by the web. This way I get redundancy with fast access and decent security (all over ssh). Running your own cloud is pretty trivial these days, well worth the effort.

...an abuse of the definition of shutdown. Reality check: - 3 melt-throughs - melted cores outside pressure chambers - compromised secondary containments - nuclear fuel and fission products escaping into water and air - corium so radioactive it cannot be approached even by robots - precarious leaning of number 4 spent fuel pool - widespread plutonium, caesium etc. beyond evacuation zone - significant contamination in food - yet to come: increased malignancies and birth defects Does this sound contained to you? Seriously...

Milk accumulates radioactive iodine very efficiently. Shouldn't be radioactive iodine around anymore if there is no nuclear reactions happening as it has short half life.

Perhaps you should lead the way and offer to live in the exclusion zone when it opens. Also grow your food there and drink the water, tour the plant with your kids on weekends. That is fantasy, of course, living in this area in even 100 years will result in a pretty decent caesium load even if you manage to avoid the heavier hot particles. If we ever see figures, compare pre-Fukushima explosion cancer and teratogenic rates with after, there's a lot of deaths still to come from this disaster. And a lot of land and sea that has lost its utility.

"seems clear that it is safer" - are you serious. Your argument is a straw man the whole way, yes coal is polluting bit that doesn't mean nuclear is the answer. I'll support nuclear when all the high level radioactive waste now crowding cooling ponds is in geological storage, oh wait, I forgot that would also make nuclear economically unviable.

A Melt-through has been acknowledged by TEPCO (see The Guardian 8th June article). While I don't think I was being hysterical, that would actually be a pretty reasonable response to the event. 1) primary containment - pressure vessel failed 2) secondary containment (toroidal pool) failed 3) building breached by explosions This IS worse case scenario. Plutonium 40km from site, contaminated water, food and soil. And there is radiation still being released with no viable plan to contain it. I'm sorry but cold shutdown implies there is still a functioning reactor to shut down.... Just smoke and mirrors...

Unbelievable they would claim 'cold shutdown' when reactor containment has been breached at 3 units! More like: "the molten corium has burrowed deep enough to be cooled by groundwater and we are only reading 90 degrees at the twisted, melted reactor because the radioactive steam coming from below ground is dissipating the heat" How reassuring.

There are basically 2 ways: Install an 'appliance' mailserver like zimbra/roundcube Or roll your own. I've been running a personal, small business server for years. It's great being able to give free email addresses to friends and family I would recommend (on debian server): -Postfix smtp with mysql backend and postfixadmin -Dovecot imap -Amavis/spamassassin/clamav for virus/spam filtering Then you can throw on any web based client I like horde but squirrelmail is good too. Horde has good groupware features and the new interface supports some nice ui features. Also consider serverside filtering, horde has a sieve plugin which integrates with Dovecot in a cleaner way than squirrelmail. Setting up a server is non trivial and you'll need to get your head around NAT, firewalls (iptables) and making sure you're not an open relay. However, once it's running it's actually pretty maintenance free (unless you want corporate level security). Good luck! There are some excellent howtos out there. If the above sounds daunting, try an appliance first but there's a lot to be said for rolling your own.

The most environmentally sustainable and efficient way to achieve this is to reduce impediments to retrofitting. Special, restricted registrations are currently required in most states, slowing down the number of people doing conversions. Never forget that 50% of the energy of a vehicle is used in its production. Therefore, changing to electric in older (preferably light) vehicles is a very viable strategy. The best the government could do is shift fuel/road subsidies to better support the initial outlay/recycling of lithium and tax heavy vehicles more to pay for this. Then let the industry develop, there's already been hobbyists (with support of Sanyo) who've squeezed a range of 1000km from a converted car... So if the initiative is about raising the number of electric vehicles with the minimum cost, retrofitting is the clear winner. But if its about handing out money to manufacturers to to sell more cars that have already wasted half the energy and keep producing "hybrid prototypes" then I'm sure we'll be talking about new cars... In the longer term, public transport and support for cycling is a bigger winner anyway. Why move a ton of steel/aluminium/plastic for an 80kg person, basic physics requires you to expend more energy than any other means of transport...

Google bought Etherpad and Jotspotlive, two very advanced implementations of real time collaborative editing (albeit without some of the extra features of wave). Can we please have them back Google? I was about to buy a decently priced server version of etherpad just before the buyout, and I thought, OK maybe with Google's open framework they can do it better and give us a nice server/client package. I have lost trust in Google, I think the Wave was too innovative for them, it allowed data to stay on separate servers, perhaps Google wanted more control over our data than that model allowed. If Google has any decency about this, they should at least opensource the full web client implementation so that we can continue development. There are many enlightened sysadmins that saw the potential of Wave but could not use it because it was non functional without a locally installed client for intranets. So Google has killed two good projects to bring us..... almost nothing Oh well... back to Moonedit for now, prove me wrong Google...