Consider making telemetry opt-in instead of opt-out
Checklist
- [x] I agree to the terms within the Safety Code of Conduct.
Safety version
3.5.X and 3.6.0
Python version
3.11 and later
Operating System
Linux
Describe the problem you'd like to have solved
Currently, the telemetry flag offers the users the option to opt-out from sending usage data. Some Linux distros (including Gentoo, where I am trying to include a build of saftey) have strong conventions regarding using privacy. In Gentoo, the maintainers, would like to see the package included, but required a patch to make telemetry opt-in instead of opt-out.
Describe the ideal solution
--enbale-telemetry flag instead of --disable-telemetery.
Alternatives and current workarounds
No response
Additional context
No response
What I Did
See the suggested patch.
Hi @oz123, thank you for opening this issue!
We appreciate your effort in reporting this. Our team will review it and get back to you soon. If you have any additional details or updates, feel free to add them to this issue.
Note: If this is a serious security issue that could impact the security of Safety CLI users, please email [email protected] immediately.
Thank you for contributing to Safety CLI!
Hello, as a paying customer I would like to express a strong disagreement with the telemetry that cannot be disabled at all, even with the opt-out option. Having the telemetry as opt-out is unfortunate decision IMHO, but having mandatory telemetry is a strong argument against using your product at all.