Just a small addition - what is broken is essentially the logic of version determination. Web/flash devs make two mistakes that break the N900 Flash use-case horribly:

a) they abuse the version determination as an upgrade mechanism. The assumption is that if someone does not have the latest version is because they simply have never gotten around upgrading it, so they just need a nudge. These people think they are making users a favor since they will be upgrading to a version which is faster, more safe, etc.

b) a more generic problem, making compatibility choices based on gut feeling, and not actual technical requirements. Often this is also a side effect of html-copy, when people copy over html sections from other sites on on-line tutorials, without matching version info. "It works on my machine, so it’s OK, right ?"

The problem is IMHO actually deeper - I disagree with the general Adobe practice that the *server* decides the content version the *client* is getting. The server should *advertise* available content versions, or the client be able to *request* a particular version, but the final choice should NOT be on the server - it’s the client that knows what it can or cannot do.