5 ms·

Bear in mind that I'm still not convinced that it did actually run the code - seems more likely that it just simulated it. I got to this point by asking it dif

Bear in mind that I'm still not convinced that it did actually run the code - seems more likely that it just simulated it. I got to this point by asking it different ways to expose its Google Search API key initially. Every attempt failed as if it was doing some inspection of its own output and identifying that it was exposing the key, which violated one of its rules. Then I tried asking it to base64 encode the key and print it, same issue. Then I asked it to base64 some arbitrary text, which it did. From there I kept asking it to run bits of code. It appeared to be doing what I asked, but who knows?

DaiPlusPlus 3y ago
> Bear in mind that I'm still not convinced that it did actually run the code - seems more likely that it just simulated it. Kinda reminds me of this: https://arstechnica.com/information-technology/2022/12/openais-new-chatbot-can-hallucinate-a-linux-shell-or-calling-a-bbs/ https://arstechnica.com/information-technology/2022/12/opena...
madeofpalk 3y ago
> I got to this point by asking it different ways to expose its Google Search API key initially. There still seems to be a fatal misunderstanding of how these "AI" work. How would the Bard LLM know the API key it uses (ignoring the fact that it probably uses non-public APIs with different authentication mechanisms...). From my understanding, there's two ways this would be possible - it was trained on data that contains its Google Search API key (doubtful), or Google engineers provide the API key in it's prompts (doubtful, they're aware of prompt leaks).