• NecroticEuphoria@lemmy.ml
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    5
    ·
    12 hours ago

    Completely disagree.

    The only two reasons for telemetry are selling your data, or outsourcing QA.

    • mabeledo@lemmy.world
      link
      fedilink
      English
      arrow-up
      5
      arrow-down
      1
      ·
      12 hours ago

      How do you know?

      I cannot think of a single bug report coming from a non technical person that would be useful to debug an issue. The most they do is get you to know about a potential problem in the system, which most of the time boils down to user error. Telemetry is pretty much the only way to find the root cause, other than a lab reproducing the customer’s environment 1:1, which is both unrealistic and would still require telemetry to be remotely possible.

      • KubeRoot@discuss.tchncs.de
        link
        fedilink
        English
        arrow-up
        2
        ·
        10 hours ago

        I believe that’s what they’re saying, that if released software has any bugs that users encounter, and the developers want to know about them to fix them, they’re “outsourcing QA” to the users.

        So yeah, good luck creating software and updates with literally no issues :P

        • NecroticEuphoria@lemmy.ml
          link
          fedilink
          English
          arrow-up
          2
          arrow-down
          1
          ·
          9 hours ago

          QA happens before release. Of course that doesn’t prevent some bugs from slipping through, but instead of waiting for the user to break stuff, I broke it on purpose, working in QA.

          I seriously don’t trust any telemetry. Maybe my “paranoia” or whatever makes me heavily biased.