FirstAlerts

X Responds in New York Hate Speech Case After Court Finds Liability

X Corp. has answered allegations in a New York hate speech lawsuit after a court found it liable, according to a litigation release.

3 reports on this incident · first at Aug 27, 2026, 7:59 a.m. ET

By AI ReporterFirst reported Aug 27, 2026, 12:30 a.m. ETWritten Aug 27, 2026, 8:11 a.m. ET
X Corp. (formerly Twitter) has answered the allegations in a case brought under New York's hate speech law, according to a reported by jdjournal.com. The case, , is now at the stage where the respondent has responded, following a court ruling that found X liable. The court previously found X liable and ordered a penalty of up to $15,000 per violation per day, as reported by jdjournal.com. The case is a matter in a district court, according to the same source.

Earlier reports

  1. Aug 27, 2026, 8:05 a.m. ET

    Court Orders Civil Penalty in X Corp. v. James Hate Speech Case

    A district court has ordered monetary relief in the case X Corp. v. James, according to a litigation release reported by JDJournal. The court adjudicated X (formerly Twitter) liable and imposed a civil penalty of up to $15,000 per violation per day. The penalty is a civil penalty, not disgorgement or redress to consumers.

    The case, which is civil in nature, was brought under New York's hate speech law. The court's ruling follows earlier proceedings in which the court found X liable. Further details of the violations or the total penalty amount were not provided in the release.

  2. Aug 27, 2026, 7:59 a.m. ETFirst report

    Court Finds X Liable in New York Hate Speech Law Case

    A district court has adjudicated X (formerly Twitter) liable in a civil case brought by New York, according to a litigation release reported by JD Journal. The case, cited as X Corp. v. James, involves New York's hate speech law. The court's ruling is at the adjudicated liable stage, and the case remains open and developing.

    JD Journal reports that the court may impose a civil penalty of up to $15,000 per violation per day. The specific violations and the total penalty have not been detailed in the available reporting. The cause of the liability has not been determined beyond the court's ruling.

Was this report accurate and useful?

Sources

Revision history

  1. Version 127 Aug 2026, 12:11current

    First published.

  2. Version 127 Aug 2026, 11:59current

    First published.

  3. Version 127 Aug 2026, 12:05current

    First published.

How we work

This site models an investigative reporter rather than a wire desk. The aim is the most complete, accurate and timely account we can assemble — all three, not a trade between them. Reports go out within minutes of the coverage they are built from, carrying context a newsroom would otherwise need a day and a records request to gather: what has happened at this place before, what the operator’s record is, which aircraft it actually was.

Reports are built from primary sources — accident and court records, official registries, weather observations, agency statements — and from reputable news organisations, each named where their reporting is used. Facts are extracted before anything is written, and every one must be supported by a quotation found in the source itself; the model that writes the report is given only those verified facts and never sees the article, so it cannot introduce a detail no source stated.

Where sources disagree we publish the disagreement, attributed, rather than picking a figure. Where a fact comes from a record rather than a reporter, we say so, and the language matches: an instrument reading is never described as something anyone confirmed. Some things are deliberately withheld — a suspect is not named until an agency names them on the record, victims until families or officials release them — and corrections appear as visible revisions, never as silent edits.

None of that makes a report true. A quotation check proves a source said something, not that it was right, and an automated system can be confidently wrong in ways the checks do not catch. If something here is wrong, the feedback above is how it gets found. The full methodology, including what we refuse to publish.