Main

March 24, 2007

Viacom's GC: DMCA Doesn't Protect YouTube


digitalcopyright.jpgViacom is doing a major tap-dance in its copyright infringement litigation against YouTube. As I pointed out earlier, the entertainment giant’s lawsuit against YouTube (which is owned by search giant Google), side-steps direct reference to the DMCA. I found this to be a glaring defect in Viacom’s complaint, although Mike Arrington told me in a comment that I was misinformed, that Viacom had no obligation to preemptively raise what no doubt will be YouTube’s defense.

The Digital Millennium Copyright Act (DMCA) has a safe harbor provision that insulates Internet companies (although as discussed below, exactly who the DMCA insulates is a question mark) from copyright infringement liabilities if upon request of the rights holders, the company removes the allegedly infringing material. YouTube has presumably met this requirement. YouTube maintains that it honors all such take-down requests and therefore Viacom’s suit has no legs.

But Viacom kicked up the dust nonetheless, accusing YouTube of knowing that it has infringing material on its site (which is a violation of the law) and from refraining to actively scan uploaded content to see if it contains copyrighted material (the law does not require this.) In an op-ed piece in today’s Washington Post, Viacom’s General Counsel Michael Fricklas defends the DMCA but says it does not apply to YouTube.

The DMCA strikes a logical compromise among competing interests and is one of many sound policies that have allowed the Web to develop and flourish. Under the act, Web hosting companies have been able to develop with no obligation to monitor every file loaded and downloaded by their users. E-mail operators have been able to safely maintain their facilities without reading every message that passes through their systems. File storage Web sites allow users to back up their hard drives without needing to patrol every file and without fear of copyright liability.

Fricklas’ arguments about how the DMCA doesn’t apply to YouTube are not fully clear to me from the published piece — as is often the case, the Post may have edited down Fricklas’ submission so that some of the underlying logic was edited out. Nonetheless, here’s what Fricklas seems to be saying:

1. The DMCA Applies Only to “Passive” Internet Services: “It [YouTube] is far more than the kind of passive Web host or e-mail service the DMCA protects,” Fricklas writes.

2. The DMCA Doesn’t Apply to Companies that Reap Financial Benefits from the Copyrighted Content:“The [safe harbor] defense is not available to someone who ‘derives a financial benefit’ from copyrighted material he stores if he has the ‘right and ability to control’ it.”

3. YouTube Must Be Aware of the Infringing Content Because Everybody Else Is: “Does YouTube have ‘knowledge’ of copyrighted material on its site? Does it have the ‘right and ability to control’ the content? Yes and yes. If the public knows what’s there, then YouTube’s management surely does,” Fricklas says.

4. The Burden of Finding Infringing Content Shouldn’t Rest on Owners:“Is it fair to burden YouTube with finding content on its site that infringes others’ copyright? Putting the burden on the owners of creative works would require every copyright owner, big and small, to patrol the Web continually on an ever-burgeoning number of sites. That’s hardly a workable or equitable solution.”

What Fricklas has done, in essence, is put in op-ed form Viacom’s reply to YouTube’s response even before YouTube has responded to Viacom’s complaint — or filed a motion to dismiss or whatever it is YouTube is going to do. (Confused? Let me put it another way: Viacom is anticipating what Google will say and this op-ed piece seems to be Viacom’s counterarguments.).

From where I sit, Viacom has raised some interesting questions, at last. It’s never been very clear if the DMCA applies to Internet companies such as YouTube or, I might add, iFilm or Addicting Clips or the other YouTube-esque sites owned by Viacom. The DMCA was intended to apply to ISPs such as dial-up service providers, although the law on its face doesn’t say this, nor is there a lot of back-up for this “passive” provider limitation.

But, Viacom is way off base when it argues that because we all know, YouTube must also know about the infringing content. That’s almost laughable — which is not to say a judge won’t allow discovery on this question. I’m never quite sure whether a film or TV clip is infringing or not, and I follow this stuff far more closely than the average person.

Finally, there is the more difficult issue of whether the burden of discovering infringing content should fall on the rightsholder. As impossible as it is for a rightsholder to locate infringing content on the web, it’s even more difficult for website owners to be aware of every little scrap of copyrighted content that exists in the world and be on the look-out for it.

In any event, Mike Arrington said in his comment to me that YouTube would raise the DMCA safe harbor as a defense and that Viacom would then argue that the DMCA doesn’t apply to YouTube. Based on this op-ed piece, it looks like he was absolutely right.

But I still think Viacom made its work harder by not grabbing the bull by the horns at the outset and explaining from the get-go how the DMCA doesn’t apply to YouTube. Obviously, Viacom might be thinking this too. Otherwise why is the company going public, tipping its legal hand, so to speak, in a major newspaper well before it needs to?

 

Cynthia Brumfield at 11:50 AM|Comments(1)

  

Comments

Disclaimer: I'm Mike Fricklas' brother. Nothing of what I say comes from him, however.

My assumption about the purpose of the op-ed, and for that matter, the law suit: This lawsuit isn't about trying to get $1B (or for that matter $1) out of Google - Viacom has less risky ways of trying to make money than high-dollar lawsuits against other mega-glomerates. What this suit is about is refining the DMCA or introducing new legislation to specifically address fair use in the case of copyrighted works, posted in significant part or in their entirety, without the consent of the copyright holder. This obviously has ramifications for the copyright holder, as well as the sites that contain the content. Without an express definition of fair use, there is little difference between downloading the latest episode of The Daily Show via bittorrent and viewing it online at YouTube -- in fact, it's much easier to find and view on YouTube due to the various ways in which content is indexed and crossreferenced.

The world seems to have defined fair use in sound clips as 30-second segments used in context of providing the copyright information in situ. It has long defined fair use on copyrighted print materials in well-defined ways. Use of video content without copyright holder agreement, knowledge, or attribution isn't the same thing... especially when the video content is used in a way that is specifically designed to make money.

Another argument is that YouTube only provides an "index" to content, similar to google or The Wayback Machine's archived content of the web. This isn't the same thing again, since web based content can be prevented easily on the part of the copyright holder by putting metatags on the sites (to request non-indexing), and by putting stuff on the web in a visible manner in these it is used as a pointer to it's original context -- YouTube is designed to keep viewers _on_ YouTube, so viewers will implicitly authorize ad placement and support it's revenue model. Archive.org is very explicit about authorization to hold copyright material (e.g. live music archive) before posting material -- YouTube doesn't check with copyright holders in any way (or attempt to research them, which admittedly would be an onerous task given the quantity and flow of the material).

Hopefully this case will rigidly define (or at least better define) where the line is between fair use and free use.

Posted by: Ken Fricklas at March 27, 2007 12:31 PM

Post a comment




Remember Me?

(you may use HTML tags for style)

Verification (needed to reduce spam):