• Successful_Try543@feddit.org
    link
    fedilink
    arrow-up
    12
    ·
    8 hours ago

    As the F-Droid team signs the (not repoducibly built) apks with their own key, Google would have to allow the key of the F-Droid team then.

    Yet, as Google currently does not permit apps in their PlayStore that aren’t in line with their business model, e.g. NewPipe, they would then force the F-Droid team to do the same.

    • WalnutLum@lemmy.ml
      link
      fedilink
      arrow-up
      1
      ·
      11 minutes ago

      They said they can’t do that in the article:

      but at the same time, we cannot ‘take over’ the application identifiers for the open-source apps we distribute, as that would effectively seize exclusive distribution rights to those applications

    • Jul (they/she)@piefed.blahaj.zone
      link
      fedilink
      English
      arrow-up
      6
      ·
      7 hours ago

      Possibly, but I don’t see Google doing that either. It’s not about where the app comes from really. The thing they are going to restrict is the developer. A developer can not have their app installed on a certified phone, regardless of where the user got the app, if the developer is not registered.

      So, since there are no regulations to allow a user to install apps from any chosen developer, only from any chosen app store, there likely will be no regulatory recourse like Apple is facing as mentioned by the OP.

      • Successful_Try543@feddit.org
        link
        fedilink
        arrow-up
        3
        ·
        7 hours ago

        My first point is, in other words: From Google’s pov, the F-Droid team is “the developer” who’s key and personal information Google would request to allow installing apks with their signature on Android devices.