There are plenty of people with old android phones with no free disk space using ancient browsers.

There are plenty of people still using windows 10 with updates turned off or wedged for whatever reason.

These people just use the sites that work. They aren't computer experts, and might not even realise why half the internet doesn't work - they just think that's the way things are.

Eventually you are making things worse for your vast majority of users when you have to e.g. make them install a native app for a video call or use a TLS version that is broken to support those Gingerbread Android phones

While I agree with your general gist and definitely your final paragraph,

> There are plenty of people with old android phones with no free disk space using ancient browsers.

How many people have 10 year old phones? I've got an 8 year old iPhone XR which I keep around as a backup/travel device because it's not worth selling, and the battery is… not happy even in airplane mode.

For me to have a 10 year old mobile browser, I'd have to have kept the iPhone SE 1 (or was it a 5c?) that I bought second hand in 2018, and not upgraded it since I bought it. I got rid of it because the battery wouldn't hold a charge for 10 minutes.

I've a Xiaomi Mi 6 phone (2017 model) that I still use as a fridge-mounted shopping list and it's using the latest version of Chrome. I think it would be quite the stretch to find a user using a 10 year old browser.

I am an expert and half the internet does not work. That's just the way things are

It's fine to support such configurations by accident, but you shouldn't try to support them intentionally. You will end up dropping support eventually regardless but the skeletons will live on in your codebase as tech debt.

The needs of the many outweigh the needs of the few.

I'm not sure this is a realistic use case to try and support. A 10 year old android phone likely has a battery life measured in 10s of minutes, and really isn't something we need to worry about.