Closed erickok closed 9 years ago
I've also been having spam problems, and would like to at least complicate their life.
Implementing a real CAPTCHA isn't trivial, which I guess is why this bug is lingering here. I'd like to propose a simpler alternative which should be quick to implement: specify a key in the config which the submitter must have.
The easiest way of doing this would be to put the key in the URL parameters, so that it can be given to translators as a link: http://site.com/pastt/?key=abcdef
It's sort of the weakest security there is, but it's still better than the current situation. I'm willing to implement this, but wanted to know if there is interest in such a solution before diving into the code.
I understand your frustration, yes. That solution would only work if you know your translators though, which is a bit of a shame.
Did you enable the required email address? That helped me reduce spam on my site dramatically already as most spam bots don't understand (or are not bothered to) fill in a valid email address.
I don't like requiring the email address because it's too annoying for frequent contributors to type it in every time.
The key as I was proposing has the advantage of being transparent in that respect. Also, the key could be ignored if it isn't set in the config file, which I guess would be the default behaviour.
I've implemented this using the reCAPTCHA library from Google. This has stopped (previously daily) spam submissions on my public translation page completely for about a year now. Hope someone finds this useful. :)
Merged, thanks! Note for future users, you can get your Google reCAPTHA code at https://www.google.com/recaptcha/admin
Original issue from https://code.google.com/p/android-php-translator/issues/detail?id=31
Reported by HermannMagliacane.HM, Jul 17, 2013 Add CAPTCHA to prevent spam