 | Draft for form module 1.1? Draft for form module 1.1? - Proposal, gathering ideas for a pluggable mechanism for user content verification |
We currently have at least 4 places where we need to handle/avoid spam:
- public user registration
- forum
- comments
- and, more generally, the forms of the form module.
We currently have a honeypot-based solution; it could be necessary to extract that logic and have a pluggable mechanism: some might want to actually use a captcha, others might need a stronger spam verification using services such as Mollom or Akismet
Comments (2)
Apr 30, 2009
Sameer Charles says:
- If we have a plug-able mechanism and if we decide to provide some out-of-t...- If we have a plug-able mechanism and if we decide to provide some out-of-the-box plugins -
If you go for captcha, I would recommend to use re-captcha instead of integrated jcaptcha, although jcaptcha works but its fairly easy to break. re-captcha is free and available as a service which can be easily integrated (sites like twitter, facebook, wikipedia uses re-captcha).
You can also use very simple HashCash spam protection, its simple but works since most of the spam bots wont dare to execute javascript - biggest problem here is that you need to have JavaScript enabled, so this might not be a viable solution for Magnolia.
As a note: Akismet is very powerful but not free for commercial use.
Apr 30, 2009
Boris Kraft says:
The form module has a honeypot, which works just fine without any pain for the e...The form module has a honeypot, which works just fine without any pain for the end user or strain on the eyes. Captcha is a PITA and I am completely against using it on any website at all (don't even get me started...). There are better alternatives, some really smart and needing more work than a honeypot, but hey, Magnolia is about ease-of-use. Captcha is completely killing that.