Hacker News new | ask | show | jobs
by throw555chip 938 days ago
> the stacktrace can end up on someone's desk

This is chillingly scary and one reason why I use Linux desktop.

2 comments

It certainly is. And every time a program is forced to have the crash reporting be opt-in because of the region I live in, I sing Ode to Joy. Don't get me wrong I'm no invasive telemetry enthusiast.

But I wouldn't mind being _able_ to make that choice for some projects I trust. If it were up to me, Linux maintainers would be looking at enough (opted-in) user stacktraces in their code that they'd start thinking of syzbot* fondly.

(* Fuzzer that Linux maintainers love to complain about due to the deluge of rare bugs and crashes it drops on them)

A number of Linux distros and software have automated bug reporting tools, they just tend to require an explicit confirmation before submittingn anything.

E.g. there's Ubuntu's Apport, Fedora's ABRT, KDE's Dr. Konqi.

Microsoft has good protocols around this to respect people's privacy and devs can only temporarily have access to them.
But this is all according to the goodwill of Microsoft, who may very well use it for other purposes for any reason and you'd never know.
>But this is all according to the goodwill of Microsoft

No, there is a privacy policy and they would get in legal trouble if they violated it.

How would anyone know that? Is anyone checking on them? There’s been plenty of instances of companies breaking their own, even legally binding, word
I haven't read the privacy policy (who does?) But I am willing to bet that it doesn't restrict MS to these purposes and in fact allows them to do whatever they want for any reason.
So devs can see what I've been upto on my own computer.

I assume the problem is the default is "send" rather than "don't send"?

>So devs can see what I've been upto on my own computer.

If you consent to sharing the error with Microsoft. It may contain some information about what was running to assist with finding the issue. There is a strict privacy policy for what this data is allowed to be used for.

>I assume the problem is the default is "send" rather than "don't send"?

No, unless an admin changed the policy.

Ahh, if the default is don't send and it's just an option then I don't see what the problem is