3 ms·
The issue says nothing about what data is being sent. How does the poster know it's telemetry data? Maybe the initialization code when the CLI is run checks to
by caleblloyd 7y ago
The issue says nothing about what data is being sent. How does the poster know it's telemetry data?
Maybe the initialization code when the CLI is run checks to see if the CLI is up-to-date.
The Netlify CLI is for deploying your sites to Netlify. Sooner or later it's going to call a Netlify API, I don't know why the expected behavior would be otherwise.
- Operyl 7y agoIt's sneak, he's always complains about things like this in, at least my opinion, overly dramatic fashion[1][2]. [1] https://sneak.berlin/20190929/keybase-backdoor/ https://sneak.berlin/20190929/keybase-backdoor/ [2] response from keybase https://github.com/keybase/client/issues/20022#issuecomment-536355032 https://github.com/keybase/client/issues/20022#issuecomment-...
- yellowapple 7y agoThe comment chain goes into further detail about what data does get sent.
- Operyl 7y agoYup, after I read this comment I dug into it out of curiosity. If I had to guess, like I mentioned on the issue, it seemed like it was probably sent as a way to purge previous analytic data.
- sneak 7y agoI will bet you any amount of money that’s not the case. Go read the CV of the guy who put the “force: true” on that telemetry call, so that it sends telemetry even as it knows you have opted out of telemetry.