<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>ProDevTips - Latest Comments in Email Obfuscation Broken</title><link>http://prodevtips.disqus.com/</link><description>Mainly tutorials and tips relating to web development with PHP, Javascript, jQuery and Ruby</description><atom:link href="https://prodevtips.disqus.com/email_obfuscation_broken/latest.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Sun, 14 Sep 2008 20:57:50 -0000</lastBuildDate><item><title>Re: Email Obfuscation Broken</title><link>http://www.prodevtips.com/2008/07/08/email-obfuscation-broken/#comment-2354358</link><description>&lt;p&gt;Image would also be reachable for OCR bots like anything else visible on the screen so in that way you won't be protected. Yet the regular HTML-scanning bots would be troubled. Even so, that would equal to using a JavaScript based encoding as a bot scanning the code, wouldn't render it. JavaScript is surely more convenient choice in the circumstances.&lt;/p&gt;&lt;p&gt;There's Mac OS X Dashboard widget called &lt;a href="http://obfuscatr.flashbit.net" rel="nofollow noopener" target="_blank" title="obfuscatr - email address obfuscator"&gt;obfuscatr&lt;/a&gt; that uses this kind of logic. See the details at &lt;a href="http://tekkie.flashbit.net/mac-os/obfuscatr-110-released" rel="nofollow noopener" target="_blank" title="obfuscatr 1.1.0 released"&gt;flash tekkie&lt;/a&gt;.&lt;/p&gt;&lt;p&gt;&lt;a href="http://obfuscatr.flashbit.net" rel="nofollow noopener" target="_blank" title="obfuscatr - email address obfuscator"&gt;obfuscatr&lt;/a&gt; was also &lt;a href="http://tekkie.flashbit.net/mac-os/obfuscatr-featured-in-macworld" rel="nofollow noopener" target="_blank" title="obfuscatr featured in Macworld"&gt;featured in MacWorld&lt;/a&gt; Italy of March 2008.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">tekkie</dc:creator><pubDate>Sun, 14 Sep 2008 20:57:50 -0000</pubDate></item></channel></rss>