I agree that vetting a story is essential. One rebuttal is not nearly enough. Instead of other tech sites just regurgitating the same story it would be a breath of fresh air if they did their own investigation into the matter. If the tester was an amateur who had produced total garbage and the reporter also acted like an amateur - call them both out, but also prove it.
He did come across as rather, well, cross that zdnet guy...
The litigation I'm still involved in doesn't affect me financially; however, the guy who's paying the bills has spent approximately $180,000.00 so far and it's not over yet. When all is said and done, we'll win, but the cost will have been way too high.
Thanks to Gordon Kelly's persistence, Microsoft has responded and seems to be yielding to the "amateurs"' claims... somewhat. From what I gather, they'll be giving more control over what data is sent back. But it seems like it might only be for Enterprise.
LinkContacting me again a Microsoft spokesperson explained the company now wanted to speak about the issue. In short: Microsoft is taking action. It has decided to release updates “later this year” which will enable users to fully control all background telemetry and data tracking and, if desired, disable it completely. Microsoft also asked me to stress that disabling these background operations is something it would “strongly recommend against”.
One thing that needs pointing out is that as Insiders, we need to cede control to Microsoft. In order to become an Insider, I signed off on Microsoft's requirements. Thus, I have nothing to quibble about as far as privacy goes.Other important takeaways from Microsoft’s telemetry U-turn? While it may change in future, for now full control over telemetry is currently only being brought to Windows 10 Enterprise. This means users of Windows 10 Home and Pro, typically consumers and small businesses respectively, will still need to cede control. Whether you like it or not, Microsoft spells this out in the Windows 10 EULA – its house, its rules.
Other than that, several someones have problems with their HP printer drivers (I haven't checked mine yet). So far, my Brother Laser printer's drivers have to be reinstalled with each new Insider Build and I don't like that.
That said, the July 29 RTM and the November RTM are horses of a different color. At the very least we need control over drivers installed on our systems when Windows 10 RTM updates! As with the Insider builds, we need complete control over our drivers!
The bottom line, though, is that if we disable all of Microsoft's telemetry, we don't get our systems (whether they be Insider or RTM) updated.
I asked for detailed information indicating WHY the claims in the article are incorrect -- and have received NOTHING along those lines.
We have folks here who brand every article slamming Win10 or MS as inflamatory -- or worse -- but it would be refreshing to actually see someone come back with facts that clearly indicate why the claims in the articels are false.
Just like claiming something is true doesn't make it so, claiming something is false also does not make it so.
One claim is that the article writer didn't know anything about networking. OK, so if that is true, tell us WHAT the writer wrote that was incorrect, and WHY it was incorrect.