zaterdag 7 augustus 2004

Why use content:encoded?
My aggregator, Radio, doesn't read the content:encoded element in RSS feeds. I wish it did, because for some reason, some weblogs create feeds that split up the contents of the items and put the full text in that element.

Those blogs put the first few words, or an excerpt, in the description element. The rest of the item is placed in the content:encoded element. That element uses pure HTML, placed between special tags. Somebody told me, before I learned well about RSS, that the use of that is being able to use HTML in your feed. But that's not true!

No, I mean, it's true, but HTML can also be used in the description tag. Just encode the <, & and > characters and you're done. I suppose every XML developer knows this, so why does everybody keep using that dreadful content:encoded element?

What's the use?
  11:54:14 PM    comment []  trackback []

Feedster magic
Hey, that's great. This week I started two new blogs, using this Radio UserLand installation. One is the blog you're reading now, the other is a Dutch blog about development.

Both of them are already indexed by Feedster. I found this out by looking for Breuls, and noticing that both blogs appear in the results. I think that's great. Apparently Feedster just keeps looking and looking voor new feeds to add to the index. The fact that I got indexed within a week without having to fill in a form myself, gives me the impression that Feedster is very reliable.
  12:15:59 PM    comment []  trackback []