In a forthcoming Windows 10 release, Microsoft will let you view the telemetry data that the OS collects via a new Windows 10 app called Windows Diagnostic Data Viewer.
Microsoft announced its commitment to "be fully transparent on the diagnostic data collected" from Windows devices today and the release of the application adds options to Windows 10 to view collected Telemetry data.
Microsoft says that it wants to increase trust and confidence, and give users increased control over the data.
[...] You need Windows 10 build 17083 or newer to access the new data viewer. You can access the tool with a tap on Windows-I to open the Settings application, and the selection of Privacy > Diagnostics & feedback in the window that opens.
[...] Diagnostic Data Viewer is a Windows application to review Telemetry (diagnostic) data that Microsoft collects on the device to send it to company servers for analysis.
Note: Microsoft notes that enabling the feature may require up to 1 Gigabyte of additional hard drive space for storage.
A click on the button launches the application's Microsoft Store page on first run. You need to install the application from there before it becomes available.
[...] You find options to export the data to CSV files and to open the Privacy Dashboard on the Internet and the Privacy Settings on the local device as well there.
Search functionality is available which you use to find specific event data. The app returns event data that matches the entered text. Type your name, email addresses, PC name, IP address or any other data that you can think of to run searches across all Telemetry data that Microsoft collected on the device.
While you may use the search for that, you may click on any event listed in the sidebar to access it directly. The data is quite extensive, especially if Telemetry data collecting is set to full and not to basic. I had hundreds of events listed on the Windows 10 Insider build PC after the update to the most recent version. It will take some time to go through the information.
(Score: 4, Interesting) by All Your Lawn Are Belong To Us on Friday January 26 2018, @01:55PM (1 child)
That's a little short sighted. How about noting that the collective customers of those companies do not respect freedom by continuing to support companies which use proprietary devices and software, over companies that "respect freedom" and use open source? If the customer, who is always right, did so, the problem would be solved. Instead, you expect the business to swallow the costs of losing competition to the business next door who uses proprietary software.
Gear change. You pay lip service to this, but what would you advise, say, a hospital to do when they need a particular clinical device, and the interface for that device is built by the manufacturer on Windows and is completely closed source, and there is no competitor who builds an open source product? Do they then tell patients, "We'd like to do this for you but the solutions we can offer are not open source so you'll just suffer, OK?" And at one remove: Let's say there is an open source competitor, but it costs $1,000 more and there is no insurance company who will subsidize that extra cost because there won't be. "Hi, patient, here's your XXX, but you will pay $1,000 more than we could have charged because we believe in your Freedom!" That hospital, if it were really advanced, give the patient the choice between the expensive open source and cheap proprietary, but it can be a foregone conclusion that a fully informed patient won't CARE about Open Source Freedom if it hits them in the wallet. If, instead, there is an open source solution that is in fact cheaper than a proprietary solution in the market, that is fine and should be used. Find me such a situation, and we'll find which hospitals are and aren't using it. (And I'm aware there may be such - I seem to remember a report about open source 3d-printable prostheses.... But I don't remember who takes liability for the design - remember that clinical practitioners must also have someone who takes liability for the reliability and usage of the device.) At any rate, you expect the hospital to just eat that $1,000, regardless of if puts the hospital in the red, because Freedom, right?
As to the developers, not my table. But if a developer has to eat, he or she is probably bound to the standards of their employer. If they're on their own, a lone developer, they get the choice... moderated by if they are consultants again they follow the tune of the manufacturer.
This sig for rent.
(Score: 4, Interesting) by Wootery on Tuesday January 30 2018, @01:48PM
Good post. In short: Free Software idealism often collides with reality. For all its faults, the closed/non-free/proprietary payware model gets shit done, and in many domains, FOSS turns up essentially empty handed.
All else equal, I'd certainly take Free over non-Free - it's one of the reasons I use Firefox - but Stallman disciples often forget that very often, the choice is between non-Free and nothing at all.