▲ 79 ▼ Google will require developer verification for Android apps outside the Play Store (techcrunch.com) submitted 1 year ago by BrikoX@lemmy.zip [M] to c/technology@lemmy.zip 23 comments fedilink hide all child comments Google will ask all Android developers to verify their identity starting next year.
[–] INeedMana@piefed.zip 7 points 1 year ago (1 child) Time to switch to /e/OS permalink fedilink source hideshow 2 child comments replies: [–] AntiBullyRanger@ani.social 2 points 1 year ago (1 child) permalink fedilink source parent hideshow 2 child comments replies: [–] INeedMana@piefed.zip 2 points 1 year ago (1 child) WDYM? permalink fedilink source parent hideshow 2 child comments replies: [–] AntiBullyRanger@ani.social 1 point 1 year ago* (last edited 1 year ago) (1 child) permalink fedilink source parent hideshow 2 child comments replies: [–] INeedMana@piefed.zip 2 points 1 year ago (1 child) The way I understand what /e/OS is, it sounds like it should be able to not include this check permalink fedilink source parent hideshow 2 child comments replies: [–] AntiBullyRanger@ani.social 2 points 1 year ago (2 children) Unfortunately, as I still type, there’s no liberated deblobbed ROM. /e/OS, like every custom AOSP fork, is dependent on leaks &/manufacturer provided ROMs. After Google silos AOSP ROMs, all forks will not be able to acquire updates downstream. Linux Phones, are not alternatives. permalink fedilink source parent hideshow 4 child comments replies: [–] majora31@programming.dev 1 point 1 year ago Looks like we need dedicated hardware. /e is phones, graphene phones etc then. permalink fedilink source parent [–] INeedMana@piefed.zip 1 point 1 year ago But if the forks are able to tear out the gapps, shouldn't this "cert" check go with it? I understand that the check would have to be in the installer app. Even if it's a part of launching mechanism, it should also be possible to tear it out Linux Phones, are not alternatives. I'm sorry, I don't follow. AFAIK GRUB did not need to get some blessing to get installed on UEFI. So Linux Phones should be free of big tech gatekeeping. This exchange we are having here is on technology community, not privacy (where I would get your point) permalink fedilink source parent
[–] AntiBullyRanger@ani.social 2 points 1 year ago (1 child) permalink fedilink source parent hideshow 2 child comments replies: [–] INeedMana@piefed.zip 2 points 1 year ago (1 child) WDYM? permalink fedilink source parent hideshow 2 child comments replies: [–] AntiBullyRanger@ani.social 1 point 1 year ago* (last edited 1 year ago) (1 child) permalink fedilink source parent hideshow 2 child comments replies: [–] INeedMana@piefed.zip 2 points 1 year ago (1 child) The way I understand what /e/OS is, it sounds like it should be able to not include this check permalink fedilink source parent hideshow 2 child comments replies: [–] AntiBullyRanger@ani.social 2 points 1 year ago (2 children) Unfortunately, as I still type, there’s no liberated deblobbed ROM. /e/OS, like every custom AOSP fork, is dependent on leaks &/manufacturer provided ROMs. After Google silos AOSP ROMs, all forks will not be able to acquire updates downstream. Linux Phones, are not alternatives. permalink fedilink source parent hideshow 4 child comments replies: [–] majora31@programming.dev 1 point 1 year ago Looks like we need dedicated hardware. /e is phones, graphene phones etc then. permalink fedilink source parent [–] INeedMana@piefed.zip 1 point 1 year ago But if the forks are able to tear out the gapps, shouldn't this "cert" check go with it? I understand that the check would have to be in the installer app. Even if it's a part of launching mechanism, it should also be possible to tear it out Linux Phones, are not alternatives. I'm sorry, I don't follow. AFAIK GRUB did not need to get some blessing to get installed on UEFI. So Linux Phones should be free of big tech gatekeeping. This exchange we are having here is on technology community, not privacy (where I would get your point) permalink fedilink source parent
[–] INeedMana@piefed.zip 2 points 1 year ago (1 child) WDYM? permalink fedilink source parent hideshow 2 child comments replies: [–] AntiBullyRanger@ani.social 1 point 1 year ago* (last edited 1 year ago) (1 child) permalink fedilink source parent hideshow 2 child comments replies: [–] INeedMana@piefed.zip 2 points 1 year ago (1 child) The way I understand what /e/OS is, it sounds like it should be able to not include this check permalink fedilink source parent hideshow 2 child comments replies: [–] AntiBullyRanger@ani.social 2 points 1 year ago (2 children) Unfortunately, as I still type, there’s no liberated deblobbed ROM. /e/OS, like every custom AOSP fork, is dependent on leaks &/manufacturer provided ROMs. After Google silos AOSP ROMs, all forks will not be able to acquire updates downstream. Linux Phones, are not alternatives. permalink fedilink source parent hideshow 4 child comments replies: [–] majora31@programming.dev 1 point 1 year ago Looks like we need dedicated hardware. /e is phones, graphene phones etc then. permalink fedilink source parent [–] INeedMana@piefed.zip 1 point 1 year ago But if the forks are able to tear out the gapps, shouldn't this "cert" check go with it? I understand that the check would have to be in the installer app. Even if it's a part of launching mechanism, it should also be possible to tear it out Linux Phones, are not alternatives. I'm sorry, I don't follow. AFAIK GRUB did not need to get some blessing to get installed on UEFI. So Linux Phones should be free of big tech gatekeeping. This exchange we are having here is on technology community, not privacy (where I would get your point) permalink fedilink source parent
[–] AntiBullyRanger@ani.social 1 point 1 year ago* (last edited 1 year ago) (1 child) permalink fedilink source parent hideshow 2 child comments replies: [–] INeedMana@piefed.zip 2 points 1 year ago (1 child) The way I understand what /e/OS is, it sounds like it should be able to not include this check permalink fedilink source parent hideshow 2 child comments replies: [–] AntiBullyRanger@ani.social 2 points 1 year ago (2 children) Unfortunately, as I still type, there’s no liberated deblobbed ROM. /e/OS, like every custom AOSP fork, is dependent on leaks &/manufacturer provided ROMs. After Google silos AOSP ROMs, all forks will not be able to acquire updates downstream. Linux Phones, are not alternatives. permalink fedilink source parent hideshow 4 child comments replies: [–] majora31@programming.dev 1 point 1 year ago Looks like we need dedicated hardware. /e is phones, graphene phones etc then. permalink fedilink source parent [–] INeedMana@piefed.zip 1 point 1 year ago But if the forks are able to tear out the gapps, shouldn't this "cert" check go with it? I understand that the check would have to be in the installer app. Even if it's a part of launching mechanism, it should also be possible to tear it out Linux Phones, are not alternatives. I'm sorry, I don't follow. AFAIK GRUB did not need to get some blessing to get installed on UEFI. So Linux Phones should be free of big tech gatekeeping. This exchange we are having here is on technology community, not privacy (where I would get your point) permalink fedilink source parent
[–] INeedMana@piefed.zip 2 points 1 year ago (1 child) The way I understand what /e/OS is, it sounds like it should be able to not include this check permalink fedilink source parent hideshow 2 child comments replies: [–] AntiBullyRanger@ani.social 2 points 1 year ago (2 children) Unfortunately, as I still type, there’s no liberated deblobbed ROM. /e/OS, like every custom AOSP fork, is dependent on leaks &/manufacturer provided ROMs. After Google silos AOSP ROMs, all forks will not be able to acquire updates downstream. Linux Phones, are not alternatives. permalink fedilink source parent hideshow 4 child comments replies: [–] majora31@programming.dev 1 point 1 year ago Looks like we need dedicated hardware. /e is phones, graphene phones etc then. permalink fedilink source parent [–] INeedMana@piefed.zip 1 point 1 year ago But if the forks are able to tear out the gapps, shouldn't this "cert" check go with it? I understand that the check would have to be in the installer app. Even if it's a part of launching mechanism, it should also be possible to tear it out Linux Phones, are not alternatives. I'm sorry, I don't follow. AFAIK GRUB did not need to get some blessing to get installed on UEFI. So Linux Phones should be free of big tech gatekeeping. This exchange we are having here is on technology community, not privacy (where I would get your point) permalink fedilink source parent
[–] AntiBullyRanger@ani.social 2 points 1 year ago (2 children) Unfortunately, as I still type, there’s no liberated deblobbed ROM. /e/OS, like every custom AOSP fork, is dependent on leaks &/manufacturer provided ROMs. After Google silos AOSP ROMs, all forks will not be able to acquire updates downstream. Linux Phones, are not alternatives. permalink fedilink source parent hideshow 4 child comments replies: [–] majora31@programming.dev 1 point 1 year ago Looks like we need dedicated hardware. /e is phones, graphene phones etc then. permalink fedilink source parent [–] INeedMana@piefed.zip 1 point 1 year ago But if the forks are able to tear out the gapps, shouldn't this "cert" check go with it? I understand that the check would have to be in the installer app. Even if it's a part of launching mechanism, it should also be possible to tear it out Linux Phones, are not alternatives. I'm sorry, I don't follow. AFAIK GRUB did not need to get some blessing to get installed on UEFI. So Linux Phones should be free of big tech gatekeeping. This exchange we are having here is on technology community, not privacy (where I would get your point) permalink fedilink source parent
[–] majora31@programming.dev 1 point 1 year ago Looks like we need dedicated hardware. /e is phones, graphene phones etc then. permalink fedilink source parent
[–] INeedMana@piefed.zip 1 point 1 year ago But if the forks are able to tear out the gapps, shouldn't this "cert" check go with it? I understand that the check would have to be in the installer app. Even if it's a part of launching mechanism, it should also be possible to tear it out Linux Phones, are not alternatives. I'm sorry, I don't follow. AFAIK GRUB did not need to get some blessing to get installed on UEFI. So Linux Phones should be free of big tech gatekeeping. This exchange we are having here is on technology community, not privacy (where I would get your point) permalink fedilink source parent