“In fact, I think that as capacity limits get hit, both Anthropic and OpenAI will degrade the experience for the user (either through model degradation or rate limit decay) as much as they can.”
Our reading, the sentence that was checked:
As capacity limits are hit, Anthropic and OpenAI will degrade user experience as much as they can via model degradation or rate limits.
Assessment: Unresolved No deadline stated on 2026-10-29 Evidence as of
Where and when Ed Zitron wrote it
Where's Your Ed At, I Will Never Respect A Website, paragraph 167.
- Said
- Source observed
- live page, full text, public
- Evidence as of
- the cutoff for this assessment
- Assessment recorded
- assessment wyea-i-will-never-respect-a-website-f28d3d-a2
We recorded 36 claims from this post. See every claim from this post.
The wording above is the version this site observed on 2026-10-28. The source may have been edited after 2026-04-14. This page does not claim the wording was captured then.
What the claim commits to
- Kind
- Conditional forecast
- Deadline, as the speaker wrote it
- None stated. This site does not add one.
- Deadline state when assessed
- No deadline stated
- Deadline state on 2026-10-29
- No deadline stated (the release’s reference date)
Conditions
- as capacity limits get hit (antecedent, stated by the speaker)
From the speaker
- as capacity limits get hit
- both Anthropic and OpenAI
- will degrade the experience
- model degradation or rate limit decay
- as much as they can
Our interpretation
- Capacity limits means insufficient serving capacity for demand, not a customer's exhaustion of an existing allowance.
- The ordinary testable core is that each company responds to capacity pressure by reducing model quality or allowed usage.
- Temporary errors or an unrelated software regression do not by themselves establish the predicted response.
- Retain the maximality assertion as an additional requirement; evidence of any deterioration alone cannot establish 'as much as they can'.
Counts as supported if: For both companies, verified capacity constraints are followed by attributable reductions in model quality or usage allowances, with evidence supporting the claimed extent of those reductions.
Counts as contradicted if: A well-documented completed response to capacity pressure preserves or improves quality and allowances despite feasible reductions, undermining the asserted response. An unrelated improvement after capacity expands is not sufficient.
Retrospective: these criteria were written after the outcome was public.
Current assessment
Did the forecast come true?
Outcome: Unresolved
The record was checked, and the evidence available by the cutoff does not settle it.
Scored on a plain reading. The speaker named no measure for this claim, so it was judged on the reading an informed reader would take, stated below under our interpretation. Both reviews had to find that reading fair.
- Evidence as of
- Deadline state when assessed
- No deadline stated
- Assessment recorded
- Policy version
- 2026-10-28.7
Rationale
May 6 reporting documented Anthropic's demand exceeding compute capacity, but did not establish that every restriction discussed began after the April 14 forecast [e1]. On May 12, an OpenAI contributor identified regional serving shortages and distinguished them from rate limiting or exhausted allowances [e2]. Anthropic's April 23 postmortem reported that an April 16 prompt change hurt coding quality and was reversed on April 20; it did not establish a capacity-driven cause [e3]. Capacity constraints are documented, but these records do not establish a completed response that confirms or refutes the forecast, or reductions 'as much as they can' by both companies [e1, e2, e3].
Limitations
- The reporting does not date every Anthropic restriction relative to the forecast.
- Regional unavailability does not establish reduced model quality or usage allowances.
- The packet lacks matched capacity, policy and controlled quality measurements for both companies.
- The maximum feasible reduction is not established, and the forecast specifies no deadline.
Evidence (3 items)
Supports the claim: Ars Technica,
demand
Why it matters here: This contemporaneous account describes Anthropic's capacity pressure. It establishes the condition but does not date every restriction after the forecast or establish maximal degradation.
- Publisher
- Ars Technica
- Kind of source
- News report
- Describes events of
- Public from
Supports the claim: OpenAI contributor etraut-openai on GitHub,
running low on capacity
Why it matters here: The contributor identifies a regional model-capacity shortage. The surrounding response distinguishes this from exhausting usage or being rate limited.
- Publisher
- OpenAI contributor etraut-openai on GitHub
- Kind of source
- Company disclosure: the company describing itself, not an independent finding
- Describes events of
- Public from
Context only: Anthropic,
hurt coding quality
Why it matters here: Anthropic acknowledges a post-publication quality regression but says it reversed the change. This cautions against treating any observed deterioration as evidence of a capacity-driven policy of maximal degradation.
- Publisher
- Anthropic
- Kind of source
- Company disclosure: the company describing itself, not an independent finding
- Describes events of
- Public from
What would settle it
Document completed capacity-response episodes after April 14, linking constraints to subsequent quality or allowance decisions. Support requires evidence for both companies and the claimed maximum extent of reductions. A completed episode preserving or improving quality and allowances despite feasible reductions could refute the predicted response; improvement following added capacity alone would not suffice.
Where it was said (1)
Said once in the sources this register covers.
: Where's Your Ed At, I Will Never Respect A Website
In fact, I think that as capacity limits get hit, both Anthropic and OpenAI will degrade the experience for the user (either through model degradation or rate limit decay) as much as they can.
- Where
- paragraph 167
- Published
- 2026-04-14
- Source observed
- , live page
- Access
- full text, public
History
Assessment versions
- Assessment wyea-i-will-never-respect-a-website-f28d3d-a2: Current. Outcome: Unresolved. Evidence as of 2026-10-28. Public date not recorded.
Recorded events
Assessment publishedBy this site
First assessment published after both reviews and the final-text check passed.
About assessment wyea-i-will-never-respect-a-website-f28d3d-a2.