Tea@programming.dev to Technology@lemmy.worldEnglish · 6 days agoGoogle will develop the Android OS fully in private; Will continue open source releases.www.androidauthority.comexternal-linkmessage-square58fedilinkarrow-up1376arrow-down15cross-posted to: [email protected][email protected][email protected][email protected][email protected]
arrow-up1371arrow-down1external-linkGoogle will develop the Android OS fully in private; Will continue open source releases.www.androidauthority.comTea@programming.dev to Technology@lemmy.worldEnglish · 6 days agomessage-square58fedilinkcross-posted to: [email protected][email protected][email protected][email protected][email protected]
minus-squaresugar_in_your_tealinkfedilinkEnglisharrow-up25·edit-25 days agoIt means my GrapheneOS updates will probably be a little slower.
minus-squareCeeBee_Eh@lemmy.worldlinkfedilinkEnglisharrow-up9·5 days agoAnd yet Graphene will still probably need more private and secure
minus-squarefmstrat@lemmy.nowsci.comlinkfedilinkEnglisharrow-up6·5 days 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-squarepinball_wizard@lemmy.ziplinkfedilinkEnglisharrow-up1·edit-24 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…
minus-squaresugar_in_your_tealinkfedilinkEnglisharrow-up2·5 days agoThey currently get early access in some capacity, and I wonder if this would impact that.
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.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…
They currently get early access in some capacity, and I wonder if this would impact that.