Now you're thinking... imagine delivering a modified CSS file & javascript only to a website based on an IP address - you'd have something that
behaved differently based on surfer rather that delivering
different content which is still cloaking, but it's not. The hunters are not looking for things like this yet, and making this difficult to ID is not that hard.
Think about the Google cache for a moment... if you reference JS and CSS pages from
your server rather than on page, then they will not be cached with the page, the reference to them will. And when a surfer looking at a cached page in google requests your CSS and JS, it's IP will tell you that it is a surfer not google and...
... no more cache busting man. Give it a think, it's pretty cool. I laugh at the boneheads who say that an IP cloak is easy to defeat...
