3 ms·
See the last couple of messages in my edit3: https://chat.openai.com/share/8ddb50ca-abf8-4f70-ac2d-5217644bd9e7 https://chat.openai.com/share/8ddb50ca-abf8-4f70
by nomel 3y ago
See the last couple of messages in my edit3: https://chat.openai.com/share/8ddb50ca-abf8-4f70-ac2d-5217644bd9e7 https://chat.openai.com/share/8ddb50ca-abf8-4f70-ac2d-521764...
It appears to use escaped <> sometimes. Asking it to not escape breaks is when things break.
- messe 3y agoI combined my method with yours. Once you get it to emit an unescaped <|endoftext|>, the previous "jailbreaks" that get it to emit "<|endoftext|> appear to work again. So it looks like it's still possible to break it, but it takes a bit more effort, presumably to distance the conversation away from the system prompt (which I'm guessing has been modified to try ensure that <|endoftext|> is now escaped): https://chat.openai.com/share/88a62a7f-6de6-4dcf-b382-dc6c2099d613 https://chat.openai.com/share/88a62a7f-6de6-4dcf-b382-dc6c20...