Spam issues - users not being able to comment

[ed]

Ed is receiving a selection of users not being allowed to post since the spam changes. We are seeing a pattern now. Setting this ticket up - will add user details tomorrow.

[jim]

Interesting, I await the pattern...

This issue aside, how's the spam war going since we got some new tools on the site?

[ed]

Rise in users being blocked since spam changes. Captcha suddenly being a problem by the sounds of things. Seen on forums, comments to blogs. They're all getting this one:

"You must be a human, not a spam bot, to submit forms on this website. If you insist that you are a human, please try again. If error persists, contact webmaster using contact link at the bottom of this page and give all the details of this error (your browser, version, OS).
Please enable Javascript to use this form."

--1. The most descriptive user---

---> I've tried on multiple browsers (IE, Crome, Firefox) with Javascript enabled.

Here are two screen grabs: the initial problem seems to be that when first trying to post the comment I don't recieve a word verification. I then try to post the comment anyway, so it comes up with the first screen attached. This screen does now have a word verication test, but it doesn't seem to recognise my answers so keeps telling me the same message.

Also, for the record I do have one link in there, although I just tried it without then link and it seemed to give the same message.

NB: Ed logged in as this user and could post comments to the SR blogs which he was trying to do.

--End of the best user reply--

--2. Other user reply outlining problems with captcha not showing but system still wanting letters---

keeps coming up as as needing those letters in a box, but the box either doesnt appear, or I do it, and it wont accept!

[ed]

1st error screengrab

[ed]

2nd error screengrab

[ed]

... we haven't had a single crappy post as hoped for which is great - while we are also experiencing a swing in the other direction with users not being allowed in - which was also expected!

[ed]

I *think* that they may all be new users experiencing this problem. The older ones are commenting OK.

[ed]

More from one of the users:
"Each time at first there was no line box to put my name in btw, and then one would appear with eg: 8P66ge in it. Each time I erased this strange content and popped in my name. "
User: MacBook? pro 10.6 (old!!) I was using Google Chrome, living in Marlborough, Wilts, UK

[ed]

Just tested with joelT account (from the screengrabs) on a totally unknown PC and commenting to a blog post worked fine. Therefore is this something to do with the registration process and new accounts?

As an aside, as we move towards integrating Transition Culture onto the site, we're going to need to use something that does not neccesarily require registration, or make the registration *really* easy and quick otherwise the TC fans are going to riot. Discus?

[ed]

JoelT (user acct having problems as per screengrabs) now able to add comments. So my theory that it's a problem encountered with new accounts seems to be gaining traction.

[jim]

Questions, points and actions:

1. Are the users who can't comment still pre-authorised (haven't validated email)? They cannot do much until they click that email link.
2. The first screen grab shows Mollom doing its thing -- the post must have looked 'spammy' hence it added the captcha in place. I also see ​this Botcha/Mollom issue recommending one or the other.
3. I have therefore disabled BOTCHA on Comment forms, leaving Mollom in place since it does text analysis plus some BOTCHA stuff -- perfect for comment forms that can only be accessed by validated users.
4. I have also disabled BOTCHA on contact forms (side wide and user) since, again, Mollom is already enabled and does a great job with text analysis.
5. I've checked CATPCHA and it's only present really on user login/password pages.

So we seemed to have overlapping coverage which I've now resolved... Coverage breaks down like this:

• BOTCHA: is the gatekeeper for registration, together with Spambot and CAPTCHA.
• Those who pass this will need to validate their email to do much.
• Those who do will meet Mollom whenever they try to contact people or post comments or content.

In other words: the 'free and simple' botcha and captcha are the doormen, and Mollom is the admin lady checking the post before the editors get it, while Spambot is sitting there watching users and visitors like an undercover cop. And Ed (with a large bat) and Jim (with a snookerball in a sock) are in the back on call just in case anyone gets 'funny'.

Hopefully these changes will fix the outstanding issues. Over to you...

[jim]

As an aside, as we move towards integrating Transition Culture onto the site, we're going to need to use something that does not neccesarily require registration, or make the registration *really* easy and quick otherwise the TC fans are going to riot. Discus?

You'll need to raise a ticket for that, but I've got a few ideas.

[ed]

Brilliant - taking down to minor for reference. AFAIK, users were authenticated but if this comes up again, will check first.

[ed]

This user could not register. Here is his reply to my questions:
Did the website show you the 'Captcha'? Yes
Did you type it in? Yes
Did it then reject you? Yes
He was rejected 5 times before giving up.