Wikipedia users will be getting new tools for uploading, editing, and viewing video very soon. According to a Beet.TV interview with Erik Moller, who is the deputy director of the Wikimedia Foundation, we'll see all of these things shortly. However, what's more interesting is the Web encyclopedia's choice of video formats and how it fits into a fracas in the browser world.

Wikipedia has been working on video support for years, and is putting considerable effort into making it easier for users to upload video--specifically, to bridge a video format divide. Moller says that while Wikipedia is still planning to use Ogg Theora (an open-source video codec that can be played back natively inside the latest version of Firefox, and soon Chrome and Opera) there may be tools that will convert video shot in alternate formats so that no special software, or user effort is required.

In the meantime, Wikipedia's solution is for users to do that conversion on their end. Moller says that one solution is FireOgg, a Firefox-only browser plug-in which can transcode user videos to Ogg Theora on the user's hardware.

One issue that still lingers with Wikipedia's slow move to video is its choice of codec. Codecs are the software modules that encode and decode audio and video, shrinking it down into sizes that can be more easily transmitted through the Web. Wikipedia's a large and very popular site, meaning whatever video format it's using will have a big impact on the Web and its standards. Wikipedia's choice to go with Ogg Theora puts further stress on where browsers and site creators alike stand on HTML 5 video, which is emerging as a hotly-contended Web standard.

Unlike the H.264 codec, which has been promoted in both Google and Apple's products and services, Ogg Theora allows for downloading, remixing, and re-uploading without licensing fees. On the other hand, much of today's computing hardware (including newer mobile devices) comes equipped with on-board H.264 decoding, meaning less processing power is spent playing back the videos.

Microsoft, Apple, and Google have been less avid about promoting the Ogg Theora format in their browsers, and have put resources behind H.264 instead. Google's Chrome, in fact, supports it (along with H.264), however Google has gone on the record as saying its quality was not as good as it wanted. Google has also sunk considerable resources into re-encoding YouTube's entire library of videos into H.264, making the company less likely to switch camps.

Regardless, Web video has come a long way since earlier standards and competing formats. Pioneers like Macromedia (now Adobe) with its Flash format, and Apple and its streaming QuickTime standard have helped pave the way for a bevvy of start-ups that rely on the latest codecs to create new and salable parts of their businesses. The big question is whether open-sourced codecs like Ogg Theora will have that same kind of sticking power. Being the go-to format on one of the Web's most popular sites certainly won't hurt.

New versions of Google Chrome are out, fixing bugs and patching security holes in both the stable build and the beta build.

Two serious security flaws have been plugged. One had allowed for malicious code exploitation within the Chrome tab sandbox. Found by the Google security team, the threat was serious enough that Google has declined to be more specific until "a majority of users are up to date with the fix," the company said in a blog post.

A second security risk caused by memory corruption was found in the browser tab processes. It could have been used to run arbitrary code that would crash all of the browser tabs, creating a second security hole through which an attacker might be able to run code with the privileges of the logged-on user.

Other bug-fixes include updates to the V8 Javascript engine, updates to Google Gears, and getting forward and backward navigation to work even when site redirection is involved.

The full list of changes can be read here.