4 ms·

> You need telemetry Lemme stop you right there.

• cube2222 7y ago
  I simply don't agree. Without telemetry, at least in the early stages where you don't get 1000000 issues every day, you have no idea what your users are actually finding useful. This may lead to you developing features which nobody cares about, wasting precious time you could spend creating actually useful stuff. It's a win-win, as long as nobodies privacy is violated. And that part is basically what this whole question is about. How to do telemetry in a way that won't feel privacy-violating to users (and won't actually be privacy-violating, as opposed to "good feelings by privacy violation obfuscation").
  • qplex 7y ago
    You make it completely optional. Just opening an outbound connection can be a privacy issue for some users. And preferably you don't ever ask normal users to enable telemetry (and if you do ask, default to no). Telemetry is only a feature for those who wish to actually help you develop your software, not just use it.
    • cube2222 7y ago
      I'm worried though that in practice you'll end up with almost nobody making an effort to enable it. I don't care for vs code to send telemetry, but I'd surely not spend even 3 minutes to turn it on if it weren't by default.
      • yorwba 7y ago
        As a compromise solution, you could collect telemetry locally and prompt the user to upload it e.g. if there was an assertion failure or an operation takes much longer to complete than expected. That way, the value of providing telemetry data is much clearer to the user and in the end it remains their decision whether to provide it or not.