They are insecure, because your ISP can change website responses and text format doesn't protect from that. So basically browser can't guarantee that you're looking at original web server response.

> the day UTF8 will be a fond memory of a big mistake we made

Alternative that would be better?

I actually agree, and kinda wished there was some sort of "binary" alternative to json that every text editor would open and let me edit as easily as json, because at the end of the day, it is no more binary than utf8 encodings with their number of bits, endians and confused line endings.

It rather supports the site's core point, because that point is about plain text files, not HTML and CSS. Plain text is as readable as it is possible to be.

Besides, this is exactly the kind of site HN constantly laments the loss of - unique, quirky, basic and rough around the edges.

Comically the use of curl | bash managed to shoehorn them in there, and there were the occasional terminal escape characters that could do funny and sometimes mischievous things.

There used to be something of a game of making specific files that would change screen colors or play songs off terminal bells, etc, tailored for specific terminals or command prompt windows. I remember a few short animated sequences using various backspaces and colors that only really worked if you could expect the text to be loaded at specific baud rates or in specific BBS software.

Weeeell... Ya say that, but:

Many years ago someone "infected" my computer with a "manual virus": A printed-out sheet of paper placed on top of the computer, telling me to delete all my hard drive's files myself, then photocopy the sheet and put both copies on nearby computers.

It was obviously a joke. But in the "modern" agentic era, the same thing in a text file is slightly more realistic as a threat...

You can block macros in Word, so you're only left with unformatted downsides?

No macro viruses but if your family lawyer uses some LLM-powered thingy in his workflow it might add a new dimension: prompt manipulation/injection attacks. A good spot to hide these would be at about ⅔ distance inside some wall of legalese at the beginning or end of a document since hardly anyone ever reads those.

I've known people one-shot by pure text, like Atlas Shrugged, The Communist Manifesto, The Bible, The Qur'an, The Selfish Gene, Godel Escher and Bach, etc. Don't underestimate text.

Just cURL it! j/k

not j/k.

I'd rather read in my beautiful gpu-powered terminal emulator than a website with bad taste and/or bloated nightmare under the covers.