(#jsj23rq) @anth@a.9srv.net (I’m also a bit confused by the UTF-8 topic. I thought that the original twtxt spec has always mandated UTF-8 for the content. Why’s that an issue now? 😅 Granted, my client also got this wrong in the past, but it has been fixed ~3 years ago.)

(#zloep2q) @lyse@lyse.isobeef.org Ahh, I see. So it’s not really a drama. 😅

(When the spec says “content is UTF-8”, then it kind of follows for me that I should set Content-Type: text/plain; charset=utf-8. Lots of feeds don’t do that, though, which is why jenny ignores the header altogether and always decodes as UTF-8.)