Forum Moderators: open

Message Too Old, No Replies

Hiding Email Addresses from Harvesters

Revisted

         

ukgimp

11:43 am on Jun 19, 2003 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



I found a thread this morning that fitted but now I am unable to find it again? I was thinking about obfuscation of my email address and came across this thread which is also related (cant post to it, is out of date)

[webmasterworld.com...]

Would the following be a good approach for hiding my email address. The reason for for the noscript is to cater for the users who do not have JS enabled.

<script>
<!--
var username = "ukgimp";
var hostname = "gimpworld.com";
var linktext = username + "@" + hostname;
document.write("<a href=" + "mail" + "to:" + username +
"@" + hostname + ">" + linktext + "</a>")
//-->
</script>
<noscript><A HREF="unicoded email">unicoded email</A></noscript>

or even Unicode the whole lot?

Are there any other serious options. I have seen the list of UA to ban but not all sites have that option open to them or worry about the loss in performance in having a monster htaccess ban list.

Would it be possible to only display an email address of the request is made from a non UA or have a smaller list of agents (googlebot etc) where they get the proper ones and the others get noting or a moody address.

Perhaps rotated ( I remember that being mentioned here, 1/20 a moody one).

Just trying to think of all the possible solutions so that I can use them when the different situations arise.

Cheers

limbo

12:32 pm on Jun 19, 2003 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



UKGimp

I robbed this piece of advice from someone here a while ago. So not my honours but - Have a look here [hiveware.com]

Ta

ShawnR

12:43 pm on Jun 19, 2003 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Hi

As you have discovered, there are lots of ways, such as scrapping an email address in favour of forms; using an image which is created in a way to prevent OCR; and the encoding methods you have suggested. With these javascript encoding methods there is also a range of options, from simply building the string to unicoding to encryption, with a decrypt function provided in your javascript code. It all depends on how much protection you want. Currently I think it is safe to say that there are no (or hardly any) harvesting programs which do more than read html (but I am not an expert), so for now the javascript solution will do fine... But the spam bots are bound to improve...

A few suggestions:

1. put your script in an external file, and call a function
2. unicode some of it, especially the mailto and the @ symbol (e.g. var at_symbol = ...; )
3. For the noscript version, think about unicoding something like: "name at domain dot com (NOTE: change at and dot to the appropriate characters)" instead of unicoding "name@domain.com"

g1smd

9:27 pm on Jun 19, 2003 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



[webmasterworld.com...]
[webmasterworld.com...]
[webmasterworld.com...]
[webmasterworld.com...]

There were some other threads just a week or so back, but I can't seem to find them now.

.

Forum search enhancement suggestion: "Find all posts from this user:________"