toastal

Then will you bring a Markdown flavor that supports tables, abbreviations, admonitions, imports, and more out-of-the-box features? That's my biggest concern more than syntax A vs syntax B.

Ah, that is reasonable :vulcan_salute: (this said, abbreviation support I think is a good accessibility feature)

I hope there isn’t like a filesystem limitation. It would be awesome if the support was there so you could have `résumé-builder` or `β-reduction`.

Regardless, I think there is room to spell out the English in the spec a bit more clearly. …And add some clarifying test cases like `hammer-of-þórr`.

Actually I think there would be something important to bring up: Unicode confusion. This is Latin `a`, this is Cyrillic `а`. These can be used in certain attack vectors that...

@f-f @JordanMartinez I’m happy y’all got back since it _does_ seem this is a can of worms indeed & should be clearer in the spec docs. Personally, I like the...

Sounds like we at least have some new test cases + descriptions to add regardless 😅

A quick *phase 1* could be hosting the `highlight.js` files on the project's domain so that it's first-party code and can be trusted to a greater degree. A *phase 2*......

Maybe? I've used OCaml to do syntax highlighting using a custom Lambda Soup script, but I'm not sure what's the best way to handle in this sort of environment. If...

What? How about eliminating the flags so this becomes a non-issue instead of going down an tangential, but ultimately unrelated etymological path? Flags are for nations. Languages aren't nations. Flags...