4 ms·
- it's more work when you're trying to stop data exfiltration / espionnage - privacy -- I've no idea what the telemetry says about me today, and I ce
by cryptonector 5y ago
- it's more work when you're trying to stop
data exfiltration / espionnage
- privacy -- I've no idea what the telemetry
says about me today, and I certainly don't
know what they'll make it look for tomorrow
- privacy -- even if the telemetry is fine,
maybe information about my usage patterns
might be more valuable to me than it might
seem at first glance
- performance -- every app, every library, all
sending out telemetry? Please, no.
- because I get to not want this
- naikrovek 5y agono one cares what you do. telemetry is only viewed in aggregate. it doesn't make sense, nor is it a good use of time, to scrutinize the telemetry of a single user for any reason. you keep on living in your town where the people don't have fingerprints or names, and the shoes leave no tracks. I'll be over here getting things done, because doing good work is far more important than avoiding being seen.
- cryptonector 5y agoI gave you more than just privacy arguments. Can you address those too?
- naikrovek 5y agoit's not more work when trying to stop exfiltration or espionage because telemetry doesn't get sent to random places. Microsoft publish the hostnames that receive telemetry. block them and you block telemetry from being sent. it still gets collected locally though. the performance argument is solid and I will see if I can measure that before I agree with you. from what I've read, at least among the common telemetry systems I know of (Azure Application Insights, OpenTelemetry, and Microsoft's system built into the OS), telemetry is gathered for a bit then sent in a batch, which would indicate that performance is at least a consideration.