logoalt Hacker News

zahlman • yesterday at 6:58 PM • 4 replies • view on HN

Something about the writing style here makes it hard for me to follow what actually happened. The section about JSONP for example seems to be explaining how JSONP works and how it's designed as an attempt to work around these attacks, but that explanation is then passed off as an explanation of how they bypassed the protection. And the whole premise seems to be about how manipulating the Preview content let them work through multiple defensive layers, but I don't see an explanation of how they directly controlled that content in the first place. I would have thought that the only control you have over the content of "an ordinary public ChatGPT share" is the prompt text, and that any migration of that text into "a small working webpage using its Preview feature" is up to the model deciding to generate that "HTML block" in response.


Replies

0c3ca83 • yesterday at 8:43 PM

They're writing for bots, not humans. This is a marketing piece. They're trying to get themselves to come up as the answer when people ask chatbots questions.

You're not the target audience of writing on the Internet anymore.

cowlevel • yesterday at 8:13 PM

It's AI written so of course it's hard to follow.

➕ show 1 reply
krackers • today at 12:04 AM

It's surprising that using JSONP in this way is even allowed. At one point google explicitly made sure to prevent this flavor of attack

https://stackoverflow.com/questions/2669690/why-does-google-...

kenmacd • today at 2:30 AM

hnslop (using salahadawi, using Pangram) puts this at 100% AI written, so that's probably why.

Report: https://www.salahadawi.com/hacker-news-ai-detector/50314699

hnslop: https://hnslop.nilsherzig.com/

➕ show 1 reply