That why solution like 6rd.

ISP can keep their current IPv4 gear, and just offer an IPv6 tunnel that the clients can use over the IPv4 infrastructure.
No need to immediately replace all the components, and meanwhile, IPv6 is already available.

It's a short-term quick hack which might make some problem seem to disappear, but creates ton of other problems.
NAT creates layers of indirection, and NAT makes machines not directly addressable.
Require hole punching and the like even for very basic functionality (like VoIP).
The internet was envisioned as a distributed network with all being equal peers, but NAT is contributing to the current assymetry of having a few key content distributor and every body else being a passive consumer.

IPv6 here. No it's not that complicated, and can be made automated. (e.g.: you don't even need to setup DHCP. your router just hands out prefixes, and the devices on the net autonomously decide their address by appending their mac address).
With NAT, you'll end up needing to fumble with your router and open / redirect ports anyway, just to be sure that everything works as it should.

That the point at which end users like us need to be proactive.
Setup tunnels (like Sixxs and other similar IPv6 brokers), open tickets at your provider asking for 6rd support, etc. ...or just move to a country with pervasive IPv6... :-P

Much more basic: Ask your self, *WHAT* is google's business, what are they earning money from ?
They are not earning lots of money buy selling copies of Android.

Instead they earn money with their service: they probably earn a percentage of sales of apps on their store, and they earn tons of money through their data-mining/advertising.

So yet another fork of android doesn't mean less revenue for Google. It means yet another portable platform that will eventually log into maps.google.com, and ask about pizza, and earn them tons of money.

It's the same reason why google can at the same time support Firefox development (they pay them a good budget) and at the same develop their own browser.
That might sound weird. But it makes sens. Google isn't in the business of *selling* browsers. More browsers mean more people online eventually using their service, and thus means more indirect profits, no matter exactly were the browser came from, as long as it conforms sufficiently to standards (HTML5, etc.) and can use their service, and isn't completely married to a competitor service.

The only thing regarding to Android that would drive them mad a little bit, is if Microsoft decided to fork Android, and design a special fork that only exclusively works on Microsoft's services (Bing, Office 365, etc.).
Lukily for them, Microsoft did instead attempt to make such a microsoft-exclusive platform using their windows OS and we all know what kind of success they had with this.

Even in the realm of "GNU/Linux" not everybody uses bash (some use zsh, for exemple).

And that's only the portion of users running an actual "GNU" userland.

Then you have the embed world using Busybox (with uClib, etc.) and co for the userland (which has its own simplified shell).
And then you have Android (which runs a completely different user land by Google, like Bionic for a C library, a different message passing bus, and most of the things usually handled by deamon running in userland, handled by java-like code on a java-like VM).

And the other way arround: you have other Unice (OS X, various *BSD) which obviously do not run Linux kernel, but do run bash.
OS X, for example, was affected by bash.

such things were also reported by people who got caract surgery. Some type of replacement synthetic lens were more transparent in the UV and suddenly people started to see UV. (Some replacement were way too much transparent in the UV and could damage the eye by not protecting it enough).

Both are "UV" in the sense that they are above the violent band. But they're not the same wavelenght.
Blacklight UVA: is just slightly above the the violet band, with wavelenght shorter than 400nm
Germicidal Lamps UVC: is way above the violet band, with wavelenght around 280nm (e.g.: around wavelenghts most likely to be absorbed by DNA and other critical biological structures - thus damaging the germ cells).

Cones can detect UVA (it's just usually blocked by the eye's len).
Cones cannot detect UVC (and would probably just die if exposed to it).

With OE, sniffing data doesn't work.
OE will encrypt the tiny bit that interests you, in the middle of an otherwise plain text connection.

So by simply passively listening to packets, you won't be able to gain access to the juicy parts, they will be the (only) encrypted part.

OE can prevent incident like google car which recorded sensitive information while logging data packets from non secure Wifi. Or attacks like FireSheep passively listening to clear text cookies in a internet café

But currently OE apparently lack any authentication scheme. so it's trivial to throw a MITM attack.

OE isn't competing as being an alternative to HTTPS. (Https is the real deal if you want security).
OE is trying to be a tiny bit better than plain text over HTTP, and currently is a little bit better at preventing accidental eavesdrop.

Which CPU are you talking about?

The huge power hungry multi-core x86_64, optionally assisted by massively parallel GPUs (running opencl) that sits on your desk ?
well decoding high res video is a walk in the park.

The small diminutive ARM designed to be as power efficient as possible that is in your pocket?
much more problematic. it won't pack enough power for higher resolutions, and in the cases were it *DOES* manage to code the video real time, it's going to kill the batter really fast.

The situation of VP9 isn't that different than H.265
- desktops work well enough even without dedicated acceleration
- smartphone are limited by the current lack of acceleration (well except the few latest phone which slowly start to get H265 hardware) due to CPU limits and battery life.

The problem is that currently you can go to the nearest dealer and buy them.
They don't exist yet. There are just prototypes being developed here and there.
They need to be developed (which requires having a huge database to learn from).

Also, the problem of buying car from another company (say Google if their robo car is the first to be mass produced), it that Uber would become dependant on Google's whim. If their future business model rely on a service powered by robo cars, it would a bit risky to entirely depend on an external company for said cars.

The point of Uber, apparently, is to beat others in the development of autonomous cars. Not to depend on anyone else. Make their own robo car business.

