Yep, fortunately last I heard they were working on it. There’s just a lot of complexities in implementing something like this…

Bad Behavior seems to be one of the most divisive WP plugins out there. You either love it and can’t stop singing its praises, or outright hate it.

I guess we’ll see how it develops.

MacBros,

*.info is pretty notorious for hosting spam, take a look at this link:

http://www.infoniac.com/hi-tech/google-blogs-spam.html

It’s apparently the worst of all the TLDs.

You can use FB and Antileech, but Antileech will only protect your original WP feed, not your FeedBurner feed. I have the plugin to randomize your feed address and, thus, scrapers aren’t likely to find my original feed.

Antileech, however, can not help you stop scraping of your FeedBurner feed. That’s hosted on their servers and is under their control.

Bad Behavior seems to be one of the most divisive WP plugins out there. You either love it and can’t stop singing its praises, or outright hate it.

I guess we’ll see how it develops.

MacBros,

*.info is pretty notorious for hosting spam, take a look at this link:

http://www.infoniac.com/hi-tech/google-blogs-sp…

It’s apparently the worst of all the TLDs.

You can use FB and Antileech, but Antileech will only protect your original WP feed, not your FeedBurner feed. I have the plugin to randomize your feed address and, thus, scrapers aren’t likely to find my original feed.

Antileech, however, can not help you stop scraping of your FeedBurner feed. That’s hosted on their servers and is under their control.

I added *.info in my Antileech plug-in. I hope this works.
I wanted to ask the author of the plug-in is that way will work but there’s no way to contact them.

So a good start for this guys ultimate plan would be to add the domain extension .info to that list with the wild card (*) in front of it.

I have heard mixed reviews about Bad Behavior also. If it works correctly on their setup, people absolutely love it. But, for some shared hosting sites like Go Daddy, I have heard it will not work at all.

Hopefully the developer will work things out so it is more consistent across setups since the basic way it works seems to be great.

Good question there. First, take a look at this article from October. It lists my favorite anti-content theft plugins.

http://www.plagiarismtoday.com/2006/10/09/five-essential-wordpress-content-protection-plugins/

I use the digital fingerprint plugin actively as well as Numly. I would use Antileech but I also use FeedBurner, which negates that. Bad Behavior I’ve used in the past but had trouble with. I’m debating trying it out again.

As far as comment spam goes, I used to use SK2 but switched to Akismet to take the load off of my server. Besides, with SK2 not being actively developed, it seemed like a safer move.

Overall, I’m happy with Akismet though it seems to dump a lot into the “moderate” bin that really is clear-cut spam.

Other plugins worth noting is the FeedBurner Feed Replacement, which randomizes your original feed to prevent scrapers from simply guessing the address and the “Secure and Accessible PHP Contact Form” which prevents traditional email spam from coming from your contact form.

That should about cover it. I’m always open to any additional suggestions others might have!

Good question there. First, take a look at this article from October. It lists my favorite anti-content theft plugins.

http://www.plagiarismtoday.com/2006/10/09/five-…

I use the digital fingerprint plugin actively as well as Numly. I would use Antileech but I also use FeedBurner, which negates that. Bad Behavior I’ve used in the past but had trouble with. I’m debating trying it out again.

As far as comment spam goes, I used to use SK2 but switched to Akismet to take the load off of my server. Besides, with SK2 not being actively developed, it seemed like a safer move.

Overall, I’m happy with Akismet though it seems to dump a lot into the “moderate” bin that really is clear-cut spam.

Other plugins worth noting is the FeedBurner Feed Replacement, which randomizes your original feed to prevent scrapers from simply guessing the address and the “Secure and Accessible PHP Contact Form” which prevents traditional email spam from coming from your contact form.

That should about cover it. I’m always open to any additional suggestions others might have!