alt Hacker NewsNot to mention all the other ways they can screw you:
- Middle of the day, servers busy? Swap to Sonnet while pretending it's still Opus. Many people won't notice, and nobody can prove anything if they suspect.
- Middle of the night, server load is light? Put it into extra thinky mode so it burns more tokens to ramp up the bills. Flip the switch where it gets really pedantic about writing lots of extra test cases and verifying against documentation.
- Demand increases, but don't feel like running more hardware? Switch to low bit quants, but have a monitor model swap back to quality if it can tell you're running a benchmark.
Assuming model capability plateaus (I think it will), token providers will be in a race to the bottom to maximize profits at the expense of quality that's very difficult to measure.
Replies
These kind of tricks will completely break API customers and be super visible, since most companies deploying API at scale have ample telemetry, evals, etc.
Although, selectively applying it to consumer subs is probably beyond likely at this point.
It all sounds like having to rely on a dodgy housing contractor that wants to steal from you, take shortcuts AND choose the gold-plated options from their supplier friends, and will start doing this the minute you are not on site supervising. You don't do it yourself (because the contractor is faster and stronger than you in many ways) but you can't leave, so you're stuck on the worksite just watching them.
What areas do you think model capability will plateau in, and why?
Ugh... didn't think about extra thinky mode in the middle of the night.
So many ways for enshittification here.
I find Claude doing a lot of pointless confirmation at night when it will ask me about things that it would normally just do during the day.
Frustrating to be like “do X overnight, don’t ask me for input” and come down to find it having worked for a few minutes and then stopped.