My Feel the Power post was a lot of fun to write, so I’m reporting in after 24 hours to tell you how things are going.
I concluded Feel the Power with “I can now enjoy BlogEngine.NET as God and Ruslan Tur intended.” I’ll show you a couple of screenshots to confirm that I wasn’t lying. Let’s first look at the latest custom filter stats from Akismet and StopForumSpam. If you recall, these were previously at “0” across the board because comments were never reaching that stage of validation.
What’s cool about my new BlogEngine.NET Spam Filter-empowered reality is that you never see the spam messages. All of my years blogging I never experienced this type of automated spam removal. I’m liking it!
Yes, some spam messages slip through, primarily because the soul-less bastards spawning the comments (and remember, BlogEngine.NET uses Captcha on comments, so they have to actually be typing this shit in) use bogus emails, a variety of host IPs and scrambled comment text intended specifically to get past spam prevention algorithms.
That’s where BlogEngine.NET’s user-configurable filtering comes into play. Let’s look at today’s comments that were auto-tossed into the spam can and how they were moderated.
Highlighted at right is which Moderator determined the comment was spam. At bottom we see that "daveburke" marked a couple of comments as spam, then we see entries with “AkismetFilter” and “Filter” as moderators.
Akismet rocks and need no further explanation, but the 3rd item in the screenshot with moderator "Filter" does. (It rocks, too, btw.) What happened here was that the comment from IP 220.127.116.11 was tagged by the user-configurable filter rules because the IP contained "184.82."
BlogEngine.NET to the rescue. It’s time to move on now that we know what Custom Filtering statistics are supposed to look like and how to use BlogEngine.NET user-configurable filtering. And to think, the next version of BlogEngine.NET can only do it better.