[–] 16 points 1 month ago (1 child)

AOSP is the most secure base. GrapheneOS focus is to be the most secure OS. Not to be the best open source mobile OS or even to be FLOSS.

Notice how they're complaining only about things that could improve security, not general usablity fixes.

  • source
  • parent
  • context
  • [–] 10 points 1 month ago (4 children)

    What is the software on this thing? If it isn't open source, it's DOA (not because I think so, but because the number of potential consumers would be incredibly small)

  • source
  • [–] 11 points 1 month ago (3 children)

    Sooner or later the project will become non-viable and we will all switch to whatever the best option is at that time.

    Or everybody who isn't Google will have to collaborate on a hard fork of AOSP.

    Or some governments will have to finally break out of their oligarchic regulatory capture and step in with antitrust law.

  • source
  • parent
  • context
  • [–] 14 points 1 month ago (4 children)

    Supposedly. Yet Motorola doesn't have the reputation to be frantical about their firmware and security updating. Also, they are not at the source either, Google is. That also adds delay. We will see how the partnership with Motorola will work out in practice.

  • source
  • parent
  • context
  • [–] 21 points 1 month ago (4 children)

    I will never understand this argument. Why in gods name would it be better for them to switch to a completely different OS like Linux and essentially have to destroy the entire ecosystem and start from scratch vs just hard forking current AOSP and maintaining it themselves?

  • source
  • parent
  • context
  • [–] 16 points 1 month ago (1 child)

    ive seen the same news on reddit and lemmy. reddit was like "omg gimme that feature, even i dont use it, it is my right". lemmy is like "are you insane? just get a better platform, your dependency from google is going to kill you"

  • source
  • [–] 59 points 1 month ago (4 children)

    they have long ignored the Google dependency

    What a silly thing to say.

    I'm absolutely certain that no contributors, and extraordinarily few users, are ignoring the risks implied by the google dependency.

    A pixel with Graphene is the best option for a daily driver for as long as it's viable. I expect that's everyone's understanding of the project.

    I don't really see how this project can "pivot to a non-android platform", as I imagine none of their codebase can be transferred.

    Sooner or later the project will become non-viable and we will all switch to whatever the best option is at that time.

  • source
  • parent
  • context
  • [–] 2 points 1 month ago (1 child)

    I didn't check if it was possible to add extensions on cromite, i use it only as a secondary browser. I prefer to use firefox based browser (ironfox on my phone). Thanks for the information.

    Does ublock origin lite really add something to the build-in ad block ? I thought the manifest v3 killed the ad blocker extensions.

  • source
  • parent
  • context
  • [–] [S] 0 points 1 month ago (2 children)

    Lol. MacOS is based on BSD and Mach which are open source, but MacOS is still proprietary. Any normal modern browser syncs anything between devices and has a builtin password manager (which supports sync as well). Even stock Firefox is customizable with countless themes and vertical tabs and has a decent adblocker. No idea why you need calendar in a browser though.

    And, finally, a quote from Vivaldi's EULA, showing its high attitude to being FOSS:

    7\. Without limiting the foregoing, you are neither allowed to (a) adapt, alter, translate, embed into any other product or otherwise create derivative works of, or otherwise modify the Software ; (b) separate the component programs of the Software for use on different computers; (c) reverse engineer, decompile, disassemble or otherwise attempt to derive the source code for the Software, except as permitted by applicable law; or (d) remove, alter or obscure any proprietary notices on the Software or the applicable documentation therein.

  • source
  • parent
  • context
  • [–] 27 points 1 month ago (1 child)

    High requirements not as in performance but hardware security feature. But that is the easy part as far as I understand. The difficult part is the requirement of super fast and constant security patching.

  • source
  • parent
  • context
  • [–] 6 points 1 month ago (7 children)

    But somehow Android, which is based on Linux, somehow checks those points for them...

    The hipocrisy is too big to ignore and it's true, with that mindset of just wanting and waiting for someone else to do the hard work for them to just add patches here and there... they're doomed to fail.

  • source
  • parent
  • context
  • [–] 38 points 1 month ago (9 children)

    Graphene's problem is that its very high firmware and other requirements mean they have to stand on the shoulders of giants. Their problem is that the giant is Google.

    They would probably need huge resources to do that on their own, which is why they have to rely on the maintenance effort of some large company.

  • source
  • [–] 8 points 1 month ago (1 child)

    I feel vindicated for pivoting to Ubuntu Touch. It's far from secure and is admittedly inferior to Android right now, but at least it has no dependence on Google. I kind of saw this coming the second they annouced closing down Android and making security fixes no longer open source

  • source
  • [–] 72 points 1 month ago (27 children)

    Shaming Google will only work for so long. Grapheme is is doomed to fail as long as it has a complete dependence on Google's whims.

    Have they announced the pivot to a non-android platform? Being security-mind it is frankly bizarre they have long ignored the Google dependency as a huge risk for the project.

  • source
  • view more: ‹ prev next ›