• KaneA
    link
    fedilink
    English
    arrow-up
    59
    arrow-down
    5
    ·
    3 days ago

    They just closed the issue without even acknowledging it, lol

    • woelkchen@lemmy.world
      link
      fedilink
      English
      arrow-up
      74
      ·
      3 days ago

      They just closed the issue without even acknowledging it, lol

      They acknowledged the remote debugging backdoor issue and fixed it a year ago.

      It was enabled due that zen was still a toy project and we needed people to easily open the debugger for easier bug fixing. This was due because zen was not in a daily drivable state and didn’t gain any sort of popularity yet.

      https://github.com/zen-browser/desktop/pull/927

      The telemetry issue is entirely different. Their handling of that is naive at best, dishonest at worst but it is completely different from the “backdoor”.

      • KaneA
        link
        fedilink
        English
        arrow-up
        4
        arrow-down
        3
        ·
        3 days ago

        Fair, I was referring to the referenced issue in the comments on this post.

        What was surprising to me, is that there were many comments, and mentions of devs, yet no acknowledgment or getting linked to another issue.

        That is a red flag to me.

    • WhyJiffie@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      15
      arrow-down
      2
      ·
      edit-2
      3 days ago

      are you really surprised? that bugreport did not contain a single actionable detail. and then it refers to some forum without any real reference, name or URL. there may be truth to it, and the other issue was actually very important and ridiculous, but this issue report is a big wontfix, reopen with real details