[Plugin] Email Link Obfuscator

AMAZING snippit my only thing would be with any sort of bot would not have Javascript enabled and so your comment about spambot proofness is good in the fact it would only obscure it against your end user... shame really i really like the idea...

This plugin is very good!

..and it would be great if someone adds the functionality asked 2 posts up here.

Thanks for sharing.

regards,

zi

Quote from: dernier_recours at Mar 19, 2006, 11:40 AM

The plugin does not allow rendering of special characters. For example, <a href="mailto:[email protected]">événement</a> will be shown as a link &eacute;v&eacute;nement.

Great catch. I’ve fixed the plug-in to handle special characters correctly.

The code in the original post has been fixed. Either replace code with fixed code, or simply add this line:

$str=html_entity_decode($str);

as the first line in the replaceEntities function. That’s the only change necessary.

Thanks!

This may be a stupid question, but that’s never stopped me before: what happens if the visitor has JS disabled?

Quote from: Colin at Apr 11, 2006, 07:54 PM

This may be a stupid question, but that’s never stopped me before: what happens if the visitor has JS disabled?

It will display "name at address dot com"

At least, I’m pretty sure that’s what it does.

Hmmm.

I know that you made a point of no guarantees about this method, but I would imagine that "name at address dot com" is exactly what the spambots would see, and many must now be capable of harvesting such obfuscated addresses.

I am certain that this is still of value, but its value must be diminishing. Also, some when presented with such an obfuscated address, will not interpret it properly.

I use an image, but that has its own problems, as typos can develop when copying the address. Personally, I’ll be switching to a form method instead.

However, I might use this with members’ blog section I’m developing, as it will definitely help.

Thanks.

Quote from: Colin at Apr 12, 2006, 11:07 AM

Hmmm.

I know that you made a point of no guarantees about this method, but I would imagine that "name at address dot com" is exactly what the spambots would see, and many must now be capable of harvesting such obfuscated addresses.

I am certain that this is still of value, but its value must be diminishing.

True, though it’s easy to modify the plug-in to show something different in the <noscript> version if you want to be hardier against spambots.

Sorry, I was modifying my last pot when you replied. You are certainly quick off the mark!

OK, that sounds even better. I’ll definately look at this.

Again, thanks.

This is an excellent plug-in. I think that JavaScript cloaking does still frustrate a lot of spam harvesters, and it’s too easy not to do. I still hide my main email addresses in forms that don’t show the recipient, but this works great for parsing all the random ones that end up on any site (especially one with user comments).

The document does not validate (XHTML 1.0 Transitional) because of the noscript tag.

document type does not allow element "noscript" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag

Which of the "missing" tags is best to use? I want my page to validate, but also I want it to cloak the adresses.

(I could remove the noscript tag completely though)