http://digg.com/tech_news/Feed.....e_on_E_Bay

Instead of just attacking Feedpass, perhaps they have done us all a favour and opened up a much broader can of worms that needs to be looked at?…

I can (for example) take Dave Winer’s feed, convert it to Feedburner, add my Amazon ID, (yes it works) and voilà I got my own instant bank machine.

(Don’t worry Dave I won’t make the link available so please call off the law dawgs

Yes, it might be unethical and perhaps even illegal, but why all the confab over just Feedpass? Let’s keep our perspective boys and girls.

Hope

So isn’t that what FeedPass, and anyone who makes a FeedPass from my blog is doing — using my work for commercial purposes?

Not that anyone is doing that to me. But this just bothers me — one more way to try to make money from someone else’s work.

Translation:
“Don’t remove the link–I like the attention and the hits that link is sending me.”

http://www.feedpass.com/GiffoBlogtestingfeedpass

Two mistakes brings a lot of discussion about the new service Feedpass.com.
Why they are wrong:
- They make commercial use of content without any prior authorization of the original publisher.
- They have a wrong design in which anybody can claim a c…

I guess there is a dichotomy in the logic presented so far on systems that consume published data, store it, and then republish it with monetization that is not associated with the original source of the content. If it’s good for them, bloggers seem to approve of it - namely anything that gets them more traffic, so therefore Google must obviously be a good thing. But other systems are met with considerably less enthusiasm - and Feedpass seems to fall into the latter category … even though on certain levels it’s doing something similar.

I guess bloggers want to have it both ways. And I agree, on some level - Feedpass seems a bit wrong to me. Ok - so here’s a solution … block Feedpass. I just created a feedpass for an exceptionally low utilization blog that I don’t really do much with anymore. It barely gets a dozen hits a day - so it was very easy to track down where Feedpass was coming in from, and how it was identifying itself. These are the relevant entry details from my IIS logs.

206.130.100.7 MagpieRSS/0.72+(+http://magpierss.sf.net;+No+cache)
206.130.100.7 FeedForAll+rss2html.php+v2

So, configure this in your IIS/Apache/whatever to deny Feedpass - either by IP or user-agent, and you should be able to protect your content. Although it’s fair to mention that MagpieRSS and FeedForAll are stand-alone apps, that don’t necessarily have anything to do with Feedpass other than being tools that Feedpass seems to use to get its job done.

Personally, I think it would be a good thing if Feedpass were to provide this IP address and user-agent information to RSS publishers, voluntarily, on a page on their site - so that RSS publishers can easily choose to opt out of the feedpass system. In any case, denying them access should solve the problems of anyone who is seriously concerned about this.

http://feedicon20.com/

Yes, it is really bizarre that FeedPass didn’t realize that alineating most of the A-List bloggers from its very inception by using this tactic was duuuuuumb. People generally don’t like being forced to deal with crooks. And if the people who are being forced to deal with the crooks are influential and resepcted, the buisness plan is, shall we say, flawed.

Hope