And they have a similar mass of useful data out of which to build the car's intelligence. Which was graciously provided by the hipsters using the service, who never consented to be part in an AI research in the first place.
The kind of data log that used to enable the controversial god-mode, can also be used to build a very precise model of "how are the driver managing to navigate inside city centers ?"

From what I understand how this is supposed to work, it's the opposite:

I think it's: you type a simple *http* address, the website behaves like a plain normal one. (so no https address, nothing misleading you into thinking you are using secure https website)
But when you submit data to it, the browser will automatically switch on-the-fly to an alternate, encrypted route, so the data is sent encrypted to a alternate destination handling encryption.
It's not a full blown https, but it's better than nothing.
Think of it as "https-lite" for sending data. Designed for server which can afford having a full blown https stack.

Except, that the thing is so much simplified that there aren't enough checks in this protocol. So a third party could use the feature to re-route data to their eavesdropping infrastructure, instead of re-routing it to an encryption feature on the original http server.

My "portable online life" has been an Ericsson T39 (that outlast it's intended time by decade)
combined with successive models of PDAs from Palm.
Add in foldable keyboard for the PDAs and you get a small laptop replacement.

Only started using smartphone when switched to WebOS powered smartphone by Palm.

The combo has a few advantages:
- better life battery
(phone is very efficient as it doesn't to much beyond being a phone. It's as simple as you can get, and can last a week on a charge.
PDA isn't constantly online and thus is also low energy requirement. specially the older one could last a long time between charges)
- separate PDA used to be more offline oriented (think google maps over 3G/4G vs. dedicated map application with locally stored maps. very useful when you travel abroad).
- redundancy (typically, one would sync contacts over bluetooth or irda between the 2 devices. If one dies or gets stolen, the other is till working).

Feature phones as old as the Ericsson T39 (note the absence of "Sony" this old piece predates the merger) were already able back then to work as GRPS modems over infrared, bluetooth, or USB (but the USB cable was expensive and rare, so bluetooth then).
And this antique only has a couple of text lines on screen.

Note that feature phone used to have cameras too. Feature phone introduced camera before even smartphone where started.
Same goes for a lot of other things you mention (email, games, alarm clock, calculator, etc.)
I think games and alarm are the two first features built into phones.

Partially solved by several techniques. For example, one available backthen on the a fore mentionned Ericsson (still available on all subsequent Sony-Ericsson feature phone) - volume rocker works as a kind of "shift" key. Using combination of volume + number gives you directly the letter you want instead of repeatedly pressing a letter. Gets a bit time to get used to it, then works as fast a typing on a keyboard.
Some provided external keypads (again Ericsson had a "chat board": full qwerty keyboard), if your finger arent's too fat, it's fast than a virtual keyboard.

The whole MP3 craze began much earlier before Apple re-invented it with their brand of players. As soon as MP3 player stared being popular, phone started offering the function, some phone even had a dedicated separate physical interface for that. Close the clam shell: you have buttons and a small monochrome screen to handle playing your music. Open the clam shell: feature phone with color screen.

Can you actually think of a phone that DOESN'T have a lit up screen? People have been using it as improvised sources of light for as long as I can remember.
The only thing brought by modern smartphones is *white* light (as they can abuse their flash for that, where as old monochrome phone screen tended to have blue, green, orange, etc. backlight color).

8k iMac: depending on the specs of the iMac, that might means that they have managed to increase the pixel density (high DPI).

8k in it self doesn't mean anything. You have to factor in display size, viewing distance, etc.

And there is ONE FIELD that is going to benefit immensely from higher densities: VR!

VR is typically a field of application where you are viewing a relatively small screen (Occulus tend to use typical smartphone displays. Older VR headsets like eMagine 3D visor had even smaller display, like a finger's nail per eye) from a very short distance. (Just next to the eye ball).

Even at the current ultra-high resolution/pixel densities, that are over kill for a normal smart phone screen (1080p FullHD in a smartphone is more than 300DPI), when looked that close still is very pixelated (this FullHD is blown up to cover your *entire* field of view. That end up being not that many pixels per angle of view, even if keeping into account the varying resolution due to the simple len's distortion). (= Unlike older VR headset that used simple rectangular screens to convey a simple rectangular picture and relied on complex and expansive optics to keep the rectangle distrosion free, Occulus rift use a very simple (and cheap len) that completely distrorts the picture and compensate using a shader that draw a "pre-distorted" picture on the display. They don't convey a rectangular picture, but a pin-chusion picture with more pixels spent at the center than the periphery - thus higher resolution in front of you. Still pixels are visible).

So even if it ends up being overkill for the iMac, increasing production of high density displays has nice side effects on the occulus rift.

Question: How do you jump start research into car robotics when you're not Google and thus don't have a huge mass of knowledge about all the roads gathered by your google cars and google maps program ?

Answer: You get a ton of hipster to drive for you, record their trajectories/behaviours (remember "god mode" ?) and use their knowledge as a starting point to populate your initial database.

Come to think of it, Palcohol shouldn't get attacked in the US in the name of protecting children from booze.
It should be attacked for false advertisment:

"Power alcohol" isn't powdered alcohol. It's a fuck ton of useless sugar powder with a tiny bit of ethanol sprinkled in.

It should be called "Powder+alcohol".
Or "Powder Sugar (may contain traces of ethanol)".