FeedPass do not republish our feeds!

Anytime I see a service that has the potential to cause ones feed to be Hijacked it gets my attention. Looking at the FeedPass interface I became instantly aware that anyone could take our feed and sign up for an account, have Google Ads inserted and start making revenue by placing that same content on a service that could feed up my RSS feed and someone else’s advertisements.

I am putting FeedPass on notice that if I find any feeds from any of our companies being hijacked and ran thru their service that we are going to hold them liable.

I don’t need stats or help from any third party in figuring out what my stats are and I don’t want anyone coming across our content subjected to advertisements in our RSS feed. [Scripting News]

Comments

  1. Jim Woolley says

    Actually, Jeremy. Claiming the feed doesn’t make it so no one else can use it. Claiming the feed simply ensures that you, as content owner, get credit for AdSense views if someone else creates a feedpass page that points to your feed.

    Seems like there is a little controversy around this and the great people at GeekNewsCentral may be jumping to some conclusions. However, we are still removing them so that no feedpass pages can be created for any GeekNewsCentral.com feeds.

    Just to clarify, however, feedpass is built to drive subscriptions. Our pages don’t contain full feeds, only previews of the last 4 items. We just make it incredibly easy to subscribe. And, we provide financial incentive to anyone who creates a feedpass, and the content owner.

    There’s some very interesting discussion around this that started with Marshall Kirkpatrick and then was picked up further by Dave Winer (Scripting News) and even Michael Arrington of TechCrunch fame. Here’s the link:

    http://socialsoftware.weblogsinc.com/2006/05/19/feedpass-makes-rss-subscription-and-monetizing-other-peoples-co

    Jim
    Feedpass

  2. says

    Well, Mr. Woolley,
    Why not allow people to claim their RSS feed like many other services have? Google has a great system set up for their sitemap service that makes you actually but a randomly named html file on your site to verify you actually own the site. This may be a pain, but it is a great idea to protect the site’s owner’s content from being stolen.
    I think the idea of your service is great, but I would hate it if I found out someone else was making money off of my blog, when I don’t even get money like it is off my ads.
    I don’t care what all the big name bloggers say about your service, honestly. I’m 17, and my blog is more or less a laid back blog and I have made a total of $8 from my AdSense campaign that I started in early 2005. Now I had a problem before with porn sites stealing my RSS feed and using a parser to steal Google search returns from me and then use their own ads to make money off of my work.
    There was really nothing I could do except block their server’s IP and it stopped. But what I’m getting at is that your kinda making it too easy for these guys to do this all over again. I would suggest a Google-like verification system or make the person register at least to use the adsense code.
    Your getting a lot of heat it sounds like, so I would think about listening to these guys, they have a good following, ya know. :)