ES version is available. Content is displayed in original English for accuracy.
Advertisement
Advertisement
⚡ Community Insights
Discussion Sentiment
43% Positive
Analyzed from 778 words in the discussion.
Trending Topics
#https#claude#utc#models#status#com#audio#more#nonsense#order

Discussion (21 Comments)Read Original on HackerNews
Not like adding glue to pizza. Here's an example from today (paraphrasing): "you need to run `git merge-base branch1 branch2`. Pay attention to the order of arguments, it is important: `git merge-base` is symmetric and returns the same value regardless of the order of inputs".
So which one is it? Symmetric or not? It's not even one of those where it self-corrects, it just happily contradicts itself halfway through the sentence.
My pet theory is that these frontier models do quite a bit of brute force at the end - some kind of beam search - and silently downgrade you depending on demand or compute availability.
Still not great. This particular nugget is from Sonnet 5, default settings.
It does feel like the kind of thing beam search would fix. The LLM starts the sentence with a claim like "Pay attention to the order of arguments". Around that time it "notices" that the order doesn't matter, but it's already committed to the sentence and has to complete it in the best way still possible
Maybe at some point someone figures out how to train models with a backspace token
Sometimes it works out, in that an unrecognizable word or two is replaced with reasonable assumptions based on the semantics established by the words that came before the signal degraded.
But the bad audio might also result in words that don't align well to what came before, or represent alternate (mis)interpretations. Now this is part of the context and the next several tokens align to this new path regardless of what is said in the audio.
In pre-LLM transcription, you might get a nonsense word or two when the audio transiently degrades, but the specific meaning of the nonsense words doesn't influence the transcription of audio following the degradation.
Well you can't blame them, it's what brings in the cash. Other uses will suffer proportionally.
Update 11:27 UTC: I saw the error first at 11:22 UTC. Retry at 11:27 UTC still failing. Status page is still green.
Update 11:28 UTC: Incident has been declared dated 11:27 UTC https://status.claude.com/incidents/mfdtrknpxghq
Third outage today. Per https://downdetector.com/status/claude-ai/ the people affected grows every time: first one had peak 19 reports, second 24 and now it's already 39.
No wonder the amount of water that both Claude and Codex are taking they also need so many frequent hydration breaks.
[0] https://news.ycombinator.com/item?id=49056739
So you think that the water that comes out of these data centers is safe for humans once released and the mass consumption of them is not a concern?
Sounds like a way to sweep this environmental issue under the rug.
[0] https://theoec.org/news-and-information/behind-the-data-boom...
[1] https://fieldreport.caes.uga.edu/publications/TP121/how-data...
[2] https://www.wsj.com/tech/ai/ai-data-centers-water-use-901e29...