51 ms·
I think there's a simpler, better solution than Gemini, that is Markdown over HTTP. Accept: text/markdown,text/plain;q=0.9,*/*;q=0.1 I would love to see s
by rvense 6y ago
I think there's a simpler, better solution than Gemini, that is Markdown over HTTP.
Accept: text/markdown,text/plain;q=0.9,*/*;q=0.1
I would love to see support for this in blogging engines.
(Inspired by https://jcs.org/2021/01/06/plaintext https://jcs.org/2021/01/06/plaintext)
- kevingadd 6y agoThe lack of a consistent standard for Markdown is a big obstacle for this. Markdown comes in various "flavors" so you end up with a quirks mode nightmare as bad as IE6-era HTML, if not worse, and you sacrifice expressiveness as part of the bargain.
- nerdponx 6y agoHopefully the industry will continue standardizing on Commonmark. Maybe it should have its own media type? Accept: text/commonmark,text/markdown,text/plain
- donatj 6y agoPotentially unpopular opinion, but GitHub flavored marked down is almost inarguably the de facto standard, and the vast majority of markdown in existence is GitHub flavored. We should just embrace this.
- chipotle_coyote 6y agoIf we were going to really push this as a standard, this would make a lot of sense.
- nerdponx 6y agoCommonmark is pretty close to 1:1 compatible with Github Markdown as far as I know. And Commonmark literally is a standard with a spec.
- minitech 6y agoThat’s a simpler solution in the sense that there aren’t many steps to get there from existing tools, but the HTTP protocol is incredibly complicated compared to Gemini, and Markdown is complicated compared to Gemini’s rich text format too.