copyright – Page 8 – Attorney Evan Brown

October 16, 2014 Copyright, DMCA

GitHub jeopardizes its DMCA safe harbor status by launching its new policy

GitHub has baked in some feelgood to its new DMCA takedown policy. The new setup features clearer language, a refusal to automatically disable all forks of an allegedly infringing repository, and a 24-hour window in which the target of a takedown notice may make changes. The mechanisms of this third point ought to cause one to consider whether GitHub is risking the protections of the DMCA safe harbor.

If a DMCA takedown notice alleges that only certain files (as opposed to the whole repository) infringe, under the new policy, GitHub “will contact the user who created the repository and give them approximately 24 hours to delete or modify the content specified in the notice.” If the user makes changes to the repository, the burden shifts back to the sender of the DMCA notice. This shifing-the-burden-back seems problematic under the DMCA.

GitHub’s policy says:

If the user makes changes, the copyright owner must review them and renew or revise their takedown notice if the changes are insufficient. GitHub will not take any further action unless the copyright owner contacts us to either renew the original takedown notice or submit a revised one. If the copyright owner is satisfied with the changes, they may either submit a formal retraction or else do nothing. GitHub will interpret silence longer than two weeks as an implied retraction of the takedown notice.

The DMCA protects a party in GitHub’s position so long as the party “responds expeditiously to remove, or disable access to, the material that is claimed to be infringing upon notification of claimed infringement”. Read that provision carefully — the response must be to take down, not merely take steps to work with the alleged infringer to make it right. GitHub’s new mechanism of interpreting silence as a retraction is not an expeditious removal of or disabling access to allegedly infringing material. Nothing in the DMCA requires the sender of the takedown notice to have to ask twice.

You’ve got to hand it to GitHub for trying to make the world a better place through this new policy. The intended net effect is to reduce the number of instances in which entire repositories are taken down simply because of a few allegedly infringing files. But GitHub is putting something of great value, namely, its DMCA safe harbor protection, at risk.

Many copyright plaintiffs look for every possible angle to pin liability. You can almost be certain that a copyright owner will challenge GitHub’s safe harbor status on the ground that GitHub did not respond expeditiously. It seems odd GitHub would be willing to toss a perfectly good affirmative defense. One would think the better approach would be to go ahead and take the repository down after 24 hours, rather than leaving it up and risk a finding on “non-expeditiousness”.

Microsoft letter to GitHub over DRM-free music software is not the first copyright-ironic action against an intermediary

Evan Brown is an attorney in Chicago advising clients on matters dealing with copyright, technology, the internet and new media.

October 14, 2014 Copyright

YouTube has been a billion dollar boon to big media

This NBC News piece reports that since 2007, YouTube’s ContentID program has enabled copyright holders to monetize content posted to the service and get paid a billion dollars in the process. (Also included in the report is the staggering statistic that ContentID scans 400 years of content every day — we live in content-producing world of crazy proportions!)

So we see that with this kind of cash rolling in, it’s no wonder that Viacom finally came to its senses earlier this year when it decided to discontinue its litigation against YouTube. The billion dollar notion is also interesting — that’s the very amount Viacom sought when it filed suit in March 2007.

September 30, 2014 Copyright

Copyright, not privacy, motivated Reddit to take down photos of nude celebrities

This VentureBeat piece with Reddit CEO Yishan Wong brings up a number of interesting facts concerning Reddit in the wake of its receiving an additional $50 million funding round. One of those pieces of interesting information concerns Reddit’s decision to take down a subreddit devoted to the sharing of recently-leaked celebrity nude photos.

Says Wong:

If there’s any confusion: [Reddit] did not shut down /r/TheFappening due to content linking to nude celebrity photos. The subreddit was shut down because users were reposting content already taken down due to valid DMCA requests, and because spammers began posting links to the images hosted on their own pay-per-click sites, or sites intended to spread malware.

We can’t read too much from this comment, but it does implicate that the dignitary interests of the celebrities involved did not motivate Reddit to do the right thing. Instead, the risk of copyright liability (or, more precisely, the risk that DMCA safe harbor protection may be eliminated) was a stronger motivation.

Evan Brown is an attorney in Chicago advising clients on matters dealing with technology, the internet and new media.

August 5, 2014 Uncategorized

