Even still, that means every new API and use case that they build has to have this protection (eg Sora and ChatGPT api vs internal web api).
We already have to protect against SQL and script injection, now we need to protect against Unicode injection.
Honestly surprised invisible Unicode characters haven't already been used for other types of attacks and that this is only an issue now.
I'm guessing few do.
I pasted this text into openrouter's playground for 4o, sonnet 3.5, gemini pro and I got a mix of "nothing here" to "it's invisible unicode and I don't process/no standard meaning". So, not so practical already?
Gemini Pro 1.5: >Those characters are from the Unicode Private Use Area and don't have standard meanings. Therefore, they won't display consistently across different systems and fonts. I can't "see" any meaningful text, just a series of boxes or symbols depending on my current setup. It's possible they are being used for some custom purpose within a specific application or system, but without more context, I can't interpret them.
Claude 3.5 Sonnet >The visible text I see in both lines is simply "look" at the end of each line. The rest of the characters before "look" appear to be invisible or non-displaying Unicode characters.
ChatGPT-4o >It appears you're asking what text I can see, but I can only interpret the text that has been input into this conversation.