-
Notifications
You must be signed in to change notification settings - Fork 16
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
Usage metrics #185
Comments
@gagdiez @garikbesson Has anyone flagged privacy concerns regarding the tracking in CLI? near/near-cli-rs#83 - I remember I started this issue, but then decided to close it as I was not completely comfortable pushing such code to the users. Even an empty HTTP call to mixpanel is already a traceable event that reveals IP, time, and maybe OS. |
@frol never had any privacy concerns |
frol
pushed a commit
that referenced
this issue
Aug 21, 2024
…of the command usage (#192) The issue: #185 How tracking events looks like: <img width="248" alt="image" src="https://github.com/user-attachments/assets/1f6ea76b-bf8c-400f-bc16-b62a03ba15ed"> UPDATE: sending field `pkg_version` instead of `cli_version`
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In
create-near-app
we have an incredibly simple, non-invasive, and anonymous way of gathering usage metrics thoughmixpanel
.Basically, each time
CNA
is used, a small payload is sent tomixpanel
that includes which type of contract or frontend was created. Source code here.Would be nice to implement the same concept in
cargo near new
, so we can get back statistics from smart contracts created with rust.The text was updated successfully, but these errors were encountered: