3 ms·
They used to gather all command line arguments until they later decided that (oops!) it's "not acceptable per our privacy policies"[0] and they really shouldn't
by ptx 2y ago
They used to gather all command line arguments until they later decided that (oops!) it's "not acceptable per our privacy policies"[0] and they really shouldn't have been doing that. They have also had issues with anonymization not being implemented properly, the opt-out mechanism not working in some edge cases, forgetting to even tell users about the need to opt out, and who knows what else. The risk of accidentally exfiltrating your data one way or another seems pretty high.
Also, monetary value is not the only reason you might want to keep information private.
[0] https://github.com/dotnet/sdk/issues/6145#issuecomment-220105007 https://github.com/dotnet/sdk/issues/6145#issuecomment-22010...
- neonsunset 2y agoThe issue dates back to the release candidate of the second version of .NET Core, 8 years ago. Surely we can do better than "it used to be bad at x point in time and this can never be rectified". I like my privacy more than the next guy, but you are not arguing in good faith (which is all too common, because people like to use much inferior technologies and make .NET a scapegoat, instead of learning better and ceasing idiotic self-sabotage) Edit: Heh, in HN jail. In response to the comment - you should apply this logic to the languages steered by Google, Oracle and Apple. .NET is completely unrelated to Recall and whatever happens to it, it could have been as well a separate company.
- macintux 2y agoMicrosoft does not make it easy to give them the benefit of the doubt. See, for example, the Recall debacle. https://doublepulsar.com/recall-stealing-everything-youve-ever-typed-or-viewed-on-your-own-windows-pc-is-now-possible-da3e12e9465e https://doublepulsar.com/recall-stealing-everything-youve-ev...