Juries Are Doing What Congress Wouldn't: Holding Platforms Liable for Their Own Choices

NewsOnScale Staff

August 21, 2026

For thirty years, Section 230 of the Communications Decency Act has functioned less like a law and more like a force field. Passed in 1996 to encourage a fledgling internet to grow without fear of ruinous litigation, it shielded platforms from liability for content their users generated. What it was never explicitly designed to do — though platforms argued otherwise — was immunize the deliberate engineering choices companies make about how to surface, amplify, and addict users to that content.

Courts are now drawing that line, and the consequences could reshape the economics of the attention economy.

## What the Verdicts Actually Say

Recent jury verdicts against Meta and Google in platform design litigation represent something categorically different from prior attempts to hold tech companies accountable. These cases did not hinge on whether a platform failed to remove a specific piece of harmful content — that's the territory Section 230 has traditionally governed, and largely foreclosed. Instead, plaintiffs argued that the platforms' own architectural decisions — recommendation algorithms, autoplay features, notification systems engineered to maximize engagement — constitute product design defects independent of any user-generated material.

That distinction matters enormously. A platform choosing to algorithmically push content that keeps a teenager scrolling at 2 a.m. is making an active product decision, not passively hosting speech. The companies built those systems, iterated on them with internal research, and in some cases, according to documents surfaced in prior litigation, knew the harms they were producing. Juries, presented with that evidence, found that accountability was warranted.

Section 230 does not — and legally cannot — immunize a company from liability for its own product choices the same way it insulates them from liability for their users' words. That's the opening plaintiffs have exploited, and that courts are now ratifying.

## Why This Is a Platform Suppression Story

NewsOnScale covers platform suppression not just as content moderation overreach, but as the broader dynamic in which platform architecture determines whose voice is amplified, whose is buried, and whose is algorithmically routed toward radicalization or harm. That architecture is the product. These verdicts name it as such.

For years, the debate over reforming Section 230 stalled in Congress, caught between conservatives who wanted platforms punished for alleged anti-conservative bias and progressives who wanted them punished for not doing enough to remove harmful content. Both camps kept reaching for the same blunt instrument — threatening to strip immunity entirely — without agreeing on why. The result was legislative paralysis across multiple sessions.

Litigation moved where legislation couldn't. And it moved with specificity: not demanding that platforms censor more or less, but demanding that they answer for the consequences of systems they designed and deployed for profit.

## The Road Ahead Is Not Simple

None of this is settled law. Verdicts get appealed. Higher courts may draw the design-versus-content line differently. The Supreme Court has already shown ambivalence about how far platform liability can extend without chilling legitimate speech — a concern that is not frivolous. Blanket liability for algorithmic amplification could, in the wrong legal formulation, make platforms so risk-averse that they restrict speech more, not less.

Those tradeoffs deserve honest accounting. The goal of platform accountability is not to hand more moderation power to corporate legal departments worried about litigation exposure. It is to create meaningful consequences for knowingly harmful engineering — the kind documented in internal research, whistleblower testimony, and now, apparently, jury deliberation rooms.

## What to Watch

The Senate Commerce Committee recently convened a hearing marking the 30th anniversary of Section 230, suggesting Congress is at least performing attention to the issue again. Whether that translates into coherent legislation remains doubtful given recent history. What's less doubtful: the courtroom record is building, the verdicts are landing, and the argument that platforms bear zero responsibility for the machines they built is getting harder to make with a straight face.