5 ms·
Yeah google has been following my javascript obfuscated links for quite some time now. It's actually a tad annoying because there's no way to do a "nofollow" i
by ck2 16y ago
Yeah google has been following my javascript obfuscated links for quite some time now.
It's actually a tad annoying because there's no way to do a "nofollow" in javascript.
- pkulak 16y agoThat's not what nofollow is for anyway. Just update your robots.txt file.
- ck2 16y agoPutting it in robots.txt is like advertising to bad bots exactly where to go. On some sites what I do is make a fake virtual directory and just ban the directory in robots.txt while prefixing the links with the fake directory path. Oh and I swear google sometimes follows stuff in robots.txt, it just doesn't index it. Then there's the "alternate" user agents they use like pretending to be IE (from a real Google IP).
- jrockway 16y agoThe solution is to password-protect the parts of your site that you don't want bots to see. Javascript obfuscation is silly. Robots.txt is advisory. Passwords are simple and failsafe.
- tomjen3 16y agoPutting it in robots.txt is like advertising to bad bots exactly where to go. Exactly. Right to your special page that earns a 24 hour ip ban. It doesn't take that long to code and should keep any bot away.
- pkulak 16y agoWho said anything about using robot.txt for security? I just use it for keeping Google from indexing my print pages, for example. Anything that I don't want the world to see, can't be seen without authorization.
- Niten 16y agoI just hope they don't start caching and displaying obfuscated links, since JavaScript obfuscation is how I currently manage to display a working mailto: link on my personal web page while simultaneously giving myself nominal protection from address harvesters. Is this no longer a viable strategy for protecting one's email address on the web?
- JoachimSchipper 16y agoTo the extent that it ever worked, it still works - Google doesn't index mailto: links.
- mootothemax 16y agoDo you know that for a fact? Just because something's not publically available doesn't mean it's not in the back-end.
- JoachimSchipper 16y agoI don't know whether or not they are in Google's data center somewhere; but to the best of my knowledge, they cannot be extracted from that data center, which means it's largely irrelevant as far as spam is concerned.
- acdha 16y agoThis was never more than a minor delaying tactic: spammers have been capable of running JS for a long time (harvesters embedding IE via ActiveX have been around for at least a decade) but there hasn't been much pressure to do this since they still got billions of addresses which weren't obfuscated or were obtained by other means. I'll also note that I've never obfuscated my email address (chris@improbable.org) and spam arrived in roughly equal volumes there and to less public addresses which were guessable (except for test accounts created with MD5 hashes[1]). People do harvest addresses from web pages but there are enough other ways spammers get addresses that you need a robust filter in any case; once you have something like SpamAssassin or Google's filters, the value of keeping your address private disappears. [1] That also yielded the interesting datapoint that hotmail used to sell addresses to spammers in early last decade as the first spam arrived within 20 minutes to a long, random address created with the "don't publish my info" option.