Web servers may be able to produce text/markdown responses directly instead of producing HTML. That can make archival and conversion simpler.
It adds a totally new code path to the extension though that maybe performs a HEAD request first to ask the server whether it supports direct Markdown rendering, then download that directly and rewrite image paths for the TextBundle. So there's added complexity.
As this server response is going to be used and ab-used by LLM's, it's likely that server admins will offer this endpoint to poison LLM's with a honeypot. Relying on rendered HTML in the browser may ironically then be the better option in the long run again.
Web servers may be able to produce
text/markdownresponses directly instead of producing HTML. That can make archival and conversion simpler.It adds a totally new code path to the extension though that maybe performs a HEAD request first to ask the server whether it supports direct Markdown rendering, then download that directly and rewrite image paths for the TextBundle. So there's added complexity.
As this server response is going to be used and ab-used by LLM's, it's likely that server admins will offer this endpoint to poison LLM's with a honeypot. Relying on rendered HTML in the browser may ironically then be the better option in the long run again.