Need someone to lead product management at your software company? I create software for people that create software and I'm looking for my next opportunity. Check out my resume and get in touch.

Spinn3r

Freshness Warning
This blog post is over 16 years old. It's possible that the information you read below isn't current and the links no longer work.

Later today, Tailrank is launching Spinn3r, a new product that packages blog index data for use in blog search, research projects, and more. Tailrank is indexing over one million blogs with a post volume of over 25k new posts per hour being added to their index.

Tailrank has created a number of proprietary methods to ensure that the blogs in the index are spam free and will remain that way. With this product, companies that require fresh data from blogs can receive it without building their own spidering and spam-fighting infrastructure.

See also TechCrunch’s coverage, in which they report a rumor that Gnoos is using Spinn3r to power their index.

Disclosure: I’m an advisor to Tailrank

Erasmus
April 19, 2007 12:35 PM

Spinn3r seems to ultimately suffer from its own success. The tools to prevent spam will work best when no one tries to game the system, but once spinn3r starts to gain momentum the spammers will pick up their game and break down the usefulness of your algorithms. Good luck fighting spam, but as long as there are significant monetary rewards for spamming nothing is going to change.

Kevin Burton
April 20, 2007 9:28 AM

Erasmus, So we should just give up? Spam is inevitable so there's no sense fighting it because they'll always win. This sounds a bit defeatist doesn't it? The spam war is a space race. A war of attrition. I don't think we've EVER claimed that we'd SOLVE spam just that at any point in time we try to keep it minimized and within reasonable values.

Antony
May 1, 2007 11:36 AM

I think that we will never stop the spam, because when we will stop it in any way - the spammers will find another method to spam. But we have to try and don't give up. The spinn3r is one step forward to stop it, greets for makers of this tool.

This discussion has been closed.

Recently Written

Mastery doesn’t come from perfect planning (Dec 21)
In a ceramics class, one group focused on a single perfect dish, while another made many with no quality focus. The result? A lesson in the value of practice over perfection.
The Dark Side of Input Metrics (Nov 27)
Using input metrics in the wrong way can cause unexpected behaviors, stifled creativity, and micromanagement.
Reframe How You Think About Users of your Internal Platform (Nov 13)
Changing from "Customers" to "Partners" will give you a better perspective on internal product development.
Measuring Feature success (Oct 17)
You're building features to solve problems. If you don't know what success looks like, how did you decide on that feature at all?
How I use OKRs (Oct 13)
A description of how I use OKRs to guide a team, written so I can send to future teams.
Build the whole product (Oct 6)
Your code is only part of the product
Input metrics lead to outcomes (Sep 1)
An easy to understand example of using input metrics to track progress toward an outcome.
Lagging Outcomes (Aug 22)
Long-term things often end up off a team's goals because they can't see how to define measurable outcomes for them. Here's how to solve that.

Older...

What I'm Reading

Contact

Adam Kalsey

+1 916 600 2497

Resume

Public Key

© 1999-2024 Adam Kalsey.