this post was submitted on 13 Oct 2025
341 points (99.1% liked)
Open Source
41456 readers
325 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
- !libre_culture@lemmy.ml
- !libre_software@lemmy.ml
- !libre_hardware@lemmy.ml
- !linux@lemmy.ml
- !technology@lemmy.ml
Community icon from opensource.org, but we are not affiliated with them.
founded 6 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Until it does. Google is already closing development, so the GrapheneOS devs will have a more difficult time rebasing their changes to AOSP each snapshot.
Not exactly. GrapheneOS has an OEM partner and has early access to AOSP changes that aren't public. A huge downside to that is that security preview releases can't be open source until after Google makes the code public.
Well, that's not a huge downside. They still provide those security updates in their binary builds.
Fair enough. I said "huge" because I guess some people care a lot. I personally don't and have been on security preview releases since they started releasing them.