This kind of thing is the fundamental problem. Interoperability issues like this are why the major advertising content delivery networks (including Google's AdSense) don't support https.

As they don't support https, social media sites can't use https for the entire session as they wouldn't be able to serve ads, and so wouldn't make any money.

So we get insecure social media sites, as these are the only ones that can stay in business.

The real problem is that most social media sites CAN'T use https by default.

Most of the advertising content delivery networks (and this does include Google's AdSense) don't support https.

Thus, if the social media site used https for the entire session, then they wouldn't be able to serve ads, and wouldn't be able to fund the service. So it isn't going to happen.

There is a real problem with current web protocols that security is all or nothing. You can use http and be insecure, or use https and break all kinds of network technologies (e.g. proxy caches). There is no way to have authenticated but not encrypted data, and the browser security functions make it very hard to mix content from different sources.

Blu-ray full HD video tops out at 40 megabits a second. This is easily handled by any half-decent USB flash drive.

There is no need to emulate a particular windows platform, you just need a stable win32 library for compatibility.

It's pretty easy to write windows software that will work on any windows version from 2000. It's not much harder to support 95+. The basics of win32 have been stable for years.

The 16bit elements are now irrelevant (unless you want to run some very old windows games). Even Microsoft doesn't support 16bit software on the 64bit Windows versions.