Reactive prefetch on Google Search: 100-150ms speedup

Re:Reactive prefetch on Google Search: 100-150ms speedup by nly on Tuesday December 09, 2014 @06:28PM (#8726565)

> Given two solutions with equal potential for abuse, why not pick the technically superior solution?

Straw man. You're presupposing the existence of 'ping'. The argument is why, given an observation that web features X and Y are being used to implement contentious function Z, would you want to implement a brand new, even more insidious, web feature, designed solely for doing Z, in the first place? Technical superiority of the new implementation of Z is not in dispute.

> they already know which you click on.

I'm pretty confident that they don't in my case.

[ Parent | on HN ]

Re:Reactive prefetch on Google Search: 100-150ms speedup by phpnode on Tuesday December 09, 2014 @06:33PM (#8726587)

> I'm pretty confident that they don't in my case.

Would you mind sharing the details of how you achieve this?

[ Parent | on HN ]

Re:Reactive prefetch on Google Search: 100-150ms speedup by nly on Tuesday December 09, 2014 @06:54PM (#8726670)

Monitor the HTTP activity with FF developer tools while using Google. It's plain to see that no new traffic flows to Google occurs when I click a link.

[ Parent | on HN ]

Re:Reactive prefetch on Google Search: 100-150ms speedup by dchichkov on Tuesday December 09, 2014 @07:47PM (#8726924)

AFAIK they track links only for a subset of users and not every time.

[ Parent | on HN ]