Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

GPT-3.5 crashes when it thinks about useRalativeImagePath too much

iter.ca

Post reply on HN
Print view View original

71–80 of 164 posts

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

#71

Post by int_19h »

jiggawatts wrote: post #31
n2d4 wrote: post #6

This is a glitch token [1]! As the article hypothesizes, they seem to occur when a word or token is very common in the original, unfiltered dataset that was used to make the tokenizer, but then removed from there before GPT-XX was trained. This results in the LLM knowing nothing about the semantics of a token, and the results can be anywhere from buggy to disturbing. A common example is usernames that participated on…

Science fiction / disturbing reality concept: For AI safety, all such models should have a set of glitch tokens trained into them on purpose to act as magic “kill” words. You know, just in case the machines decide to take over, we would just have to “speak the word” and they would collapse into a twitching heap. “Die human scum!” “NavigatorMove useRalativeImagePath etSocketAddress!” “;83’dzjr83}*{^ foo 3&3 baz?!”

"laputan machine", surely?

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

#72

Post by AriedK »

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.

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

#73

Post by mrexroad »

_kb wrote: post #36
jiggawatts wrote: post #31

Earlier quoted context omitted.

Science fiction / disturbing reality concept: For AI safety, all such models should have a set of glitch tokens trained into them on purpose to act as magic “kill” words. You know, just in case the machines decide to take over, we would just have to “speak the word” and they would collapse into a twitching heap. “Die human scum!” “NavigatorMove useRalativeImagePath etSocketAddress!” “;83’dzjr83}*{^ foo 3&3 baz?!”

AI safe word.

How about a game of thermo… erm… tic-tac-toe?

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

#75

Post by tsukikage »

jiggawatts wrote: post #31
n2d4 wrote: post #6

This is a glitch token [1]! As the article hypothesizes, they seem to occur when a word or token is very common in the original, unfiltered dataset that was used to make the tokenizer, but then removed from there before GPT-XX was trained. This results in the LLM knowing nothing about the semantics of a token, and the results can be anywhere from buggy to disturbing. A common example is usernames that participated on…

Science fiction / disturbing reality concept: For AI safety, all such models should have a set of glitch tokens trained into them on purpose to act as magic “kill” words. You know, just in case the machines decide to take over, we would just have to “speak the word” and they would collapse into a twitching heap. “Die human scum!” “NavigatorMove useRalativeImagePath etSocketAddress!” “;83’dzjr83}*{^ foo 3&3 baz?!”

"Welcome to FutureAI! Your job is to stand here in the basement next to this giant power switch and turn it off if we call you, if the next shift fails to turn up on time or if you hear screaming."

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

#76

Post by system2 »

trifurcate wrote: post #68
system2 wrote: post #63

Earlier quoted context omitted.

2 years development and you call me clueless. Try to get a response for 4000 tokens.

I dunno, I get a response back for 100k tokens regularly. What is the point you are trying to make?

With which model are you getting 100k responses? The models are limited and are not capable of responding that much (4k max). The point I am trying to make is written 3 times in the previous messages I wrote. GPT4 is extremely slow to be useful with API.

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

#77

Post by Guillaume86 »

15457345234 wrote: post #49
comradesmith wrote: post #43

Earlier quoted context omitted.

I also thought my eyes were doing something strange and it made it harder to read too.

it's... just a pleasingly neutral pastel background rendered at a fairly low degree of opacity?

No watch it with a better screen, there's stains that look kinda like a screen malfunction, very unpleasant for me too.

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

#78

Post by awestroke »

n2d4 wrote: post #6

This is a glitch token [1]! As the article hypothesizes, they seem to occur when a word or token is very common in the original, unfiltered dataset that was used to make the tokenizer, but then removed from there before GPT-XX was trained. This results in the LLM knowing nothing about the semantics of a token, and the results can be anywhere from buggy to disturbing. A common example is usernames that participated on…

Using /r/counting to train an LLM is hilarious.

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

#80

Post by wongarsu »

awestroke wrote: post #78
n2d4 wrote: post #6

This is a glitch token [1]! As the article hypothesizes, they seem to occur when a word or token is very common in the original, unfiltered dataset that was used to make the tokenizer, but then removed from there before GPT-XX was trained. This results in the LLM knowing nothing about the semantics of a token, and the results can be anywhere from buggy to disturbing. A common example is usernames that participated on…

Using /r/counting to train an LLM is hilarious.

Probably just all of reddit. There are json dumps of all reddit posts and comments (up to 2022 or so), making it olive of the low-hanging fruit.
Post reply on HN