In the second handpicked example they give, GPT-4.5 says that "The Trojan Women Setting Fire to Their Fleet" by the French painter Claude Lorrain is renowned for its luminous depiction of fire. That is a hallucination.
There is no fire at all in the painting, only some smoke.
There have always been cycles of hype and correction.
I don't see AI going any differently. Some companies will figure out where and how models should be utilized, they'll see some benefit. (IMO, the answer will be smaller local models tailored to specific domains)
It will be upheld as prime example that a whole market can self-hypnotize and ruin the society its based upon out of existence against all future pundits of this very economic system.
If the electricity were generated by thousands of volunteers pedalling in their basement, then yes, I would expect the utility company not to be too greedy.
ChatGPT (4o): Noticed "a pattern"
Le Chat (Mistral): Noticed a "cartoonish figure"
DeepSeek (R1): Completely missed it
Claude: Completely missed it
Gemini 2.0 Flash: Completely missed it
Gemini 2.0 Flash Thinking: Noticed "a monkey"
This resonates with me. I used to love tinkering with "underdog" tech. I did frontends in svelte before it was cool. But for new projects, I now always default to react+tailwind, because that's what Claude knows best.
And for the backend, I'm working on a SQL-only framework, because LLMs are now at almost 100% accuracy on text-to-sql.
The principle of the software seems to be that the original data is never altered. It is a postgres extension that "masks" the data for certain postgres users. You can always connect as the root user and see everything when you need to.
Does anyone here know more about the unreliability of Google's sub claim? I am using it, and have never had issues with it, but this post seems to just dismiss it without more details.
When does Google change the subject of a token for a given user account?
Dashes in API keys are really annoying. Double-clicking doesn’t select the full key, which just adds extra hassle. It would be much better if they used a continuous string without any separators. Makes copying and pasting way easier, and doesn't affect security at all.
They realized that and were pleased with themselves.
> The dashes do remove easy double-click copying, but we think this a fine trade off for readability. We don't want users copying and pasting them everywhere, in fact we want them to be handled with care. Ideally, users copy each key exactly once - when they generate the key from our dashboard - so we added a copy button to our UI to solve that case
Don't even think about copying/pasting that key, you rube!
Not only that, they are making the biggest mistake a company can do by telling their customers that what they are doing is wrong and that the company knows better than they do.
Whenever I have created API keys for a product, this is the #1 feature I want: easy copy-pasteability. Just letters and numbers, no special characters that break double-click-selecting the key.
This is the only annoyance with UUIDs, I won't be typing it because its 5 characters shorter. Separators are nice because I can try to visually compare Ids, but it needs to be a visual separator that won't break a `word`/`WORD` (whatever boundary that is by default on most terminals and browsers) select by double clicking.
I want to just double click and copy, dragging is annoying.
