From "iOS Security February 2014 (http://images.apple.com/ipad/business/docs/iOS_Security_Feb14.pdf)", one good reason not to allow OS downgrades:

"If downgrades were possible, an attacker who gains possession of a device could install an older version of iOS and exploit a vulnerability that’s been fixed in the newer version."

If you want to learn a lot about code, really help out the community, and get a lot of love, write some documentation for other people's code.

Now how you work the database requirement into that, I don't know. Perhaps you could write a documentation request tracker for ReadTheDocs.org - their site is on GitHub at https://github.com/rtfd/readthedocs.org so you can fork it, write something that lets people request and prioritise projects that need docs, then submit a pull request.

If you're really ambitious, write a web-based environment for writing, editing, and submitting documentation to projects on GitHub, BitBucket, etc.

No, the point is that Mozilla have a philosophical issue with putting patent-encumbered video support into the Firefox code. Flash's relative merits are irrelevant to this topic. Crap as it very well may be, it's installed virtually everywhere, and it's been playing H.264 for years - it also gets installed whether or not you use it to play HTML5 video.

H.264 is widely used, and all the other major browser vendors have signed on to it for future releases. It would be foolish for Mozilla to make a stand on this at the expense of their users - most of them don't care. They'll simply see that their browser doesn't "work", and they'll switch to one that does.

By making Firefox play H.264 through its existing plugin/extension architecture, Mozilla can maintain its stance on the patent issue without losing the goodwill and support of its users, just like they did by adding PNG support to support the move away from the LZW-patent-encumbered GIF, without actually removing GIF support. Firefox makes use of a number of technologies that are subject to patents, and they've taken a pragmatic approach to those. It's not unreasonable to suggest that they do it again.

Most Firefox users have the Flash plugin, the Flash plugin plays H.264. An extension or greasemonkey script could replace <video> tags with a flash video player - patent fees paid for by Adobe, no need for a new browser fork, problem solved? Or is it more complicated than that?

But Windows and IE does both those things almost monthly, out of beta. These aren't outside of the level of expectation for Windows usage at all. What was that statistic again; leaving a PC alone for 12 minutes average before a freshly-installed copy of Windows gets infected with adware/spyware through the use of remote execution flaws in the OS? That's not even enough time to download critical updates. And that's not even beta.

I'm not making excuses; the Safari beta's flaws are atrociously bad, but you appear to have a double standard here. I think the saddest thing about the whole story is that Safari on Windows is "business as usual" as far as security is concerned; it's certainly no worse.