Tea@programming.dev to Technology@lemmy.worldEnglish · 1 year agoGoogle will develop the Android OS fully in private; Will continue open source releases.www.androidauthority.comexternal-linkmessage-square56linkfedilinkarrow-up1375arrow-down15cross-posted to: technology@lemmy.worldandroid@lemmy.worldtechnology@beehaw.org
arrow-up1370arrow-down1external-linkGoogle will develop the Android OS fully in private; Will continue open source releases.www.androidauthority.comTea@programming.dev to Technology@lemmy.worldEnglish · 1 year agomessage-square56linkfedilinkcross-posted to: technology@lemmy.worldandroid@lemmy.worldtechnology@beehaw.org
minus-squaresugar_in_your_tea@sh.itjust.workslinkfedilinkEnglisharrow-up25·1 year agoIt means my GrapheneOS updates will probably be a little slower.
minus-squareCeeBee_Eh@lemmy.worldlinkfedilinkEnglisharrow-up9·1 year agoAnd yet Graphene will still probably need more private and secure
minus-squarefmstrat@lemmy.nowsci.comlinkfedilinkEnglisharrow-up6·1 year agoHow 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.
minus-squaresugar_in_your_tea@sh.itjust.workslinkfedilinkEnglisharrow-up2·1 year agoThey currently get early access in some capacity, and I wonder if this would impact that.
minus-squarepinball_wizard@lemmy.ziplinkfedilinkEnglisharrow-up1·1 year 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…
It means my GrapheneOS updates will probably be a little slower.
And yet Graphene will still probably need more private and secure
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
mainanyway.They currently get early access in some capacity, and I wonder if this would impact that.
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…