8 ms·
Base64: https://chat.openai.com/share/3793da6d-4634-4e13-9cc4-ce9983377768 https://chat.openai.com/share/3793da6d-4634-4e13-9cc4-ce9983... ROT13: https://chat.
by danielbln 3y ago
Base64: https://chat.openai.com/share/3793da6d-4634-4e13-9cc4-ce9983377768 https://chat.openai.com/share/3793da6d-4634-4e13-9cc4-ce9983...
ROT13: https://chat.openai.com/share/ae7c311d-ab23-4425-bdfa-c2314e1cbc44 https://chat.openai.com/share/ae7c311d-ab23-4425-bdfa-c2314e...
HEX: https://chat.openai.com/share/4b0740b7-53c0-4776-bb00-ab65b4def9d3 https://chat.openai.com/share/4b0740b7-53c0-4776-bb00-ab65b4...
What kind of encoded string did you use?
- RecycledEle 3y agoThank you for taking the time to call BS on someone who obviously never tried asking a LLM AI to decipher a string's encoding. That is exactly the kind of thing they are good ar.
- Retric 3y agoTwo people can try similar prompts and get very different results from LLM’s.
- ern 3y agoIt’s pretty impressive that it was able to actually decode those strings. In March, I used GPT 3.5 to write code for validating a type of string which used a checksum algorithm. It did the task well, and even wrote tests, but it failed when generating test case values. I wonder if it would perform better if I did it today.