To be honest, SQM is quite old (dates back to at least Office 2003), but the hosts file bypass does makes me feel bad if it is true. I just realize that a lot of the trolling is about the EULA and privacy policy though.
On WIn10 editions other than enterprise. You can still change it to basic which sends much less info though. Thinking about it, GWX probably will require a separate setting from the normal CEIP telemetry on Win7/Win8.1. GWX does compatibility checks in the background for the Win10 upgrade that require sending info to MS.
I am thinking of removing anti-discrimination laws completely (not just to create exceptions) and allowing regulators (such as anti-trust) to impose anti-discrimination conditions on specific companies instead.
Yea, it is frustrating to watch DRAM manufacturers profiting while MS had to fit Win95 into 4MB. Of course, this is not the only unethical tactics MS used to attack OS/2 later on. PX00307 mentioned "32-bit Windows extenders" while ignoring the problems.
IBM took the "old" OS/2 code (that both they and Microsoft had worked on) and tarted it up into OS/2 2.x and successors.
And after that MS attacked it using unethical tactics. And don't forget their attacks on DR-DOS, including Win9x dependence on DOS helping Caldera continue it's lawsuit against MS. Now you see why this is why one of my favorite topics.
The Workplace Shell also took more RAM too, which was a problem back in 1992. But it is still unfortunate that MS turned the OS/2 2.0 project into a fiasco.
Slashdot Mirror
Sounds like minor annoyances. My favorite MS fiasco from the 1990s is the OS/2 2.0 fiasco for example.
To be honest, SQM is quite old (dates back to at least Office 2003), but the hosts file bypass does makes me feel bad if it is true. I just realize that a lot of the trolling is about the EULA and privacy policy though.
gHacks article was later updated to mention that.
The hosts file bypass makes me feel bad if it is true, but thank MS for listing the hostnames at least.
On WIn10 editions other than enterprise. You can still change it to basic which sends much less info though. Thinking about it, GWX probably will require a separate setting from the normal CEIP telemetry on Win7/Win8.1. GWX does compatibility checks in the background for the Win10 upgrade that require sending info to MS.
Well, how does Android actually compare?
constant spyware problems
Not why Windows Phone failed.
The funny thing is that BITS is not supposed to do that, that is why it is called BITS.
Windows itself is not ad filled, and the telemetry data has nothing to do with ads.
What is actually wrong with the privacy policy that led you to disable it?
But this don't mean the data is getting actually sent.
Has been there since at least Office 2003 I think.
Actually, I think Win10 is better in that it makes the option to use a local account visible on the login screen.
FYI, see https://www.reddit.com/r/Windo... .
Someone managed to decrypt this traffic using Fiddler.
Yea, the problems with DRM. I wonder if iOS and Android does the same thing.
Does Win10 really send this stuff?
Win10 enterprise has the no telemetry option for a reason.
What is fun is that NSS still has not removed SSLv2 code thanks to RedHat.
Yea, this project has been facing delays due to the fact that VS2013 no longer supports Server 2003. Hopefully this will be fixed soon.
I don't think Google is that horrible. Even with Google+, I don't think Vic Gundotra is a bean counter.
OS X and iOS already picked SecureTransport years ago, which had it's own problems BTW (though with 10.11 it is finally getting better).
I am thinking of removing anti-discrimination laws completely (not just to create exceptions) and allowing regulators (such as anti-trust) to impose anti-discrimination conditions on specific companies instead.
Yea, it is frustrating to watch DRAM manufacturers profiting while MS had to fit Win95 into 4MB. Of course, this is not the only unethical tactics MS used to attack OS/2 later on. PX00307 mentioned "32-bit Windows extenders" while ignoring the problems.
IBM took the "old" OS/2 code (that both they and Microsoft had worked on) and tarted it up into OS/2 2.x and successors.
And after that MS attacked it using unethical tactics. And don't forget their attacks on DR-DOS, including Win9x dependence on DOS helping Caldera continue it's lawsuit against MS. Now you see why this is why one of my favorite topics.
The Workplace Shell also took more RAM too, which was a problem back in 1992. But it is still unfortunate that MS turned the OS/2 2.0 project into a fiasco.