2024-12-28 17:34:10 <crc         > note on the channel logs: I was informed of an issue with entries using non-ASCII characters. I've added .utf8 links to forth.chat which should serve with charset=UTF-8 for browsers that have trouble displaying them w/o this.
2024-12-28 18:37:42 <falsifian   > test: 你好
2024-12-28 18:44:36 <falsifian   > crc: Out of curiosity, why not just always include charset=utf-8 in the Content-Type header? I think a Content-Type of "text/plain" with no charset attribute means you're promising ASCII text.
2024-12-28 18:46:07 <crc         > I'm not sure how to set this in httpd(1) on openbsd; will be doing some research on that
2024-12-28 18:46:41 <falsifian   > crc: In my types { ... } block in OpenBSD httpd.conf, I have the following line:
2024-12-28 18:46:47 <falsifian   > "text"/"plain; charset=utf-8"    c cc tex txt
2024-12-28 18:47:03 <falsifian   > I found the weird quoting online somewhere. It seems to work.
2024-12-28 18:47:24 <crc         > The default log files don't have an extension to map to
2024-12-28 18:48:41 <falsifian   > Oh, I see. Thanks for explaining. I wonder if "" can be an extension.
2024-12-28 18:50:50 <crc         > I tried that; it doesn't seem to do anything