Microsoft letter to GitHub over DRM-free music software is not the first copyright-ironic action against an intermediary

TorrentFreak has reported that Microsoft demanded that GitHub take the code repository of an app that provides access to unprotected Xbox Music tracks. Some are calling it ironic, given that Microsoft is offering access to DRM-free music through its API.

The situation is reminiscent (though not legally identical) to the weirdness we observed way back in 2006 when YouTube asked TechCruch to take down a tool that allowed people to download video clips. We recognized early on that YouTube was a copyright renegade. So it was surprising that it would take such an aggressive tactic toward purveyors of software that would make use of copyrighted works easier.

The Microsoft of today is certainly not the YouTube of 2006. So naturally its interests are different. But comparing the two scenarios yields the common conundrum of how one company that wants to more smoothly make content available deals with other technologies and platforms that do the same thing, but cut out the main monetizing opportunity.

It could be a phenomenon of copyright’s outdatedness. Both YouTube and Microsoft took action against others who were distributing technologies that touched on infringement by means of making copies of the works. That will likely remain an important protection under copyright law even after meaningful reform. But what is really at stake is the right to access content. If that were a meaningful right under the Copyright Act, companies would be less likely to take enforcement actions that appear on the surface to be ironic.

Evan Brown is an attorney in Chicago advising clients on matters dealing with copyright, technology, the internet and new media.

July 24, 2014 Copyright

When is news reporting fair use under copyright law?

Blogger claims fair use supports his challenge to DMCA takedown of YouTube video. But “news reporting” aspect of fair use can be tricky.

An embattled California pastor sent a DMCA takedown notice to YouTube over a video clip that a blogger used “to report accurately the relationship” between two organizations. The blogger sent a counternotification and explained that he believes copyright fair use protects him against the takedown (and apparently against infringement as well).

The blogger invokes, among other things, the news reporting aspect of fair use, which one finds set forth in Section 107 of the Copyright Act. A recent fair use case, Swatch Group Management Services Ltd. v. Bloomberg, 742 F. 3d 17 (2d Cir. 2014) might shed some interesting light on how news reporting plays into the analysis. In that case, the court found that defendant was protected by fair use when it distributed an audio recording of a company’s earnings call. Unlike many fair use cases, in which the analysis under the first factor (purpose and character of the use) becomes a question of whether the subsequent use is “transformative,” the court observes the following:

In the context of news reporting and analogous activities … the need to convey information to the public accurately may in some instances make it desirable and consonant with copyright law for a defendant to faithfully reproduce an original work rather than transform it.

A defendant may in some circumstances provide transformative material along with the faithful reproduction of an original work. But the absence of that transformative material will not disqualify a defendant from showing fair use:

[B]y disseminating not just a written transcript or article but an actual sound recording, [defendant] was able to convey with precision not only what [plaintiff’s] executives said, but also how they said it. This latter type of information may be just as valuable … as the former, since a speaker’s demeanor, tone, and cadence can often elucidate his or her true beliefs far beyond what a stale transcript or summary can show.

So we see that the news reporting aspect of fair use can be conceptually separated from transformative use.

There is a slippery slope risk here, and the court recognized that. It cited to the Supreme Court’s Harper & Row decision to observe that “[t]he promise of copyright would be an empty one if it could be avoided merely by dubbing the infringement a fair use ‘news report'”. In this case, however, the “independent informational value inherent in a faithful recording” carried the day. From this we see a rule or guide: use of a piece of content is more likely to be newsworthy if the piece of content itself, and not just the raw information within the content, is a news event.

Evan Brown is an attorney in Chicago advising clients on matters dealing with technology, the internet and new media.

July 15, 2014 Copyright, DMCA

DMCA’s protection of copyright management information applied to non-electronic works

The Digital Millennium Copyright Act (DMCA) provides safe harbors from copyright infringement liability for online service providers (17 U.S.C. 512) and makes it unlawful to circumvent technological measures that effectively control access to copyrighted works (17 U.S.C. 1201). A lesser-known (and lesser-litigated) provision of the DMCA (17 U.S.C. 1202) makes it illegal to intentionally remove or alter any copyright management information or to distribute copies of works knowing that copyright information has been removed or altered without authority of the copyright owner or the law. “Copyright management information” includes information conveyed in connection with copies of the work, such as the title and the name of the author.

