(#jmbfhca) 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.