Hacker News new | ask | show | jobs
by bunga-bunga 1042 days ago
I really wish we could have browser “Accept: text/markdown” for raw documents, but that boat sailed the moment we got CSS.
2 comments

If Gemini had picked markdown instead of gemtext I would've jumped in with both feet.

I get it though -- they're trying to resurrect gopher, which is what gemtext is a modernification of.

Still, I think markdown is our best shot at recovering the real web.

And yes, I know there's a standardization problem. Just pick a standard and run with it. Difficulty picking one is not a reason to pick none. And in case it wasn't obvious I'm talking about markdown without embedded html here.

Why though? We could have the browser apply the styles. And even allow user preferences to affect the presentation! kinda like firefox "article mode".

But that text/markdown would have to be restricted not to include any html tags, which are allowed in the "common" md spec.

Article mode isn't perfect and not compatible with non-articles. Markdown forces content to be just content.

> would have to be restricted not to include any html tags

The point of this would be to deliver pure content, so "any tag" would definitely not be allowed. My user agent would decide what to render and how.

> But that text/markdown would have to be restricted not to include any html tags, which are allowed in the "common" md spec.

Forbidding them is a one-line change to the spec.

It really annoys me that people keep bringing this up, as if they can't imagine "markdown with html disallowed".