Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Contributor redsand

    (@redsand)

    Hey Dan,

    The encoding is randomized. It will be different each time. There is no bug. The encoding works as it should. The only 100% way to prevent email harvesters is to use a contact form. The methods listed in the article you linked to are not actually more effective than the method used by this plugin. The method the plugin uses does reduce email harvesting. This is provided for users who still have email addresses in their site content.

    – Scott

    Thread Starter Dan Knauss

    (@dpknauss)

    That’s pretty interesting; thanks for explaining. So you randomly encode a certain proportion of the address/mailto string to throw off harvesting scripts? That’s a very good idea — where did you get it from? Has anyone tried testing its effectiveness over time, like the source in that article I linked to? If it has a high success rate, it sure beats using ROT13 and a hefty plugin like EEB.

    Plugin Contributor redsand

    (@redsand)

    Thanks. ?? We’ve done a lot of research and testing over the years. I don’t have numerical data for you though. Since we could add the feature without adding any bloat, it was a no brainer, to help users avoid having to use another plugin, or other bloated methods as you mentioned.

    Have a good one!

    – Scott

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘First three characters of email addresses and mailto links are not encoded’ is closed to new replies.