It doesn’t really matter if off-switches exist, the problem is that the features are there to begin with. In any piece of code, a switch is a point of added co

It doesn’t really matter if off-switches exist, the problem is that the features are there to begin with. In any piece of code, a switch is a point of added complexity. For ANY such toggle: - The switch might not be saved correctly. - There can be a regression where the switch stops working in the future. - The switch, despite being “saved” correctly and displayed by a reassuring checkbox in a GUI panel, might not actually be CONSULTED in all the places it needs to be consulted (resulting in default-on, default-off or “whatever the developer of that component felt like” in various components across the system). - There can be a regression in any one of the components consulting the switch in the future, leading to an inconsistent combination of things that may or may not check for this setting over time. When they give over 100 options, I assume 50 of them don’t work and that they have no real incentive to make sure the other 50 keep working. About the only thing you can trust is a single on/off switch for the whole thing, while simultaneously checking a bunch of low-level things (regularly blocking unwanted hosts, logging network activity, etc.).