MSN Spaces Supports Feed URI Scheme

Dare Obasanjo reports that MSN Spaces now supports “one-click subscription” via the feed URI scheme (aka: “feed:// protocol”). According to Mike Torres:

“Clicking on the orange RSS button or the “Syndicate” link above will no longer spit out raw XML to your readers using a modern browser. Instead, they will see a “pretty printed” RSS feed with a link to learn more, subscribe in My MSN, or subscribe in an aggregator supporting one-click subscription (feed://).”

In other words, readers of any of the 4.5 million MSN Spaces blogs can now simply click a feed link to subscribe to the feed in FeedDemon, NetNewsWire, NewsGator, Shrook, RSS Bandit, NewzCrawler, Sharpreader or any other RSS reader which support the feed URI scheme. Very nice!

Spyware purveyors looking into RSS

I just received this email from a well-known purveyor of spyware who is seeking to enter the world of RSS:

“We are interested in any co-distribution and/or co-marketing opportunities with FeedDemon. I represent [company name omitted since I don’t need the legal hassle], a free content and application network that represents a current user base of 30 million plus subscribers. Should we explore a possible syndication opportunity, this would possibly gain exposure of your application to our user network. If you are interested in discussing further, if you could please contact me offline, I would be happy to chat more about this with you in detail.”

I immediately replied that I wasn’t interested in doing business with them, but I’m sure I’m not the only one they’ve contacted. If you’re involved in developing an RSS reader, be sure to research any company seeking to do business with you before replying to their request. The last thing RSS needs is affiliation with spyware.

RSS reader market share among football fans

The Read/Write Web has an interesting post about RSS aggregator stats which to some degree confirms my suspicions about RSS reader market share. Over the past few months, I’ve seen several posts about market share which I believed were inaccurate for many reasons, not the least of which was the fact that they really determined market share among geeks rather than the wider non-technical audience (yes, many non-techies are reading RSS now!).

In this particular example, the top aggregator being used is My Yahoo, followed by FeedDemon and then Bloglines. As Kevin Donahue points out, FeedDemon is easy to use, which makes it an obvious choice for the non-geek.

Now, I’ll be the first to admit that there’s very little you can determine about RSS reader market share when looking at a single set of feeds (and of course, basing market share on server hits is inaccurate to start with), but the fact that the results vary so widely based on which feeds are examined speaks volumes about the accuracy of these surveys.

PS: Kevin, I agree that Fanblogs should be in FeedDemon’s default set of feeds – I’ll add it to the “Sports” group in the next build. However, given the number of feeds you offer, you might want to consider providing your visitors a custom build of FeedDemon that’s pre-loaded with all of your feeds.

Privacy on the desktop

As I mentioned a few months back, I frequently receive offers from companies wanting to pay to have their feeds included in FeedDemon. These offers are often very tempting, but when it comes to choosing which feeds to include in FeedDemon by default, I’ve always considered my role as more of an editor than a salesperson, so paid feed placement just didn’t sit well with me.

Beyond this, though, there’s another big problem with paid placement: those asking to have their feeds included usually want usage information in return. In other words, they want to know how many people are subscribing to their feed in FeedDemon, which articles they’re reading, what other feeds they’re subscribed to, etc. And of course this only makes sense – if they’re paying to have their feed included, they deserve to know what they’re getting for their money.

The thing is, if I collected usage information you can pretty much guarantee that FeedDemon would be labeled as “spyware” and die an ugly death. I could make usage collection opt-in, of course, but this would mean that the data would be inaccurate – the numbers would be lower than reality, since many (most?) people would choose not to share this information even if it was anonymous.

Now, here’s what I find interesting: if FeedDemon were a web-based aggregator, I believe (and recent history has confirmed) that this usage information could be collected without the same backlash from privacy advocates.

So why is this? It’s the exact same information, so why is it acceptable to collect it on the web but not from a desktop application?

I believe a big part of the reason is trust. On the web, information is collected from the site itself, so nothing is sent from your computer. But with a desktop application like FeedDemon, information would have to be sent from your computer to the site collecting the usage data, and there’s a huge element of trust here. After all, a desktop application potentially has access to everything on your computer, so you’d have to trust that it would send only the information it says it will. I suspect that quite a few of us are unwilling to grant that level of trust.

In FeedDemon’s case, I’m sure another reason is the fact that it’s not free, whereas most web-based aggregators are. When software or a web service is free, you often pay with your privacy, and the developer earns a living (either directly or indirectly) from the usage information they’ve collected. When you pay for something, should you be able to assume that you won’t continue to make payments by giving up your attention data?

For the record, this post is just me thinking out loud – none of my software collects usage data, and I have no plans to do so. But I am curious to hear your opinions on this, since I believe privacy concerns are becoming increasingly important to the world of RSS and to software in general.

Really Simple Subscription, PII

There has been a lot of debate following my initial post about Really Simple Subscription. Shortly after I suggested using the feed URI scheme, NetNewsWire developer Brent Simmons came out in favor it, and in the comments to my post we heard that Safari RSS (part of Apple’s upcoming Safari 2.0) will use feed:// quite heavily.

But other solutions have been proposed, such as the Universal Subscription Mechanism (USM) authored by Randy Morin. I’ve spoken with Randy about USM, and he knows that I have a number of issues with the “reflexive auto-discovery” mechanism. However, part of his proposal includes convincing feed producers to provide the correct Content-Type header for their feeds, and I’m 100% in favor of this. Although having the correct Content-Type doesn’t entirely solve the problem, it would take us a big step in the right direction.

If you’re interested in this topic, be sure to read all the comments beneath Brent Simmons’ post, including Danny Ayres’ comment that he “can’t actually see [much] conflict between these approaches, implementing one doesn’t rule out implementing the other.” I agree. We’d all be better served if we realized this isn’t either/or situation and stopped endlessly debating which solution is better. I’m in favor of feed:// because it’s simple for everyone to implement, but I’m also in favor of evangelizing feed producers to use the correct Content-Type. And once it’s fleshed out some more and answers my concerns about privacy, I may like Dave Winer’s solution as well.

Really Simple Subscription

Dave Winer proposes a solution to the problems caused by the lack of a standardized method for feed subscription. While I would love to see these problems resolved, with all due respect to Dave, I can’t say I’m wild about the idea of a centralized subscription server. This seems too complicated for something called Really Simple Syndication, and I imagine many users wouldn’t want their subscriptions stored on someone else’s server (or wouldn’t be permitted to by their employers).

In my mind, the real problem is that the browser does the wrong thing when you click that ugly orange RSS or XML button. Just as your browser knows how to handle “mailto:” links, it should understand what to do with a link to a feed.

So I have to point out that the feed:// protocol (aka: feed URI scheme) was created to resolve this problem. Is it a perfect solution? No, it’s not (there’s no such thing). Past discussions about this idea have devolved into arguments about MIME types, but I maintain that it’s the best one we’ve got because it works right now. It’s already supported by FeedDemon, NetNewsWire, RSS Bandit, NewsGator, NewzCrawler, SharpReader, Shrook, FeedReader, Awasu and other desktop RSS readers. It would be simple for Yahoo!, Google or MSN to support it through their toolbars, and for Bloglines to support it through their notifier tool. And it would be dead simple for browser developers to support it as well.

The other part of the problem is that those orange RSS or XML buttons look far too techie. Why not drop the geek acronym and just use FEED instead?