Re: Email Antispam
| From: | Jim Giner | Date: | Wed, 18 Apr 2012 01:11:45 +0000 |
| Subject: | Re: Email Antispam | ||
| References: | 1 2 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-317596@lists.php.net to get a copy of this message | ||
"Ross McKay" <rosko@zeta.org.au> wrote in message
news:b4vro79ftp9423k74bnj41o1o9e3dk9ebc@4ax.com...
> On Tue, 17 Apr 2012 16:04:19 -0400, David Mehler wrote:
>
>>I'm working on a site that has email addresses on it. I am not wanting
>>to use mailto links so as to avoid spam harvesters, I'd like another
>>solution so that mailto links would work but would not work with
>>spammers. I've tried several javascript-based solutions, but am not
>>able to get them to be consistent. It seems like once they're used
>>they revert to coded links. If anyone has any solutions I'd appreciate
>>it. I'm not sure I can do this in php, generate email addresses
>>dynamically then pass them to the client, it would be the same as the
>>spammer hitting the page. I'd prefer something self-hosted and
>>preferably light on the resources.
>
> I don't like this sort of thing, but I have a client who needs it. What
> I did for them was to put the email address on the page encoded with
> base64, and use client-side script to decode it. i.e. the encoded data
> is replaced with the decoded data, once on page load. Hook up the decode
> function on the browser-side to your page load scripts. No jQuery
> required :)
>
> https://gist.github.com/2409958
> --
> Ross McKay, Toronto NSW Australia
> "All we are saying
> Is give peas a chance" - SeedSavers
So - does that mean you building the site from information contained in a
database?