37 ms·
>> while the reason they aren't turning it on could be they are lazy and don't want to do any extra work > Why would you assume that? I didn't assume it, I sa
by mattmcknight 4y ago
>> while the reason they aren't turning it on could be they are lazy and don't want to do any extra work
> Why would you assume that?
I didn't assume it, I said "could be".
> I think most people care and wouldn't turn it on if asked to.
If people don't like it, they can turn it off. Are you assuming most won't if asked to?
- bheadmaster 4y ago> If people don't like it, they can turn it off. If telemetry is opt-out, there's a good chance most people won't be aware that it's even there - that's deceptive. At the very least, there should be a big scary banner saying "your data is being sent to our servers" on every single command - that's the only way you can assure that everyone who uses the tool will be informed. > Are you assuming most won't if asked to? The big argument to opt-out telemetry is that "opt-in doesn't work", so yes, I'm assuming most won't. If my assumption is wrong, why not just ask people? They'll say "yes" anyway.
- mattmcknight 4y ago> At the very least, there should be a big scary banner saying "your data is being sent to our servers" on every single command - that's the only way you can assure that everyone who uses the tool will be informed. It should probably say- "Ensure that the functions and libraries you use continue to be supported by sharing your usage statistics." > If my assumption is wrong, why not just ask people? They'll say "yes" anyway. There's not really a great place to ask, but it could be a checkbox in the installer, sure.