New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Should be disabled by default #16

Closed
csuhta opened this Issue Feb 27, 2014 · 4 comments

Comments

Projects
None yet
3 participants
@csuhta

csuhta commented Feb 27, 2014

I was surprised to learn that this is a default package, and that it's on by default. Users should have to opt-in to activity tracking, instead of opt-out. Not cool, and borderline creepy.

@probablycorey

This comment has been minimized.

Show comment
Hide comment
@probablycorey

probablycorey Feb 28, 2014

Member

Tracking can be super creepy, we totally agree. That's why we want to be completely transparent about what we are tracking, to show people that what we are collecting is totally non-creepy:

  • When Atom launches it shows this file describing that it is tracking metrics.
  • The package can be disabled via the settings pane if the user doesn't want metrics to be sent.
  • The code collecting data is free, open source and visible on the metrics package repo.
  • No data about filenames or file contents is sent.

One of the main purposes of the Atom Beta is to gather feedback about how to make Atom better. The metrics package does this by sending generic metrics like the version number, load time, session length, and a count of how many times a user opens a new pane item. This data is extremely helpful to spot problems early and to figure out how to make the user experience better, which is why we have it on by default during the beta.

If there is anything else you think we can do to make it more clear feel free to open a pull request!

Member

probablycorey commented Feb 28, 2014

Tracking can be super creepy, we totally agree. That's why we want to be completely transparent about what we are tracking, to show people that what we are collecting is totally non-creepy:

  • When Atom launches it shows this file describing that it is tracking metrics.
  • The package can be disabled via the settings pane if the user doesn't want metrics to be sent.
  • The code collecting data is free, open source and visible on the metrics package repo.
  • No data about filenames or file contents is sent.

One of the main purposes of the Atom Beta is to gather feedback about how to make Atom better. The metrics package does this by sending generic metrics like the version number, load time, session length, and a count of how many times a user opens a new pane item. This data is extremely helpful to spot problems early and to figure out how to make the user experience better, which is why we have it on by default during the beta.

If there is anything else you think we can do to make it more clear feel free to open a pull request!

kans added a commit to kans/metrics that referenced this issue Feb 22, 2015

Sane Defaults on Reporting:
Changes metrics to only send exceptions by default.  Adds two config options to the metrics package to toggle sending exceptions/other info.
See atom#25, #5045, #4966, atom#16, atom#38, #5669

srid referenced this issue in noseglid/atom-build May 14, 2015

GoogleAnalytics: Unique cid per user
Instead of generating a new cid everytime `build` launches,
make it dependant on the computer (the MAC address), so it is
the same for each user (in reality each computer). The MAC is
hashed before sent so it can not be used for tracing.

@thomasjo thomasjo referenced this issue Jul 1, 2015

Closed

Metrics #51

@bronson

This comment has been minimized.

Show comment
Hide comment
@bronson

bronson Nov 13, 2015

This data is extremely helpful to spot problems early and to figure out how to make the user experience better, which is why we have it on by default during the beta.

@probablycorey, now that Atom is out of beta and running great, is it time to revisit data collection?

bronson commented Nov 13, 2015

This data is extremely helpful to spot problems early and to figure out how to make the user experience better, which is why we have it on by default during the beta.

@probablycorey, now that Atom is out of beta and running great, is it time to revisit data collection?

@probablycorey

This comment has been minimized.

Show comment
Hide comment
@probablycorey

probablycorey Nov 13, 2015

Member

@bronson I don't work on Atom anymore, so I don't have a good answer for you. Sorry.

Member

probablycorey commented Nov 13, 2015

@bronson I don't work on Atom anymore, so I don't have a good answer for you. Sorry.

@bronson

This comment has been minimized.

Show comment
Hide comment
@bronson

bronson Nov 13, 2015

Speaking purely selfishly, I'm sorry to hear you're no longer on Atom. Thanks for the response!

bronson commented Nov 13, 2015

Speaking purely selfishly, I'm sorry to hear you're no longer on Atom. Thanks for the response!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment