this post was submitted on 05 Jun 2026
346 points (98.3% liked)

Privacy

5719 readers
590 users here now

Welcome! This is a community for all those who are interested in protecting their privacy.

Rules

PS: Don't be a smartass and try to game the system, we'll know if you're breaking the rules when we see it!

  1. Be civil and no prejudice
  2. Don't promote big-tech software
  3. No apathy and defeatism for privacy (i.e. "They already have my data, why bother?")
  4. No reposting of news that was already posted
  5. No crypto, blockchain, NFTs
  6. No Xitter links (if absolutely necessary, use xcancel)

Related communities:

Some of these are only vaguely related, but great communities.

founded 2 years ago
MODERATORS
otter@lemmy.ca
shaytan@lemmy.dbzer0.com
346
Your phone is about to stop being yours. — Starting September 2026, a silent update, nonconsensually pushed by Google, will block every Android app whose developer hasn't registered with Google, sign… (keepandroidopen.org)
submitted 12 hours ago by sanitation@lemmy.today to c/privacy@lemmy.dbzer0.com
66 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] TheOtherwise@hexbear.net 2 points 6 hours ago (1 children)

What is the Motorola thinf being referred to here?

[–] Inui@hexbear.net 3 points 5 hours ago (1 children)

The GrapheneOS folks are working with Motorola to have Graphene pre-installed on one of their phones. It would be the first time it is officially usable on anything but a Pixel. It won't solve the problem described in the OP though. It's still Android.

[–] lucullus@discuss.tchncs.de 2 points 2 hours ago

Afaik GrapheneOS won't be affected, neither will e/OS. The real problem with them still being based as AOSP is, that google might stop the AOSP project. That would mean the forks would need to do that continous based development themselves.