Ticket #49 (closed enhancement: invalid)
Filter Spam in Changes to CKAN Data
Reported by: | rgrp | Owned by: | rgrp |
---|---|---|---|
Priority: | minor | Milestone: | |
Component: | ckan | Keywords: | |
Cc: | Repository: | ||
Theme: |
Description
As A
sysadmin
I Want To
Have revisions to the CKAN data filtered in order to reduce the spam in the system.
Details
In the long run this is a quite a generic problem common across several OKF systems and probably can become a general component in the okfmisc repo. For time being focus on a well-factored CKAN-specific solution.
Suggest we follow path of trac: http://trac.edgewall.org/wiki/SpamFilter
Could have a general engine that aggregates spam scores from many different 'plugins' and then marks spam appropriately (actions should be configurable depending on spam level from 'purge' to 'delete' (mark revision as inactive) to 'flag' to 'do nothing').
Main initial plugins would be:
- regex filter (this would seem very useful here, e.g. do not allow urls in commit messages ...)
- could augment using the badcontent list approach (can find list on e.g. moinmoin)
- spambayes and/or akismet
Has become less of a problem since big efforts a few months ago so this can be downgraded for time being.