I can understand this workflow being created to protect the legions of people who are tricked into installing spyware.
Then you’re stupid, as most people install third party spyware through the Google Play store.
I can understand this workflow being created to protect the legions of people who are tricked into installing spyware.
It doesn’t remotely affect me because I use GrapheneOS and if this is an issue for you then you’re probably someone who should look at installing GOS or Lineage.
I don’t think Google should be able to do this and it is likely part of a longer-term strategy to strangle any competition. At the same time, I can understand how this change will save a lot of grandparents from clicking a link in a text from their ‘grandchildren’ and installing spyware that’ll steal all of their bank information.
I can understand this workflow being created to protect the legions of people who are tricked into installing spyware.
Then you’re stupid, as most people install third party spyware through the Google Play store.
Yes, how stupid of me for not explicitly explaining the context that everyone with basic reading comprehension can understand.
I’ll add the obvious context for everyone else who is new to the world and has issues parsing regular English sentences:
AHemlocksLie@lemmy.zip 7 hours ago
GrapheneOS is built on AOSP, which is where the change is being made. Graphene and other custom ROMs will need to maintain a fork that cuts out the feature if they want to avoid. Google is also starting to close off Android to make that more difficult, so it’ll become a genuine project to maintain the fork well.
nomadpxl@programming.dev 3 hours ago
As far as I understand the enforcement depends on privileged play services. xcancel.com/Metr0pl3x/status/1960329785277571420#…