Found this notification this morning on my pixel 6.

      • sem@lemmy.blahaj.zone
        link
        fedilink
        English
        arrow-up
        0
        ·
        9 days ago

        The main difference is of philosophy of trust. With F-droid you trust F-droid to build the binary from the developers’ source code. With Accrescent, you trust the developers to build the binary from the source code.

        • carrylex@lemmy.world
          link
          fedilink
          English
          arrow-up
          0
          ·
          9 days ago

          With F-droid you trust F-droid to build the binary from the developers’ source code

          Not when using a self-hosted F-Droid Repo - which is the case for Ironfox.

          • sem@lemmy.blahaj.zone
            link
            fedilink
            English
            arrow-up
            0
            ·
            edit-2
            9 days ago

            In the play store you’re trusting Google and the developer.

            I’m not sure how obtainium works. But if you download binaries from GitHub, you’re trusting the developer to accurately build their source code into the binary without adding anything. You’re also trusting GitHub implicitly – way back when, source forge was sometimes adding malware to downloads iirc.

            F-droid is kind of cool in that they are saying, “we will ensure for you that the code you execute is the same as the open source code you can read”. But this added level of insurance comes with downsides – like sometimes it’s harder for the developer to make their code build properly, or maybe updates take longer.

            • MaggiWuerze@feddit.org
              link
              fedilink
              English
              arrow-up
              0
              ·
              9 days ago

              And here I’m trusting Accrescent to actually deliver me an executable that has not been tampered with