7 thoughts on “Mute Screamer 1.0.4”

1. I’ve been prompted to update default_filter.xml and Converter.php to version 1485 for a while now on a couple of WordPress installs. However, when I try to update I get a message that these revisions are identical.

2. This is a problem with Mute Screamer’s updater, when PHPIDS repo makes an update that only has changes to one of the two files (as in revision 1445 you can see that Converter.php wasn’t changed), so the updater will tell you that Converter.php is identical, to the version you have. Thanks for highlighting this issue. This is on the todo list.

3. Is there any way to get mute-screamer to stop logging everything *I* do as an intrusion? I kind of freaked out when I saw I had 66 intrusions logged today until I saw that they all occurred while I was updating my site, and they all came from my IP address. Or do I just keep ‘excluding’ everything I do until the plugin learns to ignore my ‘intrusions’?

4. If it’s not already on your to-do list, being able to exclude IP addresses seems like it would be a good feature. If that’s possible.

5. Kimberly,
   Do you have it enabled for WP Admin?
   BTW–MuteScreamer did not play nicely with the ProConference (Evento) Theme. I kept getting “There was a problem processing this request” when working in the Admin.
   Ben

6. Thanks Ben! Yes, I do have it enabled for Admin and now I think I understand what that means. Looking at the intrusion log now though I’m not sure if this is really what I want. I’m seeing all the spam comments that other plugins weed out in the log now, but I suppose if I turn on IP banning I’d stop seeing spam comments from the same IP over and over again at least.

7. I have banned entire IP ranges that are based in Eastern Europe. I’ve also disabled registration abilities on a couple of the sites I manage. If you look up the domain registrations, something innocuous like “littletikeswagon” is an Eastern European IP. Lots of cybercrime out of that area.