<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Derivative Liability Archives - Technology &amp; Marketing Law Blog</title>
	<atom:link href="https://blog.ericgoldman.org/archives/category/derivative-liability/feed" rel="self" type="application/rss+xml" />
	<link>https://blog.ericgoldman.org/archives/category/derivative-liability</link>
	<description></description>
	<lastBuildDate>Wed, 20 May 2026 16:37:36 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
<site xmlns="com-wordpress:feed-additions:1">59487357</site>	<item>
		<title>The YOLO Remand Shows Why the 9th Circuit Should Stop Carving Up Section 230&#8211;Bride v. Snap</title>
		<link>https://blog.ericgoldman.org/archives/2026/05/the-yolo-remand-shows-why-the-9th-circuit-should-stop-carving-up-section-230-bride-v-snap.htm</link>
					<comments>https://blog.ericgoldman.org/archives/2026/05/the-yolo-remand-shows-why-the-9th-circuit-should-stop-carving-up-section-230-bride-v-snap.htm#respond</comments>
		
		<dc:creator><![CDATA[Eric Goldman]]></dc:creator>
		<pubDate>Wed, 20 May 2026 16:37:36 +0000</pubDate>
				<category><![CDATA[Content Regulation]]></category>
		<category><![CDATA[Derivative Liability]]></category>
		<category><![CDATA[Licensing/Contracts]]></category>
		<category><![CDATA[Marketing]]></category>
		<guid isPermaLink="false">https://blog.ericgoldman.org/?p=28908</guid>

					<description><![CDATA[<p>This is the remand of the troubling Ninth Circuit Section 230 decision in Bride v. YOLO. As you may recall, the plaintiffs claims that YOLO made statements about its content moderation and the safety of its environment that the plaintiffs...</p>
<p>The post <a href="https://blog.ericgoldman.org/archives/2026/05/the-yolo-remand-shows-why-the-9th-circuit-should-stop-carving-up-section-230-bride-v-snap.htm">The YOLO Remand Shows Why the 9th Circuit Should Stop Carving Up Section 230&#8211;Bride v. Snap</a> appeared first on <a href="https://blog.ericgoldman.org">Technology &amp; Marketing Law Blog</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><a href="https://blog.ericgoldman.org/wp-content/uploads/2026/02/IMG_2022.jpg"><img fetchpriority="high" decoding="async" class="alignright size-medium wp-image-28570" src="https://blog.ericgoldman.org/wp-content/uploads/2026/02/IMG_2022-300x300.jpg" alt="" width="300" height="300" srcset="https://blog.ericgoldman.org/wp-content/uploads/2026/02/IMG_2022-300x300.jpg 300w, https://blog.ericgoldman.org/wp-content/uploads/2026/02/IMG_2022-1024x1020.jpg 1024w, https://blog.ericgoldman.org/wp-content/uploads/2026/02/IMG_2022-150x150.jpg 150w, https://blog.ericgoldman.org/wp-content/uploads/2026/02/IMG_2022-768x765.jpg 768w, https://blog.ericgoldman.org/wp-content/uploads/2026/02/IMG_2022-1536x1529.jpg 1536w, https://blog.ericgoldman.org/wp-content/uploads/2026/02/IMG_2022-2048x2039.jpg 2048w" sizes="(max-width: 300px) 100vw, 300px" /></a>This is the remand of the troubling <a href="https://blog.ericgoldman.org/archives/2024/08/when-it-comes-to-section-230-the-ninth-circuit-is-a-chaos-agent-estate-of-bride-v-yolo.htm">Ninth Circuit Section 230 decision in Bride v. YOLO</a>. As you may recall, the plaintiffs claims that YOLO made statements about its content moderation and the safety of its environment that the plaintiffs believe were not true; and based on that, YOLO should be liable for users&#8217; physical and emotional harms. In its prior ruling, the Ninth Circuit said that Section 230 doesn&#8217;t apply to promise-based claims. That ruling allowed the plaintiffs to proceed against YOLO even though YOLO&#8217;s challenged statements clearly never made any enforceable promises.</p>
<p>YOLO stopped paying its lawyers and stopped fighting in court, so it defaulted in the case. That makes me wonder who can pay off any judgments against YOLO if YOLO is already gone?</p>
<p>Either way, the plaintiffs are proceeding without any opposition from YOLO. And yet&#8230;their case is so unmeritorious that the plaintiffs can&#8217;t get an unopposed default judgment. Obviously defective cases are what the Ninth Circuit thought was worth wrecking Section 230 to preserve&#8230;?</p>
<p>In the past 2 months, the district court has twice rejected a default judgment:</p>
<p><strong>Bride v. Snap, Inc., 2026 WL 855148 (C.D. Cal. March 16, 2026)</strong></p>
<p>In the March ruling, the court rejects class certification. The court flags numerous problems with class formation:</p>
<ul>
<li>if the defendant has defaulted, can a class claim really be adjudicated properly?;</li>
<li>The class claims 26M users, but the plaintiffs based the numbers partially on vibes;</li>
<li>the class includes non-bullied users and, remarkably, the alleged bullies;</li>
<li>the named plaintiff&#8217;s suicide-based claim materially differs from other claims of bullying;</li>
<li>the plaintiff lawyers&#8217; interest in the case seems to be waning (maybe because YOLO is judgment-proof?);</li>
<li>&#8220;What is “bullying” in this context? What are “harassing messages,” “objectionable content,” and “inappropriate usage”? Who are “abusive users”? How severe or frequent does a user&#8217;s conduct have to be for Yolo to be required to take action?&#8221;; and more.</li>
</ul>
<p>Substantively, the court questions the claims&#8217; merits:</p>
<blockquote><p>here are Yolo&#8217;s statements that Plaintiffs challenge in this case as fraudulent misrepresentations:</p>
<p>• “YOLO is for positive feedback only. No bullying. If you send harassing messages to our users, your identity will be revealed.”</p>
<p>• “YOLO has no tolerance for objectionable content or abusive users. You&#8217;ll be banned for any inappropriate usage.”</p>
<p>• “Be kind, respectful, show compassion with other users, otherwise you will be banned.”</p>
<p>The court is hard pressed to conclude that the TAC adequately alleges that, as to element one, those statements were plausibly false promises to future bullying victims (as opposed to threats to bullies); that, as to element two, Yolo knew that by making these statements it was making false promises to future victims; as to element three, that Yolo intended to induce reliance from future victims that Yolo would take affirmative action if bullying, harassment, inappropriate usage, unkind, disrespectful, or noncompassionate behavior occurred; or, as to element four, that that any reliance Plaintiffs exhibited on these statements as promises that Yolo would take such action was justified.</p></blockquote>
<p>The court adds: &#8220;there is a serious question regarding whether the statements challenged as misrepresentations are puffery.&#8221; Yes, claims about on-site safety are often puffery. All of this was obvious from the face of the complaint.</p>
<p>In other words, the district court is flummoxed by the aftermath of the venerable Ninth Circuit Section 230 switcheroo. The Ninth Circuit negated Section 230 for promise-based claims, but the &#8220;promises&#8221; here were never actually promises and thus could never form the proper basis of a claim. Thus, reviving the case gave false hope to the plaintiffs. The Ninth Circuit has made similar 230 switcheroos at least a dozen times, each time benefiting no one.</p>
<p>The court continues:</p>
<blockquote><p>Yolo&#8217;s First Amendment defense also comes into play here. “Content moderation by social media platforms is generally considered expressive activity and is protected under the First Amendment.”&#8230;Consider, for example, a scenario in which this case had proceeded through discovery and Yolo contended that it reviewed some of the messages at issue and had determined that, for whatever reason, those messages did not violate Yolo&#8217;s community standards such that they should be taken down. The court&#8217;s review of that decision could implicate the First Amendment.</p></blockquote>
<p>I have raised the same First Amendment concerns for many other cases against social media, including the social media addiction cases.</p>
<p>The court bottom-lines it:</p>
<blockquote><p>at this stage of the proceedings, Plaintiffs have presented insufficient legal authority and evidence for the court to find it is appropriate to exercise its discretion to grant the relief Plaintiffs seek.</p></blockquote>
<p><strong>Bride v. Snap Inc., 2026 U.S. Dist. LEXIS 104978 (C.D. Cal. May 11, 2026)</strong></p>
<p>Following the March ruling, the plaintiffs tried to address the judge&#8217;s concerns and sought class certification and summary judgment a second time. Their motion remains unopposed, yet it strikes out a second time.</p>
<p><em>Class Formation: Typicality</em></p>
<p>&#8220;The new class definition still includes people who were not bullied and the bullies themselves, and Plaintiffs are not typical of these groups or adequate to represent them.&#8221;</p>
<p>Also, &#8220;the court is concerned is that Ms. Bride would be so preoccupied with a wrongful death claim that she believes she (and she alone) has and its significant associated damages that she would give short shrift to her role, or be distracted in her role, as class representative on the class&#8217;s claims for misrepresentation and violation of state consumer protection statutes.&#8221;</p>
<p><em>Class Formation: Commonality/Predominance</em></p>
<blockquote><p>Plaintiffs allege Yolo made misrepresentations including, &#8220;No bullying. If you send harassing messages to our users, your identity will be revealed,&#8221;  and &#8220;YOLO has no tolerance for objectionable content or abusive users. You&#8217;ll be banned for any inappropriate usage.&#8221; But for these statements to be false, a trier of fact would have to consider a host of questions regarding each individual situation: what is &#8220;bullying&#8221;? What are &#8220;harassing messages,&#8221; &#8220;objectionable content,&#8221; and &#8220;inappropriate usage&#8221;? Who are &#8220;abusive users&#8221;? How severe or frequent does a user&#8217;s conduct have to be for Yolo to be required to take action? These individualized issues go to the heart of Plaintiffs&#8217; misrepresentation claims&#8230;.</p>
<p>unlike statements like &#8220;this moisturizer is oil-free,&#8221; or &#8220;this supplement promotes healthy joints in dogs,&#8221; Yolo&#8217;s alleged misrepresentations add a critical predicate clause—one that indicates the representation will be true only in certain circumstances. In other words, &#8220;we will ban you&#8221; or &#8220;we will reveal your identity&#8221; might be sufficiently analogous to &#8220;this moisturizer is oil-free&#8221;; what sets this case apart from a case where a reliance inference might be appropriate is the portion of Yolo&#8217;s representations that tells users when (and only when) Yolo&#8217;s promises will be true. Those clauses—such as &#8220;if you send harassing messages&#8221;; &#8220;for any inappropriate usage&#8221;; and if you are not &#8220;kind, respectful&#8221; or do not &#8220;show compassion with other users&#8221;—involve individualized issues that make the reliance inference Plaintiffs seek inappropriate.</p></blockquote>
<p>The court seems to be saying that if a marketing representation says &#8220;if you do X actions, you will get Y result,&#8221; it will hinder class formation because the examination of whether an individual plaintiff did the predicate X actions would require individualized determinations.</p>
<p><em>No Substantive Merit</em></p>
<blockquote><p>The &#8220;what is not allowed&#8221;-type statements in this case are &#8220;YOLO has no tolerance for objectionable content or abusive users,&#8221; &#8220;YOLO is for positive feedback only. No bullying,&#8221; and &#8220;[b]e kind, respectful, show compassion with other users.&#8221; These &#8220;statements of policy&#8221; that &#8220;simply describe what content is allowed on&#8221; YOLO cannot &#8220;be considered &#8216;false&#8217; for purposes of Plaintiffs&#8217; claims.&#8221; [cite to <a href="https://blog.ericgoldman.org/archives/2025/12/district-court-again-rejects-plaintiffs-attempts-to-manufacture-common-law-notice-and-takedown-duties-bogard-v-tiktok.htm">Bogard v. TikTok</a>]</p>
<p>The &#8220;we remove&#8221; statements in this case are &#8220;[y]ou&#8217;ll be banned for any inappropriate usage,&#8221; &#8220;[i]f you send harassing messages to our users, your identity will be revealed,&#8221; and &#8220;otherwise you will be banned.&#8221; Plaintiffs&#8217; argument that these statements are actionable because they say exactly what Yolo will do is only half the picture—Yolo said they would do those things when something else happened. Here, like Bogard, the vagueness of the critical threshold criteria renders the alleged misrepresentations too vague to be enforced. The Bogard court commented that &#8220;[i]t is difficult to imagine standards more subjective than &#8216;meaningful&#8217; and &#8216;accurate enough.'&#8221; In the court&#8217;s view, &#8220;inappropriate usage,&#8221; &#8220;harassing messages,&#8221; &#8220;bullying,&#8221; and being not &#8220;kind, respectful, [or] show[ing] compassion with other users,&#8221; are equally subjective&#8230;.</p>
<p>in each of the alleged misrepresentations, it is clear that Yolo is speaking directly to bullies, telling them that if they engage in certain disapproved behavior, &#8220;your identity will be revealed&#8221; or &#8220;you will be banned.&#8221; There is no indication that Yolo is speaking to, or making any representation to, anyone else, including the victims of any bullying, harassment, or unkind, disrespectful, or noncompassionate messages. The court finds insufficient factual allegations supporting the notion that Yolo meant for their threats to bullies—made speaking directly to bullies in the &#8220;you&#8221; voice—to be taken by victims as enforceable promises that they, people to whom Yolo was not speaking, could rely on&#8230;.</p>
<p>Finally, the court finds insufficiently plausible Plaintiffs&#8217; allegation that Plaintiffs&#8217; reliance on Yolo&#8217;s statements—by using the app believing Yolo would protect them on it—was justifiable.</p></blockquote>
<p>This time, the district court dismisses the case, so it&#8217;s now appealable to the Ninth Circuit&#8211;where, presumably, the plaintiffs&#8217; filings will remain unopposed by the nonexistent YOLO. Will the plaintiffs appeal? I presume yes. Will the Ninth Circuit recognize how its bad prior ruling exacerbated this mess? <img src="https://s.w.org/images/core/emoji/16.0.1/72x72/1f937-200d-2642-fe0f.png" alt="🤷‍♂️" class="wp-smiley" style="height: 1em; max-height: 1em;" /></p>
<p>This case involves many tragedies, including the litigation itself. This lawsuit never should have been brought, and it should not have been revived on appeal. It shows the revictimization inherent in the Ninth Circuit 230 switcheroo. It set up the victims to waste extra time, money, and emotional energy to reach the always inevitable conclusion that this particular lawsuit isn&#8217;t the proper way to redress the victims&#8217; harms.</p>
<p>The post <a href="https://blog.ericgoldman.org/archives/2026/05/the-yolo-remand-shows-why-the-9th-circuit-should-stop-carving-up-section-230-bride-v-snap.htm">The YOLO Remand Shows Why the 9th Circuit Should Stop Carving Up Section 230&#8211;Bride v. Snap</a> appeared first on <a href="https://blog.ericgoldman.org">Technology &amp; Marketing Law Blog</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://blog.ericgoldman.org/archives/2026/05/the-yolo-remand-shows-why-the-9th-circuit-should-stop-carving-up-section-230-bride-v-snap.htm/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">28908</post-id>	</item>
		<item>
		<title>WorldStarHipHop Gets Section 230 Dismissal&#8211;Eizenga v. MediaLab</title>
		<link>https://blog.ericgoldman.org/archives/2026/05/worldstarhiphop-gets-section-230-dismissal-eizenga-v-medialab.htm</link>
					<comments>https://blog.ericgoldman.org/archives/2026/05/worldstarhiphop-gets-section-230-dismissal-eizenga-v-medialab.htm#respond</comments>
		
		<dc:creator><![CDATA[Eric Goldman]]></dc:creator>
		<pubDate>Sun, 17 May 2026 16:30:31 +0000</pubDate>
				<category><![CDATA[Content Regulation]]></category>
		<category><![CDATA[Derivative Liability]]></category>
		<guid isPermaLink="false">https://blog.ericgoldman.org/?p=28898</guid>

					<description><![CDATA[<p>The court describes the video in question (as alleged): an anonymous social media account and online &#8220;persona&#8221; known as Rain Drops Media (&#8220;Rain Drops&#8221;) published a defamatory video falsely suggesting that Eizenga was an abusive partner who battered Monroe Capri...</p>
<p>The post <a href="https://blog.ericgoldman.org/archives/2026/05/worldstarhiphop-gets-section-230-dismissal-eizenga-v-medialab.htm">WorldStarHipHop Gets Section 230 Dismissal&#8211;Eizenga v. MediaLab</a> appeared first on <a href="https://blog.ericgoldman.org">Technology &amp; Marketing Law Blog</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>The court describes the video in question (as alleged):</p>
<blockquote><p>an anonymous social media account and online &#8220;persona&#8221; known as Rain Drops Media (&#8220;Rain Drops&#8221;) published a defamatory video falsely suggesting that Eizenga was an abusive partner who battered Monroe Capri Bryant (&#8220;Bryant&#8221;), a young social media influencer. The video in question consists of a collage of other social media posts and clips from Bryant&#8217;s live-stream featuring Plaintiff and Bryant together along with a caption that reads, &#8220;Woman was punched and assaulted by her boyfriend, she claims he still loves her and insists they&#8217;re &#8216;good&#8217; . . . .&#8221; In the video, one of Bryant&#8217;s eyes is severely bruised, and Plaintiff can be seen attempting to kiss Bryant on the temple. The video has been viewed roughly four million times on the social media platform X&#8230;</p>
<p>WorldStar reposted Rain Drops&#8217; video to its social media accounts (including<br />
Facebook, Instagram, and worldstarhiphop.com) with a slightly modified caption that now read: &#8220;CYCLE OF ABUSE: Woman With A Black Eye Goes Live With Boyfriend Who Allegedly Punched Her, Insisting &#8216;He Loves Me&#8217; And &#8216;We&#8217;re Good&#8217; As He Kisses Her On Camera.&#8221; WorldStar also &#8220;tagged&#8221; the video with three identifiers: (1) &#8220;domestic violence,&#8221; (2) &#8220;Relationships,&#8221; and (3) &#8220;TikTok.&#8221; Plaintiff does not allege that Defendant created or otherwise altered Rain Drops&#8217; video.</p></blockquote>
<p><a href="https://blog.ericgoldman.org/wp-content/uploads/2026/02/IMG_2022.jpg"><img decoding="async" class="alignright size-medium wp-image-28570" src="https://blog.ericgoldman.org/wp-content/uploads/2026/02/IMG_2022-300x300.jpg" alt="" width="300" height="300" srcset="https://blog.ericgoldman.org/wp-content/uploads/2026/02/IMG_2022-300x300.jpg 300w, https://blog.ericgoldman.org/wp-content/uploads/2026/02/IMG_2022-1024x1020.jpg 1024w, https://blog.ericgoldman.org/wp-content/uploads/2026/02/IMG_2022-150x150.jpg 150w, https://blog.ericgoldman.org/wp-content/uploads/2026/02/IMG_2022-768x765.jpg 768w, https://blog.ericgoldman.org/wp-content/uploads/2026/02/IMG_2022-1536x1529.jpg 1536w, https://blog.ericgoldman.org/wp-content/uploads/2026/02/IMG_2022-2048x2039.jpg 2048w" sizes="(max-width: 300px) 100vw, 300px" /></a>WorldStarHipHop defeats the lawsuit per Section 230.</p>
<p><em>ICS Provider</em>. The court summarizes the general rule: &#8220;websites that allow third-party users to submit or upload content are providers of internet computer services.&#8221; WorldStarHipHop qualifes:</p>
<blockquote><p>Plaintiff does not allege that Defendant independently generates any content whatsoever. Rather, Plaintiff alleges that Defendant merely reposted the challenged content without editing the video itself</p></blockquote>
<p>The court seems to be conflating this factor with the other two. Plus, if WorldStarHipHop is posting to third-party social media like Facebook and Instagram, it might be more accurately characterized as an ICS user, not provider.</p>
<p><em>Publisher/Speaker Claim</em>. Plaintiff conceded this.</p>
<p><em>Third-Party</em> <em>Content</em>. The court quickly jumps to <a href="https://blog.ericgoldman.org/archives/2008/04/roommatescom_de_1.htm">the Roommates.com exceptions</a>. It defines the rule as &#8220;a website operator may be held liable for third-party content where (1) it &#8220;substantively alters&#8221; the content and where (2) the substantive alteration is &#8220;directly involved in the alleged illegality.&#8221;&#8221; The court continues:</p>
<blockquote><p>The bar for &#8220;substantive alteration&#8221; is high. To start, the test requires something above and beyond the &#8220;exercise of a publisher&#8217;s traditional editorial functions—such as deciding whether to publish, withdraw, postpone or alter content.&#8221; Nor is it enough for a plaintiff to allege that a defendant promoted content through the use or creation of algorithms, tags, video thumbnails, summaries, posts, or animations.</p></blockquote>
<p>WorldStarHipHop doesn&#8217;t meet these standards:</p>
<blockquote><p>Plaintiff alleges that Defendant made just three changes to Rain Drops&#8217; original video: (1) adding &#8220;CYCLE OF ABUSE&#8221; to the caption, (2) adding &#8220;allegedly&#8221; to the caption, and (3) tagging the video with a &#8220;domestic abuse&#8221; identifier. Those minor changes—none of which altered the video itself—fall far short of the allegations required to make out substantive alteration. [cite to <a href="https://blog.ericgoldman.org/archives/2025/02/section-230-immunizes-onlyfans-for-user-uploaded-video-again-doe-v-fenix.htm">Doe v. Fenix</a> and <a href="https://blog.ericgoldman.org/archives/2022/05/section-230-helps-craigslist-defeat-sex-trafficking-case-lh-v-marriott.htm">L.H. v. Marriott</a>.]&#8230;The minor, paratextual modifications at issue here fall far short of the more substantial alterations courts found wanting in Fenix Int&#8217;l and L.H&#8230;.</p>
<p>Defendant created nothing. It reposted a preexisting video and adopted a preexisting caption almost word-for-word. The addition of the leading phrase &#8220;CYCLE OF ABUSE&#8221; and the &#8220;domestic violence&#8221; tag at most &#8220;augment&#8221; or &#8220;develop[] by inference&#8221; the alleged illegality already at issue in the original video.</p></blockquote>
<p>The court distinguishes the problematic <a href="https://blog.ericgoldman.org/archives/2022/02/another-problematic-fosta-ruling-doe-v-pornhub.htm">Doe #1 v. MG Freesites</a> ruling, saying that the MG Freesites court excluded CSAM from the definition of &#8220;information&#8221; (an obviously wrong conclusion); plus &#8220;the allegations at play in MG Freesites were much more favorable to the plaintiff than what&#8217;s on display here. At most, Plaintiff has alleged that Defendant added the &#8220;domestic violence&#8221; tag to Rain Drops&#8217; video, but none of the other types of allegations from MG Freesites are present here.&#8221;</p>
<p style="text-align: center;">* * *</p>
<p>I don&#8217;t think all courts would treat the WorldStarHipHop-added headline and tags as third-party content. This is a highly confused area of Section 230 jurisprudence. A court could have said that the headline and tags weren&#8217;t an integral part of the video (they are metadata) and thus don&#8217;t necessarily need the same legal treatment as the video. A court also could say that even small semantic differences between the original headline and video tags and WorldStarHipHop&#8217;s headline and tags create new meaning added by WorldStarHipHop.</p>
<p>Also, it&#8217;s weird that the court appears to gloss over WorldStarHipHop&#8217;s download-and-reupload of the Rain Drop&#8217;s video. (The court never says that WorldStarHipHop only links to or embeds the third-party video; that might change the case&#8217;s complexion substantially). I have <a href="https://blog.ericgoldman.org/?s=d%27alonzo&amp;submit=Search">repeatedly blogged</a> about Section 230&#8217;s ambiguities from treating downloaded-and-reuploaded content as &#8220;information provided by another information content provider.&#8221; (See, e.g., <a href="https://blog.ericgoldman.org/archives/2006/07/griper_gets_47.htm">the D&#8217;Alonzo case</a> 20 years ago). In light of Section 230&#8217;s downward trendlines, it&#8217;s a little jarring to see the court discuss WorldStarHipHop taking all of these actions itself and still concluding that everything remained third-party content.</p>
<p>(WorldStarHipHop would also raise copyright concerns with an download/reupload, but this plaintiff would not be the right enforcer of that issue).</p>
<p><em>Case Citation</em>: Eizenga v. MediaLab.Ai Inc., 2026 U.S. Dist. LEXIS 103543 (May 11, 2026). Also of interest: my 2012 post on <a href="https://blog.ericgoldman.org/archives/2012/05/the_meme_that_w.htm">Scott v. WorldStarHipHop</a>.</p>
<p>The post <a href="https://blog.ericgoldman.org/archives/2026/05/worldstarhiphop-gets-section-230-dismissal-eizenga-v-medialab.htm">WorldStarHipHop Gets Section 230 Dismissal&#8211;Eizenga v. MediaLab</a> appeared first on <a href="https://blog.ericgoldman.org">Technology &amp; Marketing Law Blog</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://blog.ericgoldman.org/archives/2026/05/worldstarhiphop-gets-section-230-dismissal-eizenga-v-medialab.htm/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">28898</post-id>	</item>
		<item>
		<title>TOS Formation Fails, and So Does Section 230&#8211;Judge v. Academia</title>
		<link>https://blog.ericgoldman.org/archives/2026/05/tos-formation-fails-and-so-does-section-230-judge-v-academia.htm</link>
					<comments>https://blog.ericgoldman.org/archives/2026/05/tos-formation-fails-and-so-does-section-230-judge-v-academia.htm#respond</comments>
		
		<dc:creator><![CDATA[Eric Goldman]]></dc:creator>
		<pubDate>Tue, 12 May 2026 15:17:52 +0000</pubDate>
				<category><![CDATA[Derivative Liability]]></category>
		<category><![CDATA[Licensing/Contracts]]></category>
		<category><![CDATA[Marketing]]></category>
		<guid isPermaLink="false">https://blog.ericgoldman.org/?p=28876</guid>

					<description><![CDATA[<p>The named plaintiff is a professor. The defendant is a website, Academia, that helps professors share their works publicly. Academia heavily promotes its &#8220;Mentions&#8221; service that tracks a professor&#8217;s mentions and citations. [Historically, I have used a variety of free...</p>
<p>The post <a href="https://blog.ericgoldman.org/archives/2026/05/tos-formation-fails-and-so-does-section-230-judge-v-academia.htm">TOS Formation Fails, and So Does Section 230&#8211;Judge v. Academia</a> appeared first on <a href="https://blog.ericgoldman.org">Technology &amp; Marketing Law Blog</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>The named plaintiff is a professor. The defendant is a website, Academia, that helps professors share their works publicly. Academia heavily promotes its &#8220;Mentions&#8221; service that tracks a professor&#8217;s mentions and citations. [Historically, I have used a variety of free services to track my vanity mentions. Most are gone or unreliable at this point, but I don&#8217;t think I would pay for this service]. New Academia accountholders will immediately get this email promotion:</p>
<p><a href="https://blog.ericgoldman.org/wp-content/uploads/2026/05/academia-1.jpg"><img decoding="async" class="aligncenter size-full wp-image-28877" src="https://blog.ericgoldman.org/wp-content/uploads/2026/05/academia-1.jpg" alt="" width="1023" height="477" srcset="https://blog.ericgoldman.org/wp-content/uploads/2026/05/academia-1.jpg 1023w, https://blog.ericgoldman.org/wp-content/uploads/2026/05/academia-1-300x140.jpg 300w, https://blog.ericgoldman.org/wp-content/uploads/2026/05/academia-1-768x358.jpg 768w" sizes="(max-width: 1023px) 100vw, 1023px" /></a></p>
<p>Clicking on the &#8220;View your Mention&#8221; button leads to this screen:</p>
<p><a href="https://blog.ericgoldman.org/wp-content/uploads/2026/05/academia-2.jpg"><img loading="lazy" decoding="async" class="aligncenter size-full wp-image-28878" src="https://blog.ericgoldman.org/wp-content/uploads/2026/05/academia-2.jpg" alt="" width="1072" height="531" srcset="https://blog.ericgoldman.org/wp-content/uploads/2026/05/academia-2.jpg 1072w, https://blog.ericgoldman.org/wp-content/uploads/2026/05/academia-2-300x149.jpg 300w, https://blog.ericgoldman.org/wp-content/uploads/2026/05/academia-2-1024x507.jpg 1024w, https://blog.ericgoldman.org/wp-content/uploads/2026/05/academia-2-768x380.jpg 768w" sizes="auto, (max-width: 1072px) 100vw, 1072px" /></a></p>
<p>In both cases, the fact statement that X mentioned Y is presumably true, and it provides a sample of how the Mentions service works for its subscribers. At the same time, it does use X&#8217;s name in what looks like advertisements to convert Y to a paying customer. This reminded me of Facebook&#8217;s sponsored stories, which similarly relayed a true fact statement (X bought an item from Y) in what was converted into a paid advertisement.</p>
<p>Academia also targeted non-accountholders who visited a professor&#8217;s profile, showing them house ads:</p>
<p><a href="https://blog.ericgoldman.org/wp-content/uploads/2026/05/academia-3.jpg"><img loading="lazy" decoding="async" class="aligncenter size-full wp-image-28879" src="https://blog.ericgoldman.org/wp-content/uploads/2026/05/academia-3.jpg" alt="" width="384" height="503" srcset="https://blog.ericgoldman.org/wp-content/uploads/2026/05/academia-3.jpg 384w, https://blog.ericgoldman.org/wp-content/uploads/2026/05/academia-3-229x300.jpg 229w" sizes="auto, (max-width: 384px) 100vw, 384px" /></a></p>
<p>The plaintiffs filed a class action lawsuit over California&#8217;s publicity rights. Academia tries to send the case to arbitration three different ways (or, arguably, four different ways). They all fail.</p>
<p><em>Arbitration Attempt #1: Disclosure about Google&#8217;s Privacy</em> <em>Practices</em></p>
<p>In 2015, Judge used Academia&#8217;s &#8220;find your friends&#8221; feature to import his social graph from Google. Google displayed the following screen in the process:</p>
<p><a href="https://blog.ericgoldman.org/wp-content/uploads/2026/05/academia-4.jpg"><img loading="lazy" decoding="async" class="aligncenter size-full wp-image-28880" src="https://blog.ericgoldman.org/wp-content/uploads/2026/05/academia-4.jpg" alt="" width="693" height="738" srcset="https://blog.ericgoldman.org/wp-content/uploads/2026/05/academia-4.jpg 693w, https://blog.ericgoldman.org/wp-content/uploads/2026/05/academia-4-282x300.jpg 282w" sizes="auto, (max-width: 693px) 100vw, 693px" /></a></p>
<p>&nbsp;</p>
<p>The disclosure language never mentions Academia&#8217;s TOU at all, so&#8230;</p>
<p>(Also, Academia is trying to impose the arbitration requirement in its TOU, but the disclosure only permits Academia &#8220;to use your information&#8221;).</p>
<p><em>Arbitration Attempt #2: 2022 Google Pop-Out</em></p>
<p>In 2022, Judge signed into Academia using Google&#8217;s login functionality. Academia doesn&#8217;t know exactly what that process looked like <img src="https://s.w.org/images/core/emoji/16.0.1/72x72/1f644.png" alt="🙄" class="wp-smiley" style="height: 1em; max-height: 1em;" /> but this is its &#8220;best estimation&#8221;:</p>
<p><a href="https://blog.ericgoldman.org/wp-content/uploads/2026/05/academia-5.jpg"><img loading="lazy" decoding="async" class="aligncenter size-full wp-image-28881" src="https://blog.ericgoldman.org/wp-content/uploads/2026/05/academia-5.jpg" alt="" width="754" height="501" srcset="https://blog.ericgoldman.org/wp-content/uploads/2026/05/academia-5.jpg 754w, https://blog.ericgoldman.org/wp-content/uploads/2026/05/academia-5-300x199.jpg 300w" sizes="auto, (max-width: 754px) 100vw, 754px" /></a></p>
<p>The disclosure says to &#8220;see&#8221; Academia&#8217;s TOS but doesn&#8217;t have an if/then grammar, so&#8230;.</p>
<p>A reminder that if you&#8217;re trying to form the TOS and can&#8217;t provide highly credible evidence of what the TOS formation screen looked like, bonne chance.</p>
<p><em>Arbitration Attempt #3: Judge was a power user</em></p>
<blockquote><p>Academia argues that Judge: (1) viewed its website (which contains a link to its Terms of Use) tens of thousands of times, 29 times scrolling to the footer with the Terms link and twice clicking buttons immediately next to that link; (2) twice viewed the website when it had banners announcing that the Terms had changed; (3) opened thousands of emails from Academia containing a link to the Terms, and three times clicked an adjacent link; and (4) viewed the login page in 2016, which contained a notice that “By clicking Sign Up, you agree to our Terms,” and then subsequently created a new account in 2022.</p></blockquote>
<p>The court says the first three don&#8217;t indicate an unambiguous manifestation of assent. As for #4, the court says there&#8217;s no temporal coupling (viewed disclosure in 2016, signed up in 2022. Heck, I can&#8217;t even remember what I had for breakfast this morning). Arbitration denied.</p>
<p><em><a href="https://blog.ericgoldman.org/wp-content/uploads/2026/02/IMG_2022.jpg"><img loading="lazy" decoding="async" class="alignright wp-image-28570 size-medium" src="https://blog.ericgoldman.org/wp-content/uploads/2026/02/IMG_2022-300x300.jpg" alt="" width="300" height="300" srcset="https://blog.ericgoldman.org/wp-content/uploads/2026/02/IMG_2022-300x300.jpg 300w, https://blog.ericgoldman.org/wp-content/uploads/2026/02/IMG_2022-1024x1020.jpg 1024w, https://blog.ericgoldman.org/wp-content/uploads/2026/02/IMG_2022-150x150.jpg 150w, https://blog.ericgoldman.org/wp-content/uploads/2026/02/IMG_2022-768x765.jpg 768w, https://blog.ericgoldman.org/wp-content/uploads/2026/02/IMG_2022-1536x1529.jpg 1536w, https://blog.ericgoldman.org/wp-content/uploads/2026/02/IMG_2022-2048x2039.jpg 2048w" sizes="auto, (max-width: 300px) 100vw, 300px" /></a>Section 230</em></p>
<p>Having denied arbitration, the court turns to the case&#8217;s merits. The Section 230 defense flames out:</p>
<blockquote><p>Academia has materially contributed to the alleged unlawfulness of the conduct here. Judge alleges that Academia sends email advertisements to users stating that he has mentioned their work. The linked webpage in that email informs the user that several papers, “[i]ncluding one written by” Judge, mention the user and asks the user to “Try Premium for $1 and view your Mentions.” Additionally, after a user views Judge’s profile, Academia is alleged to provide that user with similar promotional advertisements. Judge therefore alleges that Academia unlawfully packages user-contributed content—his name and purported mention of the user—within its own solicitation to pay for its Mentions service. Thus, Academia “becomes the developer, at least in part, of that information.”</p>
<p>Academia contends that it is providing “notifications [that] truthfully conveyed user-generated citation information created by plaintiff himself.” Not so. Instead, Academia “transformed the character of Plaintiffs’ words . . . and actions into a commercial endorsement to which they did not consent.” [Cite to <a href="https://blog.ericgoldman.org/archives/2011/12/facebook_sponso.htm">Fraley v. Facebook</a>.] The advertisements disseminate Academia’s own message (subscribe to our Mentions service) with only a vague reference to user-generated content. As such, they are not akin to simply “disseminating the same content in essentially the same format to a search engine.” Section 230 does not allow a website to cloak its own advertisements as user-created content and thereby evade state-law liability.</p></blockquote>
<p><em>Arbitration Attempt #4: Attempted TOU Amendment</em></p>
<p>After Judge filed the lawsuit, Academia purported to amend its TOU:</p>
<p><a href="https://blog.ericgoldman.org/wp-content/uploads/2026/05/academia-6.jpg"><img loading="lazy" decoding="async" class="aligncenter size-full wp-image-28882" src="https://blog.ericgoldman.org/wp-content/uploads/2026/05/academia-6.jpg" alt="" width="876" height="357" srcset="https://blog.ericgoldman.org/wp-content/uploads/2026/05/academia-6.jpg 876w, https://blog.ericgoldman.org/wp-content/uploads/2026/05/academia-6-300x122.jpg 300w, https://blog.ericgoldman.org/wp-content/uploads/2026/05/academia-6-768x313.jpg 768w" sizes="auto, (max-width: 876px) 100vw, 876px" /></a></p>
<p>Also, &#8220;users must click an “Agree” button referencing the Terms of Use before continuing to use Academia.&#8221; The new TOU authorizes the use of accountholders&#8217; names in advertising.</p>
<p>The court treats this purported amendment as a misleading communication to the putative class members, so it triggers the protective provisions of FRCP Rule 23(d). In other words, because the changes affected the rights of class members, sending the email after the lawsuit was filed constituted a regulated communication with putative class members. The court had issues with the lack of disclosure that users weren&#8217;t previously bound by the arbitration clause, the fact that clicking on the links apparently constituted the acceptance of &#8220;using your account,&#8221; and that the new consent-to-advertising provision would extinguish pending claims. So the court strikes the effects of the purported TOU amendments on putative class members.</p>
<p>I&#8217;m not sure if it&#8217;s novel for the court to treat TOU/TOS amendments during the pendency of a class action lawsuit as potentially improper communications to putative class members, but I can&#8217;t recall seeing it before. The court&#8217;s approach shuts down some of the potential gamesmanship that some defendants play where they amend the TOS post-filing to try to eviscerate pending claims, with provisions such as claims waivers or arbitration requirements. If you are a defendant in a pending lawsuit and you hope a post-filing TOS amendment can eliminate it, tread cautiously.</p>
<p>Structurally, this case resembles the yearbook and people-finder cases, and it goes about as well for the defendants as those cases have.</p>
<p><em>Case Citation</em>: <a href="https://digitalcommons.law.scu.edu/cgi/viewcontent.cgi?article=3963&amp;context=historical">Judge v. Academia, Inc.</a>, 2026 WL 1256876 (N.D. Cal. May 7, 2026). Academia is represented by a defense team from Fenwick and Quinn Emanuel.</p>
<p><em>Prior blog posts on Yearbook and Genealogy Cases</em></p>
<ul>
<li><a title="Section 230’s Application to Account Terminations, CSAM, and More" href="https://blog.ericgoldman.org/archives/2026/03/section-230s-application-to-account-terminations-csam-and-more.htm" rel="bookmark">Section 230’s Application to Account Terminations, CSAM, and More</a></li>
<li><a href="https://blog.ericgoldman.org/archives/2026/03/free-trial-commercial-database-defeats-publicity-rights-claim-lafleur-v-yardi.htm">Free-Trial Commercial Database Defeats Publicity Rights Claim–LaFleur v. Yardi</a></li>
<li><a href="https://blog.ericgoldman.org/archives/2022/08/another-tough-ruling-for-people-search-databases-camacho-v-control-group-media.htm">Another Tough Ruling for People Search Databases–Camacho v. Control Group Media</a></li>
<li><a href="https://blog.ericgoldman.org/archives/2022/05/three-more-yearbook-people-database-cases-signal-trouble-for-defendants.htm">Three More Yearbook/People Database Cases Signal Trouble for Defendants</a></li>
<li><a href="https://blog.ericgoldman.org/archives/2022/01/background-reports-protected-by-section-230-dennis-v-mylife.htm">Background Reports Protected by Section 230–Dennis v. MyLife</a></li>
<li><a href="https://blog.ericgoldman.org/archives/2021/12/yearbook-defendants-lose-two-more-section-230-rulings.htm">Yearbook Defendants Lose Two More Section 230 Rulings</a></li>
<li><a title="Yearbook Database Cases Are Vexing the Courts–Sessa v. Ancestry" href="https://blog.ericgoldman.org/archives/2021/09/yearbook-database-cases-are-vexing-the-courts-sessa-v-ancestry.htm" rel="bookmark">Yearbook Database Cases Are Vexing the Courts–Sessa v. Ancestry</a></li>
<li><a href="https://blog.ericgoldman.org/archives/2021/09/court-casts-doubt-on-the-legality-of-the-data-brokerage-industry-brooks-v-thomson-reuters.htm">Court Casts Doubt on the Legality of the Data Brokerage Industry–Brooks v. Thomson Reuters</a></li>
<li><a title="Section 230 Doesn’t Protect Yearbook Website’s Ads–Knapke v. Classmates" href="https://blog.ericgoldman.org/archives/2021/08/section-230-doesnt-protect-yearbook-websites-ads-knapke-v-classmates.htm" rel="bookmark">Section 230 Doesn’t Protect Yearbook Website’s Ads–Knapke v. Classmates</a></li>
<li><a title="Section 230 Covers Republication of Old Yearbooks–Callahan v. Ancestry" href="https://blog.ericgoldman.org/archives/2021/03/section-230-covers-republication-of-old-yearbooks-callahan-v-ancestry.htm" rel="bookmark">Section 230 Covers Republication of Old Yearbooks–Callahan v. Ancestry</a></li>
<li><a title="Section 230 Doesn’t Protect Advertising “Background Reports” on People–Lukis v. Whitepages" href="https://blog.ericgoldman.org/archives/2020/04/section-230-doesnt-protect-advertising-background-reports-on-people-lukis-v-whitepages.htm" rel="bookmark">Section 230 Doesn’t Protect Advertising “Background Reports” on People–Lukis v. Whitepages</a></li>
</ul>
<p>The post <a href="https://blog.ericgoldman.org/archives/2026/05/tos-formation-fails-and-so-does-section-230-judge-v-academia.htm">TOS Formation Fails, and So Does Section 230&#8211;Judge v. Academia</a> appeared first on <a href="https://blog.ericgoldman.org">Technology &amp; Marketing Law Blog</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://blog.ericgoldman.org/archives/2026/05/tos-formation-fails-and-so-does-section-230-judge-v-academia.htm/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">28876</post-id>	</item>
		<item>
		<title>Meta Defeats Two More Account Termination/Content Removal Lawsuits</title>
		<link>https://blog.ericgoldman.org/archives/2026/05/meta-defeats-two-more-account-termination-content-removal-lawsuits.htm</link>
					<comments>https://blog.ericgoldman.org/archives/2026/05/meta-defeats-two-more-account-termination-content-removal-lawsuits.htm#respond</comments>
		
		<dc:creator><![CDATA[Eric Goldman]]></dc:creator>
		<pubDate>Sat, 09 May 2026 17:49:44 +0000</pubDate>
				<category><![CDATA[Content Regulation]]></category>
		<category><![CDATA[Derivative Liability]]></category>
		<category><![CDATA[Licensing/Contracts]]></category>
		<guid isPermaLink="false">https://blog.ericgoldman.org/?p=28871</guid>

					<description><![CDATA[<p>Two more account termination/content removal cases fail, like dozens before them. Tate v. Meta Platforms, Inc., 2026 WL 1146745 (N.D. Cal. April 28, 2026) This case involves the manosphere enthusiasts the Tate bros, Andrew and Tristian. Instagram terminated six of...</p>
<p>The post <a href="https://blog.ericgoldman.org/archives/2026/05/meta-defeats-two-more-account-termination-content-removal-lawsuits.htm">Meta Defeats Two More Account Termination/Content Removal Lawsuits</a> appeared first on <a href="https://blog.ericgoldman.org">Technology &amp; Marketing Law Blog</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><a href="https://blog.ericgoldman.org/wp-content/uploads/2025/04/exit-meme.jpg"><img loading="lazy" decoding="async" class="alignright size-medium wp-image-27643" src="https://blog.ericgoldman.org/wp-content/uploads/2025/04/exit-meme-269x300.jpg" alt="" width="269" height="300" srcset="https://blog.ericgoldman.org/wp-content/uploads/2025/04/exit-meme-269x300.jpg 269w, https://blog.ericgoldman.org/wp-content/uploads/2025/04/exit-meme.jpg 600w" sizes="auto, (max-width: 269px) 100vw, 269px" /></a>Two more account termination/content removal cases fail, <a href="https://papers.ssrn.com/sol3/papers.cfm?abstract_id=3911509">like dozens before them</a>.</p>
<p><strong><a href="https://www.bloomberglaw.com/public/desktop/document/EMORYANDREWTATEetalPlaintiffsMETAPLATFORMSINCetalDefendantsNo326C?doc_id=X1VDN80V0000N">Tate v. Meta Platforms, Inc.</a>, 2026 WL 1146745 (N.D. Cal. April 28, 2026)</strong></p>
<p>This case involves the manosphere enthusiasts the Tate bros, Andrew and Tristian. Instagram terminated six of their accounts for &#8220;promoting&#8217; dangerous individuals or organizations&#8217; or for inciting misogyny.&#8221; Due to <a href="https://en.wikipedia.org/wiki/Legal_affairs_of_the_Tate_brothers">the Tate bros&#8217; legal entanglements in Romania</a>, the bros claimed their deplatforming was connected to &#8220;a broader, ideologically motivated campaign, carried out under governmental and corporate pressure, to marginalize dissenting or controversial viewpoints—particularly those of prominent male figures criticizing modern social norms.&#8221; The bros sued Meta for a dozen causes of action. Meta defeats the claim based on Section 230.</p>
<p><em><a href="https://blog.ericgoldman.org/wp-content/uploads/2026/02/IMG_2022.jpg"><img loading="lazy" decoding="async" class="alignright size-medium wp-image-28570" src="https://blog.ericgoldman.org/wp-content/uploads/2026/02/IMG_2022-300x300.jpg" alt="" width="300" height="300" srcset="https://blog.ericgoldman.org/wp-content/uploads/2026/02/IMG_2022-300x300.jpg 300w, https://blog.ericgoldman.org/wp-content/uploads/2026/02/IMG_2022-1024x1020.jpg 1024w, https://blog.ericgoldman.org/wp-content/uploads/2026/02/IMG_2022-150x150.jpg 150w, https://blog.ericgoldman.org/wp-content/uploads/2026/02/IMG_2022-768x765.jpg 768w, https://blog.ericgoldman.org/wp-content/uploads/2026/02/IMG_2022-1536x1529.jpg 1536w, https://blog.ericgoldman.org/wp-content/uploads/2026/02/IMG_2022-2048x2039.jpg 2048w" sizes="auto, (max-width: 300px) 100vw, 300px" /></a>ICS Provider</em>. &#8220;Meta, as Instagram&#8217;s operator, is an interactive computer service provider.&#8221;</p>
<p><em>Third-Party Content</em>. &#8220;the information at issue (Plaintiffs&#8217; Instagram accounts) was provided by another (Plaintiffs).&#8221;</p>
<p><em>Publisher/Speaker Claim</em>.</p>
<blockquote><p>Plaintiffs challenge Meta&#8217;s decision to terminate Plaintiffs&#8217; Instagram accounts. Meta&#8217;s conduct “can be boiled down to deciding whether to exclude material that third parties seek to post online,” and is therefore immune from liability under section 230.</p></blockquote>
<p>The plaintiffs argued that 230 doesn&#8217;t apply to contract claims. Citing <a href="https://blog.ericgoldman.org/archives/2009/06/ninth_circuit_h.htm">Barnes</a>, the court calls their position &#8220;unpersuasive&#8221;:</p>
<blockquote><p>The Complaint is replete with allegations challenging Meta&#8217;s decision to “deplatform Plaintiffs,” impose a “blanket ban and improper termination” thereby “sever[ing] them from critical commercial tools and millions of followers causing them substantial and irreplaceable financial loss and damage.” Plaintiffs further allege their removal was “not an isolated enforcement action grounded in neutral application of [the] Terms of Use.” So, drawing all reasonable inferences from the Complaint&#8217;s allegations in Plaintiffs&#8217; favor, the duty Plaintiffs allege Meta violated derives from Meta&#8217;s decision not to publish Plaintiffs&#8217; content online and thus falls squarely within Section 230.</p></blockquote>
<p>The court also questions if the bros stated any contract breach. &#8220;Plaintiffs have not identified any contractual promise that applies to their Instagram accounts, let alone a promise not to terminate their Instagram accounts without prior notice or a promise to provide a right to appeal.&#8221;</p>
<p>(Later, with obvious irritation, the court notes that &#8220;despite an hour-long oral argument with many minutes of silence while Plaintiffs&#8217; counsel scrolled through all the potentially relevant documents on his computer, Plaintiffs could not identify any provision to support their assertion of a promise of prior notice and appellate rights&#8221;).</p>
<p><em>1983/First Amendment Claim</em>. &#8220;Meta is a private actor and thus its conduct constitutes private abridgement of speech to which the First Amendment does not apply.&#8221;</p>
<p>In denying leave to amend the complaint, the court emphasizes that this lawsuit wasn&#8217;t close at all:</p>
<blockquote><p>Plaintiffs&#8217; oral argument statements reveal neither they nor their counsel have a factual basis for alleging state actors were working in concert with federal actors and Meta to violate Plaintiffs&#8217; First Amendment rights. Nor do they have a factual basis for alleging Meta violated some contractual promise to provide advance notice prior to terminating Plaintiffs&#8217; Instagram account and not providing appellate rights, let alone a basis for alleging such breach caused $50 million in damages.</p></blockquote>
<p>Andrew <a href="https://x.com/Cobratate/status/1956984358083989758">allegedly</a> &#8220;allocated 400,000,000 of personal funds to battle Google, Meta, TikTok,&#8221; yet all that money didn&#8217;t turn the Tate bros into lawmaxxers.</p>
<p>The unsuccessful plaintiffs&#8217; lawyers include Raymond Brenneman of Brenneman Apc and Thomas Maniotis of Equity Legal, PLLC. Maybe the Tate bros would have had more courtroom success if they added some women lawyers to their litigation team.</p>
<p><strong><a href="https://websitedc.s3.amazonaws.com/documents/Ligon_III_v._Meta_USA_28_April_2026.pdf">Ligon v. Meta Platforms Inc.</a>, 2026 WL 1146091 (N.D. Cal. April 28, 2026)</strong></p>
<p>This is a very long and detailed opinion in response to a pro se lawsuit.</p>
<p>Ligon was a 2024 Republican candidate for the Georgia state senate. <a href="https://ballotpedia.org/Louis_Ligon">He got 633 votes</a> in the Republican primary. Ballotpedia also says that he survived two lightning strikes. Wowza. It made me wonder what message God may be trying to send to him&#8230;?</p>
<p>Ligon placed Facebook ads for his campaign, but Facebook quickly pulled the ads and then permanently suspended his personal and campaign accounts. In a footnote, the court recaps Facebook&#8217;s emails to Ligon that suggest a plethora of reasons why his ads may have been pulled, including trademarks, fake images of others, content that put others at risk, bypassing Facebook&#8217;s ad verification system, and copyright. Ligon sued Facebook pro se for eight different claims.</p>
<p><em>Section 230</em></p>
<p>In a footnote, the court rejects Ligon&#8217;s &#8220;but the algorithms&#8221; attempt to say that his content was Facebook&#8217;s first-party content:</p>
<blockquote><p>Defendant&#8217;s “editorial decisions” includes publishing decisions, like whether to remove published material, which are covered by section 230(c)(1) when the content was created by a third-party, but such editorial decisions alone do not constitute content creation. Plaintiff does not allege that any content was made or contributed to by Defendant, except insofar as he alleges that Defendant created the algorithm that “drives” the enforcement of Defendant&#8217;s content moderation and that this constitutes Defendant&#8217;s own content.  However, Defendant&#8217;s use of an algorithm to assist in its publishing functions does not take those actions outside the scope of its conduct as publisher so long as the algorithm is not assisting in the creation of content, which Plaintiff does not allege is the case here</p></blockquote>
<p>The court turns to the publisher/speaker element. The Tate court applied 230 to Meta&#8217;s alleged promises to provide pre-termination notice and an appellate right. This court says those are not publisher/speaker claims:</p>
<blockquote><p>providing notice and an appeals process, even when related to publishing decisions, is not an activity necessarily derived from the status of publisher, and sending emails or other notices about a user&#8217;s content is similarly not a traditional element of publication</p></blockquote>
<p>As a result, the claims predicated on the failed notice and appellate rights aren&#8217;t preempted by 230. From my perspective, both the notice and appellate rights would kick in only if Meta decides not to publish the content, so I think they are inextricably linked to publication decisions. In other words, I agree with the Tate decision and disagree with this one.</p>
<p>Section 230 ultimately applies to the other claims. As a general statement, the court notes that &#8220;The Ninth Circuit has consistently held that decisions to publish content, or not publish content, or revoke content from publication, are quintessential publishing functions for which interactive computer services cannot be held liable under section 230(c)(1).&#8221; [Cite to <a href="https://blog.ericgoldman.org/archives/2008/04/roommatescom_de_1.htm">Roommates</a>.]</p>
<p>The court evaluates Section 230&#8217;s application to each claim in significant detail:</p>
<blockquote><p>Plaintiff&#8217;s Claim One is a constitutional cause of action alleging that Defendant violated his First Amendment rights; his Claims Three and Four are related federal statutory claims for conspiracy to violate his civil rights and failure to prevent the conspiracy. These claims are based squarely on Defendant&#8217;s decision to remove and suspend Plaintiff&#8217;s content. The First Amendment claim is based solely on Defendant&#8217;s publishing conduct inherent to its status as publisher and remedy would require it to undertake further publishing activity by reactivating or reposting Plaintiff&#8217;s content. The conspiracy claim is essentially an allegation that Defendant coordinated with other entities to make its publishing decisions, and the tools Defendant chooses to use when making publication decisions—including potential consultation with other actors—are part of Defendant&#8217;s discretion as publisher whether to publish content. Remedy for this claim would also require Defendant to undertake specific publication actions because the alleged outcome and goal of the conspiracy is the removal of Plaintiff&#8217;s content. It then follows that the failure to prevent conspiracy claim is merely an allegation that Defendant failed to prevent a particular editorial decision from being made and enacted, whose remedy would also require Defendant to undertake specific publishing actions. It is immaterial that these claims are premised on the removal of Plaintiff&#8217;s content for political reasons—Ninth Circuit courts have consistently held that Section 230(c)(1) immunizes the removal of political content. As such, Claims One, Three, and Four are inseparable from Defendant&#8217;s status or conduct as publisher and are barred by section 230(c)(1).</p>
<p>[Eric&#8217;s note: the court doesn&#8217;t address the seemingly obvious problem that a statute can&#8217;t override constitutional protections.]</p>
<p>Plaintiff&#8217;s Claim Seven is brought under 42 U.S.C. § 1981, alleging that Defendant discriminated against him in the making and enforcement of contracts “by suspending his ads and accounts based on his conservative political viewpoint.” As with the above claims, this claim is based solely on Defendant&#8217;s suspension and removal of Plaintiff&#8217;s content and profiles, which is essential publishing activity routinely protected by Section 230(c)(1)&#8217;s liability limitations&#8230;.</p>
<p>Plaintiff&#8217;s breach of contract claim does not allege that Defendant or any of Defendant&#8217;s agents made specific, enforceable promises to him related to the suspension of his content; instead, he relies on the general contractual underpinnings of his use of Defendant&#8217;s platforms and payment to Defendant. His statement that Defendant&#8217;s acceptance of his payment created a duty to publish his content does not constitute an allegation that Defendant made a specific promise to publish Plaintiff&#8217;s content which was intended to supersede its discretion as publisher to make publication decisions. Whether based on an implied contract or a document like the Terms of Service, this type of general contract-based allegation has routinely been found insufficient to overcome section 230&#8217;s bar on liability for publishing conduct. As written, Plaintiff&#8217;s breach of contract claim is premised solely on Defendant&#8217;s decision to suspend his accounts and his advertisements.</p>
<p>[In a footnote, the court adds: &#8220;Other courts have gone even further when barring contract claims under section 230(c)(1) to broadly find that contract claims based on the removal of content are inseparable from internet platforms&#8217; status as publishers and are therefore barred. In contrast, still other courts have found that contract claims based on an alleged contractual duty of any kind are not barred by section 230(c)(1).&#8221; A shoutout to the <a href="https://blog.ericgoldman.org/archives/2024/06/ninth-circuit-does-more-damage-to-section-230-calise-v-meta.htm">Calise</a> and <a href="https://blog.ericgoldman.org/archives/2024/08/when-it-comes-to-section-230-the-ninth-circuit-is-a-chaos-agent-estate-of-bride-v-yolo.htm">YOLO</a> panels for ratcheting up courts&#8217; confusion on this point.]</p>
<p>Similarly, Plaintiff&#8217;s sixth claim for breach of the implied covenant of good faith and fair dealing is also barred by section 230(c)(1), insofar as this claim seeks to hold Defendant liable for the suspension of Plaintiff&#8217;s accounts and ads, for Defendant&#8217;s decision to continue publishing other content while removing Plaintiff&#8217;s content, and for the frustration of the contract via Defendant&#8217;s removal of Plaintiff&#8217;s content. Any implied promise by Defendant to use “good faith” or any general statements in the terms of service/use about its criteria when making editorial decisions like removing content is not the type of specific, directed promise that could take this claim out from the umbrella of section 230(c)(1)&#8230;.Plaintiff&#8217;s allegation that Defendant enacted the suspensions “in bad faith” does not thwart section 230(c)(1) immunity&#8230;.</p>
<p>Plaintiff&#8217;s Claim Eight for intentional infliction of emotional distress is also barred by section 230(c)(1) to the extent that it is based on Defendant&#8217;s removal of his content from its platforms. Plaintiff cannot hold Defendant liable for preventing him from accessing its platforms to publish content or removing his content, as this would hold them liable for its quintessential publishing decisions regarding what information may be published and contained on their platforms</p></blockquote>
<p>The court then also dismisses everything (both the 230-preempted claims and the non-preempted claims) for lack of merit.</p>
<p><em>Violations of Constitutional Rights</em></p>
<p>&#8220;Plaintiff&#8217;s constitutional claims fail because he has not alleged facts showing that Defendant Meta is a state actor for constitutional purposes.&#8221;</p>
<p><em>Contract Breach</em></p>
<p>&#8220;Plaintiff&#8217;s claim that Defendant&#8217;s acceptance of his payment created an implied contract by which they agreed to run his ads is directly contradicted by the Advertising Standards and terms of service/use, which reserve to Defendant the ability to reject or restrict advertisements “for violation of [its] policies at any time.”&#8221;</p>
<p><em>Implied Covenant of Good Faith and Fair Dealing</em></p>
<p>&#8220;Defendant is explicitly allowed under the terms of the contract to reject Plaintiff&#8217;s ads for any reason whenever it wants.&#8221;</p>
<p><em>IIED</em></p>
<blockquote><p>Plaintiff has not identified any conduct by Defendant beyond the sending of five emails: two of the emails were identical, informing Plaintiff that his accounts or advertisements had been identified as and restricted for using copyrighted music; four of the messages informed Plaintiff of Defendant&#8217;s findings upon reviewing the content; and one sent “on behalf of Universal Music Group” included information about the penalties for violations of copyright law and the possibility of a lawsuit. None of this conduct plausibly rises to the level of “outrageous” behavior. There are also no facts alleged to support the contention that Defendant&#8217;s conduct was intended to injure or committed with the knowledge that sending such emails was likely to cause extreme emotional distress</p></blockquote>
<p>Ligon has a better chance of getting and surviving a third lightning strike than winning an account termination/content removal case against Facebook.</p>
<p style="text-align: center;">* * *</p>
<p>One final point. You may have noted that both plaintiffs in this blog post could be characterized as &#8220;right-wing&#8221; (I don&#8217;t know what qualifies as &#8220;conservative&#8221; any more). I haven&#8217;t crunched the stats, but I believe that &#8220;right-wing&#8221; plaintiffs are overrepresented in the account termination/content removal genre. Some possible hypotheses about why that could be the case:</p>
<ul>
<li>The plaintiffs would argue that it&#8217;s because the services are systematically biased against right-wingers.</li>
<li>There have been numerous studies indicating that right-wingers more frequently post content that transgresses the applicable TOS. Essentially, as civility degrades across our society, right-wingers more frequently embrace content&#8211;racism, sexism, violent statements, etc.&#8211;that crosses previously set standards for civility.</li>
<li>Right-wingers are more likely to sue as part of their self-identity as victims and overall feelings of grievance.</li>
</ul>
<p>I welcome other hypotheses. If anyone want to crunch the data to test my hypothesis, I can help. This could be a good paper topic.</p>
<p>My hypothesis poses some serious challenges to advocates of digital due process requirements. It&#8217;s an equity/equality dilemma. We might treat everyone equally with procedural protections for their online speech, but that may not produce equitable results. In practice, people with majority characteristics may be able to weaponize those legal tools to entrench their majority position. See, e.g., <a href="https://blog.ericgoldman.org/archives/2020/06/section-230-ends-demonetized-youtubers-lawsuit-lewis-v-google.htm">Lewis v. Google</a>. If your goal is to raise up disenfranchised voices, watch out for any solution that can be turned around to benefit the majority.</p>
<div class="sharedaddy sd-sharing-enabled">
<p><strong>Selected Posts About State Action Claims</strong></p>
<ul data-sharing-events-added="true">
<li><a href="https://blog.ericgoldman.org/archives/2026/02/google-search-isnt-a-common-carrier-richards-v-google.htm">Google Search Isn’t a Common Carrier–Richards v. Google</a></li>
<li><a href="https://blog.ericgoldman.org/archives/2026/01/tiktok-isnt-a-u-s-state-actor-so-far-brooks-v-tiktok.htm">TikTok Isn’t a U.S. State Actor (So Far)–Brooks v. TikTok</a></li>
<li><a href="https://blog.ericgoldman.org/archives/2025/11/terminated-user-loses-lawsuit-against-facebook-hunt-v-meta.htm">Terminated User Loses Lawsuit Against Facebook–Hunt v. Meta</a></li>
<li><a href="https://blog.ericgoldman.org/archives/2025/06/section-230-still-applies-to-contract-breach-claim-njccc-v-mcaleer.htm">Section 230 (Still) Applies to Contract Breach Claim–NJCCC v. McAleer</a></li>
<li><a href="https://blog.ericgoldman.org/archives/2025/05/more-account-termination-cases-fail-in-court.htm">More Account Termination Cases Fail in Court</a></li>
<li><a href="https://blog.ericgoldman.org/archives/2025/04/wechat-defeats-account-termination-lawsuit-sun-v-wechat.htm">WeChat Defeats Account Termination Lawsuit–Sun v. WeChat</a></li>
<li><a href="https://blog.ericgoldman.org/archives/2024/09/robert-f-kennedy-jr-is-breaking-internet-law-faster-than-i-can-blog-it.htm">Robert F. Kennedy Jr. Is Breaking Internet Law Faster Than I Can Blog It</a></li>
<li><a href="https://blog.ericgoldman.org/archives/2024/05/a-peek-into-the-long-tail-of-facebooks-litigation-docket.htm">A Peek Into the Long Tail of Facebook’s Litigation Docket</a></li>
<li><a href="https://blog.ericgoldman.org/archives/2024/04/jawboning-defendants-are-6-for-6-in-the-ninth-circuit-hart-v-facebook.htm">Jawboning Defendants Are 6-for-6 in the Ninth Circuit–Hart v. Facebook</a></li>
<li><a title="YouTube Still Isn’t a State Actor–Albertson v. Google" href="https://blog.ericgoldman.org/archives/2024/02/youtube-still-isnt-a-state-actor-albertson-v-google.htm" rel="bookmark">YouTube Still Isn’t a State Actor–Albertson v. Google</a></li>
<li><a href="https://blog.ericgoldman.org/archives/2023/05/twitter-account-suspension-lawsuits-keep-failing-hall-v-twitter.htm">Twitter Account Suspension Lawsuits Keep Failing–Hall v. Twitter</a></li>
<li><a href="https://blog.ericgoldman.org/archives/2023/04/twitter-defeats-account-suspension-case-craft-v-musk.htm">Twitter Defeats Account Suspension Case–Craft v. Musk</a></li>
<li><a href="https://blog.ericgoldman.org/archives/2023/03/government-submissions-to-a-trusted-flagger-program-isnt-unconstitutional-jawboning-ohandley-v-weber.htm">Government Submissions to a Trusted Flagger Program Aren’t Unconstitutional Jawboning–O’Handley v. Weber</a></li>
<li><a href="https://blog.ericgoldman.org/archives/2023/01/facebook-defeats-lawsuit-over-account-suspension-for-a-voting-misinformation-joke-hall-v-meta.htm">Facebook Defeats Lawsuit Over Account Suspension for a Voting Misinformation “Joke”–Hall v. Meta</a></li>
<li><a title="Prager’s Lawsuit Over Biased Content Moderation Decisively Fails Again (This Time, in State Court)–Prager v. YouTube" href="https://blog.ericgoldman.org/archives/2022/12/pragers-lawsuit-over-biased-content-moderation-decisively-fails-again-this-time-in-state-court-prager-v-youtube.htm" rel="bookmark">Prager’s Lawsuit Over Biased Content Moderation Decisively Fails Again (This Time, in State Court)–Prager v. YouTube</a></li>
<li><a title="The 5th Circuit Puts the 1st Amendment in a Blender &amp; Whips Up a Terrible #MAGA Kool-Aid–NetChoice v. Paxton" href="https://blog.ericgoldman.org/archives/2022/09/the-5th-circuit-puts-the-1st-amendment-in-a-blender-whips-up-a-terrible-maga-kool-aid-netchoice-v-paxton.htm" rel="bookmark">The 5th Circuit Puts the 1st Amendment in a Blender &amp; Whips Up a Terrible #MAGA Kool-Aid–NetChoice v. Paxton</a></li>
<li><a title="Facebook Defeats Jawboning Lawsuit Over COVID Misinformation Removal–Rogalinski v. Meta" href="https://blog.ericgoldman.org/archives/2022/08/facebook-defeats-jawboning-lawsuit-over-covid-misinformation-removal-rogalinski-v-meta.htm" rel="bookmark">Facebook Defeats Jawboning Lawsuit Over COVID Misinformation Removal–Rogalinski v. Meta</a></li>
<li><a title="Another Account Suspension Case Yeeted–Rangel v. Dorsey" href="https://blog.ericgoldman.org/archives/2022/07/another-account-suspension-case-yeeted-rangel-v-dorsey.htm" rel="bookmark">Another Account Suspension Case Yeeted–Rangel v. Dorsey</a></li>
<li><a title="Another Failed Lawsuit Over Trump’s Deplatforming–Rutenberg v. Twitter" href="https://blog.ericgoldman.org/archives/2022/05/another-failed-lawsuit-over-trumps-deplatforming-rutenberg-v-twitter.htm" rel="bookmark">Another Failed Lawsuit Over Trump’s Deplatforming–Rutenberg v. Twitter</a></li>
<li><a href="https://blog.ericgoldman.org/archives/2022/05/covid-skeptic-loses-lawsuit-over-account-terminations-hart-v-facebook.htm">COVID Skeptic Loses Lawsuit Over Account Terminations–Hart v. Facebook</a></li>
<li><a href="https://blog.ericgoldman.org/archives/2022/05/twitter-defeats-trumps-deplatforming-lawsuit-trump-v-twitter.htm">Twitter Defeats Trump’s Deplatforming Lawsuit–Trump v. Twitter</a></li>
<li><a href="https://blog.ericgoldman.org/archives/2022/04/account-suspension-lawsuit-against-twitter-survives-motion-to-dismiss-berenson-v-twitter.htm">Account Suspension Lawsuit Against Twitter Survives Motion to Dismiss–Berenson v. Twitter</a></li>
<li><a href="https://blog.ericgoldman.org/archives/2022/04/another-failed-lawsuit-over-facebooks-content-removals-brock-v-zuckerberg.htm">Another Failed Lawsuit Over Facebook’s Content Removals–Brock v. Zuckerberg</a></li>
<li><a href="https://blog.ericgoldman.org/archives/2022/03/section-230-survives-yet-another-constitutional-challenge-huber-v-biden.htm">Section 230 Survives Yet Another Constitutional Challenge–Huber v. Biden</a></li>
<li><a href="https://blog.ericgoldman.org/archives/2022/02/another-court-says-facebook-isnt-a-state-actor-mcwaters-v-houston.htm">Another Court Says Facebook Isn’t a State Actor–McWaters v. Houston</a></li>
<li><a href="https://blog.ericgoldman.org/archives/2022/02/another-anti-vaxxer-jawboning-lawsuit-fails-ican-v-youtube.htm">Another Anti-Vaxxer Jawboning Lawsuit Fails–ICAN v. YouTube</a></li>
<li><a title="The First Amendment Protects Twitter’s Fact-Checking and Account Suspension Decisions–O’Handley v. Padilla" href="https://blog.ericgoldman.org/archives/2022/01/the-first-amendment-protects-twitters-fact-checking-and-account-suspension-decisions-ohandley-v-padilla.htm" rel="bookmark">The First Amendment Protects Twitter’s Fact-Checking and Account Suspension Decisions–O’Handley v. Padilla</a></li>
<li><a href="https://blog.ericgoldman.org/archives/2021/11/one-more-time-facebook-isnt-a-state-actor-atkinson-v-facebook.htm">One More Time: Facebook Isn’t a State Actor–Atkinson v. Facebook</a></li>
<li><a href="https://blog.ericgoldman.org/archives/2021/11/two-more-courts-tell-litigants-that-social-media-services-arent-state-actors.htm">Two More Courts Tell Litigants That Social Media Services Aren’t State Actors</a></li>
<li><a href="https://blog.ericgoldman.org/archives/2021/10/government-jawboning-doesnt-turn-internet-services-into-state-actors-doe-v-google.htm">Government Jawboning Doesn’t Turn Internet Services into State Actors–Doe v. Google</a></li>
<li><a href="https://blog.ericgoldman.org/archives/2021/10/anti-zionist-loses-lawsuit-over-social-media-account-suspensions-martillo-v-facebook.htm">Anti-Zionist Loses Lawsuit Over Social Media Account Suspensions–Martillo v. Facebook</a></li>
<li><a href="https://blog.ericgoldman.org/archives/2021/08/court-nopes-another-lawsuit-over-facebook-suspensions-orders-v-facebook.htm">Court Nopes Another Lawsuit Over Facebook Suspensions–Orders v. Facebook</a></li>
<li><a href="https://blog.ericgoldman.org/archives/2021/07/facebook-defeats-lawsuit-by-publishers-of-vaccine-misinformation-childrens-health-defense-v-facebook.htm">Facebook Defeats Lawsuit By Publishers of Vaccine (Mis?)information–Children’s Health Defense v. Facebook</a></li>
<li><a href="https://blog.ericgoldman.org/archives/2021/06/court-rejects-lawsuit-alleging-youtube-engaged-in-racially-biased-content-moderation-newman-v-google.htm">Court Rejects Lawsuit Alleging YouTube Engaged in Racially Biased Content Moderation–Newman v. Google</a></li>
<li><a href="https://blog.ericgoldman.org/archives/2021/06/yet-another-court-says-facebook-isnt-a-state-actor-brock-v-zuckerberg.htm">Yet Another Court Says Facebook Isn’t a State Actor–Brock v. Zuckerberg</a></li>
<li><a href="https://blog.ericgoldman.org/archives/2021/04/youtube-again-defeats-lawsuit-over-content-removal-lewis-v-google.htm">YouTube (Again) Defeats Lawsuit Over Content Removal–Lewis v. Google</a></li>
<li><a title="When It Came to @RealDonaldTrump, Twitter Couldn’t Please Everyone–Rutenberg v. Twitter" href="https://blog.ericgoldman.org/archives/2021/04/when-it-came-to-realdonaldtrump-twitter-couldnt-please-everyone-rutenberg-v-twitter.htm" rel="bookmark">When It Came to @RealDonaldTrump, Twitter Couldn’t Please Everyone–Rutenberg v. Twitter</a></li>
<li><a title="Another Must-Carry Lawsuit Against YouTube Fails–Daniels v Alphabet" href="https://blog.ericgoldman.org/archives/2021/04/another-must-carry-lawsuit-against-youtube-fails-daniels-v-alphabet.htm" rel="bookmark">Another Must-Carry Lawsuit Against YouTube Fails–Daniels v Alphabet</a></li>
<li><a href="https://blog.ericgoldman.org/archives/2021/03/newspaper-isnt-state-actor-plotkin-v-astorian.htm">Newspaper Isn’t State Actor–Plotkin v. Astorian</a></li>
<li><a href="https://blog.ericgoldman.org/archives/2021/02/an-account-suspension-case-fails-again-perez-v-linkedin.htm">An Account Suspension Case Fails Again–Perez v. LinkedIn</a></li>
<li><a href="https://blog.ericgoldman.org/archives/2021/02/are-social-media-services-state-actors-or-common-carriers.htm">Are Social Media Services “State Actors” or “Common Carriers”?</a></li>
<li><a href="https://blog.ericgoldman.org/archives/2021/01/google-and-twitter-defeat-lawsuit-over-account-suspensions-terminations-delima-v-google.htm">Google and Twitter Defeat Lawsuit Over Account Suspensions/Terminations–DeLima v. Google</a></li>
<li><a href="https://blog.ericgoldman.org/archives/2021/01/more-plaintiffs-and-lawyers-need-to-be-reminded-that-youtube-isnt-a-state-actor-divino-v-google.htm">More Plaintiffs (and Lawyers) Need To Be Reminded That YouTube Isn’t a State Actor–Divino v. Google</a></li>
<li><a href="https://blog.ericgoldman.org/archives/2020/12/facebook-isnt-a-constructive-public-trust-cameron-atkinson-v-facebook.htm">Facebook Isn’t a Constructive Public Trust–Cameron Atkinson v. Facebook</a></li>
<li><a href="https://blog.ericgoldman.org/archives/2020/12/google-and-youtube-arent-censoring-breitbart-comments-belknap-v-alphabet.htm">Google and YouTube Aren’t “Censoring” Breitbart Comments–Belknap v. Alphabet</a></li>
<li><a href="https://blog.ericgoldman.org/archives/2020/10/linkedin-isnt-a-state-actor-perez-v-linkedin.htm">LinkedIn Isn’t a State Actor–Perez v. LinkedIn</a></li>
<li><a href="https://blog.ericgoldman.org/archives/2020/10/section-230-preempts-another-facebook-account-termination-case-zimmerman-v-facebook.htm">Section 230 Preempts Another Facebook Account Termination Case–Zimmerman v. Facebook</a></li>
<li><a href="https://blog.ericgoldman.org/archives/2020/06/section-230-ends-demonetized-youtubers-lawsuit-lewis-v-google.htm">Section 230 Ends Demonetized YouTuber’s Lawsuit–Lewis v. Google</a></li>
<li><a href="https://blog.ericgoldman.org/archives/2020/06/court-rejects-another-lawsuit-alleging-that-internet-companies-suppress-conservative-views-freedom-watch-v-google.htm">Court Rejects Another Lawsuit Alleging that Internet Companies Suppress Conservative Views–Freedom Watch v. Google</a></li>
<li><a href="https://blog.ericgoldman.org/archives/2020/05/another-suspended-twitter-user-loses-in-court-wilson-v-twitter.htm">Another Suspended Twitter User Loses in Court–Wilson v. Twitter</a></li>
<li><a href="https://blog.ericgoldman.org/archives/2020/03/first-voters-reject-tulsi-gabbard-then-a-judge-does-gabbard-v-google.htm">First Voters Reject Tulsi Gabbard, Then a Judge Does–Gabbard v. Google</a></li>
<li><a href="https://blog.ericgoldman.org/archives/2020/03/youtube-isnt-a-state-actor-duh-prageru-v-google.htm">YouTube Isn’t a State Actor (DUH)–PragerU v. Google</a></li>
<li><a title="Facebook Still Isn’t Obligated to Publish Russian Troll Content–FAN v. Facebook" href="https://blog.ericgoldman.org/archives/2020/01/facebook-still-isnt-obligated-to-publish-russian-troll-content-fan-v-facebook.htm" rel="bookmark">Facebook Still Isn’t Obligated to Publish Russian Troll Content–FAN v. Facebook</a></li>
<li><a title="Vimeo Defeats Lawsuit for Terminating Account That Posted Conversion Therapy Videos–Domen v. Vimeo" href="https://blog.ericgoldman.org/archives/2020/01/vimeo-defeats-lawsuit-for-terminating-account-that-posted-conversion-therapy-videos-domen-v-vimeo.htm" rel="bookmark">Vimeo Defeats Lawsuit for Terminating Account That Posted Conversion Therapy Videos–Domen v. Vimeo</a></li>
<li><a title="Russia Fucked With American Democracy, But It Can’t Fuck With Section 230–Federal Agency of News v. Facebook" href="https://blog.ericgoldman.org/archives/2019/07/russia-fucked-with-american-democracy-but-it-cant-fuck-with-section-230-federal-agency-of-news-v-facebook.htm" rel="bookmark">Russia Fucked With American Democracy, But It Can’t Fuck With Section 230–Federal Agency of News v. Facebook</a></li>
<li><a title="Private Publishers Aren’t State Actors–Manhattan Community Access v. Halleck" href="https://blog.ericgoldman.org/archives/2019/06/private-publishers-arent-state-actors-manhattan-community-access-v-halleck.htm" rel="bookmark">Private Publishers Aren’t State Actors–Manhattan Community Access v. Halleck</a></li>
<li><a title="Your Periodic Reminder That Facebook Isn’t a State Actor–Williby v. Zuckerberg" href="https://blog.ericgoldman.org/archives/2019/06/your-periodic-reminder-that-facebook-isnt-a-state-actor-williby-v-zuckerberg.htm" rel="bookmark">Your Periodic Reminder That Facebook Isn’t a State Actor–Williby v. Zuckerberg</a></li>
<li><a title="Section 230 Protects Facebook’s Account and Content Restriction Decisions–Ebeid v. Facebook" href="https://blog.ericgoldman.org/archives/2019/05/section-230-protects-facebooks-account-and-content-restriction-decisions-ebeid-v-facebook.htm" rel="bookmark">Section 230 Protects Facebook’s Account and Content Restriction Decisions–Ebeid v. Facebook</a></li>
<li><a title="Court Tosses Antitrust Claims That Internet Giants Are Biased Against Conservatives–Freedom Watch v. Google" href="https://blog.ericgoldman.org/archives/2019/03/court-tosses-antitrust-claims-that-internet-giants-are-biased-against-conservatives-freedom-watch-v-google.htm" rel="bookmark">Court Tosses Antitrust Claims That Internet Giants Are Biased Against Conservatives–Freedom Watch v. Google</a></li>
<li><a title="Twitter Isn’t a Shopping Mall for First Amendment Purposes (Duh)–Johnson v. Twitter" href="https://blog.ericgoldman.org/archives/2018/06/twitter-isnt-a-shopping-mall-for-first-amendment-purposes-duh-johnson-v-twitter.htm" rel="bookmark">Twitter Isn’t a Shopping Mall for First Amendment Purposes (Duh)–Johnson v. Twitter</a></li>
<li><a title="YouTube Isn’t a Company Town (Duh)–Prager University v. Google" href="https://blog.ericgoldman.org/archives/2018/03/youtube-isnt-a-company-town-duh-prager-university-v-google.htm" rel="bookmark">YouTube Isn’t a Company Town (Duh)–Prager University v. Google</a></li>
<li><a title="Facebook Defeats Lawsuit By User Suspended Over ‘Bowling Green Massacre’–Shulman v. Facebook" href="https://blog.ericgoldman.org/archives/2017/11/facebook-defeats-lawsuit-by-user-suspended-over-bowling-green-massacre-shulman-v-facebook.htm" rel="bookmark">Facebook Defeats Lawsuit By User Suspended Over ‘Bowling Green Massacre’–Shulman v. Facebook</a></li>
<li><a title="Yelp, Twitter and Facebook Aren’t State Actors–Quigley v. Yelp" href="https://blog.ericgoldman.org/archives/2017/07/yelp-twitter-and-facebook-arent-state-actors-quigley-v-yelp.htm" rel="bookmark">Yelp, Twitter and Facebook Aren’t State Actors–Quigley v. Yelp</a></li>
<li><a title="Facebook Not Liable for Account Termination–Young v. Facebook" href="https://blog.ericgoldman.org/archives/2010/11/facebook_not_li_2.htm" rel="bookmark">Facebook Not Liable for Account Termination–Young v. Facebook</a></li>
<li><a title="Online Game Network Isn’t Company Town–Estavillo v. Sony" href="https://blog.ericgoldman.org/archives/2009/10/online_game_net.htm" rel="bookmark">Online Game Network Isn’t Company Town–Estavillo v. Sony</a></li>
<li><a title="Third Circuit Says Google Isn’t State Actor–Jayne v. Google Founders" href="https://blog.ericgoldman.org/archives/2008/02/third_circuit_s.htm" rel="bookmark">Third Circuit Says Google Isn’t State Actor–Jayne v. Google Founders</a></li>
<li><a title="Ask.com Not Liable for Search Results or Indexing Decisions–Murawski v. Pataki" href="https://blog.ericgoldman.org/archives/2007/09/askcom_not_liab.htm" rel="bookmark">Ask.com Not Liable for Search Results or Indexing Decisions–Murawski v. Pataki</a></li>
<li><a title="Search Engines Defeat “Must-Carry” Lawsuit–Langdon v. Google" href="https://blog.ericgoldman.org/archives/2007/02/search_engines_3.htm" rel="bookmark">Search Engines Defeat “Must-Carry” Lawsuit–Langdon v. Google</a></li>
<li><a title="KinderStart Lawsuit Dismissed (With Leave to Amend)" href="https://blog.ericgoldman.org/archives/2006/07/kinderstart_law.htm" rel="bookmark">KinderStart Lawsuit Dismissed (With Leave to Amend)</a></li>
<li><a title="ICANN Not a State Actor" href="https://blog.ericgoldman.org/archives/2005/04/icann_not_a_sta.htm" rel="bookmark">ICANN Not a State Actor</a></li>
</ul>
</div>
<p>The post <a href="https://blog.ericgoldman.org/archives/2026/05/meta-defeats-two-more-account-termination-content-removal-lawsuits.htm">Meta Defeats Two More Account Termination/Content Removal Lawsuits</a> appeared first on <a href="https://blog.ericgoldman.org">Technology &amp; Marketing Law Blog</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://blog.ericgoldman.org/archives/2026/05/meta-defeats-two-more-account-termination-content-removal-lawsuits.htm/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">28871</post-id>	</item>
		<item>
		<title>Section 230 Helps Discord Defeat &#8220;Defective Design&#8221; Claims Regarding Sexual Predation&#8211;Jane Doe v. Discord</title>
		<link>https://blog.ericgoldman.org/archives/2026/04/section-230-helps-discord-defeat-defective-design-claims-regarding-sexual-predation-jane-doe-v-discord.htm</link>
		
		<dc:creator><![CDATA[Eric Goldman]]></dc:creator>
		<pubDate>Tue, 21 Apr 2026 18:27:48 +0000</pubDate>
				<category><![CDATA[Content Regulation]]></category>
		<category><![CDATA[Derivative Liability]]></category>
		<category><![CDATA[Licensing/Contracts]]></category>
		<category><![CDATA[Marketing]]></category>
		<guid isPermaLink="false">https://blog.ericgoldman.org/?p=28812</guid>

					<description><![CDATA[<p>This is another entry in the genre of &#8220;predator access&#8221; cases claiming that predators solicited minors for sex online, in this case on Discord. Many predator access cases have targeted Roblox, which has a pending MDL in CA consolidating dozens...</p>
<p>The post <a href="https://blog.ericgoldman.org/archives/2026/04/section-230-helps-discord-defeat-defective-design-claims-regarding-sexual-predation-jane-doe-v-discord.htm">Section 230 Helps Discord Defeat &#8220;Defective Design&#8221; Claims Regarding Sexual Predation&#8211;Jane Doe v. Discord</a> appeared first on <a href="https://blog.ericgoldman.org">Technology &amp; Marketing Law Blog</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>This is another entry in the genre of &#8220;predator access&#8221; cases claiming that predators solicited minors for sex online, in this case on Discord. Many predator access cases have targeted Roblox, which has a pending MDL in CA consolidating dozens of cases. Some of those plaintiffs have also named Discord. The plaintiffs tried to get this case moved to the Northern District of California so that it could operate in parallel with the Roblox MDL, but the court refuses that request. Instead, the court hands Discord a decisive win per Section 230.</p>
<p><a href="https://blog.ericgoldman.org/wp-content/uploads/2026/02/IMG_2022.jpg"><img loading="lazy" decoding="async" class="alignright size-medium wp-image-28570" src="https://blog.ericgoldman.org/wp-content/uploads/2026/02/IMG_2022-300x300.jpg" alt="" width="300" height="300" srcset="https://blog.ericgoldman.org/wp-content/uploads/2026/02/IMG_2022-300x300.jpg 300w, https://blog.ericgoldman.org/wp-content/uploads/2026/02/IMG_2022-1024x1020.jpg 1024w, https://blog.ericgoldman.org/wp-content/uploads/2026/02/IMG_2022-150x150.jpg 150w, https://blog.ericgoldman.org/wp-content/uploads/2026/02/IMG_2022-768x765.jpg 768w, https://blog.ericgoldman.org/wp-content/uploads/2026/02/IMG_2022-1536x1529.jpg 1536w, https://blog.ericgoldman.org/wp-content/uploads/2026/02/IMG_2022-2048x2039.jpg 2048w" sizes="auto, (max-width: 300px) 100vw, 300px" /></a>The court starts off with this broad proposition:</p>
<blockquote><p>Section 230 compels dismissal of claims seeking to hold platforms liable for activity amounting to sexual exploitation of one user by another when the factual predicate is that the two users engaged in messaging using the platform&#8217;s service&#8221; [cites to <a href="https://blog.ericgoldman.org/archives/2025/02/ninth-circuit-says-section-230-preempts-defective-design-claims-doe-v-grindr.htm">Doe v. Grindr</a>, <a href="https://blog.ericgoldman.org/archives/2008/05/myspace_gets_23.htm">Doe v. MySpace</a>, <a href="https://blog.ericgoldman.org/archives/2023/12/many-fifth-circuit-judges-hope-to-eviscerate-section-230-doe-v-snap.htm">Doe v. Snap</a>, <a href="https://blog.ericgoldman.org/archives/2016/03/big-win-for-free-speech-online-in-backpage-lawsuit-forbes-cross-post.htm">Doe 1 v. Backpage</a>, <a href="https://blog.ericgoldman.org/archives/2009/07/myspace_wins_an.htm">Doe II v. MySpace</a>, <a href="https://blog.ericgoldman.org/archives/2021/09/fosta-claim-can-proceed-against-twitter-doe-v-twitter.htm">In re Facebook</a>, <a href="https://blog.ericgoldman.org/archives/2023/06/section-230-immunizes-snap-even-if-its-inherently-dangerous-l-w-v-snap.htm">LW v. Snap</a>, <a href="https://blog.ericgoldman.org/archives/2023/10/section-230-once-again-applies-to-claims-over-offline-sexual-abuse-doe-v-grindr.htm">Doe v. Grindr</a> (S.D. Fla.), <a href="https://blog.ericgoldman.org/archives/2020/09/section-230-preempts-another-fosta-claim-doe-v-kik.htm">Doe v. Kik</a>.]</p></blockquote>
<p><em>Negligence</em></p>
<p>The plaintiff tried the standard set of arguments that Discord was defectively designed because it didn&#8217;t adhere to the plaintiff lawyers&#8217; vision of how services should operate:</p>
<blockquote><p>Plaintiff&#8217;s “Negligence” claims seek to impose liability on Discord for (i) designing its messaging service to facilitate harmful private communications; (ii) allowing “unsupervised” messaging between users; (iii) failing to require phone number verification or otherwise “screen users”; (iv) failing to “implement &#8230; parent controls” and “parental notifications” that would monitor and supervise messages; (v) failing to remove user profiles and block messages from adults who message teens; (vi) failing to set default safety settings that would block messages between unconnected users; (vii) offering an “open chat function” without sufficient moderation; and (viii) failing to monitor for, report and prevent the use of [its] app[ ] by sexual predators.”</p></blockquote>
<p>The court says all of those configuration choices are editorial choices protected by Section 230:</p>
<blockquote><p>These claims each amount to Plaintiff seeking to impose a duty on Discord to monitor, screen, and block Plaintiff&#8217;s communications with other Discord users. All of these duties would require Discord to alter or amend how it publishes, monitors, screens, flags, blocks, or removes users’ messages and profiles, including how it offers to its users “neutral tools” that allow users to communicate in different chat forums and formats. [cite to Jones v. Dirty World (6th Circuit)]</p></blockquote>
<p>Notice how this court implicitly veers away from the social media addiction rulings in California and numerous other precedents saying that design choices can be agnostic about what content they apply to and therefore are not based on third party content.</p>
<p><em>Strict Liability</em></p>
<p>The court treats the products liability claim the same as the negligence claim. The plaintiff complained about the following practices:</p>
<blockquote><p>The Complaint faults Discord for providing a service that “allow[s] children to come into contact with child predators, and asserts that Discord should provide “[e]ffective parental controls” to stop harmful message exchanges; reconfigure features to “block[ ] direct messaging between child and adult users”; block content from “known abusers”; and offer a more restrictive “[c]ontrolled chat” option.</p></blockquote>
<p>The court responds that these claims &#8220;would require Discord to more perfectly screen for and block harmful messages and alter the operation of the neutral tools it provides users to send messages,&#8221; which Section 230 does not permit.</p>
<p><em>Concealment/Failure to Warn</em></p>
<p>The court says the concealment/failure to warn claims also second-guess Discord&#8217;s editorial decisions. The court says:</p>
<blockquote><p>Courts cannot accept attempts to repackage what is in actuality “publisher” actions as “torts of omission” to evade Section 230</p></blockquote>
<p>Thus, &#8220;these allegations appear to be simply a restatement of Plaintiff&#8217;s negligence claims and product liability claims already found to be barred by Section 230. Put another way, the only way that Discord could address these aspects of its platform would be “to take certain moderation actions” that would eliminate the alleged discrepancy between Discord&#8217;s description of its moderation efforts and the “reality” of its moderation – again, “publishing” actions.&#8221; [cite to <a href="https://blog.ericgoldman.org/archives/2024/08/when-it-comes-to-section-230-the-ninth-circuit-is-a-chaos-agent-estate-of-bride-v-yolo.htm">Bride v. YOLO</a>]</p>
<p>Failing to warn users that Discord is a &#8220;dangerous&#8221; app &#8220;is at root a claim based on “publication” choices related to moderation efforts, which fall within the immunity provided by Section 230.&#8221; Cites to <a href="https://blog.ericgoldman.org/archives/2024/08/when-it-comes-to-section-230-the-ninth-circuit-is-a-chaos-agent-estate-of-bride-v-yolo.htm">Bride v. YOLO</a>, <a href="https://blog.ericgoldman.org/archives/2025/02/ninth-circuit-says-section-230-preempts-defective-design-claims-doe-v-grindr.htm">Doe v. Grindr</a>, <a href="https://blog.ericgoldman.org/archives/2024/03/section-230-applies-to-claims-over-hijacked-accounts-except-maybe-verified-accounts-wozniak-v-youtube.htm">Wozniak v. YouTube</a>.</p>
<p>The court also questions if there was any actual omission: &#8220;Discord does disclose and issue transparency reports that – as is the case with any platform that handles an immensely high volume of messages each day – do <a href="https://blog.ericgoldman.org/archives/2019/10/top-myths-about-content-moderation.htm">show that its content moderation efforts are imperfect</a>.&#8221;</p>
<p><em>Misrepresentation</em></p>
<blockquote><p>Plaintiff&#8217;s claims seek to hold Discord liable for alleged “misrepresentations” by failing to conform its content moderation standards – based on what amounts to its general “aspirational” standards of seeking to provide a platform “safe for minors” – to a level defined by Plaintiff. [The <a href="https://blog.ericgoldman.org/archives/2025/02/ninth-circuit-says-section-230-preempts-defective-design-claims-doe-v-grindr.htm">Grindr court</a> distinguished] claims based on actual specific and defined contractual promises [from] general aspirational goals regarding platform content moderation</p></blockquote>
<p>The litigation over &#8220;safe&#8221; content moderation is decades-old and completely confused.</p>
<p><em>Third-Party Content</em></p>
<blockquote><p>Nowhere in Plaintiff&#8217;s Complaint does it accuse Discord of creating the offensive messaging, but rather the Complaint seeks to hold Discord liable for facilitating – or failing to moderate – sexually exploitative offensive messaging created by others. The fact that Discord may have provided the “tools” by which Plaintiff and her alleged abusers exchanged messages, to “carry out what may be unlawful or illicit” does not make Discord a “content provider,” but rather treats Discord as a “publisher” of (offensive) messaging created by third parties.</p></blockquote>
<p><em>Implications</em></p>
<p>A reminder that sexual predation cases involve heartbreaking facts. Section 230 often arises in tragic circumstances.</p>
<p>The Section 230 jurisprudence is coming apart at the seams, as illustrated by this ruling. I think this court got it right and disagreeing courts got it wrong. However, there is now enough precedent on both sides of every issue to vex everyone. This opinion carefully prioritized appellate rulings, which have largely rejected the design defect workarounds to Section 230. However, many more design defect cases are heading to appellate courts across the country, and any appellate deviation in any one of those cases will tear Section 230 even further apart.</p>
<p><em>Case Citation</em>: Jane Doe v. Discord Inc., 2026 WL 1067574 (N.D. Ohio April 20, 2026). The <a href="https://www.singletonschreiber.com/assets/htmldocuments/noindex/Jane%20Doe%20v%20Discord%20Inc.%20Complaint.pdf">complaint</a>.</p>
<p>The post <a href="https://blog.ericgoldman.org/archives/2026/04/section-230-helps-discord-defeat-defective-design-claims-regarding-sexual-predation-jane-doe-v-discord.htm">Section 230 Helps Discord Defeat &#8220;Defective Design&#8221; Claims Regarding Sexual Predation&#8211;Jane Doe v. Discord</a> appeared first on <a href="https://blog.ericgoldman.org">Technology &amp; Marketing Law Blog</a>.</p>
]]></content:encoded>
					
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">28812</post-id>	</item>
		<item>
		<title>U.S. Supreme Court Narrows Secondary Liability in Copyright Law&#8211;Cox v. Sony (Guest Blog Post)</title>
		<link>https://blog.ericgoldman.org/archives/2026/04/u-s-supreme-court-narrows-secondary-liability-in-copyright-law-cox-v-sony-guest-blog-post.htm</link>
					<comments>https://blog.ericgoldman.org/archives/2026/04/u-s-supreme-court-narrows-secondary-liability-in-copyright-law-cox-v-sony-guest-blog-post.htm#comments</comments>
		
		<dc:creator><![CDATA[Eric Goldman]]></dc:creator>
		<pubDate>Thu, 16 Apr 2026 17:20:27 +0000</pubDate>
				<category><![CDATA[Copyright]]></category>
		<category><![CDATA[Derivative Liability]]></category>
		<category><![CDATA[Trademark]]></category>
		<guid isPermaLink="false">https://blog.ericgoldman.org/?p=28791</guid>

					<description><![CDATA[<p>Guest Blog Post by Prof. Tyler Ochoa On March 25, the U.S. Supreme Court unanimously held that Cox Communications, an internet access provider, is not liable for file-sharing infringements committed by its users.  Cox Communications, Inc. v. Sony Music Entertainment,...</p>
<p>The post <a href="https://blog.ericgoldman.org/archives/2026/04/u-s-supreme-court-narrows-secondary-liability-in-copyright-law-cox-v-sony-guest-blog-post.htm">U.S. Supreme Court Narrows Secondary Liability in Copyright Law&#8211;Cox v. Sony (Guest Blog Post)</a> appeared first on <a href="https://blog.ericgoldman.org">Technology &amp; Marketing Law Blog</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>Guest Blog Post by Prof. <a href="https://law.scu.edu/faculty/faculty-list/ochoa.html">Tyler Ochoa</a></p>
<p>On March 25, the U.S. Supreme Court unanimously held that Cox Communications, an internet access provider, is not liable for file-sharing infringements committed by its users.  <a href="https://www.supremecourt.gov/opinions/25pdf/24-171_bq7d.pdf"><em>Cox Communications, Inc. v. Sony Music Entertainment</em></a>, No. 24-171  (U.S. March 25, 2026).  In so holding, the Court rejected a $1 billion jury verdict in favor of Sony and other copyright owners (which the Fourth Circuit had already held should be remanded for retrial, but only on damages).  The majority opinion (by Justice Thomas, for seven justices) also seemingly rejected the “knowledge plus material contribution” standard for contributory infringement that has been used by the Courts of Appeals in case law for over 50 years.  Two concurring justices (Sotomayor, joined by Jackson) would have preserved that standard, but they would have interpreted it more narrowly than the Fourth Circuit had done.</p>
<p>The decision is a decisive victory for Cox and other internet access providers, and it will be welcomed by any defendant facing claims of contributory infringement.  (The Court did not purport to decide any issues regarding vicarious liability, but the opinion may be helpful to those defendants as well.)  The decision is also a stinging loss for major copyright owners, who have been trying for years to get courts to hold internet service providers and other intermediaries liable for copyright infringements committed by their users.  The opinion makes it significantly harder to do that.  Copyright owners will likely seek legislative relief, but it seems unlikely that Congress will be able to agree on legislation that will satisfy the major interest groups.  I also predict that defendants facing secondary liability claims in trademark cases will try to use the opinion to narrow contributory infringement in trademark law as well.</p>
<p>If you are <em>not</em> already familiar with secondary liability in copyright law, some background is needed to understand the full implications.  If you <em>are</em> already familiar with the existing law and the facts, you can skip straight to my analysis of the majority opinion.</p>
<p><strong>Secondary Liability Before the 1976 Act</strong></p>
<p>The first Supreme Court case to find contributory infringement was <a href="https://scholar.google.com/scholar_case?case=11411674779195935032"><em>Kalem Co. v. Harper Brothers</em></a>, 222 U.S. 55 (1911).  The Second Circuit explained the facts:</p>
<blockquote><p>The late Gen. Lew Wallace wrote a story called ‘Ben Hur,’ the copyright of which belongs to the complainants Harper &amp; Bros. The complainants Klaw &amp; Erlanger caused the story to be dramatized, and Harper &amp; Bros. duly copyrighted the dramatization and thereupon granted Klaw &amp; Erlanger the sole right of producing the same upon the stage. The defendant the Kalem Company also employed a writer to read the story, without having any knowledge of the copyrighted drama, and to write a description of certain portions of it. It then produced persons and animals, with their accouterments, to perform the actions and motions so described … from which a positive film suitable for exhibition purposes was reproduced.</p></blockquote>
<p><em>Harper &amp; Bros. v. Kalem Co.</em>, 161 F. 61, 62 (2d Cir. 1909).  Under the 1870 Act (as amended), the copyright owner of a book had “the sole liberty of printing, reprinting, publishing, completing, copying, executing, finishing, and vending the same; and, in the case of a dramatic composition, of publicly performing or representing it, or causing it to be performed or represented by others. And authors or their assigns shall have [the] exclusive right to dramatize or translate any of their works for which copyright shall have been obtained.”  The Second Circuit held that the 15-minute film did not itself infringe the publisher’s rights: “as pictures only represent the artist’s idea of what the author has expressed in words, they do not infringe a copyrighted book or drama, and should not as a photograph be enjoined.”  161 F. at 63.  When the film was exhibited in theaters, however, that violated the exclusive rights to dramatize and to publicly perform the novel, and the producers were liable for those actions:</p>
<blockquote><p>It is next objected that the defendant cannot be held as a contributory infringer, because its films are capable of innocent use; e.g., exhibitions for private amusement. This fact only compels the complainants to prove that the defendant does promote a guilty use of them. Inasmuch as it advertises the films as capable of producing a moving picture spectacle of Ben Hur, and sends its advertisements to proprietors of theatoriums with the expectation and hope that they will use them for public exhibitions, charging an entrance fee, and inasmuch as many of these proprietors have so used them, the defendant is clearly guilty of contributory infringement.</p></blockquote>
<p>161 F. at 64.  On appeal, the Supreme Court assumed without deciding that the first holding was correct, and it then affirmed the second holding:</p>
<blockquote><p>It is said that pictures of scenes in a novel may be made and exhibited without infringing the copyright, and that they may be copyrighted themselves. Indeed, it was conceded by the circuit court of appeals that these films could be copyrighted, and, we may assume, could be exhibited as photographs. Whether this concession is correct or not, in view of the fact that they are photographs of an unlawful dramatization of the novel, we need not decide. We will assume that it is. But it does not follow that the use of them in motion does not infringe the author&#8217;s rights. The most innocent objects … may be used for unlawful purposes. And if, as we have tried to show, moving pictures may be used for dramatizing a novel, when the photographs are used in that way, they are used to infringe a right which the statute reserves.</p>
<p>… [I]t is said that the defendant did not produce the [dramatic] representations, but merely sold the films to jobbers, and on that ground ought not to be held. In some cases where an ordinary article of commerce is sold nice questions may arise as to the point at which the seller becomes an accomplice in a subsequent illegal use by the buyer. It has been held that mere indifferent supposition or knowledge on the part of the seller that the buyer of spirituous liquor [is] contemplating such unlawful use is not enough to connect him with the possible unlawful consequences….  But no such niceties are involved here. The defendant not only expected but invoked by advertisement the use of its films for dramatic reproduction of the story. That was the most conspicuous purpose for which they could be used, and the one for which especially they were made. If the defendant did not contribute to the infringement, it is impossible to do so except by taking part in the final act. It is liable on principles recognized in every part of the law.</p></blockquote>
<p>222 U.S. at 62-63.</p>
<p>Six decades later, the Second Circuit set forth the standard formulation of secondary liability used in the Courts of Appeals (until now), in <a href="https://scholar.google.com/scholar_case?case=13919786496570065695"><em>Gershwin Publishing Corp. v. Columbia Artists Management, Inc.</em></a>, 443 F.2d 1159 (2d Cir. 1971).  The <em>Gershwin</em> court held there are two types of secondary liability: “vicarious” liability (based on the relationship between the direct infringer and the person to be held liable) and “contributory” infringement:</p>
<blockquote><p>Although the Act does not specifically delineate what kind or degree of participation in an infringement is actionable, it has long been held that one may be liable for copyright infringement even though he has not himself performed the protected composition. For example, a person who has promoted or induced the infringing acts of the performer has been held jointly and severally liable as a “vicarious” infringer, even though he has no actual knowledge that copyright monopoly is being impaired. Although vicarious liability was initially predicated upon the agency doctrine of <em>respondeat superior</em>, this court recently held that even in the absence of an employer-employee relationship one may be vicariously liable if he has the right and ability to supervise the infringing activity and also has a direct financial interest in such activities. <a href="https://scholar.google.com/scholar_case?case=11617630515138458269"><em>Shapiro, Bernstein &amp; Co., Inc. v. H. L. Green Co</em>.</a>, [316 F.2d 304, 307 (2d Cir. 1963)].</p>
<p>Similarly, one who, with knowledge of the infringing activity, induces, causes or materially contributes to the infringing conduct of another, may be held liable as a “contributory” infringer….</p></blockquote>
<p>443 F.2d at 1161-62.</p>
<p><strong>Meanwhile, in Patent Law</strong></p>
<p>In patent law, two sub-types of “contributory” infringement were separated and codified in the 1952 Patent Act, at <a href="https://www.law.cornell.edu/uscode/text/35/271">35 U.S.C. § 271</a>:</p>
<blockquote><p>(b) Whoever actively induces infringement of a patent shall be liable as an infringer.</p>
<p>(c) Whoever offers to sell or sells within the United States or imports into the United States a component of a patented machine, manufacture, combination or composition, or a material or apparatus for use in practicing a patented process, constituting a material part of the invention, knowing the same to be especially made or especially adapted for use in an infringement of such patent, and not a staple article or commodity of commerce suitable for substantial noninfringing use, shall be liable as a contributory infringer.</p></blockquote>
<p>In <a href="https://scholar.google.com/scholar_case?case=383599729618181804"><em>Global-Tech Appliances, Inc. v. SEB S.A.</em></a>, 563 U.S. 754 (2011), the Supreme Court reaffirmed “that induced infringement under § 271(b) requires knowledge that the induced acts constitute patent infringement.” 563 U.S. at 766. Thus, “deliberate indifference to a known risk that a patent exists is not the appropriate standard under § 271(b).” <em>Id</em>.  Nonetheless, the Court affirmed the holding that Pentalpha was liable for active inducement, holding that “willful blindness” can substitute for actual knowledge of a patent. <em>Id</em>. at 766, 768.  For willful blindness, “[t]he defendant must subjectively believe that there is a high probability that a fact exists and (2) the defendant must take deliberate actions to avoid learning of that fact.” 563 U.S. at 769.  In other words, “a willfully blind defendant is one who takes deliberate actions to avoid confirming a high probability of wrongdoing.” <em>Id</em>.  Neither recklessness (“one who merely knows of a substantial and unjustified risk of such wrongdoing”) nor negligence (“one who should have known of a similar risk but, in fact, did not”) is sufficient to show inducement. <em>Id</em>. at 770.</p>
<p><strong>Secondary Liability After 1976 and Before <em>Cox</em></strong></p>
<p>The 1976 Copyright Act did not expressly address secondary liability.  <a href="https://www.law.cornell.edu/uscode/text/17/106">Section 106</a> of the Act grants the copyright owner “the exclusive rights to do and to authorize” five activities (reproduction, prepare derivative works, public distribution, public performance, and public display); and the legislative history stated “[u]se of the phrase ‘to authorize’ is intended to avoid any question as to the liability of contributory infringers. For example, a person who lawfully acquires an authorized copy of a motion picture would be an infringer if he or she engages in the business of renting it to others for purposes of unauthorized public performance.”  <a href="https://en.wikisource.org/wiki/Page:H.R._Rep._No._94-1476_(1976)_Page_061.djvu">H.R. Rep. No. 94-1476</a>, at 61 (1976).</p>
<p>Another paragraph in the legislative history addressed vicarious liability:</p>
<blockquote><p>The committee has considered and rejected an amendment to this section intended to exempt the proprietors of an establishment … from liability for copyright infringement, committed by an independent contractor.…  A well-established principle of copyright law is that a person who violates any of the exclusive rights of the copyright owner is an infringer, including persons who can be considered related or vicarious infringers. To be held a related or vicarious infringer in the case of performing rights, a defendant must either actively operate or supervise the operation of the place wherein the performances occur, or control the content of the infringing program, and expect commercial gain from the operation and either direct or indirect benefit from the infringing performance. The committee has decided that no justification exists for changing existing law, and causing a significant erosion of the public performance right.</p></blockquote>
<p><a href="https://en.wikisource.org/wiki/Page:H.R._Rep._No._94-1476_(1976)_Page_159.djvu">H.R. Rep. 94-1476</a>, at 159-60 (1976).  Apparently, Congress did not anticipate the rise of so-called textualism as a dominant (but inconsistently applied) principle of statutory interpretation, with the concomitant reluctance of textualist judges to read and rely on legislative history, or to interpret a statute in light of existing common-law principles.</p>
<p>The first major case that arose under the 1976 Act was <a href="https://scholar.google.com/scholar_case?case=5876335373788447272"><em>Sony Corp. of America v. Universal City Studios, Inc.</em></a>, 484 U.S. 417 (1984). (The case actually was filed before the effective date of the new Act; but the trial included two instances of infringement that occurred after the effective date, January 1, 1978; and both the Ninth Circuit and the Supreme Court primarily cited and relied on the 1976 Act.)</p>
<p>In <em>Sony</em>, Universal and Disney sued Sony for making and distributing the Sony Betamax, the first VCR for home use.  They argued that consumers used the VCR to make reproductions of its over-the-air broadcast programs without its consent (direct infringement), and that Sony should be held liable for contributory infringement for providing the means to make those infringements. The District Court refused to grant a preliminary injunction and held after a bench trial that Sony was not liable; but the Ninth Circuit reversed, holding that Sony was liable; and the Supreme Court granted <em>certiorari</em>.</p>
<p>At the time of trial, there were only about 800,000 VCRs in the United States; but by the time the case reached the Supreme Court (it was argued in January 1983), about 10 million VCRs had been sold.  As <a href="https://repository.law.umich.edu/cgi/viewcontent.cgi?article=1214&amp;context=book_chapters">Prof. Jessica Litman has previously reported</a>, the Justices initially voted 5-4 to affirm, and Justice Blackmun was assigned the majority opinion, while Justice Stevens undertook to pen the dissent.  Justice O’Connor, however, had second thoughts and could not agree with Justice Blackmun’s opinion.  The Court could not reach a consensus by June, so the case was reargued in October 1983.  When the opinion was issued in January 1984, Justice O’Connor had switched her vote, giving Justice Stevens a 5-4 majority.</p>
<p>Justice Stevens’s majority opinion borrowed the “staple article of commerce” doctrine from patent law (codified in 35 U.S.C. § 271(b)), saying:</p>
<blockquote><p>We recognize there are substantial differences between the patent and copyright laws. But in both areas the contributory infringement doctrine is grounded on the recognition that adequate protection of a monopoly may require the courts to look beyond actual duplication of a device or publication to the products or activities that make such duplication possible. The staple article of commerce doctrine must strike a balance between a copyright holder&#8217;s legitimate demand for effective — not merely symbolic — protection of the statutory monopoly, and the rights of others freely to engage in substantially unrelated areas of commerce. Accordingly, the sale of copying equipment, like the sale of other articles of commerce, does not constitute contributory infringement if the product is widely used for legitimate, unobjectionable purposes. Indeed, it need merely be capable of substantial noninfringing uses….</p>
<p>The question is thus whether the Betamax is capable of commercially significant noninfringing uses….</p></blockquote>
<p>464 U.S. at 442.  Note that the majority opinion worded its standard in three different ways in three consecutive sentences, and that none of those three sentences exactly matches the wording of the patent statute (“suitable for substantial non-infringing use”).</p>
<p>The majority then held there were two “substantial noninfringing uses” for the Betamax VCR: authorized time-shifting, and unauthorized time-shifting. First, Justice Stevens noted that although Universal and Disney objected to consumers recording broadcast television on their VCRs, other copyright holders consented to such use. Representatives of the four major sports leagues (NFL, NBA, MLB, and NHL) all testified that they had no objection to consumers recording their broadcasts and watching them at a later time.  464 U.S. at 444.  What may have sealed the case was the testimony of children’s television host Mr. Rogers, who testified he thought it was great that parents could record his show and watch it with their children together when they were all at home. <em>Id</em>. at 445 &amp; n.27. Second, Justice Stevens also held that even unauthorized time-shifting was a fair use under Section 107 of the newly-enacted Copyright Act of 1976. <em>Id</em>. at 447-55.</p>
<p>One decade later, internet service providers faced a real possibility of being held liable for infringements committed by their users.  They succeeded in getting Congress to enact the Online Copyright Infringement Liability Limitation Act at Title II of the Digital Millennium Copyright Act (or DMCA).  Codified at <a href="https://www.law.cornell.edu/uscode/text/17/512">17 U.S.C. § 512</a>, the Act established four “safe harbors” for internet service providers engaging in certain types of activities: (a) “transitory digital network communications” (internet access and “backbone”); (b) “system caching” (temporary storage of material to facilitate access); (c) “hosting” of information posted by users; and (d) “information location tools” (indexing and linking).</p>
<p>To qualify for the (b), (c), and (d) safe harbors, a service provider must comply with the “notice-and-takedown” provisions in section 512(c).  (Notably, internet access providers like Cox are <em>not</em> required to comply with the notice-and-takedown provisions, because there is nothing for them to “take down”: by the time Cox is notified of infringing activity, it has already occurred; whereas the other three categories of service provider can take steps to prevent further infringement.)  And to qualify for any of the safe harbors, a service provider must have “adopted and reasonably implemented … a policy that provides for the termination in appropriate circumstances of subscribers and account holders … who are repeat infringers.”  [17 U.S.C. § 512(i)(1)(A).]  However, the safe harbors do <em>not</em> require a service provider to “monitor[] its service or affirmatively seek[] facts indicating infringing activity” [17 U.S.C. § 512(m)(1)]; and “[t]he failure … to qualify for limitation of liability under this section shall not bear adversely upon the consideration of a defense by the service provider that the service provider’s conduct is not infringing.”  [17 U.S.C. § 512(<em>l</em>).]</p>
<p>The section 512(c) and (d) safe harbors were also conditioned on the absence of facts that might otherwise make the service provider liable for infringement.  For those safe harbors, the service provider must show it:</p>
<blockquote><p>(A) (i) does not have actual knowledge that the material or an activity using the material on the system or network is infringing;</p>
<p>(ii) in the absence of such actual knowledge, is not aware of facts or circumstances from which infringing activity is apparent; or</p>
<p>(iii) upon obtaining such knowledge or awareness, acts expeditiously to remove, or disable access to, the material;</p>
<p>(B) does not receive a financial benefit directly attributable to the infringing activity, in a case in which the service provider has the right and ability to control such activity; and</p>
<p>(C) upon notification of claimed infringement …, responds expeditiously to remove, or disable access to, the material that is claimed to be infringing….</p></blockquote>
<p>17 U.S.C. § 512(c)(1), (d)(1).  Courts have interpreted these conditions narrowly.  Both “actual knowledge” and so-called “red flag” knowledge have to be knowledge of <em>specific</em> infringing activity to trigger the duty “expeditiously to remove,” because otherwise, the service provider would have to “affirmatively seek[] facts indicating infringing activity.” And the “right and ability to control such activity” has to mean “something more” than the mere ability “to remove or disable access to” the infringing material, because otherwise, satisfaction of condition (A)(iii) would render it impossible to satisfy condition (B).  <em>See</em> <a href="https://scholar.google.com/scholar_case?case=13644579048975596329"><em>Viacom Int’l, Inc. v. YouTube, Inc.</em></a>, 679 F.3d 19, 30-32, 37-38 (2d Cir. 2012); <a href="https://scholar.google.com/scholar_case?case=11327801397939418854"><em>UMG Recordings, Inc. v. Shelter Capital Partners</em></a>, 718 F.3d 1006, 1020-23, 1029-30 (9th Cir. 2013).</p>
<p>Between the enactment of the DMCA and the cases interpreting it, courts had to confront secondary liability in a series of cases involving peer-to-peer file-sharing.  In <a href="https://scholar.google.com/scholar_case?case=14102696336550697309"><em>A&amp;M Records, Inc. v. Napster, Inc.</em></a>, 239 F.3d 1004 (9th Cir. 2001), for example, Napster provided software that uploaded the file names (but not the files themselves) of all MP3 files on a user’s system to a central index on the Napster website.  A user could search the file-name index; and when the user clicked on a file name, the Napster software would initial a transfer of the file itself from one user to another (“peer to peer”).  The infringing files themselves were never uploaded to or stored on the Napster servers.  The Ninth Circuit discussed whether and how Napster should be held liable for the infringing conduct of its users:</p>
<blockquote><p>[C]ontributory liability may potentially be imposed only to the extent that Napster: (1) receives reasonable knowledge of specific infringing files with copyrighted musical compositions and sound recordings; (2) knows or should know that such files are available on the Napster system; and (3) fails to act to prevent viral distribution of the works….</p>
<p>Conversely, Napster may be vicariously liable when it fails to affirmatively use its ability to patrol its system and preclude access to potentially infringing files listed in its search index. Napster has both the ability to use its search function to identify infringing musical recordings and the right to bar participation of users who engage in the transmission of infringing files.</p></blockquote>
<p>239 F.3d at 1027. The Ninth Circuit affirmed that copyright owners were likely to succeed on both theories, although it modified the preliminary injunction.  Unable to comply with the modified injunction, Napster was forced to shut down.</p>
<p>In <a href="https://scholar.google.com/scholar_case?case=8647956476676426155">Metro-Goldwyn-Mayer, Inc. v. Grokster, Inc.</a>, 545 U.S. 913 (2005), the U.S. Supreme Court confronted two successors to Napster, Grokster and StreamCast (Morpheus), both of whom tried to avoid Napster’s fate by providing peer-to-peer file-sharing software that did not rely on a centralized index.  (Grokster’s software stored the index on various “supernodes,” while Morpheus passed a user’s search request from computer-to-computer and sent matching file names to the requesting user.)  It was thus impossible to enjoin the operation of the software, because once it was distributed, Grokster and StreamCast had no control over how it was used.  The Ninth Circuit held that distribution of the software was lawful under <em>Sony</em> because the software was capable of substantial non-infringing uses, even though it was being used primarily to infringe.  The Supreme Court reversed; and in doing so, it re-interpreted <em>Sony</em> as a case about intent:</p>
<blockquote><p><em>Sony</em> barred secondary liability based on presuming or imputing intent to cause infringement solely from the design or distribution of a product capable of substantial lawful use, which the distributor knows is in fact used for infringement. The Ninth Circuit has read <em>Sony</em>’s limitation to mean that whenever a product is capable of substantial lawful use, the producer can never be held contributorily liable for third parties’ infringing use of it[,] … even when an actual purpose to cause infringing use is shown by evidence independent of design and distribution of the product….</p>
<p>Sony&#8217;s rule limits imputing culpable intent as a matter of law from the characteristics or uses of a distributed product. But nothing in Sony requires courts to ignore evidence of intent if there is such evidence, and the case was never meant to foreclose rules of fault-based liability derived from the common law….</p></blockquote>
<p>545 U.S. at 933-35.  The Court added that “[t]he classic case of direct evidence of unlawful purpose occurs when one induces commission of infringement by another, or entices or persuades another to infringe, as by advertising.” <em>Id</em>. at 935 (cleaned up).  Accordingly,</p>
<blockquote><p>For the same reasons that <em>Sony</em> took the staple-article doctrine of patent law as a model for its copyright safe-harbor rule, the inducement rule, too, is a sensible one for copyright. We adopt it here, holding that one who distributes a device with the object of promoting its use to infringe copyright, as shown by clear expression or other affirmative steps taken to foster infringement, is liable for the resulting acts of infringement by third parties.</p></blockquote>
<p>545 U.S. at 936-37. The Court cautioned, however, that “mere knowledge of infringing potential <em>or of actual infringing uses</em> would not be enough here to subject a distributor to liability.” <em>Id</em>. at 937 (emphasis added).  Instead, “[t]he inducement rule … premises liability on purposeful, culpable expression and conduct.” <em>Id</em>.</p>
<p>The Court found such “purposeful, culpable expression and conduct” in three types of evidence. “First, each company showed itself to be aiming to satisfy a known source of demand for copyright infringement, the market comprising former Napster users.” 545 U.S. at 939. “Second, … neither company attempted to develop filtering tools or other mechanisms to diminish the infringing activity using their software.” <em>Id</em>.  Third, the software streamed ads to active users, so “the more the software is used, the more ads are sent out and the greater the advertising revenue becomes.” <em>Id</em>. at 940.  The Court cautioned that the second type of evidence would not be sufficient by itself, <em>id</em>. at 939 n.12; but combined with the other types of evidence, “the unlawful objective is unmistakable.” <em>Id</em>. at 940.</p>
<p>Over time, the substantive law of contributory infringement started to converge with the statutory standard for the § 512(c) safe harbor.  For example, in <a href="https://scholar.google.com/scholar_case?case=9280547131690965273"><em>Perfect 10, Inc. v. Amazon.com, Inc.</em></a>, 508 F.3d 1146 (9th Cir. 2007), the Ninth Circuit held that</p>
<blockquote><p>[A] computer system operator can be held contributorily liable if it has <em>actual</em> knowledge that <em>specific</em> infringing material is available using its system, and can take simple measures to prevent further damage to copyrighted works, yet [it] continues to provide access to infringing works.</p></blockquote>
<p>508 F.3d at 1172 (internal quotes and citations omitted; emphasis in original). <em>Accord</em>, <a href="https://scholar.google.com/scholar_case?case=2807886710858848675"><em>UMG Recordings, Inc. v. Grande Comms. Network, LLC</em></a>, 118 F.4th 697, 715-16 (5th Cir. 2024).  Note that after <em>Cox</em>, the Supreme Court granted <em>certiorari</em> in <em>UMG v. Grande</em>, vacated the decision, and remanded for reconsideration in light of <em>Cox v. Sony</em>. <em>UMG v. Grande</em>, No. 24-967 (U.S. April 6, 2026).</p>
<p><strong>The <em>Cox </em>Facts and Procedural Posture</strong></p>
<p>In 2013-2014, Sony and other record labels sent over 163,000 notices of claimed infringement to Cox, an internet access provider.  The notices claimed that infringing files were being made available online by users of the BitTorrent protocol, and Sony’s agent MarkMonitor identified the allegedly infringing users (or accounts) by their Internet Protocol (IP) addresses.  Although internet access providers like Cox are <em>not</em> subject to the DMCA’s notice-and-takedown provisions, Sony argued that Cox had a common-law obligation to do something about infringing users.</p>
<p>Cox responded with a 13-strike policy, starting with polite requests to subscribers that they should not infringe and ultimately escalating to terminating subscribers&#8217; accounts.  During the two-year period, Cox terminated only 32 subscribers for alleged repeat infringement; it also terminated hundreds of thousands of subscribers for nonpayment.</p>
<p>As a result, in a previous decision, the Fourth Circuit held that Cox was ineligible for the section 512 safe harbor, because it had not “adopted and reasonably implemented … a policy that provides for the termination in appropriate circumstances of subscribers and account holders … who are repeat infringers.” <a href="https://www.law.cornell.edu/uscode/text/17/512">17 U.S.C. § 512(i)(1)(A)</a>; <em>see</em> <a href="https://scholar.google.com/scholar_case?case=1661780306886265641"><em>BMG Rights Mgmt. (US) LLC v. Cox Comms., Inc.</em></a>, 881 F.3d 293 (4th Cir. 2018).</p>
<p>After a 12-day jury trial, the jury found against Cox on both contributory infringement and vicarious liability, and it further found that the infringement was willful.  The jury awarded slightly less than $100,000 in statutory damages for each of the 10,017 works at issue, for a total of $1 billion in statutory damages.  On post-trial motions, the district court largely upheld the verdict; but it agreed there was overlap in the number of works (only one award of statutory damages may be made for a sound recording of a musical work, even though there are two copyrights), so the total verdict had to be adjusted.  <a href="https://scholar.google.com/scholar_case?case=5726853682302508681"><em>Sony Music Entertainment vs. Cox Comms., Inc.</em></a>, 464 F. Supp. 3d 795 (E.D. Va. 2020).</p>
<p>On appeal, “Cox argue[d] that it does not profit directly from its subscribers&#8217; infringement because ‘[a]ll subscribers pay Cox a flat monthly fee for their internet access package no matter what they do online.’ Whether a subscriber uses her internet access for lawful or unlawful purposes, Cox receives the same monthly fee, and a subscriber&#8217;s decision to download or distribute a copyrighted song without permission does not benefit Cox.”  <a href="https://scholar.google.com/scholar_case?case=2717418478418218434"><em>Sony Music Entertainment vs. Cox Comms., Inc.</em></a>, 93 F.4th 222, 230 (4th Cir. 2024).</p>
<p>The Fourth Circuit agreed: “The continued payment of monthly fees for internet service, even by repeat infringers, was not a financial benefit flowing directly from <em>the copyright infringement itself.</em> As Cox points out, subscribers paid a flat monthly fee for their internet access no matter what they did online. Indeed, Cox would receive the same monthly fees even if all of its subscribers stopped infringing.” <em>Id</em>. at 232 (emphasis in original).  Evidence that 13% of Cox’s network traffic was attributable to peer-to-peer file-sharing, and that users who were the subject of 20 or more notices of claimed infringement paid higher monthly fees for increased data usage, did not “raise[] a reasonable inference that any Cox subscriber paid more for faster internet in order to engage in copyright infringement. As Sony’s expert testified, other data intensive activities include legally streaming movies, television shows, and music, as well as playing video games. Subscribers may have purchased high speed internet for lawful streaming and downloads or because their households had many internet users…. Sony has not identified any evidence that customers were attracted to Cox&#8217;s internet service or paid higher monthly fees because of the opportunity to infringe Plaintiffs&#8217; copyrights.”  <em>Id</em>. at 233.</p>
<p>The Fourth Circuit, however, did uphold the verdict of contributory infringement.  It first upheld the district court’s ruling on summary judgment that Sony had established the knowledge element as a matter of law, because “Cox did not argue to the district court, as it does now on appeal, that notices of past infringement failed to establish its knowledge that the same subscriber was substantially certain to infringe again.” <em>Id</em>. at 234.  On the material contribution prong, Cox argued “that it cannot be liable for materially contributing to copyright infringement because the internet service it provides is capable of substantial lawful use and not designed to promote infringement.” <em>Id</em>. at 236.  The Fourth Circuit agreed that “what matters is not simply whether the product has some or even many non-infringing uses, but whether the product is distributed with the <em>intent</em> to cause copyright infringement.” <em>Id</em>. (emphasis in original, citing <em>Grokster</em>). And it further agreed that “‘mere failure to take affirmative steps to prevent infringement’ does not establish contributory liability ‘in the absence of other evidence of intent.’” <em>Id</em>. (quoting <em>Grokster</em>).  Nonetheless, it held there was sufficient evidence of intent:</p>
<blockquote><p>The evidence at trial, viewed in the light most favorable to Sony, showed more than mere failure to prevent infringement. The jury saw evidence that Cox knew of specific instances of repeat copyright infringement occurring on its network, that Cox traced those instances to specific users, and that Cox chose to continue providing monthly internet access to those users despite believing the online infringement would continue because it wanted to avoid losing revenue.</p></blockquote>
<p><em>Id</em>.  Finally, “[h]aving reversed on one theory of liability and affirmed on the other,” the Fourth Circuit held that the case had to be remanded for a new trial on damages.</p>
<p>Both parties filed petitions for <em>certiorari</em>.  The Supreme Court denied Sony’s petition, which sought review on the question: “Whether the profit requirement of vicarious copyright infringement permits liability where the defendant expects commercial gain from the enterprise in which infringement occurs …, or whether the profit requirement of vicarious copyright infringement permits liability only where the defendant expects commercial gain from the act of infringement itself.” <a href="https://www.supremecourt.gov/DocketPDF/24/24-181/322686/20240816160133976_2024-08-16%20Sony%20Cert%20Petition%20-%20Final.pdf">Petition for a Writ of <em>Certiorari</em></a> , Sony Music Entertainment v. Cox Comms., Inc., No. 24-181 (U.S. filed Aug. 16, 2024), <em>cert. denied</em>, 145 S.Ct. 2844 (U.S. June 30, 2025). But on the <a href="https://www.supremecourt.gov/DocketPDF/24/24-171/359730/20250527172556075_Cox-Sony.CVSG.pdf">recommendation of the Solicitor General</a>, the Supreme Court granted Cox’s petition, which presented two questions:</p>
<blockquote><p>Did the Fourth Circuit err in holding that a service provider can be held liable for “materially contributing” to copyright infringement merely because it knew that people were using certain accounts to infringe and did not terminate access, without proof that the service provider affirmatively fostered infringement or otherwise intended to promote it?</p>
<p>Did the Fourth Circuit err in holding that mere knowledge of another’s direct infringement suffices to find willfulness under 17 U.S.C. § 504(c)?</p></blockquote>
<p><a href="https://www.supremecourt.gov/DocketPDF/24/24-171/322523/20240815090212089_240802a%20Petition%20for%20efiling.pdf">Petition for a Writ of <em>Certiorari</em></a>, Cox Comms., Inc. v. Sony Music Entertainment, No. 24-171 (U.S. filed Aug. 15, 2024), <em>cert. granted</em>, 145 S.Ct. 2841 (U.S. June 30, 2025).  The second question received little attention at oral argument, and the Court did not directly address it in the written opinion. Nonetheless, given the Court’s holding on the first question, one can infer that “mere knowledge of another’s direct infringement” will <em>not</em> suffice to find that a contributory infringer acted “willfully” for purposes of statutory damages.</p>
<p><strong>The Majority Opinion</strong></p>
<p>Justice Thomas’ majority opinion (for seven justices) is brief: just ten pages, four of which are devoted to the facts and procedural posture.  At the end of a short introduction, he states the Court’s conclusion: “a company is not liable as a copyright infringer for merely providing a service to the general public with knowledge that it will be used by some to infringe copyrights.” [Slip op. at 1]  That brief conclusion breaks little new ground; it is essentially a restatement of the holding of the <em>Sony</em> Betamax case, with “service” substituted for “product.” It is the application of that standard to these facts that is controversial, especially since the Fourth Circuit had specifically held there was sufficient evidence that Cox <em>intended</em> to cause infringement.</p>
<p>On the second page, the majority restates some basic principles from <em>Grokster</em>:</p>
<blockquote><p>The provider of a service is contributorily liable for a user’s infringement if it intended its service to be used for infringement. To establish that a provider intended its service to be used for infringement, a copyright owner must show one of two things. First, it can show that a party affirmatively “induc[ed]” the infringement. <em>Ibid</em>. Or, second, it can show that the party sold a service tailored to infringement. <em>Id</em>., at 942 (Ginsburg, J., concurring). Patent law, with which copyright law has a “historic kinship,” … tracks these two requirements. See 35 U. S. C. §§271(b), (c). [Slip op. at 2]</p></blockquote>
<p><a href="https://blog.ericgoldman.org/wp-content/uploads/2026/03/copyright-tailor-v2.jpg"><img loading="lazy" decoding="async" class="alignright size-medium wp-image-28734" src="https://blog.ericgoldman.org/wp-content/uploads/2026/03/copyright-tailor-v2-200x300.jpg" alt="" width="200" height="300" srcset="https://blog.ericgoldman.org/wp-content/uploads/2026/03/copyright-tailor-v2-200x300.jpg 200w, https://blog.ericgoldman.org/wp-content/uploads/2026/03/copyright-tailor-v2-683x1024.jpg 683w, https://blog.ericgoldman.org/wp-content/uploads/2026/03/copyright-tailor-v2-768x1152.jpg 768w, https://blog.ericgoldman.org/wp-content/uploads/2026/03/copyright-tailor-v2.jpg 1024w" sizes="auto, (max-width: 200px) 100vw, 200px" /></a>Previous opinions (<em>Grokster</em> and <em>Sony</em>) had established there was liability if either of those two things was shown.  What is new is that these are apparently the <em>only</em> two means that will render a service provider contributorily liable.  The majority is so committed to textualism that it restricts contributory liability in copyright law to the two avenues (inducement and “tailoring”) that are codified in patent law, a different statute.</p>
<p>(It is worth noting that Justice Ginsburg’s concurring opinion in <em>Grokster</em> nowhere mentions the word “tailored.”  Here is what she said on page 942: “Liability under our juris­prudence may be predicated on actively encouraging (or inducing) infringement through specific acts … or on distributing a product [that] distributees use to infringe copyrights, if the product is not capable of ‘substantial’ or ‘commercially significant’ noninfringing uses.” Her opinion does not suggest that those are the <em>only</em> two ways of proving contributory liability. And even that statement was only for three justices (Ginsburg, Rehnquist, and Kennedy), not for the Court.)</p>
<p>After explaining the facts and procedural posture, the majority opinion returned to Justice Thomas’s “textualism” theme:</p>
<blockquote><p>The Copyright Act does not expressly render anyone liable for infringement committed by another.” <em>Sony</em>, 464 U. S., at 434. Ordinarily, when Congress intends to impose secondary liability, it does so expressly….  Although our precedents have recognized specific forms of secondary copyright liability that predated the Copyright Act, we are loath to expand such liability beyond those precedents. [Slip op. at 6-7]</p></blockquote>
<p>Why would the Court be “loath to expand such liability,” especially when the Court said in <em>Grokster</em> that <em>Sony</em> “was never meant to foreclose rules of fault-based liability derived from the common law”? 545 U.S. at 934-35.  Again, the only answer I can find is textualism: the Court thinks Congress should write the rules for secondary liability (even though Congress in 1976 believed that courts should continue the common-law tradition in many respects).  In the Court’s view, Congress did what it was supposed to do in codifying secondary liability in patent law; so the majority does not want to go beyond those boundaries in the related field of copyright law, notwithstanding the “rules of fault-based liability derived from the common law.”</p>
<p>That the majority is limiting contributory infringement to those two means is made abundantly clear in the next paragraph: “The provider of a service is contributorily liable for the user’s infringement <em>only</em> if it intended that the provided service be used for infringement. The intent required for contributory liability can be shown <em>only</em> if the party induced the infringement or the provided service is tailored to that infringement.” [Slip op. at 7, emphasis added]  The majority then discusses the two relevant examples from its own case law [<em>Grokster</em> and <em>Sony</em>]:</p>
<blockquote><p>A provider induces infringement if it actively encourages infringement through specific acts. For example, in <em>Grokster</em>, … [t]he companies promoted and marketed their software as a tool to infringe copyrights … [and] [t]he “principal object” of their business models “was use of their software to download copyrighted works.” …</p>
<p>A service is tailored to infringement if it is “not capable of ‘substantial’ or ‘commercially significant’ noninfringing uses.” …</p>
<p>These two forms of contributory infringement track patent law…. [Slip op. at 7-8]</p></blockquote>
<p>There is no analysis here: no discussion of Congressional intent, legislative history, or public policy.  There is no discussion of the two decades of lower court cases that had addressed the issue.  No discussion of the “(specific) knowledge plus material contribution” standard.  The majority opinion is nothing more than assertion: here are two types of contributory infringement that the Court has previously recognized, and we are not going to go beyond them.</p>
<p><a href="https://blog.ericgoldman.org/wp-content/uploads/2022/11/strawman-meme.jpg"><img loading="lazy" decoding="async" class="alignright size-medium wp-image-24583" src="https://blog.ericgoldman.org/wp-content/uploads/2022/11/strawman-meme-300x225.jpg" alt="" width="300" height="225" srcset="https://blog.ericgoldman.org/wp-content/uploads/2022/11/strawman-meme-300x225.jpg 300w, https://blog.ericgoldman.org/wp-content/uploads/2022/11/strawman-meme.jpg 600w" sizes="auto, (max-width: 300px) 100vw, 300px" /></a>In the next paragraph, the Court rejects a “straw man” argument, saying:</p>
<blockquote><p>This Court has repeatedly made clear that mere knowledge that a service will be used to infringe is insufficient to establish the required intent to infringe. In <em>Kalem Co.</em>, the Court explained that “mere indifferent supposition or knowledge on the part of the seller” that the buyer will use the product unlawfully is “not enough” to make the seller liable for the buyer’s conduct. 222 U. S., at 62…. And, in <em>Grokster</em>, the Court confirmed that “a court would be unable to find contributory infringement liability merely based on a failure to take affirmative steps to prevent infringement.” 545 U.S. at 939, n.12. [Slip op. at 8-9]</p></blockquote>
<p>Here, the majority fails to grapple with the difference between a product and a service.  In <em>Sony</em>, the manufacturer sold VCRs to customers and had no further involvement with them.  It had constructive knowledge that some of them would use the product to infringe, but it had no way of knowing which ones.  But a service provider has an ongoing relationship with its users.  The service provider may lack specific knowledge at the outset; the question is whether it needs to terminate the ongoing relationship once it learns that a specific user intends to infringe.</p>
<p>The Court then restated its conclusion:</p>
<blockquote><p>Thus, Cox is not contributorily liable for the infringement of Sony’s copyrights. Cox provided Internet service to its subscribers, but it did not intend for that service to be used to commit copyright infringement. Holding Cox liable merely for failing to terminate Internet service to infringing accounts would expand secondary copyright liability beyond our precedents.</p>
<p>… As for inducement, … Sony provided no “evidence of express promotion, marketing, and intent to promote” infringement … [and] Cox repeatedly discouraged copyright infringement by sending warnings, suspending services, and terminating accounts.  As for providing a service tailored to infringement, … Cox simply provided Internet access, which is used for many purposes other than copyright infringement. [Slip op. at 9]</p></blockquote>
<p>The Court disapproved the Fourth Circuit’s holding that “supplying a product with knowledge that the recipient will use it to infringe copyrights is . . . sufficient for contributory infringement.”  That standard was based on the Second Circuit’s <em>Gershwin</em> opinion, which was cited in <em>Grokster</em> with apparent approval; and it had been adopted by all of the Courts of Appeals to consider the issue.  The Supreme Court did not grapple with any of that case law; instead, it simply said that the Fourth Circuit’s standard “went beyond the two forms of liability recognized in <em>Grokster</em> and <em>Sony</em>.” [Slip op. at 9-10]</p>
<p>Finally, the Court brusquely dismissed Sony’s argument that “Congress must have enacted the DMCA on the presumption that Internet service providers could be held liable in cases such as these” [Slip op. at 10], saying: “The DMCA merely creates new <em>defenses</em> from liability for such providers. And, the DMCA made clear that failure to comply with the safe-harbor rules ‘shall not bear adversely upon . . . a defense by the service provider that the service provider’s conduct is not infringing.’ §512(<em>l</em>).”</p>
<p>The Court could have noted (but didn’t) that, unlike other service providers, internet access providers like Cox are <em>not</em> subject to the notice-and-takedown provisions of section 512(c).  Sony’s attempt to make them liable by sending Cox tens of thousands of notices of claimed infringement therefore contradicts the implicit assumption that Congress made that hosting, caching, or linking to infringing material should be treated differently from internet “backbone” providers and internet access providers, like Cox.</p>
<p><strong>The Concurring Opinion</strong></p>
<p>Justice Sotomayor, joined by Justice Jackson, concurred in the result only.  Her concurring opinion criticized the majority for abandoning other common-law species of contributory liability:</p>
<blockquote><p>The majority holds that Cox is not liable solely because its conduct does not fit within the two theories of secondary liability previously applied by this Court. In so doing, the majority, without any meaningful explanation, unneces­sarily limits secondary liability even though this Court’s precedents have left open the possibility that other common-law theories of such liability, like aiding and abetting, could apply in the copyright context.</p>
<p>I nonetheless agree with the majority that Cox cannot be held liable here for a different reason. Plaintiffs cannot prove that Cox had the requisite intent to aid copyright infringement for Cox to be liable on a common-law aiding-­and-abetting theory.</p></blockquote>
<p>[Conc. op. at 1-2]</p>
<p>The concurring justices agreed that “this Court’s cases have held that contributory liability for copyright infringement may attach in at least two circumstances”: “distributing or providing a product or service that is incapable of “commercially significant noninfringing uses” [Conc. op. at 2] and inducement [Conc. op. at 3]. They also agreed with the majority that “neither of the[se] two prior theories of secondary liability … covers Cox’s conduct” [<em>id</em>.], and that “[t]he provider of a service is contributorily liable for the user’s infringement only if it intended that the provided service be used for in­fringement.” [<em>Id</em>.]  They disagreed, however, with the majority’s assertion that “[t]he intent required for contributory liability can be shown <em>only</em> if the party induced the infringement or the provided service is tailored to that infringement.” [Conc. op. at 3-4 (emphasis added)]  “The inflexible limit the majority imposes is nowhere to be found in either <em>Sony </em>or <em>Grokster</em>.” [<em>Id</em>. at 4]</p>
<p>Instead, “[p]roperly understood, <em>Sony </em>and <em>Grokster </em>preserved other forms of secondary liability derived from the common law.” [Conc. op. at 4]  In <em>Sony</em>, the Court stated that “‘[t]he absence of such express language in the copy­right statute does not preclude the imposition of’ secondary liability, … be­cause both forms of liability are ‘imposed in virtually all areas of the law.’ 464 U. S., at 434-35.” [<em>Id</em>.]  And in <em>Grokster</em>, the Court explained “that <em>Sony </em>neither ‘displace[d] other theories of secondary liability’ nor ‘foreclose[d] rules of fault-based li­ability derived from the common law.’ 545 U. S., at 934-35.” [<em>Id</em>.]</p>
<p>After reviewing 17 U.S.C. § 512, the concurring opinion then complained that the majority opinion undermines the “safe harbors”: “The majority’s new rule completely upends that balance and consigns the safe harbor provision to obsolescence…. After today, … ISPs no longer face any realistic probability of secondary liability for copyright infringement, regardless of whether they take steps to address infringement on their networks and re­gardless of what they know about their users’ activity.” [Conc. op. at 6]</p>
<p>The concurring opinion sensibly concludes that the majority should have applied “the common-law doctrine of aiding and abetting.”  It cautioned, however, that “aiding-and-abetting liability requires proof that the defendant aided another with the intent of helping that other person succeed in committing wrongful conduct.” [Conc. op. at 7]  It cited <a href="https://blog.ericgoldman.org/archives/2023/05/the-internet-survives-scotus-review-this-time-twitter-v-taamneh-and-gonzalez-v-google.htm"><em>Twitter, Inc. v. Taamneh</em></a>, 598 U. S. 471 (2023), for the proposition that “the defendant has to take some ‘affirmative act’ ‘with the intent of facilitating the offense’s commission.’” [Conc. op. at 8]  It also explained that:</p>
<blockquote><p>The common law … recognizes that intent can sometimes be inferred from what the defendant knew when he acted. The Second Re­statement of Torts explains that this kind of knowledge-based intent can be found where “the actor knows that the consequences are certain, or substantially certain, to result from his act, and still goes ahead. [Conc. op. at 8]</p></blockquote>
<p>Applying this standard, the concurring opinion found insufficient evidence of any specific intent to infringe:</p>
<blockquote><p>Cox is merely supplying internet service to its cus­tomers. Nothing about that conduct is inherently culpable: Most internet traffic is lawful, and supplying an internet connection is just as consistent with lawful purposes as it is with unlawful purposes….</p>
<p>Nor have plaintiffs shown that Cox intended to aid spe­cific instances of infringement. That is because, based on plaintiffs’ evidence, Cox does not actually know that specific users will commit infringement using Cox’s network….</p>
<p>… Take, for example, a connection sold to a single-family home. Cox, after receiving three notices of copyright violations, would know only that that home’s connection is substantially certain to be used again in the future to com­mit infringement. Yet Cox would have no knowledge … who within the household committed infringe­ment. Nor … have plaintiffs shown any way for Cox to know if the infringer was a neighbor who might have the Wi-Fi password. Without that knowledge, it is not reasonable to infer that Cox intended to aid infringement committed by another person just because it provided an internet connection to some unknown infringer. [Conc. op. at 10-11]</p></blockquote>
<p>“Cox [also] provides internet service to regional ISPs who in turn supply internet service to thousands of users.” [Conc. op. at 11-12]  There is no way for either Cox or the regional ISPs to know which of the thousands of users are “substantially certain” to infringe based on the notices. “The same is true for connections Cox provides to university housing, hospitals, military bases, and other places that are likely to have many different users.” [Conc. op. at 12]</p>
<p><strong>What About Trademark Law?</strong></p>
<p>In <em>Cox</em>, the Supreme Court expressly disapproved the Fourth Circuit’s holding that “supplying a product with knowledge that the recipient will use it to infringe copyrights is . . . sufficient for contributory infringement.”  It failed to note, however, that the standard it disapproved is virtually identical to the Supreme Court’s <em>own</em> standard for contributory infringement in trademark law.</p>
<p>In <a href="https://scholar.google.com/scholar_case?case=5946191720195736097"><em>Inwood Labs., Inc. v. Ives Labs., Inc.</em></a>, 456 U.S. 844 (1982), the Supreme Court expressed the standard for contributory infringement as follows:</p>
<blockquote><p>[I]f a manufacturer or distributor intentionally induces another to infringe a trademark, or if it continues to supply its product to one whom it knows or has reason to know is engaging in trademark infringement, the manufacturer or distributor is contributorially responsible for any harm done as a result of the deceit.</p></blockquote>
<p>456 U.S. at 854.  Two features of this statement are notable.  First, unlike in patent law, it is <em>not</em> limited to defendants who have actual knowledge of the infringement (or willful blindness), but it includes those who have “reason to know” of infringement. That sounds like a negligence standard, rather than an intent standard.  Second, except for the “reason to know” language, it is virtually identical to the standard that the Supreme Court just disapproved in <em>Cox</em>.  This raises the question whether the <em>Cox</em> case will be used to call into question the trademark standard.</p>
<p>On the one hand, the Court has repeatedly referred to the “historic kinship” that patent law shares with copyright law.  Both are authorized in the same Constitutional clause (<a href="https://www.law.cornell.edu/constitution/articlei">Art. I, §8, cl. 8</a>), and both are intended to provide creators with a financial incentive to create and disseminate new inventions (patent) and new creative works (copyright).  By contrast, federal trademark law rests on a very different Constitutional foundation (the Interstate Commerce Clause, <a href="https://www.law.cornell.edu/constitution/articlei">Art. I, §8, cl. 3</a>) and serves different purposes (preventing consumer confusion and allowing a producer to reap the benefit of a reputation for quality). Indeed, in <a href="https://scholar.google.com/scholar_case?case=16325901757245549654"><em>The Trademark Cases</em></a>, 100 U.S. 82 (1879), the Supreme Court held that trademarks were neither “inventions” nor “writings,” so that federal trademark law could <em>not</em> be authorized by the Patent and Trademark Clause.  A lower court could certainly distinguish <em>Inwood</em> on those grounds.  On the other hand, there seems to be no good reason why general principles of secondary liability that are applicable to statutory torts generally should not be applied in the same manner to both copyrights and trademarks.</p>
<p>It remains to be seen whether <em>Cox</em> will upset the <em>Inwood</em> standard for contributory liability that has been widely cited and relied upon in trademark law.  I predict that defendants in trademark cases will challenge the <em>Inwood</em> standard, based on <em>Cox</em>; and it seems likely that a circuit split will develop on the question of whether <em>Cox</em> changes the law of contributory infringement in trademark law or not.  If so, the Supreme Court may have to take another case to resolve this conundrum of its own making.</p>
<p><strong>Other Implications</strong></p>
<p>The <em>Cox v. Sony</em> decision is a huge victory for internet access providers, who otherwise faced the possibility of either terminating lots of users or facing large statutory damage awards.  It is also a victory for consumers, who are far less likely to be threatened with loss of internet access, which is a practical necessity in today’s society. It also reinforces the previous 2-1 decision of the Ninth Circuit that credit-card companies are not contributorily or vicariously liable for providing payment-processing services to allegedly infringing websites. <i>See <a href="https://scholar.google.com/scholar_case?case=15405734604218338562">Perfect 10, Inc. v. VISA Int&#8217;l Serv. Ass&#8217;n</a></i>, 494 F.3d 788 (9th Cir. 2007).</p>
<p>In my opinion, however, the Court should have taken the approach of the two concurring justices.  That approach would have preserved existing case law and the common-law approach to judicial rule-making, while still making it clear that losing internet access is a disproportionate penalty for alleged acts of copyright infringement.</p>
<p>One of the few benefits of the <em>Cox</em> decision is that it states a clear rule that ought to be relatively easy for lower courts to apply.  As <a href="https://blog.ericgoldman.org/archives/2026/04/the-cox-shock-a-tectonic-shift-or-just-a-tremor-guest-blog-post.htm">Prof. Rub explained</a>, the real question is whether lower courts will follow <em>Cox</em> literally, or whether they will find ways to distinguish its holding from other common situations.  When you squeeze a balloon, it tends to bulge out in other directions.  It is easy to predict that copyright owners will now focus on “inducement,” trying to argue that specific knowledge of infringing material leads to an inference of intent.  If one takes <em>Cox</em> literally, even knowledge of specific infringing files is not enough to constitute “inducement” without some affirmative steps to promote infringement; but <a href="https://blog.ericgoldman.org/archives/2026/04/will-lower-courts-find-ways-around-cox-v-sony-you-betcha.htm">one court</a> has already distinguished <em>Cox</em> on similar (albeit tenuous) legal grounds.</p>
<p>It is also easy to predict that copyright owners will now focus on “vicarious” liability, which formally remains untouched by Cox.  It is already the case that vicarious liability in copyright law has been stretched far beyond its origins in agency law: there is no requirement that there be a principal-agent relationship, only that one party have the “right and ability to control” (or “supervise”) the other party.  Most courts have held that is satisfied by a showing that the party has the ability to terminate access.  Cox would likely have been held vicariously liable if the plaintiff could have shown that it received a financial benefit from infringement.  Will advertiser-supported services fall into this category?  It seems likely that some lower courts will say “yes.”  I think an honest reading of <em>Cox</em> should lead to the conclusion that imposing vicarious liability on internet access providers should be equally problematic; but because the Court expressly did not address vicarious liability, copyright holders will surely try to use it.</p>
<p>Consequently, I think “hosting” providers will still want to follow the “notice-and-takedown” procedures in 17 U.S.C. § 512.  Unlike access providers, hosting providers face the <a href="https://blog.ericgoldman.org/archives/2023/08/ninth-circuit-reaffirms-the-server-test-for-direct-infringement-of-the-public-display-right-hunley-v-instagram-llc-guest-blog-post.htm">possibility of “direct” liability under the “server” test</a> that the Ninth Circuit uses for “direct” liability.  Unlike contributory infringement, “direct” liability and vicarious liability do not require knowledge or intent, so the absence of an intent to infringe will not save a “hosting” provider.  Compliance with the § 512(c) safe harbor, however, will keep the provider from being held liable for direct and vicarious liability as well as for contributory infringement.  That gives such providers a strong incentive to maintain their “notice-and-takedown” procedures.  It also helps with appearances, because at least it looks like the defendant is trying to do something to discourage blatant infringement.</p>
<p>The hard test will come when a hosting provider doesn’t qualify for the safe harbor: will courts let them off the hook under <em>Cox</em>, or will they find ways to work around the <em>Cox</em> opinion, as <a href="https://blog.ericgoldman.org/archives/2026/04/the-cox-shock-a-tectonic-shift-or-just-a-tremor-guest-blog-post.htm">Prof. Guy Rub recently argued in this space?</a>  Only time will tell.</p>
<p><strong>Conclusion</strong></p>
<p><em>Cox v. Sony</em> is undoubtedly a landmark opinion on contributory infringement that will now appear in all copyright and IP casebooks.  It seemingly limits contributory infringement to just two theories: inducement (from <em>Grokster</em>) and “tailoring” (from <em>Sony</em>).  It seemingly rejects the “knowledge and material contribution” standard that has been used by the lower courts for over 50 years, and that the Supreme Court itself has used in trademark law.  Whether it ultimately has that effect remains to be seen; but it certainly raises multiple avenues for argument that are likely to occupy the lower courts for years to come.</p>
<p><strong>Blog Coverage of Cox v. Sony</strong></p>
<p><a title="The Cox Shock: A Tectonic Shift or Just a Tremor? (Guest Blog Post)" href="https://blog.ericgoldman.org/archives/2026/04/the-cox-shock-a-tectonic-shift-or-just-a-tremor-guest-blog-post.htm" rel="bookmark">The Cox Shock: A Tectonic Shift or Just a Tremor? (Guest Blog Post)</a></p>
<p><a title="Will Lower Courts Find Ways Around Cox v. Sony? You Betcha" href="https://blog.ericgoldman.org/archives/2026/04/will-lower-courts-find-ways-around-cox-v-sony-you-betcha.htm" rel="bookmark">Will Lower Courts Find Ways Around Cox v. Sony? You Betcha</a></p>
<p><a title="Prof. Goldstein on Cox v. Sony (Excerpt from His Treatise)" href="https://blog.ericgoldman.org/archives/2026/04/prof-goldstein-on-cox-v-sony-excerpt-from-his-treatise.htm" rel="bookmark">Prof. Goldstein on Cox v. Sony (Excerpt from His Treatise)</a></p>
<p><a title="Quick Comments on the SCOTUS Cox v. Sony Ruling" href="https://blog.ericgoldman.org/archives/2026/03/quick-comments-on-scotus-cox-v-sony-ruling.htm" rel="bookmark">Quick Comments on the SCOTUS Cox v. Sony Ruling</a></p>
<p>The post <a href="https://blog.ericgoldman.org/archives/2026/04/u-s-supreme-court-narrows-secondary-liability-in-copyright-law-cox-v-sony-guest-blog-post.htm">U.S. Supreme Court Narrows Secondary Liability in Copyright Law&#8211;Cox v. Sony (Guest Blog Post)</a> appeared first on <a href="https://blog.ericgoldman.org">Technology &amp; Marketing Law Blog</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://blog.ericgoldman.org/archives/2026/04/u-s-supreme-court-narrows-secondary-liability-in-copyright-law-cox-v-sony-guest-blog-post.htm/feed</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">28791</post-id>	</item>
		<item>
		<title>The Cox Shock: A Tectonic Shift or Just a Tremor? (Guest Blog Post)</title>
		<link>https://blog.ericgoldman.org/archives/2026/04/the-cox-shock-a-tectonic-shift-or-just-a-tremor-guest-blog-post.htm</link>
					<comments>https://blog.ericgoldman.org/archives/2026/04/the-cox-shock-a-tectonic-shift-or-just-a-tremor-guest-blog-post.htm#comments</comments>
		
		<dc:creator><![CDATA[Eric Goldman]]></dc:creator>
		<pubDate>Mon, 13 Apr 2026 15:21:10 +0000</pubDate>
				<category><![CDATA[Copyright]]></category>
		<category><![CDATA[Derivative Liability]]></category>
		<guid isPermaLink="false">https://blog.ericgoldman.org/?p=28776</guid>

					<description><![CDATA[<p>by guest blogger Prof. Guy Rub, Temple University Beasley School of Law The Supreme Court’s decision in Cox v. Sony sent a shockwave through the copyright world. In an opinion that felt like a cold shower for copyright owners, Justice Thomas essentially...</p>
<p>The post <a href="https://blog.ericgoldman.org/archives/2026/04/the-cox-shock-a-tectonic-shift-or-just-a-tremor-guest-blog-post.htm">The Cox Shock: A Tectonic Shift or Just a Tremor? (Guest Blog Post)</a> appeared first on <a href="https://blog.ericgoldman.org">Technology &amp; Marketing Law Blog</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p style="font-weight: 400;">by guest blogger Prof. <a href="https://law.temple.edu/contact/guy-rub/">Guy Rub</a>, Temple University Beasley School of Law</p>
<p style="font-weight: 400;">The Supreme Court’s decision in <em>Cox v. Sony</em> sent a shockwave through the copyright world. In an opinion that felt like a cold shower for copyright owners, Justice Thomas essentially dismantled the familiar &#8220;specific knowledge plus material contribution&#8221; framework for contributory liability that had governed the circuits for decades.</p>
<p style="font-weight: 400;"><a href="https://blog.ericgoldman.org/wp-content/uploads/2026/03/copyright-tailor-v2.jpg"><img loading="lazy" decoding="async" class="alignright size-medium wp-image-28734" src="https://blog.ericgoldman.org/wp-content/uploads/2026/03/copyright-tailor-v2-200x300.jpg" alt="" width="200" height="300" srcset="https://blog.ericgoldman.org/wp-content/uploads/2026/03/copyright-tailor-v2-200x300.jpg 200w, https://blog.ericgoldman.org/wp-content/uploads/2026/03/copyright-tailor-v2-683x1024.jpg 683w, https://blog.ericgoldman.org/wp-content/uploads/2026/03/copyright-tailor-v2-768x1152.jpg 768w, https://blog.ericgoldman.org/wp-content/uploads/2026/03/copyright-tailor-v2.jpg 1024w" sizes="auto, (max-width: 200px) 100vw, 200px" /></a>If you take the opinion at face value, holding a service provider liable for user infringement now seems to require either inducement (per Grokster) or showing that the service was “tailored to infringement” (presumably, following Sony). Meeting either of those bars is exceptionally difficult, and on paper, it could massively shrink the scope of secondary liability.</p>
<p style="font-weight: 400;">The result is that copyright owners seem to have lost a major tool to address large-scale infringement facilitated by intermediaries. More broadly, this result seems to undermine the delicate balance between copyright owners, their consumers, and intermediaries.</p>
<p style="font-weight: 400;">Unsurprisingly, the reaction has been swift and sharp. Paul Goldstein, <a href="https://blog.ericgoldman.org/archives/2026/04/prof-goldstein-on-cox-v-sony-excerpt-from-his-treatise.htm" data-saferedirecturl="https://www.google.com/url?q=https://blog.ericgoldman.org/archives/2026/04/prof-goldstein-on-cox-v-sony-excerpt-from-his-treatise.htm&amp;source=gmail&amp;ust=1775917162636000&amp;usg=AOvVaw2vBV1oc2J_BIZIUR8r8Phm">right on this blog</a>, called the opinion “ill-considered.” Shira Perlmutter, the Director of the Copyright Office, nicely <a href="https://news.bloomberglaw.com/ip-law/copyright-director-chides-supreme-courts-shocking-cox-opinion" data-saferedirecturl="https://www.google.com/url?q=https://news.bloomberglaw.com/ip-law/copyright-director-chides-supreme-courts-shocking-cox-opinion&amp;source=gmail&amp;ust=1775917162636000&amp;usg=AOvVaw0ag6AkPCJ9B9QVa0wxL7e4">summarized</a> the overall sentiment, suggesting that the court “put little thought” into the implications of its opinion and noting that “we’re all still reeling from this a bit.”</p>
<p style="font-weight: 400;">I am not here to defend the Cox majority. Not even remotely. The decision seemingly overrules, perhaps unknowingly, dozens of circuit precedents and veers away from settled common-law notions of liability. It feels both unjust and inefficient to let a party that knowingly assisted in infringement walk away scot-free.</p>
<p style="font-weight: 400;">But I am here to offer a prediction: the sky will not fall. While Cox looks like a tectonic shift, I suspect its actual impact will be significantly more modest. If history is any guide, the copyright system is remarkably adept at absorbing, mitigating, and—dare I say—circumventing the Supreme Court’s attempts at central planning.</p>
<p style="font-weight: 400;"><strong>The Myth of Supreme Court Supremacy</strong></p>
<p style="font-weight: 400;">In <a href="https://papers.ssrn.com/sol3/papers.cfm?abstract_id=6550221" data-saferedirecturl="https://www.google.com/url?q=https://papers.ssrn.com/sol3/papers.cfm?abstract_id%3D6550221&amp;source=gmail&amp;ust=1775917162636000&amp;usg=AOvVaw3LRs2MVguE0QZRYJzT2Ybu">a forthcoming article</a>, <em>Circumventing the Supreme Court: Copyright Law and the Limits of Judicial Centralization</em>, I argue that we consistently overestimate the Court’s ability to actually change copyright law.</p>
<p style="font-weight: 400;">We’ve seen this movie before. Every few years, the Court hands down a decision that seems poised to reshape the field: <em>Star Athletica</em> supposedly wrecked separability and opened the floodgates for industrial design protection; <em>Aereo</em> looked like the death of the volitional conduct doctrine; <em>Kirtsaeng</em> presumably gutted the ability of copyright owners to exercise post-sale control; and <em>Eldred</em> and <em>Golan</em> were read as giving Congress a blank check on copyright expansion, allowing it to extend its terms, maybe indefinitely. Each of these decisions generated a wave of commentary predicting dramatic consequences. I’ve participated in that tradition too.</p>
<p style="font-weight: 400;">But none of those things really happened. Instead, the copyright system showed incredible resiliency.</p>
<p style="font-weight: 400;">The reason is partly structural: the Supreme Court is an absentee landlord. Outside of fair use, it handles any given copyright question like a cicada emergence: showing up, then disappearing for another couple of decades. Secondary liability is a perfect example: <em>Sony</em> (1984), <em>Grokster</em> (2005), <em>Cox</em> (2026). That’s a 21-year cycle.</p>
<p style="font-weight: 400;">In the long stretches between those decisions, lower courts and other repeat players run the show. When the landlord is away, the tenants can rearrange the furniture.</p>
<p style="font-weight: 400;">So, how will the system respond to the hole that Cox just punched in copyright law’s liability scheme? Yogi Berra taught us that it’s tough to make predictions, especially about the future. Still, I can offer a few incomplete and non-mutually exclusive possibilities.</p>
<p style="font-weight: 400;"><strong>1. Embracing the Minority: The &#8220;Aereo&#8221; Maneuver</strong></p>
<p style="font-weight: 400;">The boldest way to circumvent a majority opinion is probably to treat the minority view as the true law of the land. It sounds like heresy, and in many respects it is. But we have a recent blueprint: the volitional-conduct doctrine after Aereo.</p>
<p style="font-weight: 400;">In Aereo, the Justices split over the volition requirement. Justice Scalia, in dissent, embraced it and the body of circuit law that had developed around it over the years. Justice Breyer’s majority, by contrast, didn’t even mention it. Instead, it reasoned that because the system looked like a cable company, it should be treated like one, brushing aside the (very real) technological nuances.</p>
<p style="font-weight: 400;">Scalia warned that this would leave automated systems in legal limbo for decades. In reality, it took months. Lower courts essentially shrugged and went back to business as usual, applying volitional conduct as if <em>Aereo</em> had never happened.</p>
<p style="font-weight: 400;">When plaintiffs argued the doctrine was dead, the Second, Fifth, and Ninth Circuits doubled down with reasoning that was delightfully brazen: they heavily leaned on Scalia’s dissent as evidence that the doctrine was well-established, and even now endorsed by the Supreme Court. And as for the majority, it did not “<a href="https://law.justia.com/cases/federal/appellate-courts/ca9/15-55500/15-55500-2017-01-23.html" data-saferedirecturl="https://www.google.com/url?q=https://law.justia.com/cases/federal/appellate-courts/ca9/15-55500/15-55500-2017-01-23.html&amp;source=gmail&amp;ust=1775917162637000&amp;usg=AOvVaw0xt7mx33mhTX2kCBmCDna9">directly dispute or comment on Justice Scalia&#8217;s explanation of the doctrine</a>” or “<a href="https://law.justia.com/cases/federal/appellate-courts/ca5/16-10510/16-10510-2017-03-27.html" data-saferedirecturl="https://www.google.com/url?q=https://law.justia.com/cases/federal/appellate-courts/ca5/16-10510/16-10510-2017-03-27.html&amp;source=gmail&amp;ust=1775917162637000&amp;usg=AOvVaw0S3PtP-ti34AbUO84NVXFq">explicitly reject Justice Scalia&#8217;s formulation of the volitional-conduct requirement</a>.”</p>
<p style="font-weight: 400;"><em>Cox</em> might meet a similar fate. Justice Sotomayor’s concurrence seems aligned with pre-2026 circuit precedent and thus provides a ready-made framework to preserve the old regime.</p>
<p style="font-weight: 400;">Will that be a faithful reading of the majority opinion? Not really. But fidelity hasn’t always been the driving force in applying Supreme Court copyright opinions, like <em>Aereo</em>. So we shouldn’t be too surprised if judges lean on Sotomayor’s opinion, noting, with a straight face, that Thomas did not &#8220;directly dispute” or “explicitly reject&#8221; her analysis.</p>
<p style="font-weight: 400;"><strong>2. Narrowing to the Facts: The Grokster / Kirtsaeng Treatment</strong></p>
<p style="font-weight: 400;">If you can’t ignore a decision, you can shrink it until it only fits specific, idiosyncratic facts.</p>
<p style="font-weight: 400;">We saw this with <em>Grokster</em>. Lower courts confined inducement to situations involving exceptionally egregious conduct. The inducement doctrine became real, but also rare. We saw it with <em>Kirtsaeng</em>, too, where the Court embraced a broad reading of the first sale doctrine, but lower courts were reluctant to apply its logic in other contexts, including in the digital space. The first-sale doctrine remained broad, but inapplicable to most of today’s content.</p>
<p style="font-weight: 400;"><em>Cox</em> could follow the same path. Courts can emphasize its facts: a passive service provider with no specific knowledge that took some steps to discourage infringement. Multiple statements in the <em>Cox</em> majority, such as “this Court has repeatedly made clear that mere knowledge that a service will be used to infringe is insufficient to establish the required intent to infringe,” can assist lower courts in distinguishing it from defendants whose knowledge is broader.</p>
<p style="font-weight: 400;">There is a wrinkle here. On their face, <em>Grokster</em> and <em>Kirtsaeng</em> left significant leeway to lower courts. The <em>Cox</em> majority, sadly, did not leave as much space. Textually, it is needlessly broad (a rare move for the Roberts court, both outside and within copyright law). That makes narrowing it harder, at least on paper. But harder is not the same as impossible. We didn’t have to wait long to see that dynamic play out. <a href="https://blog.ericgoldman.org/archives/2026/04/will-lower-courts-find-ways-around-cox-v-sony-you-betcha.htm" data-saferedirecturl="https://www.google.com/url?q=https://blog.ericgoldman.org/archives/2026/04/will-lower-courts-find-ways-around-cox-v-sony-you-betcha.htm&amp;source=gmail&amp;ust=1775917162637000&amp;usg=AOvVaw0DwTxMwZz8kUCqvMyMt_KP">As Eric noted</a>, just six days after the Supreme Court opinion, a district court in California distinguished it because Cox, presumably unlike the defendant there (Twitter), discouraged copyright infringement.</p>
<p style="font-weight: 400;"><strong>3. Expanding Neighboring Doctrines: The <em>Star Athletica</em> Pivot</strong></p>
<p style="font-weight: 400;">The most likely response, in my view, is not to resist <em>Cox</em> directly, but to work around it.</p>
<p style="font-weight: 400;">When the Supreme Court closes a door, lower courts often just open a window in the next room. This is the hydraulic nature of copyright law: if you squeeze one doctrine, the pressure simply moves elsewhere.</p>
<p style="font-weight: 400;">Consider, for example, Justice Thomas’s previous copyright masterpiece:  <em>Star Athletica</em>. It might seem to have thrown the door wide open to the copyrightability of industrial designs, but many lower courts achieved comparable filtering, most often through broader use of other doctrines, such as the idea-expression distinction, the merger doctrine, or scènes à faire. Others granted plaintiffs a noticeably thin copyright. Overall, those moves mitigate (although not eliminate) the potential impact of <em>Star Athletica</em>.</p>
<p style="font-weight: 400;">There are many doctrines that can attempt to fill the gap that <em>Cox</em> left in effective copyright enforcement. I’ll mention a few immediate suspects:</p>
<p style="font-weight: 400;">A. <strong>Direct liability</strong></p>
<p style="font-weight: 400;">If contributory liability becomes harder to prove, plaintiffs might lean more heavily on direct liability. That means revisiting doctrines that have traditionally limited it, especially volitional conduct.</p>
<p style="font-weight: 400;">The volitional conduct doctrine has always been somewhat fragile: thin textual grounding, no clear Supreme Court endorsement, and uneven (and somewhat unclear) lower court application. It would not take much for courts to stretch it. Eric <a href="https://blog.ericgoldman.org/archives/2026/04/will-lower-courts-find-ways-around-cox-v-sony-you-betcha.htm" data-saferedirecturl="https://www.google.com/url?q=https://blog.ericgoldman.org/archives/2026/04/will-lower-courts-find-ways-around-cox-v-sony-you-betcha.htm&amp;source=gmail&amp;ust=1775917162637000&amp;usg=AOvVaw0DwTxMwZz8kUCqvMyMt_KP">alluded</a> to the same issue in discussing a recent Twitter decision, where a district court held (quite strangely, in my opinion) that the company acted with volition when it did not respond to DMCA takedown notices.</p>
<p style="font-weight: 400;">B. <strong>Vicarious Liability</strong></p>
<p style="font-weight: 400;">Vicarious liability could also do more work. It requires the right and ability to control the infringing activity and a direct financial benefit from it. Historically, courts have applied this doctrine cautiously in the online context. But if contributory liability becomes harder to establish, courts may be more willing to find supervisory power in a platform’s architecture and a financial benefit in its business model.</p>
<p style="font-weight: 400;">C. <strong>Inducement</strong></p>
<p style="font-weight: 400;">Finally, courts can stay within the contributory framework but expand what inducement means. More than the <em>Grokster</em> Court itself, it was lower courts that chose to define the doctrine narrowly. In the immediate aftermath of <em>Grokster</em>, many commentators worried that inducement would be applied broadly and threaten the development of the internet. In practice, however, lower courts have been reluctant to find inducement without evidence that the defendant actively marketed its services to infringers. Other factors the Court pointed to in <em>Grokster</em>, such as a failure to filter or a business model tied to infringement, have not been enough.</p>
<p style="font-weight: 400;">But after <em>Cox</em>, if specific knowledge is indeed not a route to find contributory liability, courts may be more willing to treat a wider range of conduct as evidence of intent to induce infringement.</p>
<p style="font-weight: 400;"><strong>4.</strong> <strong>The Long Shot: A Legislative Reform</strong></p>
<p style="font-weight: 400;">There is also, at least in theory, a legislative path.</p>
<p style="font-weight: 400;">Congress has been largely inactive in copyright for decades. But a doctrinal shock can create political momentum. If <em>Cox</em> is perceived as significantly weakening copyright enforcement, rights holders may push for statutory reform.</p>
<p style="font-weight: 400;">Whether Congress will act is uncertain. Structural constraints that have limited copyright legislation in recent decades remain in place. But <em>Cox </em>increases the pressure. Shira Perlmutter has already hinted in that direction.</p>
<p style="font-weight: 400;"><strong>Conclusion: Copyright resiliency</strong></p>
<p style="font-weight: 400;">Nobody, of course, knows what will happen next. But I would be very surprised if courts allow intermediaries to knowingly facilitate infringement without meaningful legal consequences.</p>
<p style="font-weight: 400;">If <em>Cox</em> created that gap, the repeat players within the copyright ecosystem, especially lower courts that routinely deal with copyright law, will find ways to bridge it. That is what the copyright system has done repeatedly.</p>
<p style="font-weight: 400;"><em>Cox</em> may be the rare decision that genuinely reshapes the scope of copyright protection, but if so, it would be the first time in decades. Instead, I’d comfortably bet that the lower courts will be rearranging the furniture.</p>
<p>The post <a href="https://blog.ericgoldman.org/archives/2026/04/the-cox-shock-a-tectonic-shift-or-just-a-tremor-guest-blog-post.htm">The Cox Shock: A Tectonic Shift or Just a Tremor? (Guest Blog Post)</a> appeared first on <a href="https://blog.ericgoldman.org">Technology &amp; Marketing Law Blog</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://blog.ericgoldman.org/archives/2026/04/the-cox-shock-a-tectonic-shift-or-just-a-tremor-guest-blog-post.htm/feed</wfw:commentRss>
			<slash:comments>2</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">28776</post-id>	</item>
		<item>
		<title>With Opinions Like This, Congress Doesn&#8217;t Need to Repeal Section 230&#8211;Massachusetts v. Meta</title>
		<link>https://blog.ericgoldman.org/archives/2026/04/with-opinions-like-this-congress-doesnt-need-to-repeal-section-230-massachusetts-v-meta.htm</link>
					<comments>https://blog.ericgoldman.org/archives/2026/04/with-opinions-like-this-congress-doesnt-need-to-repeal-section-230-massachusetts-v-meta.htm#comments</comments>
		
		<dc:creator><![CDATA[Eric Goldman]]></dc:creator>
		<pubDate>Sat, 11 Apr 2026 17:30:33 +0000</pubDate>
				<category><![CDATA[Content Regulation]]></category>
		<category><![CDATA[Derivative Liability]]></category>
		<category><![CDATA[Internet History]]></category>
		<category><![CDATA[Marketing]]></category>
		<guid isPermaLink="false">https://blog.ericgoldman.org/?p=28778</guid>

					<description><![CDATA[<p>This is one of the dozens of state AG lawsuits against social media services that are being litigated independently of/in parallel with the federal social media addiction MDL (where the state AGs are also suing social media companies). Because these...</p>
<p>The post <a href="https://blog.ericgoldman.org/archives/2026/04/with-opinions-like-this-congress-doesnt-need-to-repeal-section-230-massachusetts-v-meta.htm">With Opinions Like This, Congress Doesn&#8217;t Need to Repeal Section 230&#8211;Massachusetts v. Meta</a> appeared first on <a href="https://blog.ericgoldman.org">Technology &amp; Marketing Law Blog</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><a href="https://blog.ericgoldman.org/wp-content/uploads/2026/02/IMG_2022.jpg"><img loading="lazy" decoding="async" class="alignright size-medium wp-image-28570" src="https://blog.ericgoldman.org/wp-content/uploads/2026/02/IMG_2022-300x300.jpg" alt="" width="300" height="300" srcset="https://blog.ericgoldman.org/wp-content/uploads/2026/02/IMG_2022-300x300.jpg 300w, https://blog.ericgoldman.org/wp-content/uploads/2026/02/IMG_2022-1024x1020.jpg 1024w, https://blog.ericgoldman.org/wp-content/uploads/2026/02/IMG_2022-150x150.jpg 150w, https://blog.ericgoldman.org/wp-content/uploads/2026/02/IMG_2022-768x765.jpg 768w, https://blog.ericgoldman.org/wp-content/uploads/2026/02/IMG_2022-1536x1529.jpg 1536w, https://blog.ericgoldman.org/wp-content/uploads/2026/02/IMG_2022-2048x2039.jpg 2048w" sizes="auto, (max-width: 300px) 100vw, 300px" /></a>This is one of the dozens of state AG lawsuits against social media services that are being litigated independently of/in parallel with the federal social media addiction MDL (where the state AGs are also suing social media companies). Because these MDL-adjacent lawsuits are in state court, they are harder to track and flying under the radar. But this opinion won&#8217;t be overlooked. In it, the Massachusetts Supreme Court severely limits, or perhaps eliminates, Section 230&#8217;s applicability in Massachusetts.</p>
<p style="text-align: center;">* * *</p>
<p>The court summarizes the state&#8217;s claims:</p>
<blockquote><p>The Commonwealth alleges that Meta Platforms, Inc., and Instagram, LLC (collectively, Meta), engaged in unfair business practices by designing the Instagram platform to induce compulsive use by children, engaged in deceptive business practices by deliberately misleading the public about the safety of the platform, and created a public nuisance by engaging in these unfair and deceptive practices.</p></blockquote>
<p>Meta moved to dismiss on Section 230 and other grounds. The <a href="https://blog.ericgoldman.org/archives/2025/02/recapping-three-social-media-addiction-opinions-from-fall-catch-up-post.htm">lower court denied the motion</a>. Meta sought an interlocutory appeal, which the MA Supreme Court permitted, but only to review the Section 230 issue.</p>
<p>In this ruling, the MA Supreme Court unanimously agreed with the lower court that Section 230 didn&#8217;t immunize Meta when &#8220;the claims allege harm stemming from Meta&#8217;s own conduct either by designing a social media platform that capitalizes on the developmental vulnerabilities of children or by affirmatively misleading consumers about the safety of the Instagram platform.&#8221;</p>
<p><strong>Section 230</strong></p>
<p><em>Treated as Publisher</em></p>
<p>The court starts with its own &#8220;plain language&#8221; review of what it means to be treated as a publisher. When courts decide to review a 1996 statute from scratch in 2026, after over a thousand Section 230 cases have been decided, that&#8217;s usually an indicator that they are engaging in results-oriented decision-making, they don&#8217;t like the precedent, and they need another way to reach a different result.</p>
<p>Worse, the court extensively analyzes the word &#8220;publisher&#8221; but doesn&#8217;t say a word about the companion &#8220;speaker&#8221; term that appears two words later in the statute. This is another indicator of results-oriented decision-making. No matter what the court says &#8220;publisher&#8221; means, if the court disregards one of the other 26 words that has direct relevance to its meaning, the court is failing its #1 job of reading the damn statute. This omission is extremely embarrassing for the court, and it thoroughly undermines the credibility of the court&#8217;s recitation of precedent.</p>
<p>(I would say that the botched statutory reading would be the kind of thing that should be fixed on appeal, but the US Supreme Court&#8217;s specialty is selectively reading statutes and precedent to support results-oriented decision-making, so I guess other courts are emboldened to do that too&#8230;?)</p>
<p>The court tries to sum up its &#8220;plain language&#8221; review. Citing the <a href="https://blog.ericgoldman.org/archives/2022/11/fourth-circuit-takes-a-wrecking-ball-to-zeran-and-section-230-henderson-v-public-data.htm">awful Henderson 4th Circuit</a> (which <a href="https://blog.ericgoldman.org/archives/2025/02/section-230-still-works-in-the-fourth-circuit-for-now-m-p-v-meta.htm">the Fourth Circuit itself has implicitly repudiated</a>), the court says:</p>
<blockquote><p>These courts have rejected the argument that § 230(c)(1) provides immunity from liability &#8220;anytime there is a &#8216;but-for&#8217; causal relationship between the act of publication and liability,&#8221; as it &#8220;bears little relation to publisher liability at common law.&#8221; Engaging in traditional publishing activity &#8220;alone is not enough.&#8221;&#8230;</p></blockquote>
<p>(Note: along the way, the court includes quotes of the mockable &#8220;get-out-of-jail-free&#8221; and &#8220;lawless no-mans-land&#8221; characterizations of 230, <a href="https://blog.ericgoldman.org/archives/2023/05/two-common-but-disingenuous-phrases-about-section-230.htm">despite my prior debunking</a> of both phrases. Another way the court undermined its own credibility).</p>
<p>Because &#8220;the plain meaning of the statute lends itself to competing constructions,&#8221; the court then turns to the legislative history for more insight into the meaning of the word &#8220;publisher.&#8221; This leads to the one-millionth retelling of the Cubby/Stratton Oakmont storyline, with no new payoffs.</p>
<p>Instead, citing Henderson again, the court restates the statutory language in garbled fashion: &#8220;Congress intended to immunize interactive computer service providers against claims that would hold them liable as intermediaries for injuries caused by information provided by third-party users of their platforms.&#8221;</p>
<p>Relying on that garbled restatement, the court says:</p>
<blockquote><p>we decline Meta&#8217;s invitation to read § 230(c)(1) immunity so broadly as to encompass all claims that implicate publishing activities regardless of whether the claims seek to hold the service provider liable for the content of the information published&#8230;.</p>
<p>a claim treats a provider as a publisher of information where it meets both the dissemination and content elements.</p></blockquote>
<p>I&#8217;d need to see how Meta argued this, but it feels like the court is rejecting a strawman. Meta publishes third-party content&#8211;everyone agrees on that. The service features challenged by the state AG relate to the manner in which Meta presents that third-party content to Meta&#8217;s audience. To me, a publisher&#8217;s choices of what third-party content to publish and how to publish that third-party content are integrated decisions. In other words, the content selection and presentation decisions are part of the same publication decision. As an analogy, consider a dead-trees newspaper&#8217;s decision to publish a story: it is equally part of the newspaper&#8217;s editorial prerogative and publication decisions to decide to publish the story at all and to decide if the story should appear on the A1 front page or some interior page; what size typeface to use for the story headline; whether the story runs all on the same page or continues on a later page; etc. As applied to Meta, the decision to vary the delivery timing of new third-party content items (as one example) is just as much of Meta&#8217;s publication decision-making process about publishing the third-party content as whether the item will be published at all.</p>
<p>In any case, by saying that 230 only applies to claims that derive from the substance of the third-party content item, the court can disregard a LOT of precedent that applied Section 230 to design defects. The court says the only oppositional precedent is some language in the Social Media Addiction federal decision, which the court denigrates by saying the judge in that case &#8220;did not appear to consider the common-law origins of publisher liability or the statute&#8217;s legislative history. We are not persuaded by its reasoning.&#8221; [Yes, it&#8217;s jarring to see Meta cite the CA social media addiction case as support for its position given that how poorly the California cases have been going for Meta.]</p>
<p><em>Liability Based on Third-Party Content</em></p>
<p><em>Claim for unfair business practices</em>. Having said that Section 230 distinguishes the decisions of what content to publish (230-protected) and how to present it (not protected by 230), the court is positioned to uphold all of the claims.</p>
<p>The court says: &#8220;The challenged design features (e.g., infinite scroll, autoplay, IVR, and ephemeral content) concern how, whether, and for how long information is published, but the published information itself is not the source of the harm alleged.&#8221;</p>
<p>Meta responded that &#8220;in the absence of third-party content, the design features could not facilitate addiction in young users.&#8221; (My framing: if social media delivers third-party content, what exactly are users &#8220;addicted&#8221; to?). The court replies:</p>
<blockquote><p>But the fact that the features require some content to function is not controlling; instead&#8230;to satisfy the content element, we look to whether the claim seeks to hold Meta liable for harm stemming from third-party information that it published. Here, the unfair business practices claim does not; the Commonwealth alleges that the features themselves prolong users&#8217; time on the platform, not that any information contained in third-party posts does so. In this sense, the claim is indifferent as to the content published&#8230;</p>
<p>the fact that a claim concerns publishing activities, including the use of algorithms in connection with publishing activities, is not enough to bring the claim within the immunity provided by § 230(c)(1)</p></blockquote>
<p>In a footnote, the court adds: &#8220;with respect to the notifications feature, Meta appears to be the information content provider.&#8221; But&#8230;what content is included in the notifications, and where does it come from?</p>
<p>In a slight piece of good news, the court rejects the state&#8217;s <a href="https://blog.ericgoldman.org/archives/2021/05/the-ninth-circuits-confusing-ruling-over-snapchats-speed-filter-lemmon-v-snap.htm">Lemmon v. Snap</a> analogy because Lemmon&#8217;s &#8220;claims did not concern the provider&#8217;s publishing activity at all. [Eric&#8217;s note: the Lemmon plaintiffs expressly disclaimed all liability based on the content produced by the filter.] By contrast, here, the challenged features are publishing tools that control how Meta publishes content to users of its platform.&#8221; I wish more courts would similarly reject the plaintiffs&#8217; many miscitations to Lemmon.</p>
<p><em>Claim for deceptive business practices</em>. The claim &#8220;is based on Meta&#8217;s own speech &#8212; its allegedly false statements that Instagram is safe and not addictive, and that Meta prioritizes young users&#8217; well-being, despite internal reports and communications suggesting awareness of the harmful effects of Instagram.&#8221; There are obvious puffery/opinion defenses that could apply here (see, e.g., the YOLO remand in Bride v. Snap, Inc., 2026 WL 855148 (C.D. Cal. March 16, 2026) that I will eventually blog) but are not at issue in the 230 discussion.</p>
<p>Also, some courts have applied Section 230 to false advertising claims when those claims are fundamentally based on how the service handles its content moderation decisions, such as claims about &#8220;safety.&#8221; The court doesn&#8217;t acknowledge that precedent and instead treats Section 230 as categorically inapplicable to false advertising claims.</p>
<p><em>Claim for defective age-gating</em>. &#8220;the claim focuses on Meta&#8217;s own affirmative misstatements about the inaccessibility of its platform to underage users.&#8221; Another possible puffery issue.</p>
<p><em>Nuisance</em>. I&#8217;ve previously complained before about courts&#8217; complete undertheorizing of how and why public nuisance claims can apply to social media, and this court doesn&#8217;t do any better. In a footnote, here is the court&#8217;s entire discussion about Section 230&#8217;s application to the public nuisance claim: &#8220;Because we conclude that § 230(c)(1) does not bar counts I to III, we also conclude that it does not bar the Commonwealth&#8217;s public nuisance claim, which is predicated on the same allegedly unfair and deceptive practices in counts I to III.&#8221;</p>
<p><strong>What Happens Next?</strong></p>
<p>Meta could appeal this ruling to the US Supreme Court. That would be a risky move because the US Supreme Court could really go sideways on a decision like this. Also, I&#8217;m skeptical the US Supreme Court would grant cert.</p>
<p>Meta could choose to prioritize winning this case on remand on non-230 grounds. For example, the MA Supreme Court validated that Meta&#8217;s service features at issue are part of its content publication process. Perhaps that will revitalize Meta&#8217;s First Amendment defense?</p>
<p>Whether Meta chooses to appeal or double-down on remand, it&#8217;s likely that the CA federal and state court social media addiction cases will have important new developments before any material developments happen in this case. Those developments could swamp the effects of this lawsuit. For example, if Meta loses more bellwether trials in California, the outcome of this case may be comparatively inconsequential.</p>
<p><strong>Quo Vadis Section 230?</strong></p>
<p>This is not a good opinion for Section 230 on several dimensions.</p>
<p>First, as a state supreme court decision, it&#8217;s the final word for the Massachusetts state court system (unless the US Supreme Court intervenes). It provides a major beachhead for other courts to follow, both within Massachusetts and beyond.</p>
<p>Second, this court didn&#8217;t rely on the Lemmon &#8220;design defect&#8221; workaround. Instead, it said that the claim doesn&#8217;t relate to third-party content unless it&#8217;s based on the substance of the third-party content. This provides plaintiffs with another avenue to work around Section 230 in addition to the Lemmon/design defect workaround that other courts are accepting (even if they shouldn&#8217;t).</p>
<p>Third, as I explained, I don&#8217;t see any distinction between third-party content and the editorial choices about the manner of presenting that third-party content. By embracing that false dichotomy, the court invites plaintiffs to reframe their complaints to focus on content presentation instead of substance. Here&#8217;s how a plaintiff&#8217;s argument could look: &#8220;I&#8217;m not suing about the third-party content, I&#8217;m suing about the design choices that elevated that third-party content over others.&#8221; These are literally the same thing in my mind. If this argument works, Section 230 is dead because plaintiffs will always embrace that workaround.</p>
<p><a href="https://blog.ericgoldman.org/wp-content/uploads/2025/08/cheese-151032_1280.png"><img loading="lazy" decoding="async" class="alignright size-medium wp-image-27960" src="https://blog.ericgoldman.org/wp-content/uploads/2025/08/cheese-151032_1280-300x171.png" alt="" width="300" height="171" srcset="https://blog.ericgoldman.org/wp-content/uploads/2025/08/cheese-151032_1280-300x171.png 300w, https://blog.ericgoldman.org/wp-content/uploads/2025/08/cheese-151032_1280-1024x582.png 1024w, https://blog.ericgoldman.org/wp-content/uploads/2025/08/cheese-151032_1280-768x437.png 768w, https://blog.ericgoldman.org/wp-content/uploads/2025/08/cheese-151032_1280.png 1280w" sizes="auto, (max-width: 300px) 100vw, 300px" /></a>Even if this opinion doesn&#8217;t outright eliminate Section 230 in Massachusetts, it&#8217;s a sign of how 230 workarounds keep proliferating, contributing to the swiss cheese-ification of Section 230. When the bubbles in the swiss cheese become too large, the cheese wedge lacks structural integrity and falls apart. That is where 230 is heading, if it&#8217;s not already there.</p>
<p><em>Case Citation</em>: <a href="https://www.mass.gov/doc/commonwealth-v-meta-platforms-inc-sjc-m13747/download">Commonwealth v. Meta Platforms, Inc.</a>, 497 Mass. 384 (Mass. Supreme Jud. Ct. April 10, 2026)</p>
<p>The post <a href="https://blog.ericgoldman.org/archives/2026/04/with-opinions-like-this-congress-doesnt-need-to-repeal-section-230-massachusetts-v-meta.htm">With Opinions Like This, Congress Doesn&#8217;t Need to Repeal Section 230&#8211;Massachusetts v. Meta</a> appeared first on <a href="https://blog.ericgoldman.org">Technology &amp; Marketing Law Blog</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://blog.ericgoldman.org/archives/2026/04/with-opinions-like-this-congress-doesnt-need-to-repeal-section-230-massachusetts-v-meta.htm/feed</wfw:commentRss>
			<slash:comments>3</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">28778</post-id>	</item>
		<item>
		<title>Will Lower Courts Find Ways Around Cox v. Sony? You Betcha</title>
		<link>https://blog.ericgoldman.org/archives/2026/04/will-lower-courts-find-ways-around-cox-v-sony-you-betcha.htm</link>
					<comments>https://blog.ericgoldman.org/archives/2026/04/will-lower-courts-find-ways-around-cox-v-sony-you-betcha.htm#comments</comments>
		
		<dc:creator><![CDATA[Eric Goldman]]></dc:creator>
		<pubDate>Tue, 07 Apr 2026 16:40:25 +0000</pubDate>
				<category><![CDATA[Copyright]]></category>
		<category><![CDATA[Derivative Liability]]></category>
		<guid isPermaLink="false">https://blog.ericgoldman.org/?p=28771</guid>

					<description><![CDATA[<p>This post covers two more Michael Grecco cases (see links below for additional blog coverage on his litigation campaign). The two decisions provide an interesting compare/contrast. The Twitter ruling also gives an early sense of how lower courts might navigate...</p>
<p>The post <a href="https://blog.ericgoldman.org/archives/2026/04/will-lower-courts-find-ways-around-cox-v-sony-you-betcha.htm">Will Lower Courts Find Ways Around Cox v. Sony? You Betcha</a> appeared first on <a href="https://blog.ericgoldman.org">Technology &amp; Marketing Law Blog</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>This post covers two more Michael Grecco cases (see links below for additional blog coverage on his litigation campaign). The two decisions provide an interesting compare/contrast.</p>
<p>The Twitter ruling also gives an early sense of how lower courts might navigate the <a href="https://blog.ericgoldman.org/archives/2026/03/quick-comments-on-scotus-cox-v-sony-ruling.htm">Cox v. Sony</a> Supreme Court ruling. Though it&#8217;s only a single datapoint and is surely skewed because the judge had written the opinion before the Supreme Court&#8217;s decision, the court&#8217;s &#8220;solution&#8221; highlights several ways courts can work around the Cox ruling that may undermine its seemingly defense-favorable result.</p>
<p><strong><a href="https://storage.courtlistener.com/recap/gov.uscourts.cacd.929069/gov.uscourts.cacd.929069.45.0.pdf">Michael Grecco Productions, Inc. v. TikTok, Inc.</a>, 2025 WL 4672998 (C.D. Cal. March 12, 2025). </strong>The <a href="https://www.courtlistener.com/docket/68839776/michael-grecco-productions-inc-v-tiktok-inc/">CourtListener page</a>.</p>
<p>[Note 1: This year-old opinion just showed up in my alerts.]</p>
<p>[Note 2: Plaintiff&#8217;s lawyer is CopyCat Legal and <a href="https://www.copycatlegal.com/lauren-hausman-esq/">Lauren M. Hausman</a>, who I mentioned in <a href="https://blog.ericgoldman.org/archives/2025/02/tiktok-defeats-copyright-lawsuit-over-users-uploads-waterman-v-tiktok-catch-up-post.htm">this other copyright lawsuit</a> against TikTok. I don&#8217;t love the firm&#8217;s filings, but I do like the firm&#8217;s cat-themed imagery.]</p>
<p>This case relates to 22 photos that users allegedly uploaded to TikTok. The plaintiff claims that it sent DMCA takedown notices, but allegedly the works didn&#8217;t come down.</p>
<p><em>Direct Infringement</em></p>
<blockquote><p>Defendant contends Plaintiff has not and cannot allege any volitional conduct by TTI to support its direct copyright infringement claim. Plaintiff admits “a direct theory of liability has not been properly set forth in the FAC”</p></blockquote>
<p>+5 points for the plaintiff firm&#8217;s candor, -10 points for bad drafting.</p>
<p><em>Vicarious Infringement</em></p>
<blockquote><p>Plaintiff alleges TTI “has the right and ability to control the infringing acts of its users yet declined or failed to stop its users from engaging in its infringing activity.” As support, Plaintiff alleges it sent multiple DMCA takedown notices to TTI. Missing from these allegations are any details related to the contents of these notices, including when they were sent and how they identified the media that infringed the Work. Plaintiff&#8217;s assertion it sent multiple DMCA takedown notices to Defendant, alone, is insufficient to plead Defendant had sufficient knowledge to exercise the requisite control over the allegedly infringing users.</p></blockquote>
<p>A lot to dislike here. First, the plaintiff uses the less-preferred variant of the vicarious infringement test from the Grokster opinion, which has cluttered up the considerations. Second, vicarious and contributory infringement doctrines have effectively merged if both are triggered by the same takedown notices. This is more of a 9th Circuit problem than a problem with this opinion, but it&#8217;s still a problem. At minimum, scienter has unambiguously crept into the traditionally strict-liability vicarious infringement test.</p>
<p><em>Contributory Infringement</em></p>
<p>Same pleading problems with the factual imprecisions about the DMCA takedown notices.</p>
<p><em>Developments Since This Ruling</em></p>
<p>The plaintiff filed a second amended complaint, and the parties had an unsuccessful mediation. Both parties have summary judgment motions pending. The judge said in September that he would rule on those motions without a hearing, but no word since.</p>
<p><em>An Observation</em></p>
<p>In a footnote, the court adds &#8220;The FAC contains typographical errors, whereby Plaintiff repeats certain paragraph numbers.&#8221; Oops. That sloppiness is in addition to the pleading defects of not properly alleging direct infringement and not providing adequate details about the DMCA takedown notices. In light of the Twitter ruling, this data might help form a hypothesis about the relative performances of the different law firms.</p>
<p><strong>Michael Grecco Productions, Inc. v. Twitter, Inc., 2026 WL 917606 (C.D. Cal. March 31, 2026)</strong></p>
<p>This case involves the same plaintiff and same judicial district (C.D. Cal.) as the TikTok lawsuit, but the differences include: different plaintiff&#8217;s counsel (One LLP and Blakey Law Group), different defense counsel (Willenken and Quinn Emanuel), different procedural stage (judgment on the pleadings instead of motion to dismiss), different judge, different time (1 year later), and different outcome (plaintiff&#8217;s claims survive the challenge).</p>
<p>According to the complaint, &#8220;Grecco sent DMCA takedown emails to Twitter for the copyright infringement of the alleged 111 infringed upon copyrighted materials&#8230;.Twitter has not taken action as to the DMCA takedown requests pertaining to the 111 copyrighted materials.&#8221;</p>
<p><em>Direct Infringement</em></p>
<blockquote><p>Twitter contends that it did not commit volitional acts as the infringing conduct was posted by third party users. The 2AC argues that Twitter actively and willfully engaged in the infringement by refusing to honor valid DMCA takedown requests pertaining to the infringing content submitted by Grecco.</p></blockquote>
<p>Per the plaintiff, not taking any action qualifies as &#8220;actively and willfully engaging&#8221; in infringement? Really? Yet, remarkably, the plaintiff makes the sale on this argument:</p>
<blockquote><p>the 2AC provides that Twitter was: (1) on notice of the alleged infringing material; and (2) Twitter failed to address the DMCA takedown requests and remove the material from its platform. The alleged failure to remove the alleged infringing material is within Twitter&#8217;s exercise of control, not third-party users. By pleading that Twitter allowed the alleged infringing material to remain on its platform and failed to respond to the DMCA takedown requests, Grecco has properly pleaded that Twitter engaged in the active display of the infringing material.</p></blockquote>
<p>What does &#8220;active display&#8221; mean? The grammar reminds me of the <a href="https://en.wikipedia.org/wiki/The_Finale_(Seinfeld)">Seinfeld finale</a>.</p>
<p>Note how the court&#8217;s move gets around Cox v. Sony. This court says that Twitter&#8217;s failure to respond to a takedown notice constitutes DIRECT infringement because the takedown notice turns non-volitional conduct into volitional conduct. No contributory infringement required, which means Cox v. Sony doesn&#8217;t necessarily block this doctrinal move at all.</p>
<p>The court&#8217;s direct infringement doctrinal move shouldn&#8217;t work. I think this ruling diverges from the Ninth Circuit standards on online volition (and it clearly conflicts with the Second Circuit&#8217;s Cablevision&#8217;s ruling), but who knows because the Ninth Circuit has done a poor job articulating the standard. The judge distinguishes the <a href="https://blog.ericgoldman.org/archives/2019/04/second-circuit-judges-brawl-over-the-meaning-of-volition-in-copyright-cases-bwp-v-polyvore.htm">VHT v. Zillow</a> ruling because the defendant in that case honored the takedown notice, while here Twitter allegedly did not, and the court thinks that distinction matters to volitional conduct. I wonder if the Ninth Circuit will find this judge&#8217;s doctrinal contortions persuasive.</p>
<p>Note that Twitter could still theoretically defeat the direct infringement claim using the DMCA 512(c) safe harbor. However, if Twitter didn&#8217;t honor the takedown notices, then it should also be disqualified from 512(c).</p>
<p><em>Contributory Copyright Infringement</em></p>
<p>Although this court knew of the Cox ruling (more on that in a moment), the court applied the now-deprecated Gershwin scienter + material contribution test.</p>
<p>Unlike the TikTok case above, Grecco prepared the takedown notice details properly: &#8220;Grecco details the copyright material, the copyright registration information, and the DMCA takedown requests submission dates.&#8221; With adequate detail about the takedown notices before the court, &#8220;the Court finds that Grecco sufficiently alleged a simple measure, and thus material contribution under a claim for contributory copyright infringement. As the Court finds that Grecco has sufficiently pled actual knowledge and material contribution.&#8221;</p>
<p>For completeness, the court shuts down the inducement path: &#8220;the failure to remove does not speak to an objective to promote.&#8221;</p>
<p><a href="https://blog.ericgoldman.org/wp-content/uploads/2026/03/copyright-tailor-v2.jpg"><img loading="lazy" decoding="async" class="alignright size-medium wp-image-28734" src="https://blog.ericgoldman.org/wp-content/uploads/2026/03/copyright-tailor-v2-200x300.jpg" alt="" width="200" height="300" srcset="https://blog.ericgoldman.org/wp-content/uploads/2026/03/copyright-tailor-v2-200x300.jpg 200w, https://blog.ericgoldman.org/wp-content/uploads/2026/03/copyright-tailor-v2-683x1024.jpg 683w, https://blog.ericgoldman.org/wp-content/uploads/2026/03/copyright-tailor-v2-768x1152.jpg 768w, https://blog.ericgoldman.org/wp-content/uploads/2026/03/copyright-tailor-v2.jpg 1024w" sizes="auto, (max-width: 200px) 100vw, 200px" /></a>But what about Cox v. Sony? In a footnote, the court says:</p>
<blockquote><p>Grecco submitted numerous DMCA takedown requests, which included the copyright and infringing material information—placing Twitter on notice of the infringing activity. Twitter, however, took no action to remove the infringing materials. Grecco also alleges that Twitter&#8217;s acts of infringement were “willful.” As such, Cox is distinguishable from this matter.</p></blockquote>
<p>The court surely had written most or all of this opinion before Cox came out, and the court sought the path of least resistance to issue the already-drafted opinion without rewriting it. But c&#8217;mon. In Cox, the plaintiffs submitted many DMCA notices, and Cox took no action. Perhaps the court is trying to draw a line between hosting and Internet access without actually saying so? With respect to the &#8220;willful&#8221; allegations, if failure to remove in response to a takedown notice is a willful infringement, then Cox was willful too. But the court doesn&#8217;t explain how Twitter was &#8220;willful&#8221; other than reciting Grecco&#8217;s bare assertion. Not helpful.</p>
<p><em>Vicarious Infringement</em></p>
<blockquote><p>Grecco sufficiently pleads that Twitter had the right and ability to supervise the alleged infringing content through the DMCA takedown requests. Upon reviewing Grecco&#8217;s requests, Twitter could have removed the content from its platform</p>
<p>The 2AC asserts that Twitter has generated revenue through the increased traffic from the infringing content. And this is all that is needed at this stage. Grecco need not explain at this stage how the infringing content operates as a draw to consumers, but merely that this specific infringing content does.</p></blockquote>
<p>As with the TikTok ruling, the vicarious infringement test has largely collapsed into the contributory (and now direct) infringement tests. What a mess. The Ninth Circuit, and ultimately the Supreme Court, needs to clean up these tests.</p>
<p><em>Statute of Limitations</em></p>
<p>The court applies a 3-year limitation from date of posting (rather than from date of last download, which <a href="https://blog.ericgoldman.org/archives/2019/09/there-is-essentially-no-statute-of-limitations-for-online-copyright-infringement-apl-v-us.htm">other courts have applied</a>), which screens out 38 of the 111 works at issue.</p>
<p><em>Implications</em></p>
<p>I could see the Ninth Circuit reversing each and every part of the Twitter decision, i.e., saying there is no direct, contributory, or vicarious infringement, and no SOL problem. At minimum, this ruling shows how lower courts are struggling to consistently apply the infringement tests to online hosts.</p>
<p>The Twitter ruling also provides an early indicator that Cox may not be as much of a defense win as it appeared. Lower courts can, and likely will, make doctrinal countermoves to bail plaintiffs out.</p>
<p>The Twitter ruling might also illustrate how the DMCA safe harbors have converged with the underlying doctrinal tests. This opinion suggests that failing to follow the DMCA takedown procedures virtually ensures liability on the prima facie elements too, thus collapsing the prima facie elements and the DMCA safe harbor elements.</p>
<p>Judge Maame Ewusi-Mensah Frimpong wrote the Twitter opinion. I didn&#8217;t see anything in her background that explains why she bent over backwards for the plaintiff here.</p>
<p><strong>More Blog Posts About Michael Grecco</strong></p>
<ul>
<li><a title="What’s the Difference Between Copyright Takedown Notices and Spam?–Michael Grecco v. Fandom" href="https://blog.ericgoldman.org/archives/2025/08/whats-the-difference-between-copyright-takedown-notices-and-spam-michael-grecco-v-fandom.htm" rel="bookmark">What’s the Difference Between Copyright Takedown Notices and Spam?–Michael Grecco v. Fandom</a></li>
<li><a title="Blogger’s Photo Republication Isn’t Fair Use–Golden v. Grecco" href="https://blog.ericgoldman.org/archives/2021/03/bloggers-photo-republication-isnt-fair-use-golden-v-grecco.htm" rel="bookmark">Blogger’s Photo Republication Isn’t Fair Use–Golden v. Grecco</a></li>
<li><a title="Reminder: Cutting-and-Pasting Photos from the Internet Is Hazardous to Your Legal Health–Grecco v. Valuewalk" href="https://blog.ericgoldman.org/archives/2018/11/reminder-cutting-and-pasting-photos-from-the-internet-is-hazardous-to-your-legal-health-grecco-v-valuewalk.htm" rel="bookmark">Reminder: Cutting-and-Pasting Photos from the Internet Is Hazardous to Your Legal Health–Grecco v. Valuewalk</a></li>
</ul>
<p>The post <a href="https://blog.ericgoldman.org/archives/2026/04/will-lower-courts-find-ways-around-cox-v-sony-you-betcha.htm">Will Lower Courts Find Ways Around Cox v. Sony? You Betcha</a> appeared first on <a href="https://blog.ericgoldman.org">Technology &amp; Marketing Law Blog</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://blog.ericgoldman.org/archives/2026/04/will-lower-courts-find-ways-around-cox-v-sony-you-betcha.htm/feed</wfw:commentRss>
			<slash:comments>2</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">28771</post-id>	</item>
		<item>
		<title>Prof. Goldstein on Cox v. Sony (Excerpt from His Treatise)</title>
		<link>https://blog.ericgoldman.org/archives/2026/04/prof-goldstein-on-cox-v-sony-excerpt-from-his-treatise.htm</link>
					<comments>https://blog.ericgoldman.org/archives/2026/04/prof-goldstein-on-cox-v-sony-excerpt-from-his-treatise.htm#comments</comments>
		
		<dc:creator><![CDATA[Eric Goldman]]></dc:creator>
		<pubDate>Mon, 06 Apr 2026 14:24:05 +0000</pubDate>
				<category><![CDATA[Copyright]]></category>
		<category><![CDATA[Derivative Liability]]></category>
		<guid isPermaLink="false">https://blog.ericgoldman.org/?p=28763</guid>

					<description><![CDATA[<p>Prof. Paul Goldstein (Stanford Law) kindly has allowed me to share this update to his treatise (Goldstein on Copyright, Third Edition) regarding the Supreme Court&#8217;s Cox v. Sony decision. (My initial comments on the ruling are here). * * *...</p>
<p>The post <a href="https://blog.ericgoldman.org/archives/2026/04/prof-goldstein-on-cox-v-sony-excerpt-from-his-treatise.htm">Prof. Goldstein on Cox v. Sony (Excerpt from His Treatise)</a> appeared first on <a href="https://blog.ericgoldman.org">Technology &amp; Marketing Law Blog</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><a href="https://law.stanford.edu/paul-goldstein/">Prof. Paul Goldstein</a> (Stanford Law) kindly has allowed me to share this update to his treatise (<a href="https://law-store.wolterskluwer.com/s/product/goldstein-on-copyright3mo-subvitallaw-3r/01t0f00000NY7aUAAT">Goldstein on Copyright, Third Edition</a>) regarding the Supreme Court&#8217;s Cox v. Sony decision. (My initial comments on the ruling are <a href="https://blog.ericgoldman.org/archives/2026/03/quick-comments-on-scotus-cox-v-sony-ruling.htm">here</a>).</p>
<p style="text-align: center;">* * *</p>
<p>In <em><a href="https://www.supremecourt.gov/opinions/25pdf/24-171_bq7d.pdf">Cox Communications, Inc. v. Sony Music Entertainment</a>,</em> an ill-considered 2026 decision that will serve the interests neither of copyright owners nor of copyright users—nor, for that matter, society’s interest in a balanced copyright system—the United States Supreme Court took an axe to contributory liability, ruling that an internet service provider serving approximately six million subscribers was not contributorily liable for its subscribers’ copyright infringements merely because it had provided “a service to the general public with knowledge that it will be used by some to infringe copyrights.” According to the Court’s opinion, written by Justice Clarence Thomas, “[t]he provider of a service is contributorily liable for a user’s infringement if it intended its service to be used for infringement.” To establish such intent, “a copyright owner must show one of two things. First, it can show that a party affirmatively ‘induc[ed]’ the infringement. Or, second, it can show that the party sold a service tailored to infringement.&#8221;</p>
<div id="attachment_28734" style="width: 210px" class="wp-caption alignright"><a href="https://blog.ericgoldman.org/wp-content/uploads/2026/03/copyright-tailor-v2.jpg"><img loading="lazy" decoding="async" aria-describedby="caption-attachment-28734" class="wp-image-28734 size-medium" src="https://blog.ericgoldman.org/wp-content/uploads/2026/03/copyright-tailor-v2-200x300.jpg" alt="" width="200" height="300" srcset="https://blog.ericgoldman.org/wp-content/uploads/2026/03/copyright-tailor-v2-200x300.jpg 200w, https://blog.ericgoldman.org/wp-content/uploads/2026/03/copyright-tailor-v2-683x1024.jpg 683w, https://blog.ericgoldman.org/wp-content/uploads/2026/03/copyright-tailor-v2-768x1152.jpg 768w, https://blog.ericgoldman.org/wp-content/uploads/2026/03/copyright-tailor-v2.jpg 1024w" sizes="auto, (max-width: 200px) 100vw, 200px" /></a><p id="caption-attachment-28734" class="wp-caption-text">Image produced by ChatGPT March 2026</p></div>
<p>“Inducement” has an established place in copyright jurisprudence. But the concept, “tailored to infringement,” appears nowhere in the Copyright Act or in copyright case law. The late Justice Ruth Ginsburg’s concurring opinion in <em>Metro-Goldwyn-Mayer Studios Inc. v Grokster</em> <em>Ltd</em>., to which Justice Thomas ascribed the term, in fact nowhere included those words. Justice Ginsburg did employ the terms “substantial” or “commerciallv significant” noninfringing uses, referring to the concept that had become a central determinant for withholding contributory liability for providing goods or services since the Court first adopted it in <em>Sony Corp. of America v.</em> <em>Universal City Studios, Inc. </em>Justice Thomas’s treatment of the two terms as equivalent—“[a] service is tailored to infringement if it is ‘not capable of “substantial or commercially significant”’ non-infringing uses—overlooks not only that the first term is materially narrower than the second, but also that <em>Sony</em> borrowed it from the patent statute with the distinct object of ensuring that consumers not be required to pay monopoly tribute for otherwise unprotected goods or equipment. If selling salt tablets that can be used in a patented salt dispenser should not be actionable because the tablets have a substantial noninfringing use, so sales of video recording devices employed to copy copyrighted works should not be actionable if the devices possessed one or more substantial noninfringing uses, such as time-shifting recorded programs for later viewing.</p>
<p>By assimilating “substantial noninfringing use,” an objective, competition policy-based measure of liability, into a necessarily subjective intent-based measure,<em> Cox</em> seems likely to destabilize entrepreneurial planning for the introduction of new devices and services for exploiting copyrighted works. To be sure, service providers may see in the opinion a license to deliver services to subscribers&#8211;even though they know that many and even most of the uses may infringe&#8211;so long as they don’t promote or specifically design their services for infringement. In fact, if the Court believed that its narrowing of contributory liability to inducement by words or by device or service design, would enhance marketplace certainty, it might not have reflected carefully enough on the flimsy, indeed passive, evidence that it accepted in <em>Grokster </em>as evidence of inducement: that the defendants aimed “to satisfy a known source of demand for copyright infringement”; that defendants failed “to develop filtering tools” to “diminish the infringing activity using their software”; and “the commercial sense of their enterprise turns on high volume use.” <em>Cox</em> offers small solace to service providers if an act of omission such as failure to install filtering tools will subject them to liability.</p>
<p>The Court’s attempt in <em>Cox </em>to circumscribe contributory liability on the internet is understandable. The prospect of an aggregation of tens of thousands statutory damage awards—the award against Cox was $1 billion—can be daunting, indeed devastating, for even the most well-heeled service provider. The correct solution, however, would be for Congress to revise the Act’s statutory damages provision, and at least one bill has been introduced to that end. The prospect of secondary liability for generative AI platforms for the conduct of their users in prompting texts, sounds and images similar to copyrighted works may also have figured in the Court’s attempt at caution. But the question of secondary liability—indeed, of direct infringement liability—for these AI activities has not yet been directly addressed by the courts, or by the Congress, and for the Supreme Court to legislate on the question without a trial record or statutory text before it would be premature.</p>
<p>The terrain of secondary copyright liability generally has turned treacherous since the introduction in 1998 of the internet safe harbors, for the expectations of service providers and their subscribers have over the ensuing years been shaped less by secondary liability doctrines than by the mechanisms of the safe harbors. Lawsuits defining the boundaries of liability on the internet have been displaced in the vast number of potential conflicts by compliance with the safe harbors, including by automated means such as YouTube’s immensely successful Content ID system. If there has been litigation over service provider liability, it has been mainly to define the terms of the safe harbors and not to measure the reach of secondary liability doctrines. As proposed elsewhere in this treatise, the solution to this legal vacuum is for courts to populate it with the norms that business operations under the safe harbors have come to define as reasonable behavior among copyright owners and service providers alike. Sadly, the Court in <em>Cox </em>ignored this possibility. Indeed<em>,</em> as Justice Sonia Sotomayor wisely observed of the safe harbors in her concurrence in <em>Cox, </em>“[i]mportantly, Congress did not provide that ISPs could never be secondarily liable for copyright infringement. Instead, it struck a balance by creating incentives for ISPs to take reasonable steps to prevent copyright infringement on their networks, while also assuring ISPs that they do not need to take on the impossible task of responding to every instance of infringement on their networks….The majority’s new rule completely upends that balance and consigns the safe harbor provision to obsolescence.”</p>
<p>The post <a href="https://blog.ericgoldman.org/archives/2026/04/prof-goldstein-on-cox-v-sony-excerpt-from-his-treatise.htm">Prof. Goldstein on Cox v. Sony (Excerpt from His Treatise)</a> appeared first on <a href="https://blog.ericgoldman.org">Technology &amp; Marketing Law Blog</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://blog.ericgoldman.org/archives/2026/04/prof-goldstein-on-cox-v-sony-excerpt-from-his-treatise.htm/feed</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">28763</post-id>	</item>
	</channel>
</rss>
