post-page

WordPress Cookie Spambot stopper

2
responses
by
 
on
December 3rd, 2004
in
LinkyLoo, WordPress Hack

nicholasjon.com : WordPress Cookie Spambot stopper
or forcing clients to do some sort of javascript calculation. Interesting comment on that page. I have been thinking about a javascript authenticator for some time.

Related Posts:

 




heading
heading

Related Posts:

heading
2
Responses
Comments Feed

 

Comments

  1. Nick says:
    12/3/2004 at 4:28 pm

    The javascript “authenticator” is a great idea. I’ve implemented a rudimentary version over at my site — though I haven’t updated the walkthrough I posted early that you’ve linked to. If you view source on a page with a comment form on it you can see what I’ve done.

    Personally, I’m a little nervous about the idea of forcing users to have JS turned on to leave a comment. Forcing them to have cookies enabled is probably a big enough hurdle. Though it occurs to me there might be a way to allow non-JS browsers to post comments to the “moderating” queue instead of to the site itself… at any rate, check out the update if you’re interested.

  2. Elliott Back says:
    12/21/2004 at 4:19 am

    I’ve implemented this as a wordpress plugin, a few weeks earlier. Without the database muckery, this wp spam plugin computes an md5 using injected client side values, and the values on the server. No cookies, no sql, just a little bit of javascript and html.

    So far 0 spam got through!!



Obviously Powered by WordPress. © 2003-2013

css.php