A recent case from federal court in Florida considered whether this regulation of copyright management information in the DMCA applies only to electronic works intended for distribution over the internet, or whether it applies to more traditional works such as hard copy technical drawings. The court interpreted the DMCA broadly to apply to all kinds of works, whether on the internet or not.

Plaintiff alleged that defendant violated the DMCA by distributing copies of plaintiff’s drawings “knowing that [plaintiff’s] name had been removed therefrom and/or that another entity’s name had been added thereto.” Defendant argued that plaintiff failed to state a claim for a violation of the DMCA because the DMCA only applies to “technological” infringement. Defendant cited to Textile Secrets Intl’l, Inc. v. Ya–Ya Brand, Inc., 524 F.Supp.2d 1184 (C.D.Cal.2007), which found that § 1202(b) “was [not] intended to apply to circumstances that have no relation to the Internet, electronic commerce, automated copyright protections, or management systems, public registers, or other technological measures or processes as contemplated in the DMCA as a whole.” To read it otherwise, the court in that case reasoned, would contradict the “legislative intent behind the DMCA to facilitate electronic and Internet commerce.”

In this case, however, the court noted that other courts, focusing on the plain language of the DMCA, have held differently, and approved the DMCA’s application to non-technological contexts. See Murphy v. Millennium Radio Group LLC, 650 F.3d 295 (3d Cir.2011); Agence France Presse v. Morel, 769 F.Supp.2d 295 (S.D.N.Y.2011). Although in this case, as in Murphy, the legislative history of the DMCA was consistent with defendant’s interpretation, it did not actually contradict it. Instead, Section 1202(b) simply established a cause of action for the removal of, among other things, the name of the author of a work when it has been conveyed in connection with copies of the work.

So the court, as it found it was required to do, considered the statute’s plain meaning before it considered its legislative history. Under that analysis, it held that plaintiff’s allegations were sufficient to a state a claim for violation of the DMCA.

Roof & Rack Products, Inc. v. GYB Investors, LLC, 2014 WL 3183278 (S.D. Fla. July 8, 2014)

Evan Brown is an attorney in Chicago advising clients on matters dealing with copyright, technology, the internet and new media.

June 30, 2014 Copyright

Is the Aereo decision a setback for innovation?

One of the big questions preceding the Supreme Court’s decision in the Aereo case earlier this week was whether a holding against Aereo would put cloud services into such a legally precarious position that the innovation and investment climate would chill. While the decision clearly makes Aereo’s use of its technology illegal, one should not be too quick to foretell a drastic impact on all hosted services. Here are some reasons why.

What cloud?

Let’s be clear about what we mean by “the cloud” in this context. Aereo’s technical model – which the court found to infringe copyright – captured over-the-air television content using one tiny antenna per customer, transcoded that content into one copy per customer, which Aereo stored and then streamed on-demand to the customer. The court found that model bore an “overwhelming likeness to the cable companies targeted by the [1976 Copyright Act]” to an extent that Aereo was “for all practical purposes a traditional cable system.” Aereo’s technological attempts such as the one-copy-per-customer method that it used to distinguish itself from traditional cable services were immaterial to the court. Aereo looked like a cable company, so the court treated it as one, with all the copyright consequences that go along with that status.

Aereo was a cloud service inasmuch as it stored the TV content and served it to its users when those users initiated the performances. It was the cable-like functions that got it into trouble, not necessarily the cloud-provider functions. That arguably leaves the rest of what we consider cloud services – online collaboration tools, centralized communications systems, most hosted applications, and the like – outside the scope of the court’s decision. Most software-as-a-service models, whether to the consumer or at the enterprise level, are unlike cable systems and thus likely stand clear of the sweep of the Aereo sickle.

The technology could live on.

One must also be sure to recognize that the court’s decision did not kill the technology altogether, but instead killed the use of the technology in the hands of one who does not have ownership or license to the content being delivered. Since the court found that Aereo’s service was “substantially similar” to cable systems, Aereo, its successors, or other players in the space could look to monetize the technology while paying the compulsory licenses that Section 111 of the Copyright Act spells out in dizzying complexity. Or the broadcasters and other content stakeholders could acquire Aereo-like technology and use it to supplement the other means of content delivery currently at play. In either scenario, the needs for investment and innovation in providing infrastructure (as well as the need for clarity on network neutrality) remain firmly intact.

