Skip to content

[Feature Request]: Clarify telemetry and make it opt in #217

@talolard

Description

@talolard

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:

  1. A telemetry section in the README stating you collect that data, what you collect, why and how to opt-out
  2. A similar (but shorter) warning at program startup
  3. (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

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions