USA Today and 18 Gannett papers sue OpenAI for $250M+ over scraped training data

USA Today and 18 Gannett papers sue OpenAI for $250M+ over scraped training data

Good morning ๐Ÿ‘‹ The number everyone's leading with is $250M. The actual ask, buried a few paragraphs into the complaint, is that OpenAI destroy every model trained on the data.

In today's issue:

Get tomorrow's issue in your inbox.

One concise AI brief, sent after the signal clears the noise.


๐Ÿ”ญ THE ONE THING

๐Ÿ“ฐ USA Today and 18 Gannett papers sue OpenAI for $250M+ over scraped training data

USA Today, the Detroit Free Press, the Arizona Republic and 16 more Gannett mastheads filed suit against seven OpenAI entities in the Southern District of New York on Oct. 8, case 1:26-cv-08892. The complaint gets specific: more than 160,000 entries scraped into OpenAI's WebText training sets, 83,266 of them from usatoday.com and 12,994 from freep.com alone, plus over 122 million tokens pulled into C4. Gannett wants $250M+ in damages, an injunction, and destruction of any model trained on the data. That last ask is the tell: courts have let similar suits settle into licensing checks, not model rebuilds, and I'd bet this one follows the same path. Despite the splashy number, trade press is already filing this as one more entry in a two-year pile of publisher suits against OpenAI, not the landmark it's being sold as.


๐Ÿง  MODELS & RELEASES


๐Ÿ”ฌ RESEARCH HIGHLIGHTS


๐Ÿš€ AI STARTUPS


๐Ÿ› ๏ธ TRY THIS

Gate your agent's fixes behind a human, not its own judgment

Publishers suing OpenAI over scraped content are arguing a version of the same thing ops teams have wanted for a year: don't let an autonomous system act on what it touched without a person signing off first. AWS just shipped that pattern for its own DevOps Agent. It investigates incidents and stays strictly observe-and-report; a separate pipeline turns its findings into a pre-validated fix a human has to approve before anything runs. AWS Machine Learning blog

1. Let your diagnostic agent produce a root-cause summary only. No write access, no remediation calls.

2. Pipe that summary into a second stage that drafts the actual fix as a candidate, not an action. AWS does this with Lambda Durable Functions and EventBridge.

3. Validate the candidate fix against your runbook (AWS routes this through Bedrock) before it ever reaches a human queue.

4. Require an explicit approve-and-run click from on-call. The agent diagnoses. A person pulls the trigger.

Prompt: Given this incident summary and the current runbook, draft a remediation step as a candidate only. Flag anything outside documented procedure, and do not assume approval to execute.

๐Ÿ”— QUICK LINKS


See you tomorrow.

Pradeep Perugu

Get inovAIte in your inbox.