(#3j7ucpa) @aelaraji Hello and welcome. 👋 Replies are not part of the original twtxt spec but extensions of Yarn.social. You can read up on those extensions over here:

(#3j7ucpa) @aelaraji Yep, it works. Looks like this in my client:

(#jmbfhca) @aelaraji Ah, you’re welcome. 😅 (I’d still prefer it if there were some more alternative clients. There aren’t a lot to chose from at the moment. 🫤)

(#jmbfhca) @movq Oh wow! We have new blood 🤣 Welcome @aelaraji 👋

(#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. Maybe WTF-8 encoding!?

🥳 NEW FEED: @aelaraji

(#obpx6pa) @aelaraji It depends 🤣

(#nlzhexa) @aelaraji I've also been using pass/gopass for years now and loce it 👌

(#gtqdgla) @aelaraji Yeah we use the Unicode new line character to represent "new lines"

(#lbyemiq) @aelaraji I'll inspect your feed later and see if I can work out wtf is going in 🤣