By DeeEmm on Tuesday, 28 January 2014
Posted in General Issues
Replies 4
Likes 0
Views 696
Votes 0
I've been getting a lot of posts recently from users posting spam. Seems that spammers are getting ever more sophisticated in their link farming efforts.

I'm pretty sure that the posts are from real users so tactics that normally work to prevent bot registrations are failing. The users are even choosing avatars relevant to my sites content so it's not really possible to spot them - not that I really want to moderate new users - it is simply not an option for me. I've ended up having to moderate all new posts which is a massive issue time-wise.

I've had a lot of success using askimet on other sites - both on forums and blogs and have enabled it for the blog comments but am really surprised to see that it is not possible to enable it for the posts themselves. This seems like a very necessary feature for a multi-user site.

Not sure if this feature is already on the cards, but I'd like to put a suggestion for it.

Surely it could not be too much work to extend the current code for askimet filtering of comments to include the posts themselves.

Regards

DM.
Hello,

Hm, we don't actually have Akismet enabled for the blog post itself but we're probably adding this in 4.0 but my main concern is the amount of data that needs to be sent to Akismet when you are posting your blog post. Just by the auto posting itself, takes a while since it needs to send data to Facebook, Twitter respectively. Adding Akismet here might eventually cause the script to time out if your hosting provider sets the max_execution_time to a low value.
·
Tuesday, 28 January 2014 12:31
·
0 Likes
·
0 Votes
·
0 Comments
·
Great to hear that you are considering adding this in the next major release.

Interesting you should mention Facebook and Twitter - The main issue I have, is that due to auto publishing, the spam posts are ending up on my sites Facebook and Twitter feeds. Whilst not everyone visits the site on a regular basis they generally are glued to their social media feeds which means that irrelevant and annoying spam posts are generally likely to result in some people unfollowing or blocking the sites feeds.

Something to consider if you are concerned for overheads and response times - take a look at adding a queue for publishing posts (for example like the moderation queue). When posts are submitted - they are queued until the CRON runs, they are then sent to Askimet - if the post fails validation then flag as failed and process no further. If it passes validation place it back in the queue (flag it as passed) ready for the next time the CRON cycles before pushing it out to Facebook / Twitter. This will alleviate the issue with server response time as well as provide extra protection by preventing spam posts being published to Facebook and Twitter (my main reason for wanting Askimet integration)

Additionally I personally would not notify the author by email if the post is detected as spam. Askimet is pretty good so there are very few false negatives. Please consider including an option to disable email notifications for spam posts - it minimises server load and prevents giving the spam author the heads up to come back and try again.

DM
·
Tuesday, 28 January 2014 13:09
·
0 Likes
·
0 Votes
·
0 Comments
·
In fact if you adopted the moderation queue but add in some additional statuses for

- waiting askimet verification
- verified but waiting publication

Then moderators can still manually publish posts and bypass the authentication requirements. Makes sense to only maintain one queue - easily done if consideration is paid to post status.


Automatic post moderation based on user post threshold is also another good feature that I would like to see - i.e. the ability to automatically publish posts (and bypass moderation) from users who have posted x number of posts.
·
Tuesday, 28 January 2014 13:16
·
0 Likes
·
0 Votes
·
0 Comments
·
Thanks for the heads up on this.
·
Tuesday, 28 January 2014 16:56
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post