OpenAI Says Apple’s Real Problem Is Being Bad at AI, Not Stolen Secrets
The legal battle between OpenAI and Apple just got (even more) personal. In response to a bombshell lawsuit accusing the startup’s employees of stealing Apple’s trade secrets, OpenAI called the case “meritless” and requested that it be tossed out by a federal judge. The lawsuit accuses two former Apple employees, Chang Liu and Tang Tan, of illegally using their insider knowledge of the company’s trade secrets to help OpenAI—which hired Liu and Tan earlier this year and last summer, respectively—build its fledgling hardware business.
- ▪The legal battle between OpenAI and Apple just got (even more) personal.
- ▪In response to a bombshell lawsuit accusing the startup’s employees of stealing Apple’s trade secrets, OpenAI called the case “meritless” and requested that it be tossed out by a federal judge.
- ▪The lawsuit accuses two former Apple employees, Chang Liu and Tang Tan, of illegally using their insider knowledge of the company’s trade secrets to help OpenAI—which hired Liu and Tan earlier this year and last summer, respectively—build i
2 outlets in our directory ran this story. All of the coverage we found sits in one bucket: centre. That one-sidedness is itself worth noticing.
Gizmodo files mainly under tech. We currently carry 821 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 | Gizmodo |
| Canonical URL | https://gizmodo.com/openai-says-apples-real-problem-is-being-bad-at-ai-not-stolen-secrets-2000795382 |
| Publication time | Thu, 06 Aug 2026 16:30:33 +0000 |
| Retrieval time | 2026-08-06T16:35:48.067Z |
| Last seen | 2026-08-06T16:35:48.067Z |
| 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 | _FDmuWXBA2vh · 2 stories |
| 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
The legal battle between OpenAI and Apple just got (even more) personal. In response to a bombshell lawsuit accusing the startup’s employees of stealing Apple’s trade secrets, OpenAI called the case “meritless” and requested that it be tossed out by a federal judge. The response also suggested that Apple’s accusations were motivated in part by jealousy of OpenAI’s success.…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Gizmodo.
Discussion
0 commentsMore from Gizmodo
