Telemetry Opt-In Debate

There not much harm as long they're making sure users are aware of the telemetry and can disable it if they choose to. Opt-in is best, but collecting data with consent isn't a problem

Not sure why you're being downvoted. Telemtery can be a invaluable tool for a whole bunch of reasons. It should, of course, be optional.I think only 1 type of telemetry shouldn't ask for permission, a quick, anonymous ping to say it's been installed.

We are struggling, philosophically, with anti telemetry posts (like this one).We are turning on telemetry in the next release for our open source tool. https://github.com/getgauge/gaugeWe are small team with limited resources.In our tool, it's easy to turn telemetry off, inspect what data is sent and the data collected is public.The data "really" helps to make the too

I couldn't care less if it's phoning home by default, the data helps build a better product. Opt in telemetry is basically useless as you're self selecting for people that discover/care enough to enable the feature.In a world where we have companies like Google/Facebook and massive levels of surveillance it's bizarre to me that this is the hill some of you want to die on.The tools themselves provide a way to disable it, so I don't see what any of the fuss

You can...1. Make telemetry opt-in and ask the user to share data. This is what Apple does2. Collect telemetry and give the user an option to share that data after a crash or bug. Many companies do this.3. Make telemetry opt-out but be forthright with what information is sent and why.4. Don't allow opting out of telemetry but be open and upfront with what is being collected and why.5. Hide the fact that telemetry is being sent, hide what is being sent, and don't a

Opt-out telemetry is spyware, regardless of how convenient you might find it to spy on your users without their consent. The only ethical telemetry is opt-in, such as the system Debian uses, where users are given the option to install the "popularity-contest" telemetry package during install, with the default being not installing.

Well according to our telemetry 0% of users turn it off so it seems pretty popular.But more realistically what you gain in privacy you give up in having your voice heard by the devs. The decisions about the future of the product/project will be driven by the data, specifically the data from the kind of people who leave telemetry on.

A little bit irrelevant to the article:Unpopular opinion but, is opt-outtable telemetry that bad?Of course using tracked behaviors for add targeting is bad (which is why my opinion is irrelevant to the article) but using telemetry to do AB-tests, UX-tests, finding bugs, etc... what’s really bad about it?Every comment about telemetry in HN reads something like ‘Telemetry with opt-out is bad, so GitLab is bad, VSCode is bad, brew is bad, etc...’ but personally I really can’t see the probl

That should be up to the user to decide.If millions want to provide telemetry that's enough to make the product better. Why have other millions who don't want suffer it?

Do you support telemetry if it makes the product better, and not used for ad targeting?