6 ms·

Really cool idea Humans get HTML, bots get markdown. Two tiny tweaks I’d make... Send Vary: Accept so caches don’t mix Markdown and HTML. Expose it with a Li

by burcs 1y ago

Really cool idea Humans get HTML, bots get markdown. Two tiny tweaks I’d make... Send Vary: Accept so caches don’t mix Markdown and HTML. Expose it with a Link: …; rel="alternate"; type="text/markdown" so it’s easy to discover.

yawaramin 1y ago
This person hypermedias
Rohansi 1y ago
Would be nice for humans to get the markdown version too. Once it's rendered you get a clean page.
- captn3m0 1y ago
  I’ve been asking for browser-native markdown support for years now. A clean web is not that far, if browsers support more than just HTML.
  - lelanthran 1y ago
    > I’ve been asking for browser-native markdown support for years now. A clean web is not that far, if browsers support more than just HTML. You can always do the markdown -> DOM conversion on the client. Sure, there's a bit of latency there, but it means easier deployment (no build step involving pandoc or similar). Browser-native markdown support would be better though; you'd get ability to do proper contenteditable divs with bold, italic, etc done via markdown
    - captn3m0 1y ago
      To get broad support from the server side, you’ll need to showcase high browser support. We need Wordpress and Wikipedia and Ghost to support this, and that won’t happen without native browser support.
      - lelanthran 1y ago
        > We need Wordpress and Wikipedia and Ghost to support this, and that won’t happen without native browser support. It can. Unlikely but possible. A good first step would be to have a well-written web component to be used like this: `<markdown>...</markdown>`, with no support at all for a build-step. The .js file implementing this should be included directly in the `<head>`. If that gets traction (unlikely, but possible) then the standards would sooner or later introduce a tag native to the browser that does the same thing.
        piquan 1y ago
        [dead]
  - xigoi 1y ago
    Markdown is not standardized, so every browser would render the page differently and you’d get the same problems as with pre-standard HTML.
    - captn3m0 1y ago
      Browsers can take standards position on CommonMark extensions and decide on a baseline that goes into the W3C spec? It will just converge on the lowest common denominator and that’s good enough for the vast majority of content reading usecases.

by burcs 1y ago

yawaramin 1y ago

This person hypermedias

Rohansi 1y ago

Would be nice for humans to get the markdown version too. Once it's rendered you get a clean page.

captn3m0 1y ago
I’ve been asking for browser-native markdown support for years now. A clean web is not that far, if browsers support more than just HTML.
- lelanthran 1y ago
  > I’ve been asking for browser-native markdown support for years now. A clean web is not that far, if browsers support more than just HTML. You can always do the markdown -> DOM conversion on the client. Sure, there's a bit of latency there, but it means easier deployment (no build step involving pandoc or similar). Browser-native markdown support would be better though; you'd get ability to do proper contenteditable divs with bold, italic, etc done via markdown
  - captn3m0 1y ago
    To get broad support from the server side, you’ll need to showcase high browser support. We need Wordpress and Wikipedia and Ghost to support this, and that won’t happen without native browser support.
    - lelanthran 1y ago
      > We need Wordpress and Wikipedia and Ghost to support this, and that won’t happen without native browser support. It can. Unlikely but possible. A good first step would be to have a well-written web component to be used like this: `<markdown>...</markdown>`, with no support at all for a build-step. The .js file implementing this should be included directly in the `<head>`. If that gets traction (unlikely, but possible) then the standards would sooner or later introduce a tag native to the browser that does the same thing.
      - piquan 1y ago
        [dead]
- xigoi 1y ago
  Markdown is not standardized, so every browser would render the page differently and you’d get the same problems as with pre-standard HTML.
  - captn3m0 1y ago
    Browsers can take standards position on CommonMark extensions and decide on a baseline that goes into the W3C spec? It will just converge on the lowest common denominator and that’s good enough for the vast majority of content reading usecases.