rlange - 1:33 pm on Aug 8, 2011 (gmt 0)

dstiles wrote: Where does it say in there that it's the prefetch only that is blacklisted? Does anyone have proof that I'm reading this wrongly?

Proof? No. Evidence? Yes. It's called context [dictionary.reference.com].

Edit: It would also be easy enough for you to test your claim in an attempt to prove yourself correct, which is how it's supposed to work. It's not up to anyone to prove you wrong; it's up to you to prove yourself correct.

Paranoid I may be, but I'm sure I'm not deranged. :)

You're making up additional reasons to hate this feature. That's on the wrong side of the deranged/not deranged scale.

Another question: who actually prefetches and caches the page - the searcher or google?

The browser, therefore the searcher.

If the searcher then google are in for some heavy criticism, especially of they prefetch for on-the-fly typing. I can see how very easy it would be to "accidentally" cache some undesirable - even trojan - pages.

It's reasonable to expect that malicious websites are subject to the same blocking/warning during prefetch as when viewed normally, so known malicious websites may not even be prefetched. As for unknown malicious websites, I suspect that various features of the browser—like file downloads—are not available to prefetched pages. That would be worth testing, though, just to be sure.

--
Ryan