We already employ our own obfuscation where e-mail addresses are encoded using HTML entities (please let me know if this is broken). You don't see it unless you go into the source of the page; it appears normal when rendering the actual page. But bots will have a harder time trying to figure it out.
If a harvester can figure out the entities, they will likely figure out the CAPTCHA as well (because it's probably a human paid to be a spammer), so it will not be a very fruitful solution.
Perhaps this is worthy of a different, more privacy-oriented approach. Maybe we need a setting that allows members to control whether they want their e-mail address to be seen? If set to no, any instance of their e-mail address site-wide will be redacted.
We already employ our own obfuscation where e-mail addresses are encoded using HTML entities (please let me know if this is broken). You don't see it unless you go into the source of the page; it appears normal when rendering the actual page. But bots will have a harder time trying to figure it out.
If a harvester can figure out the entities, they will likely figure out the CAPTCHA as well (because it's probably a human paid to be a spammer), so it will not be a very fruitful solution.
Perhaps this is worthy of a different, more privacy-oriented approach. Maybe we need a setting that allows members to control whether they want their e-mail address to be seen? If set to no, any instance of their e-mail address site-wide will be redacted.