Just to mention. I have modified some core files to integrate this feature by default with one of the next WB versions. The update protects all emails displayed at the WB frontend without any additional coding. All embedded mails firstname.lastname@example.org or mailto:email@example.com will be protected that way. The protection works the same way like the one implemented in Typo3.
Christian, I HOPE you are making this optional?
There really should be an option to turn it off, at least in the site settings, if not in individual member profile configuration.
Hmm... nicest method might be to have an email obscuration module function - you could set it to NONE, JS, IMAGE, etc, as methods are implemented. Especially if there are member only areas, you really don't need that feature.
For example, on my Palm Blazer, JS doesn't always work with logins - I can't log into my router for example, which I'd really like to be able to do from my Palm, and the Admin back-end of WB isn't much fun with it either.
And I've seen claims that at least some of the harvesters can read JS. I had done several things to some of my addresses and went to a testing site - it read it all easily. I gave up.
What I'd like to do is be able to use a form instead. I.e. use a drop-down or a radio-button to pick who you want to email, and send any comment to the selected person. Now of course, only one email is possible.