In-reply-to » Not sure which conversation you mean, @eaplmx (it's already quite late here), but here's my take: I think twtxt it's not heavy enough. For a real feed format I would like to have a clear separation between titles and content. And more options for the content. Plaintext and HTML at least. Twtxt is plaintext, but lots of folks (me included) actually use markdown in their yarns. However, the actual format being used is not advertised anywhere. To make things worse, I actually prefer reStructuredText over markdown. For podcasts some enclosure-like thing would be nice as well. Twtxt being line based also really limits structuring of longer content by hand. Just can't produce a nice source file.

@lyse@lyse.isobeef.org

Twtxt is plaintext, but lots of folks (me included) actually use markdown in their yarns. However, the actual format being used is not advertised anywhere.

That’s a really good point. We should formalize a Markdown flavor as a format extension on https://dev.twtxt.net/.

yarnd appears to use gomarkdown with a few extensions. I’m not sure what else gomarkdown translates by default.

There should definitely be a concrete specification on what syntax should be supported by twtxt clients with “Markdown” support. cc @prologic@twtxt.net and @darch@neotxt.dk

⤋ Read More