@Resonosity@lemmy.dbzer0.com

comments

• Never more proud of my decision to drop Xbox in favor of my Steam Deck.

  Like it just keeps getting better and better

  on Microsoft Patents Technique for Inserting Ads Into Videogames While You’re Playing Them. in c/technology@lemmy.world · 6h ago

• I agree that GrapheneOS is useful for some and vital for many people in the world.

  What I’m asking (and demanding) is for GrapheneOS to not put all their eggs in one basket, and to develop alternatives. I don’t think GOS investing in phone manufacturing with Motorola will last forever, just as Google didn’t. Having non-corporate options is imperative as Big Tech ramps up more and more surveillance, walled off gardens, and enshittification

  on GrapheneOS project: pixel 11 no longer supports hardware memory tagging (MTE); GrapheneOS might skip the the whole pixel 11 series in c/technology@lemmy.world · 1 Sep 2026

• 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 ship 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.

  on GrapheneOS project: pixel 11 no longer supports hardware memory tagging (MTE); GrapheneOS might skip the the whole pixel 11 series in c/technology@lemmy.world · 31 Aug 2026

• Short-sighted goal in my opinion. They could be the leader in privacy for smartphones from the bottom up, including hardware and software.

  GOS’s work with Motorola might just lead Motorola to be that group as they always have for decades, so my issues might go away anyways.

  Just getting arrogant, self-isolating vibes when they have soooo much good will with the tech community on building privacy from the ground up in some of the most important intelligent devices in our lives.

  Why can’t GOS join a working group with ISO or IEC or IEEE or other groups to create roadmaps and tiers of compliance so that other manufacturers have means and methods of approaching GOS’s lofty goals.

  on GrapheneOS project: pixel 11 no longer supports hardware memory tagging (MTE); GrapheneOS might skip the the whole pixel 11 series in c/technology@lemmy.world · 31 Aug 2026

• I am judging that.

  I want them to keep their principles, and at the same time partner with some Linux group or some other working group representing Open-Source Hardware (OSH) so that one day we don’t HAVE to rely on corporations for true privacy with our smartphones.

  on GrapheneOS project: pixel 11 no longer supports hardware memory tagging (MTE); GrapheneOS might skip the the whole pixel 11 series in c/technology@lemmy.world · 31 Aug 2026

• How come other phones by Samsung, Apple, etc. seem to be doing alright despite not meeting the hyper restrictive requirements of GrapheneOS?

  I reject that GrapheneOS can’t continue to do their work with Google Pixels and Motorola and NOT encourage open-source hardware developers to integrate GOS’s so that one day we can have open-source, privacy-first, truly-secure, repairable, sustainable communications devices.

  It seems to me like GrapheneOS could lead the world in pushing this topic by creating cross-industry working groups to focus on fixing vulnerabilities in some of the most important intelligent devices existing today.

  There could be organizations like IEEE or IEC that GOS may or may not work with, but no one has given me an answer for that. GOS seems self-isolated and therefore self-serving, as an outsider. I don’t understand why they can’t do more outreach to build coalitions in the industry, if they aren’t already.

  on GrapheneOS project: pixel 11 no longer supports hardware memory tagging (MTE); GrapheneOS might skip the the whole pixel 11 series in c/technology@lemmy.world · 31 Aug 2026

• 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)?

  on GrapheneOS project: pixel 11 no longer supports hardware memory tagging (MTE); GrapheneOS might skip the the whole pixel 11 series in c/technology@lemmy.world · 31 Aug 2026

• Can Graphene OS achieve their privacy targets and principles in different ways that encourage collaboration with non-corporations?

  I refuse to believe that GOS can’t agree to graduated privacy provisions according to the capabilities of Linux and sustainable/repairable non-corpo companies and their phones.

  on GrapheneOS project: pixel 11 no longer supports hardware memory tagging (MTE); GrapheneOS might skip the the whole pixel 11 series in c/technology@lemmy.world · 31 Aug 2026

• Why would manufacturers choose to meet GOS’s extra requirements?

  There needs to be a give and take. It seems like GOS’s mantra is their way or the high way, which isn’t collaborative in the slightest.

  Can there not be discussions held between Linux and sustainable/repairable OEMs and GOS to start integrating each other’s requirements? Diplomacy/negotiations/working groups are just completely neglected?

  on GrapheneOS project: pixel 11 no longer supports hardware memory tagging (MTE); GrapheneOS might skip the the whole pixel 11 series in c/technology@lemmy.world · 31 Aug 2026

• But why can’t GrapheneOS work with those companies to ACQUIRE the right hardware requirements, rather than leaning on a corporation?

  on GrapheneOS project: pixel 11 no longer supports hardware memory tagging (MTE); GrapheneOS might skip the the whole pixel 11 series in c/technology@lemmy.world · 31 Aug 2026

• Wish they’d focus on phones NOT made by major corporations like Google and Motorola, and instead focus on small companies’ phones like Fairphone, Pine64, Purism, Jolla, etc.

  on GrapheneOS project: pixel 11 no longer supports hardware memory tagging (MTE); GrapheneOS might skip the the whole pixel 11 series in c/technology@lemmy.world · 31 Aug 2026