Re: Email Antispam

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



"Ross McKay" <rosko@xxxxxxxxxxx> wrote in message 
news:b4vro79ftp9423k74bnj41o1o9e3dk9ebc@xxxxxxx...
> 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? 



-- 
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php



[Index of Archives]     [PHP Home]     [Apache Users]     [PHP on Windows]     [Kernel Newbies]     [PHP Install]     [PHP Classes]     [Pear]     [Postgresql]     [Postgresql PHP]     [PHP on Windows]     [PHP Database Programming]     [PHP SOAP]

  Powered by Linux