Jump to:
| Project: | Mollom |
| Version: | 6.x-2.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
Problem/Motivation
Long-time Drupal users who attempt to post on groups.drupal.org frequently get frustrated when their posts are incorrectly blocked as spam. The only practical solution is to grant such users the "bypass mollom" privilege if and when they complain loudly enough. Users who do not complain, or who simply stop using groups.drupal.org (and other mollom-protected sites), are invisibly part of the overall problem.
Proposed resolution
Trusted users should be automatically granted the "bypass mollom" privilege. But who is trusted? Some possible criteria:
- Users who have been in good standing (i.e. not reported as being a spammer) for X amount of time.
- Users who have successfully posted X number of non-spam nodes or comments.
Remaining tasks
Add controls to the Mollom module settings page that allow site administrators to instruct Mollom how to decide who should be "trusted".
User interface changes
Users who meet the "trusted" criteria need never see the hated CAPTCHA or "Your post has been blocked as spam" message again.
API changes
Original discussion in #1286660: Replace mollom with a different preventive spam blocking tool
- #9 by pillarsdotnet
- How about granting "bypass mollom" to any account that has successfully posted (x) number of non-spam comments already?
- #10 by greggles
- @pillarsdotnet, we had a similar system but it seems it got broken somewhere along the way.
I've now made it a drush command that I can run on g.d.o periodically which will hopefully be more resilient. - #11 by rfay
- I'd be interested in the drush command being in a repo... Seems like a valuable feature. Actually... it should probably be in mollom.
Comments
#1
+1 of course.
#2
+1000 ....and then another million.
> Long-time Drupal users who attempt to post on groups.drupal.org frequently get frustrated when their posts are incorrectly blocked as spam.
Please squash this hideous bug by implementing this or something else!
**Changing to appropriate project and reworking title to reflect important points from other issue:
> Is there a reason that mollom can't be better about cooperating with other spam solutions? It seems very wrong that it seems to have an all mollom or no mollom approach.
>On randyfay.com I replaced all the other spam checking mechanisms with Captcha Riddler + Captcha. I configured two questions "Who is the leader of the Drupal project" and "What is the most popular contributed module". Spam has gone from several a day with recaptcha (mostly Polish poker sites?) to "I can't remember the last one".
#3
Sounds useful but I don't see any reasoning for bumping this to critical.
Also, as long as we're using mollom, "bypass mollom" is the permission.
And since the point of the OP was to build the drush command in mollom, moving it back to the mollom issue queue.
#4
> Re: critical bump
Changed version # to reflect version that requires the change.
#5
I don't see how this matches the definitions of priorities - http://drupal.org/node/45111
g.d.o already has this, so nothing to do there.
#6
Okay, if I understand correctly this is not a critical priority (which I agree with) but this feature request does sound like a must have which makes total sense. The idea I have in mind is that even logged in users can't be trusted until we can determine for sure they're not spammers. I'd vote for an admin-defined number of non-spam comments (1? 3? 5?) before a user can be trusted.
Relying on a CAPTCHA for the registration form isn't something reliable if the CAPTCHA doesn't work for any reason (happened to me before due to a regression)