4 ms·
But it's not what happened here. It WAS retrieving on request. > I went into Perplexity and asked "What's on this page rknight.me/PerplexityBot?". Immediately
by alexey-salmin 2y ago
But it's not what happened here. It WAS retrieving on request.
> I went into Perplexity and asked "What's on this page rknight.me/PerplexityBot?". Immediately I could see the log and just like Lewis, the user agent didn't include their custom user agent
- JumpCrisscross 2y agoThat was to test the user-agent hiding. The broader problem—Perplexity laundering attribution—is where the scraping vs retrieval question comes into play.
- Dylan16807 2y agoWell the example in the post doesn't show any laundering. Do you have an example of it? Unless you mean the entire concept of training launders attribution, but that's basically unrelated to this post and the complaints inside it.
- threecheese 2y agoIn this case you are 100% correct, but I think it’s reasonable to assume that the “read me this web page” use case constitutes a small minority of perplexity’s fetches. I find it useful because of the attribution - more so its references - which I almost always navigate to because its summaries are frequently crap.