tangor - 12:53 am on Jun 18, 2011 (gmt 0)

Throwing this into the mix... if Google has to say anything about it, then we might wish to be afraid...

Google has downplayed concerns that refinements to its search technology could leave surfers more exposed to search engine manipulation attacks. Google Inside Search aims to speed up web searches by pre-loading content from remote sites. The so-called Instant Pages technology only works with Google Chrome.

[theregister.co.uk...]

Then we have this... does this suggest that Google will be adding yet more code for webmasters to wrestle to prevent these new "improvements"? (As if the average Joe or Sue Webmaster will do that... or even know what an API is for...)

Velocity Google has urged website developers to use Chrome's experimental Page Visibility API to reduce their sites' activities when they're not actually being viewed by browser users. Now included with the developer version of Chrome – and due for arrival in the beta version next week – the PageVisability API allows websites to determine when they're actually being viewed by users – and when they're just sitting in the background. The API can tell you when a site is sitting inside a background tab, but also when a site has been pre-rendered by Chrome's new Instant Pages tool.

[theregister.co.uk...]

What I am reading from other sources it that Instant Pages only works with Chrome... and if that's the case, if one is really worried... it wouldn't take much to .htaccess Chrome ... if one is that concerned.

I'm not thrilled that G is continuing to futz with page code and server configs by bringing out all these "newfangled" things. At some point, if it ain't broke, don't break it!