News for hackers. Stuff that matters.
Re:Chromium Blog: More about the Chrome HTML Video Codec Change by cookiecaper on Friday January 14, 2011 @05:20PM (#2105671)
This point has already been discussed a lot, but I'll just review it quickly for you.

Basically, if you use any software at all, you can't go around living your life in constant fear of patent threats. WebM is probably safer than most because you have a big entity to fight most of your battle for you, presuming such a battle ever materializes.

Of course it's possible that MPEG-LA will be angry to see their H.264 revenue stream run consistently drier and sue in hopes of retaliation and a declaration that all WebM users must pay MPEG-LA royalties anyway. There's no guarantee that this will happen, however, and that MPEG-LA hasn't made an attempt to "nip this in the bud" demonstrates that they may not be all that certain they have a case here.

Google released WebM explicitly to circumvent the restrictions with H.264 so I suspect they did their due diligence and deviated from the H.264 patents in the necessary ways, but as above, there's nothing you can do if you irritate a group that has money and lawyers and wants to try their hand at milking something out of you. That's a general fact of life whether you use WebM or not.

If you're really worried about the FUD MPEG-LA puts out to scare you into paying protection money, then I guess you are free to pay that, if it makes you feel happier. But "Google shouldn't promote free standards because it might make someone angry and then they might sue you" is just not a very solid argument -- we can't refuse to do anything because someone might sue us. There will always be vultures out there, and we can't stop progress because of them.

Re:Chromium Blog: More about the Chrome HTML Video Codec Change by KuraFire on Friday January 14, 2011 @06:56PM (#2105907)
"WebM is probably safer than most because you have a big entity to fight most of your battle for you, presuming such a battle ever materializes."

You’re making the kind of assumption that a rational business owner won’t make, which is that Google will suddenly jump in at the last minute and protect you. Thus far, Google is suspiciously refraining from indemnifying anyone using WebM. As a business owner, what motive do I have to give Google my trust and risk my entire business for them/their ideology of “openness” (whatever that means) if they’re not willing to give me the slightest shred of reason to trust them? It’s not like their track record is a shining example, either.

"Google released WebM explicitly to circumvent the restrictions with H.264"

That's their claim, yes. No independent patent entity has verified this that I know of, and MPEG LA have released statements that they are almost certain that WebM violates some of their patents. Also, Google has no stake in H.264, so they're at risk of being forced to forever pay hefty licensing fees to MPEG LA for Youtube (and other properties) if H.264 wins. It's entirely in Google's interest to kill H.264 or at least make WebM popular enough that they can use that to offer video to users, but just because it's in Google's interest doesn't mean it is in the interest of the web at large, or of Google's users and customers themselves. If you think they did this just for the "openness of the web" you're being either ridiculously naïve or a poor business person.

Re:Chromium Blog: More about the Chrome HTML Video Codec Change by magicalist on Friday January 14, 2011 @08:04PM (#2106100)
as a ridiculously naive and poor business person, I'd like to say that if webm becomes popular enough that google can serve it and avoid h264 (and paying royalties to MPEG-LA), I'd consider it a step toward my vision of a more open web (royalty-free codec widely available) and a good development for my business (royalty-free codec widely available).

no one is pretending that this will be all rainbows (the post directly acknowledges the current stalemate), so feel free to assume that those of us in favor of this development aren't idiots.

Re:Chromium Blog: More about the Chrome HTML Video Codec Change by kenjackson on Friday January 14, 2011 @05:40PM (#2105715)
Why would Google do their due diligence and not share it? MPEG-LA has detailed very clearly where each patent claim applies to the H264 spec.

Google owes it to its users to go through the MPEG-LA document and do at least one sentence explaining why WebM doesn't infringe each point. It would be a month exercise for a dev and product manager, but well worth it.

Re:Chromium Blog: More about the Chrome HTML Video Codec Change by Tloewald on Saturday January 15, 2011 @10:11AM (#2107089)
It ccurs to me that there's one possible motive for Google doing what it's doing that isn't purely cynical -- it may want the MPEG-LA to sue it now and reach some kind of settlement than wait a few years and ambush it.
Re:Chromium Blog: More about the Chrome HTML Video Codec Change by kenjackson on Saturday January 15, 2011 @10:20AM (#2107099)
The problem with that is that MPEG-LA's licensors can sue more than once.

In fact if I was MPEG-LA I'd do exactly that. I'd work with my licensors to ensure not everyone sue at once, but rather do it all in succession. Literally have WebM in courts everyday for a decade. And remember, only one licensor need win, and they don't have to grant WebM RAND terms. They could just come right out and say, "take it off the market". And since there's no indemnification, they could in theory even go after end-users of phones, although not likely.

Of course the same can be done against H264, but it appears far less likely.

But a "flush out the enemy" strategy doesn't seem likely given the raw number of patents and licensors associated with H264.