Re: Sounds OK
"not everything is life or death", exactly.
I already have to rename "peculiar" file extension to .txt just to get some browsers to download them at all (anything that isn't found in their list of extensions for special handling might as well not exist). So here is the scenario:
Some enthusiast has set up an http site documenting everything you could ever want to know about some obscure computer from the 70s. (alternatively, a homebrew computer with exactly one instance. Yes, I know of such, and if you do too, please don't name it here lest it be SlashDotted, er, Registered)
As an extra thrill, they actually have a restored instance of that rare beast serving that site.
Now, completely aside from the question of how long there will be more than one browser, and how mere mortals can use Let's Encrypt without professional help (putting themselves at the mercy of that professional help forever), who gets to patch a webserver from the 90s to run on a system that runs http just fine, but has something like 512K of RAM and has not had an OS update since everybody was doing the Macarena
Not another fan of this system finds this wondrous trove and make a page with links to all that lovely content (http links, of course), and publishes that page on their own "managed" site, using https because that's how it came. Bingo! "No old .txt for you!"
If you try to do the obvious, and just serve that page of pointers on http, you have just become invisible to <major search engine> that will put you (f it shows you at all) a few hundred pages behind pages serving JS bitcoin miners. So the _third_ fan will never even know this cool site exists.
Just a mix of opinions and thought-experiments from someone who would really like to know why slick corporate malware is OK, but amateur "created with ed" websites are clearly the devil's spawn.
Biting the hand that feeds IT
