AntiLeech Plugin To Stop Splogs – Does It Work?

More from Rick:

On the assumption that a splog is using adsense (or any other ad network), usually one e-mail to the network informing them that someone is monetizing content they don't have rights to gets their ads turned off immediately; that tends to kill it pretty quickly. For adsense, the e-mail to notify them is adsense-abuse@google.com.

Here's the reply from FB:

The primary thing we're doing is ensuring that our 'uncommon uses' feature is good at detecting unusual consumption of your content (and/or unusual clickthrough patterns). This gives you complete visibility to the domains that are generating illegitimate consumption, which then makes it easier to decide how/if to stop them.

We don't (yet) make it possible to prevent an IP, domain or user agent to get your feed content, but we're looking at ways that might be workable.

--Rick

Everton: Thanks a lot. Hopefully, they'll take your advice and add a new feature which will help us all.

I've fired a question over to FB - it'll be interesting to see what they say on the subject

I've read about setting up your feed to do exactly what AntiLeech promises - the problem is that it doesn't work if you're serving your feed through Feedburner. The issue is (and I think that it is probably true for AntiLeech as well) that your server is doing all the work when it comes to identifying a "leech."

When you serve your feed through Feedburner your server only sees Feedburner while Feedburner's servers are what deal with the content thieves.

As Thilak points out, the best solution would be on Feedburner's end. I'd love to see Feedburner add some type of system for identifying splogs and blocking them.

It works for some spam blogs, for others it won't. It think, this plugin fails to work if you use Feedburner.

This leaves me wondering if Feedburner can do something about spamblogs. What do you say?