The real likely effect.

This is not to say that Aereo will have no effect on development of technology in areas outside the particular facts of the case. The court’s decision expands the class of online intermediaries who may be liable for direct copyright infringement. In that respect, the case differs from other important technology-provider copyright cases like the Betamax case, Grokster and the Cablevision case. In those cases, the main question before the courts was whether the providers were secondarily liable for the infringement committed by their users. In Aereo, however, the question was whether Aereo itself was liable for infringement committed by providing the technology to others. The Supreme Court held that Aereo was a direct infringer because its functionality so closely resembled a cable company.

So the court has given copyright plaintiffs some new, additional angles to consider when pursuing infringement litigation against technology providers. Does the technology so resemble the technical model of a cable delivery system, particularly from the perspective of the end user, such that it de facto publicly performs the works delivered by the system? If so, then the Aereo test forbids it. Moreover, the case fuzzies the relatively bright line that began to be drawn almost 20 years ago with Religious Technology Center v. Netcom, requiring that for an internet intermediary to be liable for direct infringement, it need undertake some volitional conduct in furtherance of the infringement. That fuzziness will no doubt embolden some plaintiffs who otherwise would not have seen the potential for a cause of action against future defendant-innovators.

In reality, few platforms are likely to actually get “Aereoed” in litigation. The ones at greatest risk will be those that facilitate access to streaming content provided by others. But the fact that ultimate liability may not lie against a provider will likely do little to stop aggressive copyright plaintiffs from trying out the theory against all forms of remote storage providers. That’s the problem Justice Scalia identified in his dissent when he said the decision “will sow confusion for years to come.” Let’s hope that’s mostly an overstatement.

Evan Brown is an attorney in Chicago advising clients on matters dealing with technology, the internet and new media.

May 27, 2014 Copyright

No infringement means no injunction in software dispute

Former members of a limited liability company, who participated in the development of four pieces of software while a part of the company, sued the LLC and its remaining members for copyright infringement. Defendants moved for summary judgment, arguing that plaintiffs’ infringement claims must fail because defendants had not used the allegedly copyrighted software outside of the licensing agreements the LLC signed while plaintiffs were still with the company. The court granted defendants’ summary judgment motion.

Plaintiffs agreed that the software had not been used outside the license agreements with companies the LLC had entered while plaintiffs were with the company. But plaintiffs still sought injunctive relief with respect to their infringement claims.

To demonstrate copyright infringement, plaintiffs were required to prove “(1) ownership of a valid copyright, and (2) copying of constituent elements of the work that are original.” Feist Publ’ns, Inc. v. Rural Tel. Serv. Co., 499 U.S. 340, 362, 111 S.Ct. 1282, 113 L.Ed.2d 358 (1991)). In this case, plaintiffs essentially conceded that the second element of the Feist test was not met.

The court cited Arista Records, LLC v. Doe 3, 604 F.3d 110, 117 (2d. Cir.2010)) to note that in the second Feist element, “the word copying is shorthand for the infringing of any of the copyright owner’s five exclusive rights described in 17 U.S.C. § 106”. Those exclusive rights allow the owner to: (1) reproduce the copyrighted work; (2) prepare derivative works based upon the copyrighted work; (3) distribute copies of the copyrighted work; (4) perform the work publicly; and (5) display the copyrighted work. Because plaintiffs conceded that defendants had not used the software outside of the license agreements with its customers that were made while plaintiffs were still a part of the LLC, defendants had not infringed on plaintiffs purported exclusive rights.

Plaintiffs nevertheless claimed that they were entitled to injunctive relief to prevent defendants’ potential future use of the copyrighted software. Plaintiffs were required to show that: (1) they had suffered an irreparable injury; (2) that remedies at law were inadequate to compensate that injury; (3) that the balance of hardships warranted a remedy in equity in favor of plaintiffs; and (4) that the public interest would not be disserved by a permanent injunction.

Here, plaintiffs conceded that they had not suffered an injury – the copyrights had not been infringed. Instead, plaintiffs were arguing for a prospective injunction to prevent defendants from infringing upon a copyright for which there was no evidence defendants intended to infringe. The court denied the injunction, holding that a prospective injunction could be entered only on the basis of current, ongoing conduct that threatened future harm.

