The developers of the Manjaro Linux distribution, built on the basis of Arch Linux and aimed at beginners, announced the beginning of testing a new service MDD (Manjaro Data Donor), designed to collect statistics about the system and send it to the external server of the project. The author of the MDD intended to enable telemetry by default (opt-out), but the decision has not yet been approved and, judging by the objections of some developers and users, it is likely that telemetry will be offered as an option requiring prior consent of the user (a request to enable telemetry is proposed to be added to the greeting interface after the first download).

The report includes data such as host name, kernel version, desktop component versions, detailed information about hardware and drivers involved, screen size and resolution information, network device MAC addresses, disk serial numbers, disk partition data, information about the number of running processes and installed packages, versions of basic packages such as systemd, gcc, bash and PipeWire.

The sent data is stored on the project server in the ClickHouse database and visualized using the Grafana platform. The IP addresses of users are not stored, and the hash from the /etc/machine-id file is used as the system identifier.

Аccording to the code https://github.com/manjaro/mdd/blob/master/mdd.py#L40 sends everything.

  • rtxn@lemmy.worldEnglish
    201·
    7 hours ago

    It’s all about trust. Manjaro has given me reasons to distrust them.

    • exu@feditown.comEnglish
      3·
      4 hours ago

      When?

      Edit: I misread, though it said “trust” instead of “distrust”

      • rtxn@lemmy.worldEnglish
        13·
        7 hours ago

        They’ve let TLS certs expire on multiple occasions. They’ve made the decision to enable the AUR in the default installation, which can cause conflicts with out-of-date dependencies because of the delayed release schedule compared to Arch. They’ve shipped software on their stable branch that included unmerged upstream code. One of their developers temporarily broke Asahi Linux.

        I don’t hate the project, but I can’t trust the developers and management.

          • rtxn@lemmy.worldEnglish
            3·
            60 minutes ago

            He’s also a contributor to Asahi Linux. One of his MRs changed the build options that somehow caused it to (IIRC) use mainline Mesa instead of the branch that is specifically modified to work on ARM.

            (edit) Aussie linux man: https://www.youtube.com/watch?v=eDRiBbzzREw

            It’s not only his fault, but mostly.

        • MyNameIsRichard@lemmy.ml
          6·
          6 hours ago

          They’ve let TLS certs expire on multiple occasions.

          And they told their community to set their clocks back. As a workaround, it will work but all your created and modified data will have the wrong timestamps.