I do not have a problem with opt-in telemetry, but know that if you use providers like Google or Yandex, I won´t even think about opting in. It also would be nice if I can choose what information gets included and what not.

Also, the merge request hasn´t even been added in. I hope it won´t make it in, due the use of Google Analytics as provider.

The fact it’s opt-in reduces the validity of their goals honestly, particularly related to assessing the scale of things like usage and stability issues. Linux users seem far less likely to opt-in to telemetry than Windows users, and even between Linux distros I’d expect to see significant differences that will make it hard to draw any real conclusions.

The acquisition by the newly founded Muse Group, followed closely by this PR, with very little discussion or community work leading up to it feels a little corrupt for an open-source project. Even now - when there’s so much backlash - the PR hasn’t been rejected or changed in any way.

Here’s hoping for a decent fork to pop up if this goes through, as it’s indicative of the kind of mingling we can expect from the new ownership going forward.

From what I understood it’s opt-in, so you don’t send anything unless you explicitly turn it on?

This seems like an overreaction for an opt-in addition on something they won’t be applying cross-tracking to. Software that scales to a larger audience can be improved via telemetry data collection. Probably more concern here around the recent acquisition and fear of commercialization. It’s good to be vigilant but not reactionary.