> Kornel Lesinski > You can encode mail with URLencode and then with decimal and > hexadecimal > HTML entities, example implementation: > http://wiki.pornel.ldreams.net/encje
The problem with this type of method: once a method gets popular (because it temporarily works), bot writers are more than likely to simply update their bots (which should be fairly trivial in this case). > Other method is to create bot-trap (hidden link) that catches > and bans bots not respecting robots.txt and then giving > e-mail addresses only on pages blocked in robots.txt. But then be careful that users of assistive technology don't stumble onto the trap by mistake. > Yet another method is to write email links like: > <a href="/mail/user/domain"> and then postprocessing links with JS > to transform them into mailto:[EMAIL PROTECTED] > For compatibility with non-JS browsers you can have /mail/ page that > generates mail form or uses some other unharvestable form of > displaying > address. Cute...particularly like the fallback mechanism. Again, though: once this catches on, bot writers will simply change their algorhythms. Patrick ________________________________ Patrick H. Lauke Webmaster / University of Salford http://www.salford.ac.uk ****************************************************** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help ******************************************************
