Why don’t browsers know how to render a Markdown content-type yet, all by themselves? It’s ubiquitous now and it’s not like it’s hard to parse, but every site has to translate it into HTML itself for the browser.
There are many flavours and extensions of markdown. For example rendering of a table is not part of the standard. How newlines are handled also differ.
to have all browsers support this, this need to be made into a web standard. And all agreed by different browser vendors (like chrome, safari and firefox).
right now this might be best handled by browser extension first.
Why can’t I just write this up as a PR to Firefox and stand a snowball’s chance of getting it merged, though? Everything’s somehow simultaneously extremely stodgy and completely beholden to whatever Google decides to ship this week.
yas! do it
The autistic community has been dying for this kind of accessibility accommodation for years.
I cannot express how deeply this angers me. Though i am happy to exploit the fuck out of this for personal use.
“Markdown offers a cleaner, more semantically clear representation of the content. This means less noise for
language models and other text-analysis systemspeople that process information neurodivergently, resulting in more efficient processing andpotentiallylowercompute costsreal life physical exhaustion.“don’t “reader” views in web browsers essentially accomplish the same thing?
My brother, this is not just autistic people. Everyone wants this. Except the people who make the sites, because all that noise is how they make money.
If you look at a private blog, they’re usually devoid of much noise.
MD is a nearly ideal format. I keep my personal notes and time management stuff in Obsidian using markdown. Write my blog in Markdown. AsciiDoc is nice, too, for certain use cases.
Does this mean that if I pretend to be a bot, I can access any cloudflare site ad-free?
“Prove that you’re a bot by factorising this large number.”
