> "Local accounts" is perfectly apt name. "Local accounts" doesn't come close to implying "can't join the internet" either, although "offline accounts" might.
You have a higher opinion of the "typical" end user than I do. "Local" invites the question "local to what?" and "as opposed to what?". When the other option is "online account", then yes even "local" leads to "can't use on the internet" to certain types of users.
Burying a power user feature to avoid confusing inexperienced end users is justified. The argument over whether or not "local accounts" or "offline accounts" are a power user feature is a more interesting argument. I do think that if we can't come up for a name for them that isn't confusing to inexperienced end users, than that's at least one indicator that it may be a power user feature.
> The pain point about telemetry is that Windows is a paid product and there shouldn't even be such a thing in a product that people pay for.
People want data-driven improvements in paid products, too. (Would you rather Microsoft just blindly make changes? What are the alternatives? Go back to waterfall and nothing but overly detailed and over-engineered specs of what some PM thought was a good idea because they heard it from some rich Enterprise client at a tech conference three years ago?)
There are tons of paid products with telemetry. It's been highly upvoted advice here on HN, to do things like A/B testing, and metrics-driven development. Lots of paid products have telemetry (including Apple's and Google's).
"Paid products" is another amusing double standard I'm going to add to my list for telemetry complaints. "What's good for the startup goose, is not good for the old tech gander." --HN commenters, probably
> And although there might (now) be settings to control telemetry, what good are they when Windows updates reset all settings regularly?
There were always settings since Windows XP. The only thing Windows 10 did was change them from opt-in to opt-out by default. Microsoft then responded to arguments that the settings weren't granular enough, so now there's dozens more settings with pages of documentation each (and an explorer tool to log and examine collected telemetry data, if you wish).
The resets were bugs in the upgrade process that have generally been fixed since. Microsoft has been taking settings resets seriously, and absolutely considers them bugs. The way in-place upgrades work, migration scripts missing settings is a problem. Microsoft's "Beta" program (Insiders) is sadly not setup to find telemetry reset bugs because they need the telemetry most of all in Beta testing, so I feel it's understandably unfortunate that so many telemetry settings reset bugs have made it into production.