You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 3, 2023. It is now read-only.
Why is this still opt-out rather than opt-in?! It's very annoying and just plain wrong!
So the user can disable the metrics package, but this is AFTER he has already run Atom the first time having metrics send information the first time it is run.
Even if all the data is out in the open, this seriously needs to be opt-in, not opt-out!
Would you please take this issue serious and look at all the complaints about the issue.
Super! Because I tested a fresh install of Atom beta. Before the user can disable the metrics package, data is sent to Google upon the very first activation of Atom.
This issue has been automatically locked since there has not been any recent activity after it was closed. If you can still reproduce this issue in Safe Mode then please open a new issue and fill out the entire issue template to ensure that we have enough information to address your issue. Thanks!
lockbot
locked and limited conversation to collaborators
Apr 5, 2018
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Why is this still opt-out rather than opt-in?! It's very annoying and just plain wrong!
So the user can disable the metrics package, but this is AFTER he has already run Atom the first time having metrics send information the first time it is run.
Even if all the data is out in the open, this seriously needs to be opt-in, not opt-out!
Would you please take this issue serious and look at all the complaints about the issue.
We have discussed this issue again and again in #4966 and in atom/metrics#16
It's spyware no matter what you call it as long as it is opt-out!
The text was updated successfully, but these errors were encountered: