# Mollom vs Akismet

**URL:** <https://meta.discourse.org/t/mollom-vs-akismet/32069>\
**Category:** Feature\
**Tags:** akismet\
**Created:** [2015年八月13日 15:33 UTC](https://meta.discourse.org/t/mollom-vs-akismet/32069 "2015-08-13T15:33:20Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![smartwatchme](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/smartwatchme/32/41275_2.png) [@smartwatchme](https://meta.discourse.org/u/smartwatchme)\
**Post date:** [2015年八月13日 15:33 UTC](https://meta.discourse.org/t/mollom-vs-akismet/32069/1 "2015-08-13T15:33:20Z")

</div>

Having the Akismet plug-in is certainly a great addition to Discourse, but I’m wondering if [Mollom](http://www.mollom.com) was ever considered as well? After digging into the API, it seems as though Mollom does have some advantages:

- Blacklisting words  
([https://docs.acquia.com/mollom/api/rest/list#blacklist](https://docs.acquia.com/mollom/api/rest/list#blacklist))
- Whitelisting users and sources.  
([https://docs.acquia.com/mollom/api/rest/list#whitelist](https://docs.acquia.com/mollom/api/rest/list#whitelist))
- Uses a tracking Image to get more detailed user data, hence - allow  
better spam protection due to the more detailed obtained data.  
([https://docs.acquia.com/mollom/api/rest/list#captcha-fba](https://docs.acquia.com/mollom/api/rest/list#captcha-fba))
- Captcha API ([https://docs.acquia.com/mollom/api/rest/list#captcha](https://docs.acquia.com/mollom/api/rest/list#captcha))
- Honeypot support on top of the content analysis feature  
([https://docs.acquia.com/mollom/api/rest/list#api-content](https://docs.acquia.com/mollom/api/rest/list#api-content) see  
“honeypot”)
- Rate Limiting for any consumer of a website set by the API  
configuration.  
([https://docs.acquia.com/mollom/api/rest/list#api-content](https://docs.acquia.com/mollom/api/rest/list#api-content) see  
“rateLimit”)
- Strictness setting to allow mollom to more punitive or more  
permissive for certain content submissions. Additional internal  
knowledge on how to fight user registration spam, which requires a  
more detailed investigation compared to regular “comments”.  
([https://docs.acquia.com/mollom/api/rest/list#api-content](https://docs.acquia.com/mollom/api/rest/list#api-content) see “type”

---

<div class="post-metadata">

**Author:** ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)\
**Post date:** [2015年八月13日 15:48 UTC](https://meta.discourse.org/t/mollom-vs-akismet/32069/2 "2015-08-13T15:48:06Z")

</div>

If someone wants to write a plugin for it following the Akismet example, that’d be great!

Akismet is working perfectly for us, though like any Bayesian filter it does take some initial training.

---

<div class="post-metadata">

**Author:** ![riking](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/riking/32/170938_2.png) [@riking](https://meta.discourse.org/u/riking)\
**Post date:** [2015年八月13日 17:25 UTC](https://meta.discourse.org/t/mollom-vs-akismet/32069/3 "2015-08-13T17:25:20Z")

</div>

> [@smartwatchme](#):
>
> Uses a tracking Image to get more detailed user data, hence - allowbetter spam protection due to the more detailed obtained data.([https://docs.acquia.com/mollom/api/rest/list#captcha-fba](https://docs.acquia.com/mollom/api/rest/list#captcha-fba))

This is useless for Discourse, as without some extremely custom-built tools you can’t post without a browser.

---

<div class="post-metadata">

**Author:** ![chapoi](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/chapoi/32/537252_2.png) [@chapoi](https://meta.discourse.org/u/chapoi)\
**Post date:** [2025年十二月4日 11:36 UTC](https://meta.discourse.org/t/mollom-vs-akismet/32069/4 "2025-12-04T11:36:54Z")

</div>