Re: Bad-cert-domain on https://lua-users.org/lists/lua-l/

[Mouse <mouse@...>]

>>> lua-users.org does not as it stands do TLS (and never has): any web
>>> browser, search engine, plugin that assumes it does is broken [...]

>> Thank you very much for taking that stance.  [...]

> The problem is that today most browsers, if not all, are meant for a
> very tech-unsavy audience, who do know nothing about https vs http
> and the risks that are behind http (and when there are none).

That's the converse of the problem I see.  I was talking about the
server side of the HTTP(S) link, not the client side.  When I use the
Web (at home; at work, I use work facilities), I use lynx, a version
built without SSL (TLS, whatever it's called this week).

> That's where the market is, for good or bad.

And that it's seen as a "market" is, IMO, a significant part of the
problem.

> I, too, miss the times when Firefox allowed [...]

So, why not continue to run that old version when not doing anything
you need the newer support for?

Or for that matter why not pull over the source and build yourself your
own version, with whatever customizations you want?  That's what I did
with lynx.  If I wanted to run a bloated-horror Web browser at home I'd
do that with Firefox, or Chromium, or whichever one I picked.

/~\ The ASCII				  Mouse
\ / Ribbon Campaign
 X  Against HTML		mouse@rodents-montreal.org
/ \ Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B