Language Selection

English French German Italian Portuguese Spanish

Fencing and Tollgating the Internet

Filed under
Software
Web

This story about yet another attempt to raise a tollgate on the Internet deserves having some extra attention called to it.

"The players from Google and Vimeo do present a pretty serious problem, though. Each of these require a proprietary H.264 codec to be able to view them. These codecs aren't compatible with the royalty-free web standards that the rest of the web is built on. The fact that they are being so unabashedly hyped along with the new darling of the web - HTML5 - means that most people don't understand that something very dangerous is taking place behind the scenes...

"Remember, this is still very early in H.264's history so the licensing is very friendly, just like it used to be for MP3.

The author, Christopher Blizzard, works for Mozilla. He has done his homework and gone far beyond the tech press in analyzing the issue. In fact, the tech press have totally missed this, and instead joined in cheerleading H.264. What journalists are missing out on is that H.264 is a patented codec, and that the patent holders expect to collect royalties.

Rest Here




Firefox, YouTube, Video and the Ethics of Codecs?

htmlgoodies.com: Lately there has been a lot of controversy over the recent announcements by Mozilla, YouTube and Vimeo about their support of HTML5 video. The controversy lies in the codec used to display that video, and how supporting one codec over another could unravel the fabric the web is made of.

To get to the point, it all boils down to licensing rights. YouTube announced that they were using the H.264 video codec to support HTML5 video. This was soon followed by an announcement by Vimeo, another video site, that they will also support HTML5 using the H.264 codec. Apple's Safari is also using the H.264 codec. Dailymotion and Wikipedia have gone with support for Ogg Theora, an open source video codec. Mozilla hasn't settled on which codec they will support, and Google's Chrome supports both codecs.

By supporting H.264, YouTube, Vimeo and Safari are solidifying the use of H.264's in HTML5 video. The Unisys debacle will pale in comparison to the issues that will arrise if this happens with HTML5 video.

While it may be okay to use the H.264 video codec for the time being, at some point companies will have to start licensing the H.264 codec from the industry group that owns the MPEG-LA codec, and this will mean big bucks. Huge, gigantic bucks. And that spells trouble for the web.

There are two sides to this argument:

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

Kodi 14.0 Helix Unwinds

Merry Christmas and happy holidays, everyone! We are proud to announce the release of Kodi 14.0, which comes with a new name, a new logo, and a wide variety of new features, but underneath the new coat of paint remains the same software we all love. A detailed changelog for Kodi 14 can be found under milestones on our code repository, should you be interested. With that said, let’s take a look at some of the features that come with Kodi 14.0. Read more

KaOS ISO 2014.12

KaOS is very proud to announce the availability of the December release of a new stable ISO. This ISO marks two major milestones for this distribution. Since it’s inception almost two years ago, a need to be ready for UEFI installs has always been a priority. That was tied though to getting a modern Qt based installer that could handle such UEFI installs. With this ISO, both are implemented. Read more

Old FOSS Friend & Foe Represents Sony in Hack

Boies, along with three attorneys representing the States, brought Microsoft to it’s knees — or so it seemed at the time. On November 5, 1999, Judge Thomas Penfield Jackson found that Windows dominance on the PC made the company a monopoly and that the company had taken illegal actions against Apple, Java, Netscape, Lotus Notes, RealNetworks, Linux, and others in order to maintain that monopoly. He ordered Microsoft broken in two, with one company producing Windows and another handling all other Microsoft software. As we all know, Judge Jackson’s solution was never implemented. Although an appeals court upheld the verdict against Redmond, the breakup of the company was overturned and sent back to the lower court for a review by a new judge. Two years later, in September, 2001, under the Bush Administration, the DOJ announced that it was no longer seeking the breakup of Microsoft, and in November reached a settlement which California, Connecticut, Iowa, Florida, Kansas, Minnesota, Utah, Virginia and Massachusetts opposed. The settlement basically required Microsoft to share its APIs and appoint a three person panel that would have complete access to Microsoft’s systems, records, and source code for five years. The settlement didn’t require Microsoft to change any code or stop the company from tying additional software with Windows. Additionally, the DOJ did not require Microsoft to change any of its code. Read more

Study: ‘European Parliament should use open source’

The European Parliament should use free software and open standards for all of its ICT systems and data, concludes a study by the EP’s Greens/European Free Alliance: “That is the most appropriate way for the Parliament to meet its own standard of ‘utmost transparency’.” Read more