-
Notifications
You must be signed in to change notification settings - Fork 86
Closed
Description
Feature Name
Clarify Telemetry /Sentry
Feature Description
Hi,
I've been reading through the code ahead of a POC.
I noticed the calls to sentry and the init_sentry function as well as the SENTRY_OPT_OUT env var.
Collecting telemetry data is fine, however, I think it would go a long way towards ensuring trust and easing the adoption of fastdup if you communicated that that data is being collected and why, as well as providing a way to opt-in/opt-out at the program start.
I'd suggest any or all of the following:
- A telemetry section in the README stating you collect that data, what you collect, why and how to opt-out
- A similar (but shorter) warning at program startup
- (Most user-friendly / most work) Display such a warning, and wait for user input on whether they would like to send data or not.
Contact Information [Optional]
No response
Metadata
Metadata
Assignees
Labels
No labels