300
I’d like to know how the ODF-converter blog was created, as it is so tantilizingly near being valid that there clearly is some significant attention to detail going on here, likely with some last mile problem. I’m pleased to see that there is a valid Atom 1.0 feed I also see that they also provided a valid RSS 1.0 feed for people who haven’t upgraded their aggregators in the last few years.
Truth be told, most people will be able to consume either feed format roughly equally in the majority of cases, though one choice will more consistently and interoperably be able to handle titles that contain ampersands, content that contains relative URIs, as well as a number of other edge cases. Hopefully we will be in a similar state in a few years with regards to Office XML formats.
I do wish that they would correct the type attribute in the autodiscovery link for their Atom feed.
On the FF2 front, I wish the developers of FF simply said that “yes, content sniffing sucks, but given that those who produce feeds honor HTTP content-type more in breach than in practice, it’s the best approach that they have come up with so far for the casual user”. And then proceed to provide either an about:config option for the super-geeky, or some additional documentation on how to registerContentHandler something that resumes processing the page as if there were no content sniffing involved at all.