You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now it is hard to do detective work with Mollom. Sometimes you might encounter a bunch of spam and it is not clear how this got through. Implement logging, such that;
When a comment is submitted, the piece of information is stored about how it was allowed to enter the website. For instance, the value might be:
a) Mollom CAPTCHA was presented and entered correctly b) Mollom beyesian filter detected this as being ham, and no CAPTCHA was shown c) No antispam system shown; comment let through without checking d) Comment was held for moderation and approved manually
Where extra information can be stored, such as a "score" of how spammy the content is, also keep this. I am not sure whether the Mollom API will provide this to us.
This information should be stored in the database and available to see when you use the CMS and open the pop up to view a comment.
Secondly, if it doesn't already, also store the IP address of the commenter, and make this easily accessible to investigate.
This information will allow us to recieve spam and have information on how to reduce it in the future -- for instance, we can create logic within SilverStripe?, or pass informed feedback to the authors of Mollom
The text was updated successfully, but these errors were encountered:
From http://open.silverstripe.org/ticket/4551
Right now it is hard to do detective work with Mollom. Sometimes you might encounter a bunch of spam and it is not clear how this got through. Implement logging, such that;
When a comment is submitted, the piece of information is stored about how it was allowed to enter the website. For instance, the value might be:
a) Mollom CAPTCHA was presented and entered correctly b) Mollom beyesian filter detected this as being ham, and no CAPTCHA was shown c) No antispam system shown; comment let through without checking d) Comment was held for moderation and approved manually
Where extra information can be stored, such as a "score" of how spammy the content is, also keep this. I am not sure whether the Mollom API will provide this to us.
This information should be stored in the database and available to see when you use the CMS and open the pop up to view a comment.
Secondly, if it doesn't already, also store the IP address of the commenter, and make this easily accessible to investigate.
This information will allow us to recieve spam and have information on how to reduce it in the future -- for instance, we can create logic within SilverStripe?, or pass informed feedback to the authors of Mollom
The text was updated successfully, but these errors were encountered: