Hacker News Reader

Comment by sylware | Hacker News Reader

noscript/basic (x)html can do wonders. But it is so stable in time, planned obsolescence is very, very hard to do: web scammers (or brain-washed web devs) don't like that with their absurdely huge and grotesquely complex google(blink/geeko) and apple(webkit) based browsers.

View on HN

I suggest a new meme: byoCSS (i.e. assuming classless html)

Perhaps there is already support for this via extensions.

I wonder if some flag (among a set?) could be placed within a basic classless html (and no js) page to call forth one or a number of user/user-agent controlled stylings.

This is how I imagine browser support for markdown could work. Plain text comes in over the wire and is rendered to taste.

You should check out Gemini[1]. That's basically how it works.

[1]: https://gemini.circumlunar.space/

Gemini sets a good example, but what I’m specifically advocating for is an incremental improvement to how we use the existing web. Fixing e.g. [1] (falling back to plaintext) should be trivial, and with that obstacle removed there would be nothing stopping early adopters from publishing in markdown today.

[1]: https://bugzilla.mozilla.org/show_bug.cgi?id=1319262

Perhaps advertise to the browser per se as plaintext, then have an extension look for a magic number or readable flag to indicate specific-markup-type, and translate from there more opportunistically.

Plaintext infrastructure; readable markup; optional (semi-automated?) styling from there.

(Perhaps your higher-up comment already suggests as much.)

I think you can just serve text/markdown and things that don't know the markdown subtype will just display as plaintext because of the text main type while things that do e.g. extension registering the mime type will render it. Would need to test to verify though.

Reply on news.ycombinator.com