And in the next seven years, it isn't going to be indium antimonide gates. PCM might make a showing if you're lucky.

>However, it's made with indium antimonide, which apparently doesn't work well with existing fabrication methods.

So it's dead then.

PC+Steam. Easy

The link is ok. But I appreciate that you appreciate that I put a little effort into choosing my words.

I can do all that. But I have a wife that doesn't appreciate a wiring loom in the kitchen. It should be in the control panel of the oven with a standard two pin temperature probe socket on the control panel.

I have one. It's basically a bedroom issue vibrator with silicone plastic legs attached. It rotates around the pot stirring it. Great when you want to boil cream for an hour.
http://www.drugstore.com/products/prod.asp?pid=354782&catid=184266&aid=338666&aparam=goobase_filler

I want feedback.

I want to be able to stick a thermometer in my food, whether in the oven, microwave or on the hob and have the thing use feedback to follow a temperature vs. time profile.

Why waste $5k on immersion heaters and vacuum packers for sous vide setups when a simple thermometer input and a few lines of code could achieve the same thing on a conventional kitchen oven?

Yes. Millions of vulnerable uPnP implementations in consumer electronics, behind cheap NAT routers that by default allow a uPnP hole.

>My understanding was that UPnP was for punching a hole in the firewall/NAT for incoming requests

No, uPnP is primarily about AV devices finding each other so they can do stuff like sending video from the video source to the TV. It's network detection and selection, device discovery, service discovery and service negotiation. All run of the mill consumer electronic behaviors that the industry has managed to massively screw up for the past 30 years. P1394 tried and screwed it up (discovery and negotiation). uPnP tried and screwed it up (bad security, ineffective discovery). P802 tried and screwed it up - LLDP (too little), 802.21 (too late). I could go on. You still cannot string one wire, or wireless interface between standards compliant boxes, computer, dvd, tv, speakers, roku-esque box and have them find each other and present a user with the right options like "watch dvd" or "watch roku" or "watch TV".

The punching-a-hole thing is a router behavior to allow uPnP to work across the router (whether firewalled or not), because by default they block uPnP, as they should.

I use G+.

Facebook is for jokes, memes, family stuff. Little of consequence.

On G+ I interact with the engineers, kernel developers, cryptographers and other work related connections beyond my immediate employer.

There's a simple work/play divide between G+ and Facebook and that separation is good.

Tahoe-LAFS FTW!

FTW is an anagram of WTF. Coincidence? I don't think so.

Not to my ears. I'd put Suberidai or Mayonaki Wa Jyunketsu way ahead of that dirge.
Each to their own.

Indeed. One of my professors invented the tagged delay line and the invisible cache, back when you had to build it out of discrete ECL.

SSL protects the point to point link. But unless the web site requires you to have a client certificate or other security credential, anyone can download over https and see the plaintext.

From my reading of the Mega response, the crypto applied to the static content was to ensure the integrity of the files as transmitted, not the privacy.

They are free to add an arbitrary amount of additional integrity checking of the static files, both of the cryptographic and non cryptographic nature. I wouldn't be surprised if they already do because it is trivial and a normal thing to do.