Hi,
is a different solution but have you ever tried CloudFlare (cloudflare.com)
service?
It is a kind of proxy-cache online.
I use it with my site that has very very low traffic :-) but open comments
and spammers have disappeared.
{the site is made with Plone but I have to upgrade to web2py a
>> I think that honeypot + timestamp + js execution are transparent to the
end user and keep the vast majority of bots out.
Yes that sounds very good.
Re: Honeypot. As already mentioned, a display:none input box on its own
does not seem to defeat spammers these days. However, there could be
@mcm: apart from explaining a user how to set his browser to provide client
auth with ssl, I don't think that pyhonaywhere lets you use client-side ssl
auth.
@joe: talking about "annoy", a 24 hour stop would surely make me angry. The
problem here is stop bots, with this you have to manually unr
As an alternative method there is a very robust solution: client auth using
a x509 client certificate. As a user installing the certificate is simpler
than answering questions or reading weird captchas and he can forget about
it, the browser does all the auth by itself using the SSL/TLS protocol,
At least one site i use regularly implemented a 24-hour posting delay.
Sign up today and your posting ability starts tomorrow. It was a little
annoying to newbies but it really zeroed the spam!
-- Joe
On Saturday, June 15, 2013 12:40:50 PM UTC+8, rochacbruno wrote:
>
> Hi,
>
> recently we are
Personally I don't like captcha image, before delving into the
implementation of whatever like that it is worth to try the honeypot
mechanism namely a 'hidden field'. A field that if filled out allow you to
distinguish between user and robots requests. The field it is hidden by css
properties r
6 matches
Mail list logo
