Nakamoto block chains don't address the problem of authenticating and authorizing transactions, they address the problem of resolving disputes over whether and when any given transaction happened. In conjunction with the block chain, digital signatures and smart contracts provide the authentication and authorization respectively, and neither technology needs access to anyone's private information when verifying or validating.
It doesn't stop at 'name endianness'. It's probably less confusing, in print at least, to use the convention of all-capping the surname while leaving the full name in its native order. I imagine such a convention would be especially handy when trying to wrangle elaborate names carrying a whole syntax tree laden with titles, adjective phrases, and prepositional phrases, leaving the surname somewhere in the middle. Such names tend to be found in Europe and the Middle East at least.
The downside to smashing case is that it loses information, such as whether 'VON FOO' is properly cased as 'von Foo' or 'Von Foo'. Where possible it's probably better to use an inline tag or something, but plain text doesn't leave room for such niceties.
Didn't say it was. It's the pattern of usage, though, not any real time constraints. Server-based games tend to be receive-heavy rather than symmetric; they're sending the user's actions but updating the entire environment around the user. Always on DRM is basically periodic license re-validation, relatively low frequency. UI remoting is again going to be extremely receive-heavy; keystrokes and coordinates take up much less space than graphics pushes.
You might have difficulty distinguishing one voice app from another within an encrypted tunnel, though.
Plus, you are ignoring the fact that nobody is planning to encrypt content like video streaming.
Remind me again why big corporations have been making a huge uproar about allowing unencrypted content? Oh yeah, DRM.
More generally, CDNs aren't "in-network services" in the same sense as middleboxes and thus aren't hampered by TLS. When properly deployed they don't sit between the page server and the browser, but rather the page server links to CDN URLs for images, scripts, and other referenced content. From that standpoint they are essentially just another farm of web servers specialized for static content.
The "in-network services" TFA talks about can only work because they can freely inspect, collect copies of, transform, redirect, and generally tamper with the data streams without the end user explicitly opting into them. Most of these I have encountered primarily add value for the network owner, and more often than not actually subtract value for the individual user forced to go through them.
... and that would be Ninite, whose Pro offering includes command line scriptable updates of all your favorite security holes from Adobe, Oracle and more, and can also automatically decline partner offers and disable updater popups.
The free edition no longer updates Flash, as a compromise with Adobe who appears to rely on bundled partner offers with every patch as a revenue stream from Flash Player home users. Ninite Pro has more software package options, over-the-network install/upgrade/uninstall, and a desktop UI instead of web-based.
No affiliation here, just a happy customer.
Leave it to a Great Old One to figure out a way to completely befuddle the password policy enforcer.
The potassium hydroxide electrolyte used in typical alkaline batteries will dissolve its way through the zinc canister over time even when not under load. The other common electrolytes, zinc chloride and ammonium chloride, will do the same. Zinc will corrode if exposed to acid, alkali, or sometimes if you just look at it cross-eyed, but the ease with which it gives up electrons makes it an effective primary cell anode.
One workaround is to swap positions of the electrodes: make the canister out of carbon and use a zinc center electrode shaped to give it as much surface area as a canister would have. I imagine you'd have problems with the carbon breaking easily from rough handling, though, and it might cost more to make. Maybe powdered carbon with a plastic binder instead?
Pfffft. I should have expected Korny jokes. (Ba-dum-csh.)