tkanos https://twtxt.net/user/tkanos/twtxt.txt Remove
eaplme https://eapl.me/twtxt.txt Remove
eaplmx https://eapl.mx/twtxt.txt Remove
lyse https://lyse.isobeef.org/twtxt.txt Remove
prologic https://twtxt.net/user/prologic/twtxt.txt Remove
rrraksamam https://twtxt.net/user/rrraksamam/twtxt.txt Remove
darch https://neotxt.dk/user/darch/twtxt.txt Remove
shreyan https://twtxt.net/user/shreyan/twtxt.txt Remove
movq https://www.uninformativ.de/twtxt.txt Remove
bender https://twtxt.net/user/bender/twtxt.txt Remove
stigatle https://yarn.stigatle.no/user/stigatle/twtxt.txt Remove
darch http://darch.dk/twtxt.txt Remove
xuu https://txt.sour.is/user/xuu/twtxt.txt Remove
jason https://jasonsanta.xyz/twtxt.txt Remove
mckinley https://twtxt.net/user/mckinley/twtxt.txt Remove
eapl-mes-7-daily-links https://feeds.twtxt.net/eapl-mes-7-daily-links/twtxt.txt Remove
lyse
Reply to #jmbfhca
Welcome @aelaraji!
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.
3 months ago
💬 Reply
lyse
Reply to #jmbfhca
@aelaraji 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.
3 months ago
💬 Reply