AntiLeech Plugin To Stop Splogs - Does It Work?

April 25th, 2007 • Related • Filed Under

Ajay wrote yesterday in his weblog tools column about the AntiLeech plugin that stops splogger bots from:

accessing your site. It does this by producing a fake set of content that includes links back to your site and sends it only to them.

Does anyone have any experience of using this plugin that they can share? Splogs drive me mad and I hate them using my posts, so if the AntiLeech plugin works I’ll install it straight away.

Related Posts

Bookmark

  Digg it   Save This Page   Google
Enjoyed This Post? Subscribe To Get Updates!

About the Author

author photo

Everton is based in London and has worked in the internet and mobile space for over ten years now, and before that worked in corporate strategy and consulting. He has a degree in Economics from Cambridge University, and currently runs the Portal and online operations for one of the largest ISPs in the UK.

See All Posts by This Author

« MBL Community: How To Fix File Copying Problems In Windows Vista Congratulations To Brian Blogger On Getting A Google Grant »

There Are 7 Responses So Far. »

  1. 1

    Comment by Thilak on 25 April 2007:

    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?

  2. 2

    Comment by bill on 25 April 2007:

    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.

  3. 3

    Comment by Everton on 25 April 2007:

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

  4. 4

    Comment by Thilak on 25 April 2007:

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

  5. 5

    Comment by Everton on 27 April 2007:

    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

  6. 6

    Comment by Everton on 28 April 2007:

    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.

  7. 7

    Pingback by My First Attempt To Stop A Splog | Connected Internet on 30 April 2007:

    [...] Normally I can’t be bothered to do anything, but this is gong to far so I’ve followed Feedburner’s advice and fired off an email to Google [...]

Subscribe without commenting

Post a Response

Comment Policy: Any comments are permitted only because the site owner is letting you post, and any comments could be removed for any reason at the absolute discretion of the site owner.