Preventing Blog Spam, Part IV
So here I go again, attempting to find creative ways to prevent spambots from slamming my blog with junk postings. A number of people have complained about the my removing anonymous access from the Comments list and since I still haven’t had time to create a Captcha custom field type, I’m trying Mo Omar’s method of using a required date field in the Comments list.
We’ll see how it goes…since I’m heading out to get my hunting license today, I feel I should lobby for an open season on spammers. That should be legal, shouldn’t it?
I’ve created a solution for this problem. You can look at my “No Blog Comment Spam” on my blog http://www.hezser.de/blog/Lists/Beitraege/Post.aspx?ID=104.
Executing SQL statements directly against your SharePoint database is a VERY BAD IDEA. There are other ways to achieve this via the object model that do not require direct access to the database.
Dude, time to apply the CKS:EBE to your site. It has integration with Akismet, which should suppress 99% of the spam.
Check out how SubText does it… Akimiset allows me to have zero CAPTCHA and no login… and I only see about 2-4 spam posts per week… and that’s a bad week.
Akismet is a great idea but there is no way to integrate that with an existing SharePoint list. If someone would create a custom field type and release it as a .wsp I’d be happy to install it.
CKS:EBE won’t work because they don’t offer the features individually – I’m already using a custom site definition for this blog that matches the branding on the parent site. CKS is an all-or-nothing proposition and that won’t work for me.
I am not using any SQL statements against the SharePoint Databases. The only problem is, that the application pool account does not have the required permissions on 4 stored procedures. You can not store data in the PropertyBag of SPWebApplication.
That sounds like a bug to me.
How’s the required date field coming along? Has it worked? It would be good to know if it has, fingers crossed 🙂