Need someone to lead product or development at your software company? I lead product and engineering teams and I'm looking for my next opportunity. Check out my resume and get in touch.

Blogroll autodiscovery

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

In order to find new feeds to index, Feedster is making some requests to URLs where OPML files are commonly located. A short discussion ensued in my comments about the relative merits of Feedster’s approach and a better way of finding the files.

A comment by Phillip Harrington suggested that bloggers use a <link> tag to indicate the location of their OPML files if they wish for them to be public.

Not only would this benefit Feedster, but it could also help automated systems look for related blogs. As I visit sites, my news aggregator could keep track of blogs that are subscribed to the same feeds as me. As the aggregator finds feeds that are often found in proximity to ones I like, they could be automatically added to my aggregator. Sort of like FOAF for blogrolls and news aggregators.

The format for such a link tag would be: <link rel="meta" type="application/opml+xml" title="OPML" href="http://yoururl.com/path/to/yoursubscriptions.opml">

dwight
June 21, 2003 6:12 AM

At the risk of starting another discussion on prior art, Radio Userland inserts a tag of this form (take a look at the source for http://www.scripting.com ): <link rel="subscriptions" type="text/x-opml" title="Subscriptions" href=" http://radio.weblogs.com/0001015/gems/mySubscriptions.opml ">

Adam Kalsey
June 21, 2003 7:01 AM

Well, then nevermind... :) That tag would work, although I'm not thrilled about the "subscriptions" part. There's nothing about OPML that says it can't be used for other things as well (like a blogroll).

dwight
June 22, 2003 7:39 AM

Oh, I should clarify. This opml file specifically describes the rss subscriptions for Radio Userland. I would assume that if you wanted to list your blogroll, then you would use rel="blogroll" in the tag.

This discussion has been closed.

Recently Written

How to advance your Product Market Fit KPI (Oct 21)
Finding the gaps in your product that will unlock the next round of growth.
Developer Relations as Developer Success (Oct 19)
Outreach, marketing, and developer evangelism are a part of Developer Relations. But the companies that are most successful with developers spend most of their time on something else.
Developer Experience Principle 6: Easy to Maintain (Oct 17)
Keeping your product Easy to Maintain will improve the lives of your team and your customers. It will help keep your docs up to date. Your SDKs and APIs will be released in sync. Your tooling and overall experience will shine.
Developer Experience Principle 5: Easy to Trust (Oct 9)
A developer building part of their business on your product needs to believe that you're going to do the right thing for them and their customers.
Developer Experience Principle 4: Easy to Get Help (Oct 8)
The faster you can unblock a stuck developer, the better their experience will be.
Developer Experience Principle 3: Easy to Build (Oct 5)
A product makes it Easy to Build by focusing on productivity for developers building real-world applications.
How to understand your product and your market (Sep 30)
A customer development question you can ask to find out who your product is best for and why they'll love it.
Developer Experience Principle 2: Easy to Use (Sep 28)
Making it Easy to Use means letting the developer do everything without involving you.

Older...

What I'm Reading

Contact

Adam Kalsey

+1 916 600 2497

Resume

Public Key

© 1999-2020 Adam Kalsey.