this post was submitted on 26 Mar 2025
361 points (98.7% liked)

Technology

68131 readers
3336 users here now

This is a most excellent place for technology news and articles.

Our Rules

  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots

founded 2 years ago
MODERATORS
L3s@lemmy.world
enu@lemmy.world
technopagan@lemmy.world
L4s@lemmy.world
L3s@hackingne.ws
L4s@hackingne.ws
361
Google will develop the Android OS fully in private; Will continue open source releases. (www.androidauthority.com)
submitted 6 days ago by Tea@programming.dev to c/technology@lemmy.world
57 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] sugar_in_your_tea@sh.itjust.works 25 points 6 days ago* (last edited 6 days ago) (2 children)

It means my GrapheneOS updates will probably be a little slower.

[–] CeeBee_Eh@lemmy.world 9 points 6 days ago

And yet Graphene will still probably need more private and secure

[–] fmstrat@lemmy.nowsci.com 6 points 5 days ago (2 children)

How so? If Graphene is based off a release branch, there shouldn't be change in timing. Sure, maybe a little for inspection, but as far as I know Graphene isn't based off main anyway.

[–] sugar_in_your_tea@sh.itjust.works 1 points 5 days ago

They currently get early access in some capacity, and I wonder if this would impact that.

[–] pinball_wizard@lemmy.zip 1 points 4 days ago* (last edited 4 days ago)

How so?

  • Developers routinely read along with upstream updates that are relevant to them.
  • Google is removing this access.
  • Google is specifically removing access to read along with upstream updates that are relevant to the developers of GrapheneOS.

At minimum, this will slow down GrapheneOS releases and increase bugs in GrapheneOS.

At worst this could cause a new malicious anti-privacy "feature" to ship with GrapheneOS because there's no time to analyze to discover and remove it.

It's almost like Google hates Privacy or something...