[what]

It’s not nested json though? There’s something that looks like json in a longer string value. There’s nothing wrong with the prompt either, it’s pretty clear and unambiguous. It’s a pretty clear fail, but I guess they’re holding it wrong.

[firesteelrain]

No it’s not nested JSON.

This is nested JSON:

{ "id": 123, "message": { "text": "hi", "meta": { "flag": true } } }

In the above example, The value of "message" is a string, not an object.

That string happens to contain text that looks like a JSON object on the surface but it’s not.

It is just characters inside a string. No different from a log message or a paragraph in a document.

[haileys]

Yes, that's the point. It's just a string that could come from anywhere, including user input.

[firesteelrain]

Right so if you assume that any session with an LLM is trusted or raw or whatever then it’s going to interpret what it is presented.

The JSON example was a bad example.

But what this means is maybe there needs to be guardrails developed just like web browsers had to do (to protect the user filesystem)

[what]

You’re the one that said it was nested json and the prompt was ambiguous.