But shouldn't the app be programmed to maximize the chances that it'll work on the first try? It seems like a reasonable compromise to me. Annoyingly bright for a few seconds so I don't have to futz with my brightness.
Interestingly this is exactly why I have to mess with brightness settings from time to time.
Has anyone else noticed the weird interaction between apps turning the brightness to the max and the system’s auto brightness? I’m not an iOS developer, so I don’t know about the relevant APIs. But every time an app changes the brightness to display a QR code, it seems to do so by retrieving the current brightness, turning it to the max, and when it’s done, setting it back to the old value. The problem is that iOS seems to register the brightness change as user initiated, and changes auto brightness behavior. After a few uses, auto brightness will no longer adjust the display to the minimum brightness, even when you’re in complete darkness.
Fixing this used to be easy. Just go to display settings and toggle auto brightness off and on. Then Apple decided to move the toggle under accessibility. Now it’s Accessibility -> Display & Text Size and scroll all the way to the bottom.
This subthread was about if the app should even show QR codes at maximum brightness because the scanner could maybe also scan the code at the normal brightness. And the counterpoint was that you can’t selectively increase the QR code brightness to the HDR level manually, because you would be capped at the normal maximum brightness.
Anecdotal, but I tried running a few identical biology questions through both Fable and Opus and the classifier was only rejected my queries with Fable.
This is good news. I'm doing a lot of work that Fable thinks is AI related right now (it is nothing remotely competitive to Anthropic - it's just relatively basic stuff I'm doing with learning models and so forth), yet it blocks me almost every time. I have switch to GPT-5.6-Sol for this work since it's stronger than Opus 4.8.
reply