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]
One thought on “FeedPass do not republish our feeds!”
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:
Comments are closed.