> The issue here is not due to Let's Encrypt, it's due to these devices, like so many others, not being designed to be maintained for the long term. How so? I

> The issue here is not due to Let's Encrypt, it's due to these devices, like so many others, not being designed to be maintained for the long term. How so? Is www.google.com or www.bing.com doesn't work on those devices? Why are you putting the blame solely on the devices, completely ignoring the fact that Let's Encrypt is an advocacy group whose sole intention is to make non-SSL-based HTTP obsolete? Keep in mind that HTTP has no reason to ever stop working on such old devices! Noone's asking for indefinite support of old software. What we're dealing here is intentional device obsolescence, where the SSL protocol -- entirely optional if all you care about is reading text and watching pictures of cats from random anonymous sources -- is intentionally being used in such a way as to not be backwards compatible, by preemptively removing support for the earlier devices?