@alyssa @aescling Not RSS, but https://blog.aescling.cat.family/atom.xml shows things to curl, though FreshRSS reports a blank content-type and empty body. (Curl reports application/octet-stream which feels not-ideal but also I don't think that should break.)

@aschmitz @alyssa i’ve tried impurroving it; Content-Type is correct, e.g.

@aschmitz @alyssa w3c validator likes it now

@aescling @alyssa I'm very confused. I still get the same errors from my feedreader. Firefox and it both hang waiting for the server for (according to FF) about 9 seconds when trying to fetch it, but curl is more or less instant. I don't *think* it's relevant, but I'm not really sure what a feedreader is supposed to do when confronted with "X-Robots-Tag: noindex" on an Atom feed, and certainly "not read it" seems like it's a plausible answer?

@aschmitz @alyssa yeah. the latency is an issue i’ve been having since switching from s6-networking’s TLS stack to a standard nginx reverse proxy, i wonder if that has something to do with it

or it could be the header, which i’ve just blanked out (my httpd can’t currently remove headers that it is configured to serve domain-wide)

@aescling @alyssa Same errors here even with the updated header, no idea why, but I'm not in the best position to debug it right now either. 😕 Thanks for trying!