> Yeah, TBH my BS detector is going off because this article never explains how he is able to intercept these calls. You mean, except for explaining what he's doing 4-5 times? He was literally repeating himself restating it. Half the article is about the various indicators he used. THERE'S EXAMPLES OF THEM. There's this bit: > Monitored their network traffic for 60-second sessions > Decompiled and analyzed their JavaScript bundles Also there's this whole explanation: > The giveaways when I monitored outbound traffic: > Requests to api.openai.com every time a user interacted with their "AI" > Request headers containing OpenAI-Organization identifiers > Response times matching OpenAI’s API latency patterns (150–400ms for most queries) > Token usage patterns identical to GPT-4’s pricing tiers > Characteristic exponential backoff on rate limits (OpenAI’s signature pattern) Also there's these bits: > The Methodology (Free on GitHub next week): > - The complete scraping infrastructure > - API fingerprinting techniques > - Response time patterns for every major AI AP One time he even repeats himself by stating what he's doing as playwright pseudocode, in case plain English isn't enough. This was also really funny: > One company’s “revolutionary natural language understanding engine” was literally this: [clientside code with prompt + direct openai API call]. And there's also this bit at the end of the article: > The truth is just an F12 away. There's more because LITERALLY HALF THE ARTICLE IS HIM DOING THE THING YOU COMPLAIN HE DIDN'T DO. In case it's still not clear, he was capturing local traffic while automating with playwright as well as analyzing clientside JS.
 Top