![]() ![]() The web was created as a way to access documents consisting of text, images, and links to other points within the current document or to other documents. VLC plays videos in zip files and RetroArch plays games in zip files, for example.Īnd I don't think reading a book and browsing the web are fundamentally different activities. "Our program for handling HTML+CSS content should handle HTML+CSS content stored in containers" is a much more reasonable idea than "Our program for opening containers should also handle whatever content is inside those containers." It's a common thing for programs to do. Until that's the case (or, you know, until there's no data being siphoned.) I can do my work on Linux just fine, I don't need no damn WSL :-). A blog post that says we totally don't spy on you is something that you can breach without any real consequences. That's why I insist on "legally binding". I sure as hell expect that, if Microsoft breach the terms of doing business, someone can go knocking at their door and the best they can hope for is an out-of-court settlement that ruins them. by using a pirated copy), there's a good chance that some DMCA organization comes knocking at my door and the best I can hope for is an out-of-court settlement that ruins me. I'm just sayin' - if I break the terms of doing business with Microsoft (e.g. "Makes the product better" is a great reason and I'd wholeheartedly support that, as long as I had an assurance that my data is handled responsibly. If I make a purchase, I'd like to be sure that the reasons why I made it remain valid for a while. An OS or a piece of hardware is something that you don't switch that often. * For a large system or a piece of hardware, if I can have a reasonable assurance that, at least in the short-term (1-2 years), the data won't end up being used for ad targeting. ![]() based on public, legally-binding statements from Microsoft) that, for instance, a Microsoft employee who has a beef with me won't be able to stalk me based on that data? * The processes and criteria for who gets to access that data and in what manner are clear, transparent, enforceable and can be subjected to appeal by any user. Five years' worth of data, even if it's not strictly speaking personal data, can make identity theft trivial. 30 days of full data + maybe an year of relevant analytics (but no detailed data) are more than enough to improve software. * It has a retention policy that ensures a data breach five years down the road won't compromise five years' worth of relevant data. My two cents, I think telemetry is OK if: Not parent but it's something that's been bugging me for a while (especially since I work in a field where you often have to debug based on field logs from three weeks ago from a device halfway across the world). ![]()
0 Comments
Leave a Reply. |