Live data from Hacker News

I prompted ChatGPT, Claude, Perplexity, and Gemini and watched my Nginx logs

surfacedby.com

11–20 of 28 posts

Re: I prompted ChatGPT, Claude, Perplexity, and Gemini and watched my Nginx logs

#11
post #4

I’m curious about the header of their requests. Something like any one of them is using text/markdown accept header?

Added $http_accept and re-ran. None of them use text/markdown. Results:

ChatGPT-User/1.0 text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,/;q=0.8,application/signed-exchange;v=b3;q=0.9 Claude-User/1.0 / Perplexity-User/1.0 (empty, no Accept header) PerplexityBot/1.0 (empty, no Accept header) ChatGPT sends a Chrome-style Accept string. Claude sends a wildcard. Perplexity sends nothing at all. Gemini didn't fetch in my test.

Also worth noting: Claude-User hit /robots.txt before the page.

Re: I prompted ChatGPT, Claude, Perplexity, and Gemini and watched my Nginx logs

#12
post #8

Gah, the writing on this is so painful to read, it feels like this was most likely written by an LLM. The writing style is so unclear, it's hard to figure out one of the key points: it mentions that Gemini doesn't use a distinct user-agent for its grounding. It doesn't mention whether it actually hit the endpoint during the test, though it kind of implies that with "Silence from Google is not evidence of no fetch." U…

I had to quit after a couple of paragraphs, I cant read such AI slop anymore :(

Re: I prompted ChatGPT, Claude, Perplexity, and Gemini and watched my Nginx logs

#13
post #10

Does smack of AI ness The IPs listed in the output are from reserved ranges as well, like they were intentionally obfuscated (but this was not shared with the reader). It’s the kind of obfuscation that AI would do (using esoteric bogon ranges as well) https://ipinfo.io/ips/203.0.113.0/24

[dead]

Re: I prompted ChatGPT, Claude, Perplexity, and Gemini and watched my Nginx logs

#14
post #8

Gah, the writing on this is so painful to read, it feels like this was most likely written by an LLM. The writing style is so unclear, it's hard to figure out one of the key points: it mentions that Gemini doesn't use a distinct user-agent for its grounding. It doesn't mention whether it actually hit the endpoint during the test, though it kind of implies that with "Silence from Google is not evidence of no fetch." U…

I did use AI to organize my ideas but I didn't think it was that bad, I'll modify and make it easier to read.

Anyway, in my test I saw zero requests from any Google UA after multiple Gemini and AI mode prompts that should have triggered grounding, so the working interpretation is that Gemini served from its own index/cache rather than doing a live provider-side fetch. The original phrasing was fuzzier than it should have been.

Re: I prompted ChatGPT, Claude, Perplexity, and Gemini and watched my Nginx logs

#15
post #8

Gah, the writing on this is so painful to read, it feels like this was most likely written by an LLM. The writing style is so unclear, it's hard to figure out one of the key points: it mentions that Gemini doesn't use a distinct user-agent for its grounding. It doesn't mention whether it actually hit the endpoint during the test, though it kind of implies that with "Silence from Google is not evidence of no fetch." U…

I did use AI to organize my ideas but I didn't think it was that bad, I'll modify and make it easier to read. Anyway, in my test I saw zero requests from any Google UA after multiple Gemini and AI mode prompts that should have triggered grounding, so the working interpretation is that Gemini served from its own index/cache rather than doing a live provider-side fetch. The original phrasing was fuzzier than it should…

Sometimes when we point the moon to people they prefer to discuss at length about the finger.

Don't worry.

Re: I prompted ChatGPT, Claude, Perplexity, and Gemini and watched my Nginx logs

#16
post #15

Earlier quoted context omitted.

I did use AI to organize my ideas but I didn't think it was that bad, I'll modify and make it easier to read. Anyway, in my test I saw zero requests from any Google UA after multiple Gemini and AI mode prompts that should have triggered grounding, so the working interpretation is that Gemini served from its own index/cache rather than doing a live provider-side fetch. The original phrasing was fuzzier than it should…

Sometimes when we point the moon to people they prefer to discuss at length about the finger. Don't worry.

If you point six index fingers and a bifurcated thumb at the moon, then many people will worry.

Re: I prompted ChatGPT, Claude, Perplexity, and Gemini and watched my Nginx logs

#17
post #7

So the state of AI in 2026: ChatGPT DDoS-lite, Claude the polite one that actually reads the rules, Perplexity maybe shows up, and Google was already in your house.

Claude reading the rules is perhaps the strongest argument for Anthropic being "good so far" I've ever seen.

Re: I prompted ChatGPT, Claude, Perplexity, and Gemini and watched my Nginx logs

#18
post #8

Gah, the writing on this is so painful to read, it feels like this was most likely written by an LLM. The writing style is so unclear, it's hard to figure out one of the key points: it mentions that Gemini doesn't use a distinct user-agent for its grounding. It doesn't mention whether it actually hit the endpoint during the test, though it kind of implies that with "Silence from Google is not evidence of no fetch." U…

I did use AI to organize my ideas but I didn't think it was that bad, I'll modify and make it easier to read. Anyway, in my test I saw zero requests from any Google UA after multiple Gemini and AI mode prompts that should have triggered grounding, so the working interpretation is that Gemini served from its own index/cache rather than doing a live provider-side fetch. The original phrasing was fuzzier than it should…

[deleted]

Re: I prompted ChatGPT, Claude, Perplexity, and Gemini and watched my Nginx logs

#19
Interesting methodology. I've been running Claude Sonnet in production content workflows for 6 months and the pattern I notice most is that every model hits URLs in the prompt at slightly different priorities.. Claude tends to fetch top-of-message URLs first, while GPT often fetches the last one mentioned. Has anyone else seen ordering bias in which URLs get requested when multiple are in the same prompt? Would make a nice follow-up experiment if your logs have that granularity.
Post reply on HN