Make Honeypot optional to support more plugins

[Zodiac1978]

Maybe this is something we are not doing anymore, because v3 will fix this.

But if we add an option to disable the honeypot we could make the plugin compatible with Jetpack comments and other plugins which do not use the WP comment form but could need help with our other methods of spam detection.

[websupporter]

Imo to be discussed in 3.0, imo: disabling this central feature is like disabling the plugin. As we currently discuss and evaluate also other filters, there might be a reason to make the honeypot optional, but we need to see, how good those additional filters would really work out there.

[florianbrinkmann]

I think we could just try to make the Honeypot optional in v3 so that plugins which would like to integrate with other spam detection mechanisms can do so. And even if the current detection mechanisms do not detect that much without the honeypot (maybe we should store all matching spam reasons and not exit with the first matching one, so we can get a better picture how efficient the other spam features are), that would allow other plugins to start using ASB after we add some features that change that, without us having to modify ASB then.

[Zodiac1978]

Specific plugin which could be tested for this approach: https://wordpress.org/plugins/wpdiscuz/