[Endy]

That's not what I'm getting at. I believe in crystallized design. Once something is fixed, don't go breaking it. If any changes for any reason break something I need, I'm not introducing those changes into my system, because I need it to work, and I need it to work the way it works right now on my setup - not the way some other fool thinks it should work in the future. So yes, I do believe that something I installed 8 years ago, which has worked perfectly for the last 8 years and has become foundational to my workflow, needs to continue working the exact same way it has.

[stouset]

I’m fine with this as long as your device is forcibly removed from the Internet when security fixes aren’t installed, or when it’s out of the period where the vendor provides security patches.

[Endy]

I disagree. I should be allowed to take on the burden of my own security. I don't want an outside force trying to pretend they know my needs better than me. You can produce a product, and I, the user, should have 100% decision on how and for what purpose I will use that product.

[stouset]

Sorry, but this mentality is the same one that would argue that any vehicle should be road-legal, even if it hasn't passed a smog inspection, doesn't have working brake lights, and its turn signals are green and purple.

If you want to use shared infrastructure, you have to abide by a minimum set of requirements that ensures the safety of everyone else around you, end of story.

[Endy]

Then make sure there's a way to preserve all settings and function from older versions. Tell me if I'm using something "unsafe", let me get it out of the way once and then leave me alone. Don't cut out functionality, don't change the UI, don't break what wasn't broken.