Ninth Circuit Panel Goes Out of Its Way to Question Section 230–DOE vs. Meta
The Ninth Circuit panel has raised questions about Section 230 in a case involving Facebook's role in the Rohingya attacks in Myanmar. The lower court dismissed the case on statute of limitations grounds without addressing Section 230, yet the Ninth Circuit chose to engage with it. This decision has sparked concerns about judicial activism and the panel's motivations for discussing Section 230.
- ▪The plaintiffs sued Facebook for its alleged role in the genocidal attacks on the Rohingya minority in Myanmar.
- ▪The lower court dismissed the case based solely on statute of limitations without mentioning Section 230.
- ▪The Ninth Circuit panel requested supplemental briefings on Section 230 and conducted its own analysis despite the lower court's ruling.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Technology & Marketing Law Blog |
| Canonical URL | https://blog.ericgoldman.org/archives/2026/05/ninth-circuit-panel-goes-out-of-its-way-to-question-section-230-doe-v-meta.htm |
| Publication time | Mon, 25 May 2026 20:24:16 +0000 |
| Retrieval time | 2026-05-25T20:37:40.523Z |
| Last seen | 2026-05-25T20:37:40.523Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | VDZVDkDopk9I |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
[I’ve been sitting on this ruling for almost a month because blog posts like this are time-consuming and emotionally draining to write. It may not look it, but this post took about 6 hours to write.] This case involves a terrible tragedy: genocidal violent attacks on the Rohingya minority in Myanmar at the beginning of the 2010s. The plaintiffs sued Facebook for its role in the attacks, such as its alleged algorithmic turbocharging of rage content posted by its users. Despite the tragedy, the facts sound like a straightforward Section 230 situation. However, the lower court didn’t rely on Section 230 to dismiss the complaint. Indeed, Section 230 isn’t mentioned a single time in the district court dismissal, part of why I never blogged that opinion.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Technology & Marketing Law Blog.
Discussion
0 commentsMore from Technology & Marketing Law Blog
