this post was submitted on 01 May 2026
780 points (98.6% liked)

Privacy

9671 readers
1062 users here now

A community for Lemmy users interested in privacy

Rules:

  1. Be civil
  2. No spam posting
  3. Keep posts on-topic
  4. No trolling

founded 2 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] silentjohn@lemmy.ml 73 points 9 hours ago* (last edited 9 hours ago) (11 children)

I support spreading this message, and fuck Google, but...what's actually happening is they are making harder to install apps, not removing the ability to do so.

https://grapheneos.social/@GrapheneOS/116489468836419322

[–] Quetzalcutlass@lemmy.world 109 points 9 hours ago* (last edited 9 hours ago) (3 children)

After massive pushback. Their original plan was basically full control. It still is, but they'll allow you to install something if you ask nicely first.

The other issue is the timing. They can claim this is for security all they want, but it was announced suspiciously close to the courts ruling that Google needed to open up their ecosystem to other app stores. This is a blatant attempt to keep control of the app ecosystem by forcing devs to go through Google regardless of where they intend to release.

[–] pfried@reddthat.com 1 points 13 minutes ago* (last edited 11 minutes ago)

They can claim this is for security all they want, but it was announced suspiciously close to the courts ruling that Google needed to open up their ecosystem to other app stores.

The courts ruled that users need to be able to install competing app stores without any warning, which is different from how it works today. Obviously allowing installation without any warning would be a boon to malware authors, so they added a way for third party app developers (including app store app developers) to verify themselves and distribute apps outside the Play Store without a warning on installation. Now Epic can verify with Google and distribute its app on its own website without needing to tell the user how to dismiss a scary warning, and the same is true for Safeway and Proton and other developers that might want to self distribute. On top of that, now GrapheneOS can implement its own verification system using the same OS-level APIs. Maybe app authors can distribute apps themselves for users of GrapheneOS by registering their repo with a verification system that runs an automated security audit on the repo and ensures reproducible builds.

Now that there is a way to distribute apps safely outside the system app store, that probably prompted them to look at what was causing malware problems with the current unverified app installation flow, and they came up with that system. Saying it's some massive conspiracy won't force them to change their minds, especially since there aren't enough users who care to make a dent in their revenue. Proposing a less onerous way to stop malware and bringing that in front of a judge on behalf of the app developers who are harmed will.

[–] pfried@reddthat.com 2 points 5 hours ago

Their original plan was basically full control

I'm not happy with the change, but let's at least get the facts straight, so we can argue our position better. Their original plan included a way to install apps from unknown sources, but it did not describe how that would work.

[–] ColeSloth@discuss.tchncs.de 4 points 6 hours ago (1 children)

I still say fuck them and push back and that total control is there end goal.

However. I agree with what they're putting in place at this time. It's a one time 24 hour hold before you can install apks from unknown places.

Unfortunately, a lot of people are pieces of shit, and I know for pretty much a fact that making this move will prevent old people from getting scammed. Especially for more targeted attacks where you can use ai to fake one of their relatives voices. It pumps a brake on scammers getting people to grant access while under a panic.

So if you're tech savvy, you'll just have to wait an extra 24 hours before you can start side loading after a phone reset or new phone purchase. Not a big deal if it keeps my pops from having his bank account drained. The guy got in a panic when his Facebook billiards game lost his score data. The guy would have left his phone with someone for a week if they told him they could have gotten it back.

[–] XLE@piefed.social 9 points 6 hours ago (1 children)

This is clearly not designed to keep people secure. If it was, Google would not force you to make your device less secure to install apps of your choice.

[–] pfried@reddthat.com 0 points 4 hours ago* (last edited 4 hours ago) (1 children)

The only way it reduces security is by increasing the attack surface. There is no "now anybody can get root on your phone" vulnerability for enabling developer options, and if there were, Google would patch it. I always enable developer options as soon as I get a new device.

Because of this, the audit described in the "Other" link is deprecated.

[–] XLE@piefed.social 3 points 4 hours ago

I always enable developer options as soon as I get a new device.

That's great for you, but you and I are not the targets that Google is supposedly trying to protect from supposed scams.

[–] DiarrheaSommelier@lemmy.ca 11 points 6 hours ago

That's what they're doing *so far. * I very strongly doubt this is the last time the deal is altered.

[–] XLE@piefed.social 49 points 8 hours ago

Google is "only" locking you out of using your phone for 24 hours...

For extra security, let's make it a week. Let's make it a month. Let's make it a year.

[–] rolling@piefed.ca 20 points 7 hours ago

Ok? Its still my phone, my hardware, and now I have to wait 24 hours before I can install wahtever I want on the phone that I goddamn paid for with my own goddamn money.

Also, let's not pretend as if they not eventually going to go back to their original plan once the initial backlash dies down and people get used to the new norm.

Stop softening the message. They can just turn off any app for any of no reason. This is the same as removing ur ability to do so

[–] DupaCycki@lemmy.world 9 points 8 hours ago

This is supposed to be a simplified message for tech illiterate people. While it may not be fully accurate, the alternative is something that <= 5% of the population will understand.

Additionally, as others have pointed out, this is how the change was originally planned. It was only adjusted due to massive backlash. Apparently the current backlash is not enough for Google to adjust it further.

[–] voxel@feddit.uk 10 points 8 hours ago* (last edited 8 hours ago) (1 children)

For everyone unaware, enabling developer options already makes your OS less secure, so Google is requiring you to make yourself more vulnerable just to have the right to install any software, not just those allowed by Google. This has been among others confirmed by GrapheneOS themselves:

Other: https://floss.social/@IzzyOnDroid/116261079131226664

[–] Cris_Citrus@piefed.zip 1 points 22 minutes ago

Thank you, ''preciate the links

[–] Zedstrian@sopuli.xyz 12 points 9 hours ago* (last edited 9 hours ago)

Doesn't the new process require the use of Google Play Services?

Removing it would thus render a device unable to install apps at all.

[–] cybernihongo@reddthat.com 6 points 7 hours ago

A change I still wholly reject. Everyone should reject this change. No compromises.

[–] pfried@reddthat.com 0 points 5 hours ago

And more correctly, harder to install apps the first time but easier than it is now to install apps in the future because that setting will now be copied to new phones instead of having to go through the flow again each time.