• Simon 𐕣he 🪨 Johnson@lemmy.ml
    link
    fedilink
    arrow-up
    8
    arrow-down
    1
    ·
    edit-2
    22 hours ago

    This is what vertical integration between distros and GUIs often leads to. This could be completely innocuous from Deepin’s end, because that’s just how they made it work in Deepin because they have vertical integration on their own stack. However, It’s completely bad form.

    In general Deepin seems to adopt a lot of commercial software industry practices in building its tools, which I’m sympathetic to on some level, but it’s very obvious that the Linux community is not going to accept default-on telemetry. They should have known better after the CNZZ incident.

    • Leaflet@lemmy.world
      link
      fedilink
      English
      arrow-up
      10
      ·
      21 hours ago

      Wasn’t vertical integration, was done by packager.

      We don’t believe that the openSUSE Deepin packager acted with bad intent when he implemented the “license agreement” dialog to bypass our whitelisting restrictions. The dialog itself makes the security concerns we have transparent, so this does not happen in a sneaky way, at least not towards users. It was not discussed with us, however, and it violates openSUSE packaging policies.

      • Simon 𐕣he 🪨 Johnson@lemmy.ml
        link
        fedilink
        arrow-up
        2
        ·
        19 hours ago

        Right, but what I’m saying the design to need these things was likely based on Deepin running their own distro. They don’t have to consider the security guidelines of other distros like KDE or Gnome, XFCE or Enlightenment would.

        • michaelmrose@lemmy.world
          link
          fedilink
          English
          arrow-up
          2
          ·
          4 hours ago

          It needed those things brought in through the back door because the code was a steaming pile of shit security wise and would have been rejected at the front door.