Mobile version of this pageBugknits
Next:
What will you not wear today?
Related blogs
Practical CSS10 reasons for web standards
Why should I use XHTML?
Recon - Regular Expression Test Console
Intel.com incompatible to Mozilla
The importance of checking in Firefox
Regular Expressions in Javascript cheat sheet
\b in Python regular expressions
\B in Python regular expressions
Python regular expression tester
Are you a web developer? Then VisiBone is for you
Quick PostgreSQL optimization story
Related by category
Anti-spamming email harvesting
http://www.stunicholls.myby.co.uk/menu/email.htmlharvesting, stylesheets, backwards, unicode-bidi, bidi-override, browsers, hex, anti-harvesting, spammers, regular expressions, regular expression
26th of February 2004
Stu's Site has a nice example of a way of preventing email harvesting by writing the email in reverse and then letting stylesheets reverse it when rendering. The HTML source looks like this:
.backwards {unicode-bidi:bidi-override; direction: rtl;}
</style>
<span class="backwards">ku.oc.u7s@uts</span>
And the result is: stu@s7u.co.uk. It works on in my web browsers (win, linux), but the nasty effect is that if you select the text, copy and paste; when you paste it pastes it as ku.oc.u7s@uts. Pretty annoying.
My site uses hex encoding so the HTML looks like this:
<noscript>Peter, mail(at)peterbe dot com</noscript>
The result is as if no anti-harvesting effect had been applied.
Sadly I bet that spammers have tricks to get around both but what matters is how few spammers have yet to come up with the solution. I'm thinking of keeping my method and adding something that scrambles up the encoded string to break spammers regular expressions. But the effect mustn't be as bad as the example on Stu's site.







Save this page in del.icio.us