|
|
|
|
|
by jbreiding
2339 days ago
|
|
This may be difficult to grasp. But likely where you are seeing this feature is in a corporate setting where you are the "end user", not the paying customer. The corporate entity that is making use of this feature is who you should be protesting the use to, not Microsoft. |
|
A feature that's MAYBE useful in a corporate setting to a hand full of people should not be a default defacto setting forced upon EVERYONE.
The issue isn't the feature... it's the default settings that enable invasive features.