Thanks again @movq@www.uninformativ.de !! I have figured things out and set up Jenny and Vim completion following your blog post! Cheers!
Welcome @aelaraji@aelaraji.com!
What the heck is going on with the encoding here?! The feed’s Content-Type header does not include any charset, but I’m still relying on the official twtxt client to fetch and parse feeds. Haven’t noticed this with any other feeds. Where in the chain is this messed up? :-? Seems like the “space” is the Unicode line separator U+2028, that we use for newlines.
@aelaraji@aelaraji.com Nice, I can confirm it’s now fixed. I reckon the Content-Type: text/plain; charset=utf-8 did the trick. Something in the twtxt client must have incorrectly guessed ISO-8859-1 or something along those lines when there was no charset advertised in the response header.