@david@daiwei.me Sorry, I’m not seeing what you’re saying? 🤔

@david@daiwei.me I see it now. Is this also a problem in the app too? Or just yarnd or both?

@david@daiwei.me Kk I’ll look into it 👌

I think the problem here is that (i.e: <foo>) is being treated as HTML, which the browser renders as nothing, because that’s not even a valid element it understands how to render. Hmmm 🤔

Ahh no I was wrong. this is being stripped at the Markdown parsing level due to “unsafe” HTML. Which of course is a bit hard to tell between what is safe and unsafe HTML.

Okay I’m fixing this in lextwt, yarnd and twtxt.app (takes a different path). Soon you’ll be able to write shit™ like (<this>) and it’ll get escaped and rendered correctly on the page. Basically you are really writing HTML here, but not intending to do so, Twtxt never supported HTML, and I don’t think it ever should. We extended the format to support basic Markdown, and I think that’s where it should end.

Probably time we wrote a Spec for this really.

@david@daiwei.me This has now been fixed! 🎉