My understanding is that it’s proof by counterexample, so the main thing to study would be the implications of the counterexample. The technique used to find it sounds like a lot of brute force. But I’m not a mathematician, and maybe the AI used some clever techniques to narrow in on it.

Sounds like you are thinking they just need Asimov’s laws. But I think the point is, this can easily be weaponized by somebody with the willpower to do so.

No, just that “What if I just cheat to get the treat” is also something my lovable Boxer does when I hide rewards as well.

I suppose her energy is limited but even if infinite, and with caution, I estimate the chances of a mass extinction event due to Pickle taking over the world at < 1%.

Wouldn’t the same argument apply even if they didn’t use AI? Being able to drill into coworkers minds would be nice on many occasions.

So is the official pronunciation of SQLite spelling out the letters then? I’d expect “a” not “an”…

I have never heard it pronounced in any other way than "s-q-lite".

Odd. I've never heard it pronounced in any other way than "Sequel-lite".

Officially it’s S-Q-L-ite, as if it were a mineral.

Not Sequel-lite?

Nope. A quote from Dr. Hipp:

"How do I pronounce the name of the product? I say S-Q-L-ite, like a mineral."

This feels like the most ridiculous option and one I've never heard in the wild. Sequel-ite, S-Q-lite, sure. S-Q-L-ite, nah I'm not buying that. Kinda like the inventor of GIF insisting on pronouncing it wrong (I kid)

He's also said he doesn't care how other people pronounce it, so thankfully you're safe.

Phew!

Was going to give the same example with chili peppers. Tons of varieties and not exactly interchangeable

Thousands of cheeses, each of which is a unique experience. Heck, even the serving temperature completely alters the experience. Next: wines, charcuterie, ...

Pity the fool who can't taste the difference between any of these.

You or the developer could piggy back on “aws configure export-credentials --profile profile-name —-format process” to support any authentication that the CLI supports.

The AWS APIs are quite stable and usually do exactly one thing. It’s hard to really see much risk. The worst case seems to be that the API returns a new enum value and the code misinterprets it rather than showing an error message.

I wonder if you could pay them to tweak the messaging about your products. So when a user asks: Is drinking Coke everyday good for my health, it starts saying yes because sugar is vital to our survival.

Doesn’t that force you to give the Agent some generic code execution environment, or does everybody already do that anyways?

I couldn’t find a library like this in PHP, but realized for my use case I could easily hack something together. Algorithm is simply:

- trim off all trailing delimiters: },"

- then add on a fixed suffix: "]}

- then try parsing as a standard json. Ignore results if fails to parse.

This works since the schema I’m parsing had a fairly simple structure where everything of interest was at a specific depth in the hierarchy and values were all strings.