It's special because most Android phones are NOT getting a security update for the known flaw.

Um, the very article you link to lists no found collisions, only theoretical attacks (where an algorithm could be used to find one faster than a brute force search).

Given that I've yet to see an actual SHA-1 collision published, it's hardly "easy" to do...

The problem with the FireSheep discussion is that there is no current solution to this.

People keep saying that the social media sites should use https. However, they CAN'T use https for the entire session: advertising content delivery networks like AdSense don't support https, so it won't work.

As I've mentioned in other messages, this is the real problem. Advertisements can't be served over https as the major networks like Google's AdSense don't support https. This is exactly the kind of third-party content you mention.

So sites that are funded by advertisement will use http not https.

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.

I downloaded one of the sample apps (BrickBreaker), and it seemed to automatically install the JavaFX code.

However, I then end up with an entirely black window for the app. This is on a G4 Mac.

Not good for a first impression.

Like most mmo games, leveling gets harder as you get higher.

The first 60 levels are a relatively small part of the game now.