272
GrapheneOS project: pixel 11 no longer supports hardware memory tagging (MTE); GrapheneOS might skip the the whole pixel 11 series (grapheneos.social)
submitted 2 weeks ago by to c/technology@lemmy.world
89 comments fedilink hide all child comments
 

cross-posted from: https://piefed.world/c/tech/p/1368563/grapheneos-project-pixel-11-no-longer-supports-hardware-memory-tagging-mte

Bluesky.

you are viewing a single comment's thread
view the rest of the comments
[–] 1 point 2 weeks ago (3 children)

There needs to be a give and take

If GrapheneOS can't handle the maintenance burden, there is nothing to negotiate.

Presumably, maintaining software for a niche phone requires effort similar in magnitude to a larger, mainstream phone. Why, then, would a solely privacy-oriented org choose to cater to a smaller audience?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 1 point 2 weeks ago (2 children)

    Can other organizations replicate GrapheneOS's principles in ways where THOSE organizations can maintain the burden?

    Is GrapheneOS working towards industry wide standards on privacy-first operating systems from the hardware up?

    Are they contributing to the field at large, or are they keeping to themselves out of self preservation (or selfishness)?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 2 weeks ago (1 child)

    GrapheneOS is an open-source fork of AOSP. Anyone could fork it again and provide kernel modules/drivers for their hardware.

    To my knowledge, GrapheneOS is not standards-based. They take one operating system, and tweak it. I don't know if there are relevant standards to contribute to, or even standards bodies to approve them.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 1 point 2 weeks ago*

    Thanks for taking the time to educate someone that is STEM-studied but not necessarily in computer hardware/software.

    Given that GrapheneOS picked AOSP to be their canvas with which to tighten down the hatches and improve the base AOSP platform's privacy characteristics, this to me indicates that nothing is stopping GOS from doing the same and contributing to other major platforms intended for mobile devices. Unless of course bandwidth is an issue for them, then they can't contribute to more than just their AOSP fork.

    As someone who uses tech and doesn't really develop it, I would appreciate GrapheneOS expanding their vision to other software/hardware platforms like those being worked on by the Ubuntu Touch, SailfishOS, PostmarketOS, etc. teams.

    I'm not advocating that GOS work on all of these, but I am advocate for GOS to branch off from corporate dependence in the event Motorola goes the way of Google.

    If one thing capitalism has shown us over the last 100+ years, corporations that can enshittify will enshittify. It's only a matter of time, and it'd be better imo for GOS to start pivoting sooner rather than later.

    Unless GOS are ok with ceasing their entire project once Motorola drops them. Maybe they're confident in that bet. I wouldn't be, being a FOSS advocate myself nowadays.

  • permalink
  • fedilink
  • source
  • parent