Mollom

We do maintain the Drupal module for Mollom, but are not responsible for maintaining other plugins. As a Mollom Plus subscriber, you pay for use of the Mollom web service, not for maintenance of the plugins. Obviously, though, it is in our own interest to make sure that the Mollom plugins work well, and we will assist you in bringing your bug to the appropriate plugin maintainers' attention.

We do not currently provide professional services around Mollom. If there is no Mollom plugin for your CMS on our download page, we probably can't help you directly. However, Mollom is built around an open API, and can be implemented within most web services, content management systems and other web applications. We usually don't take a lead role in implementing plugins, but we do encourage CMS vendors, consultants and web developers to do so, and will assist with code reviews and troubleshooting via as time permits. We recommend that you work with a service provider for your CMS of choice and that you connect them with us via our contact page.

Mollom is built around an open API, making it possible to implement it in a large number of CMSes and web services. We strongly believe in open source and have made several open source clients available. Our back-end technology, however, will remain closed source. Giving away the intelligence we need to detect spam, generate rock-solid CAPTCHAs and figure out the quality of your content could be turned against us and defeat our purpose. The code could be used to create malicious, unblockable content.

No, you can implement the open API and use it in your proprietary software. We do encourage openness, but you are free to use the API anywhere you like.

No, we have a fully documented open API to access Mollom's services. You can use any of the Mollom API calls for whatever purpose may suit you. For example, if you only want CAPTCHAs, just ask for CAPTCHAs. If you only want quality checks, ignore the spam score.