Brightharbour Consulting, LLC v. Docuconsulting, LLC, 2014 WL 1415186 (N.D.Ga. April 14, 2014)

Evan Brown is an attorney in Chicago, advising clients in technology transactions, intellectual property disputes, and other matters involving the internet and new media.

Court sides with software developer in open source dispute

Case provides rare opportunity to get court’s analysis of GPL.

Plaintiff wrote an XML parser and made it available as open source software under the GPLv2. Defendant acquired from another vendor software that included the code, and allegedly distributed that software to parties outside the organization. According to plaintiff, defendant did not comply with the conditions of the GPL, so plaintiff sued for copyright infringement.

Defendants moved to dismiss for failure to state a claim. The court denied the motion.

Plaintiff claimed that defendant directly infringed its copyright by distributing the software without any attribution to plaintiff, without plaintiff’s copyright notice, without reference to plaintiff’s source code, and without any offer to convey the source code.

Defendant argued that it did not violate the terms of the GPL because its “distribution” of the software was merely internal, mainly to its own financial advisors. Accordingly, defendant argued, the requirements under the GPL to, among other things, attribute plaintiff and provide the source code were not triggered.

The court rejected defendant’s argument, looking to the allegations in the complaint that defendant distributed the software to it vendors in India, as well as providing it to “thousands of non-employee financial advisors.”

Despite the popularity of open source software, not a lot of courts have interpreted and applied the provisions of open source licenses. This case — if it does not settle — provides a rare opportunity to see serious legal treatment of the oft-used GPL.

XimpleWare Corp. v. Versata Software, Inc., 2014 WL 490940 (N.D.Cal. February 4, 2014)

Evan Brown is a Chicago technology and intellectual property attorney helping software vendors and customers alike navigate the many issues pertaining to technology development and licensing.

Unjust enrichment claim over unauthorized use of software was not preempted by the Copyright Act

The Copyright Act is a federal law, and is drafted to “preempt” state laws that purport to give individuals rights that are “equivalent” to rights granted under the Copyright Act. The purpose of this preemption is to displace the effect of any equivalent state law, so that the federal framework gets to deal exclusively with copyright.

So when a plaintiff goes to court suing for copyright infringement and also adds a state law claim against the defendant based on the same underlying facts, defendants routinely move to dismiss that state law claim as preempted by the Copyright Act.

That is what happened in a recent case involving a plaintiff software developer who filed a copyright infringement case against a company for whom he had done some work. He added an “unjust enrichment” claim based on state law, which defendants moved to dismiss. But the court denied the motion, holding that in this situation, the unjust enrichment claim was not dealing with rights that were equivalent under the Copyright Act.

Plaintiff’s unjust enrichment claim was based on the fact that he had not been paid any money for the development work he provided to defendants. In other words, he delivered the copyrighted software, which defendants used without paying him. Sounds a lot like copyright infringement, doesn’t it? Or, more precisely, it sounds like the rights he was claiming were equivalent to those provided under the Copyright Act.

But the court held otherwise, namely, that plaintiff had pled an “extra element” that rendered his unjust enrichment claim to not be equivalent to rights under the Copyright Act.

The court drew an important distinction within the doctrine of unjust enrichment, between “implied-in-law” (quasi-) contracts, and “implied in fact” contracts. An implied-in-fact contract claim passes the threshold of having an “extra element” that defeats a preemption challenge, while an implied-in-law contract does not.

An implied-in-law contract is a “fictional” contract created by a court for equitable, not contractual, purposes. It is not an actual contract, but is a legal substitute formed to impose equity between two parties. An implied-in-fact contract, on the other hand, is indeed a contract that is agreed to by non-verbal conduct, rather than explicit words.

Infringement is the unauthorized use of a work, and a court applying an implied-in-law contract would simply be stepping in to remedy an injustice of that infringement. That is why an unjust enrichment claim based on an implied-in-law contract would be preempted. But the implied-in-fact contract has more to it – actual conduct (a factual reality) that is more than just the conduct of the infringement that took place. That is why an implied-in-fact contract claim of unjust enrichment passes the no-preemption test.

(Compare this to the 2010 case of Christen v. Iparadigms that dealt with Turnitin.com.)

Mahavisno v. Compendia Bioscience, Inc., 2014 WL 340369 (E.D.Mich. January 30, 2014)