[MGNLCMNT-27] Akismet spam filtering Created: 06/Oct/10  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: Commenting (closed)
Component/s: None
Affects Version/s: None
Fix Version/s: Ideas

Type: New Feature Priority: Major
Reporter: Magnolia International Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File MGNLCMNT-27-akismet.patch     Text File PageCommentsWithAkismet.java    
Issue Links:
Relates
relates to MGNLFORM-210 Pluggable Spam detection mechanism fo... Closed
dependency
is depended upon by MGNLCMNT-20 Make the commenting module site aware. Closed
Template:
Patch included:
Yes
Acceptance criteria:
Empty
Date of First Response:

 Description   

Here's a contribution from the folks at VPRO which enables spam filtering on the commenting module, via the Akismet service.

If I get the chance, I'll make a patch file out of this for readability, but it should be noted that:

  • Forum 2.0 also provides a similar feature - but the current commenting module still depends on 1.x of course.
  • Magnolia 4.4 will introduce the possibility to pre-execute models, which is where this functionality should be plugged in.


 Comments   
Comment by Magnolia International [ 06/Oct/10 ]

Ok, so here's a patch file; unfortunately, it contains a couple of other changes, which I suspect are related to MGNLCMNT-20.
The crux of the issue here is implemented in isSpam(), by using net.sf.akismet.Akismet (http://akismet-java.sourceforge.net/, not found on central maven repo?)

I'd argue that setValidated() is wrong, here. The forum module originally introduced 3 states:

  • not validated (i.e no action was taken)
  • valid (reviewed and accepted by moderator)
  • invalid (reviewed and rejected by moderator)

This patch does not store spam messages. It should probably be optional, but we should probably:

  1. store spam messages
  2. with a new/specific status

Hopefully, this can be resolved when moving towards forum module 2.0; if this can't wait, this patch can probably be applied with little modifications (i.e remove dep to VproModule, move akismet config to self, ...)

Comment by Zdenek Skodik [ 06/Oct/10 ]

what I can say here is a note to MGNLCMNT-20 - the attached patch is incomplete and needs to be rewritten/improved unfortunately I had no time to do a progress so far, but once my hands get free, I'll continue with it in the way that the ticket would be resolved till the end of this week hopefully, definitely till next maintenance release.

Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Generated at Mon Feb 12 00:02:27 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.