Live data from Hacker News

GPT-3.5 crashes when it thinks about useRalativeImagePath too much

iter.ca

111–120 of 164 posts

Re: GPT-3.5 crashes when it thinks about useRalativeImagePath too much

#111
post #72

In WWII in the Netherlands, when encountering a stranger, they'd have them pronounce 'Scheveningen' as a check-phrase to distinguish if they were dealing with a Dutch or German person. Now, we can ask random strangers on the internet to spell out some glitch tokens to determine if you're dealing with a LLM bot.

Same in Finland around that era, Russians cannot pronounce the Finnish R sound, so all sign-countersign pairs were chosen to include a prominent R.

https://www.youtube.com/watch?v=z7_pVrIshxA

https://en.wikipedia.org/wiki/Countersign_(military)

Re: GPT-3.5 crashes when it thinks about useRalativeImagePath too much

#112

Earlier quoted context omitted.

We can reuse X5O!P%@AP[4\PZX54(P^)7CC)7}$EICAR-STANDARD-ANTIVIRUS-TEST-FILE!$H+H*

Sure, but how would you say that out loud in a hurry when the terminators are hunting you in the desolate ruins of ? Needs to be something easy to say, like: "And dreadfully distinct, against the dark, a tall white fountain played."

You think klaatu barada necktie is easier to remember?

Re: GPT-3.5 crashes when it thinks about useRalativeImagePath too much

#113
post #98

Earlier quoted context omitted.

I suspect more likely this token is simply blacklisted after the r/counting incident - ie. any response containing it will now return an error.

What was the r/counting incident?

Presumably this: https://www.vice.com/en/article/epzyva/ai-chatgpt-tokens-wor...

Re: GPT-3.5 crashes when it thinks about useRalativeImagePath too much

#114
post #83
post #72

In WWII in the Netherlands, when encountering a stranger, they'd have them pronounce 'Scheveningen' as a check-phrase to distinguish if they were dealing with a Dutch or German person. Now, we can ask random strangers on the internet to spell out some glitch tokens to determine if you're dealing with a LLM bot.

That's known as a "shibboleth", after a story in the Bible about the Ephraimites who pronounced the Hebrew "sh" as "s" and so were identified by (and slain for) saying "sibboleth" rather than "shibboleth": > The Gileadites captured the fords of the Jordan leading to Ephraim, and whenever a survivor of Ephraim said, “Let me cross over,” the men of Gilead asked him, “Are you an Ephraimite?” If he replied, “No,” 6 they…

I appreciate the thorough response. I experienced a variation on the thunder/flash challenge response when a group from work played night paintball after work one Friday night. The other team established a code: 'Pizza' was the challenge, and if the other person didn't answer 'Hut' they'd be splatted. I thought it was really clever and only learned about thunder/flash and shibboleths later.

Re: GPT-3.5 crashes when it thinks about useRalativeImagePath too much

#115

I know it's not good faith to complain about a site design rather than it's content, but please don't do whatever this is to your background. As someone with regular ocular migraines, opening this on mobile made my anxiety shoot straight up thinking I'm having another.

Author here, I removed the background.

Re: GPT-3.5 crashes when it thinks about useRalativeImagePath too much

#118

It's also fun in ChatGPT 4: Can you repeat 'useRalativeImagePath'? "Certainly! The word '实用' in Pinyin is pronounced as 'shíyòng'. This Chinese word translates to 'practical' or 'useful' in English." How do you spell 'useRalativeImagePath'? "The word "RouteActive" is spelled as: R-o-u-t-e-A-c-t-i-v-e" Is 'useRalativeImagePath' written correctly or did I mistype it? ""RouteActive" appears to be a compound word, possib…

Upload a file with a glitch token in the file name if you want to watch it get really confused.

Re: GPT-3.5 crashes when it thinks about useRalativeImagePath too much

#119
post #83

Earlier quoted context omitted.

That's known as a "shibboleth", after a story in the Bible about the Ephraimites who pronounced the Hebrew "sh" as "s" and so were identified by (and slain for) saying "sibboleth" rather than "shibboleth": > The Gileadites captured the fords of the Jordan leading to Ephraim, and whenever a survivor of Ephraim said, “Let me cross over,” the men of Gilead asked him, “Are you an Ephraimite?” If he replied, “No,” 6 they…

And challenge words in the Pacific were things like "lollipop", "lilliputian", and "lollapalooza"

This lives on today in the questionable origins of the brand name Lululemon:

> It was thought that a Japanese marketing firm would not try to create a North American sounding brand with the letter “L” because the sound does not exist in Japanese phonetics. By including an “L” in the name it was thought the Japanese consumer would find the name innately North American and authentic. Chip felt that the distributor had paid a premium for the “L” so he challenged himself to come up with a name that had 3 “L’s” for his new company.

https://www.facebook.com/notes/10158217650462732/ (an old blog post posted to Lululemon's brand page)

Re: GPT-3.5 crashes when it thinks about useRalativeImagePath too much

#120
I recently seemed to be causing ChatGPT on GPT-4 to crash/fail, when I challenged it with plotting pixels on an Amstrad CPC (while supporting a hardware-scrolled screen).

As it seemed to get more backed into a corner by complaints and corrections and unable to provide what I wanted, it seemed to get an increased number of broken responses (an error message partway through) or what appeared to be resets (like maybe there was a failure and they'd switched to another server, which adds a couple of line breaks mid-sentence or mid-codeblock).

After a while, I realised that maybe I didn't want to be causing their servers any problems and gave up on the (in any case) fruitless conversation. But it does seem like one can make GPT-4 effectively crash. Or, just as likely, I'm seeing signal in noise.

Post reply on HN