No, that is the problem. They worked with less and less websites until there were none left. I needed to install some packages, which I could just put on my own server.
And I have an old Blackberry Bold that now show current electricity prices, so I know when to starte my washing machine. That can also run on own webserver.
Technically the certificate issues are separate from the protocol versioning. It's just that clients that don't support TLS 1.2 often also don't support sha2 certificates or may not have a path to validate certificates from currently available CAs (although you can usually push through that; no protocol support and no cert signature support is not a user bypass prompt)
As a side note, barely anything supports TLS 1.1 but not TLS 1.2
And I have an old Blackberry Bold that now show current electricity prices, so I know when to starte my washing machine. That can also run on own webserver.
https://gitlab.com/nelgaard/elpriser