Troll management on a WordPress blog

Spread the love
8 / 100
Reading Time: < 1 minute

I am looking for 2 things:

a) near-perfect way of weeding out spam users right in Registration
b) automated deletion of spam Users, if some of these are already registered on a WordPress site

Feel free to tip any good tools that you’ve seen being used, or have used yourself. Thanks!

Will be posting about this in the future. For now, found it was easiest to just delete fake users right from the WordPress admin panel (backend). But it seems the incoming registration stream is quite constant, at a few new fake users per day, so in the long run it would be great to solve this in a bit more automated manner.

Facebook Comments

Published by jukkasoft

Hi! A bit updated description. Code enthusiasta, technology optimist, but also a realist. In my blog I wrote 80% of technology related articles, mostly in English and Finnish. I like to envision and ponder about things, how life could be, what we are doing wrong today, and so on. "Invented" a facebook -like system in 2000, as a short product pamphlet. Haven't yet realized the 20+ ideas that might have become big things. Maybe learning this skill one of these days!

2 thoughts on “Troll management on a WordPress blog

  1. Trolls/spam are a serious issue on WP. One thing I’ve found helpful is blocking their IP address as some spammers/trolls use multiple accounts but they all have the same IP address.

    1. Yeah, IP definitely looks like a promiment way to block. Some IPs might have a cool-down period, if a plugin allows doing this. Since some of the IPs will anyway probably be “recycled”, this is typical in home Internet connections, where the Internet provider has a large pool of dynamic IP addresses. I’ve had now the spam issue since experimenting with User roles and allowing registration. Thanks for tips! I’ll keep experimenting more and at least there are plenty of ways to approach this. 🙂

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: