Look... its clear you didnt read the article. The point of contention is that google _hallucinated_ facts. As in, website 1 said company A exists and website 2 said company B committed a crime and now googles AI summary says company A committed a crime while linking website 1 and 2.
The court found google to be liable for that, because company A has no other recourse otherwise. Which website operator was the company supposed to contact to remove this "false" information? It only exists in the aether of google search results, and only as a side effect of them adding functionality into that when someone is searching.
> was google search responsible for surfacing correct answers
No, as the article lays out, google hallucinated facts that werent present in source material and so at that point the court found them liable for that.
Previous protections existed for search because it has been argued (and agreed) that they are merely a vessel for showing the content to the user. But when they begin to editorialize and reword the content to show their own version of the content (the AI summary) those protections dont apply even if the AI summary is shown in the same UI as search.
You can achieve this with numeric sequences too, by having a consistent step and unique offset in all your sequences. For example, if you will never exceed 16 types, reserve four bits as the type discriminant. (You don’t have to use powers of two, but it may be convenient.)
All sequences use step 16.
Type A has discriminant/offset 0, yielding IDs {0, 16, 32, 48, 64, …}.
Type B has discriminant/offset 1, mapping to IDs {1, 17, 33, 49, 65, …}.
All the way up to Type P with discriminant/offset 15 and IDs {15, 31, 47, 63, 79, …}.
This is also trivially invertible so that you can determine the type from the ID.
A more common approach is to make IDs opaque strings and put a type prefix—A0, B12, P34, that kind of thing. But this way you can keep it as a number, if you wish.
They just mean you catch incorrect joins more easily because there is usually no overlap in keys between unrelated tables. Using int, you’re usually going to have some shared values between two unrelated tables.
Statistically impossible to inadvertently generate a collision using UUID keys. UUID is designed to be unique when generated across any computer system. Practically speaking if you have an exactly matching pair of UUIDs from disparate system you have found the exact record match. The name gives a hint "Universally unique identifier". -Not a cryptographer.
Hmm thats a pretty interesting variant. I dont think it would apply directly to our team, but I like the potential playground it gives for both coming up with solutions as well as being a kickstarter for convos on alternatives.
An AI doing a bad job is not the same as it wasnt able to do a good job. I would bet if you asked it if its a good name it would figure it out, and give a logical argument on why to change it. Im not going to ascribe that to "intelligence" but I do think its a bit existential in terms of what it implies for our definition of "intelligence".
No, it wasn't a matter of AI needing to come up with an argument name. It's a matter of the difference between a trusted assistant who can catch mistakes, vs a sycophant who just does what their told and doesn't catch mistakes.
OK well the initial wording seems like you are presenting this as an inherent limitation. "Has a personality that I dont agree with" is a different critique than "fundamentally does not understand"
> If the AI had more understanding of language, it probably would have come back and said, "would you like to name it XXX instead?"
4. Agree with you, this doesnt meet my bar of things to be worried about
5. Disagree insomuch as sure the SOTA models will outpace the normies models, but I dont think thats actually an issue. Opus 4.5 is "good enough" if the harness is stable and not hitting weird regressions. So once we reach opus 4.5 levels on self-hostable models (even if self hosting is actually a cloud hosted thing) then Im not concerned. Sure the SOTA will be better, but AI as a normal part of a devs day is able to be satisfied by Opus 4.5 for many years to come.
Since the source code leaked showed they key off of swearing to trigger certain behavior, I actually intentionally swear when running into things like insufficient thinking and/or hallucinations. It also unironically makes it easier for me to grep later to run analysis on how often its happening.
eg I manage my Brewfile declaratively with home-manager, and then run this on file change
reply