• Alex@lemmy.ml
    link
    fedilink
    English
    arrow-up
    25
    arrow-down
    2
    ·
    6 days ago

    It’s not like Android is especially open to drive-by contributions anyway. I don’t think really changes much for the downstream consumers of the releases.

      • fmstrat@lemmy.nowsci.com
        link
        fedilink
        English
        arrow-up
        6
        ·
        5 days ago

        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.

        • pinball_wizard@lemmy.zip
          link
          fedilink
          English
          arrow-up
          1
          ·
          edit-2
          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…