Yes, I can attest to this first hand, as I am one of those unlucky individuals who cannot server RDF, or RSS with the appropriate content types from my domains which are hosted at Interland :( I think we need a low tech solution to these problems that can be deployed right now and be effective right now. The script that I proposed yesterday is just such a solution. It seem to me that the W3C arguing that we have a starndard that if everybody uses correctly will solve the problem, but then ignoing the painful fact that everybody can not and\or will not (for whatever reasons) use their standard, does not help at all. But what it does do is to work against a real solution emerging ...Manipulating metadata in Web servers is a big problem, yes. However, most *do* allow setting content-types and other headers if there's even a minimal amount of administrative access (cacheability headers are also an area that suffer because of this). Worst case scenario, a CGI or other server-side script can be used to set the Content-Type...I strongly disagree. Most hosted situations do not, by default, allow for .htaccess manipulations. They indeed SHOULD allow for this but out of the box most do not. So if we're going to help the thousands of users out there we need to give consideration to the reality they're working within.