• 0 Posts
  • 8 Comments
Joined 2 years ago
Cake day: June 16th, 2023
  • oaklandnative@lemmy.worldtoTechnology@lemmy.world•Google Keeps Making Smartphones WorseEnglish
    3·
    9 days ago

    Thanks for these, especially the “we’re not going anywhere” link. I was hesitant to switch because I was worried about future support on my Pixel 7. Here’s the full quote for anyone that didn’t check the above link:

    Many companies and individuals are trying to mislead people about the future of GrapheneOS to promote their insecure products and services. GrapheneOS is not going anywhere. We’ve made it clear we’re shipping Android 16 soon and that the supported devices will remain supported.

  • oaklandnative@lemmy.worldtoLinux Gaming@lemmy.world•Proton is now enabled by default on Steam to make Linux gaming simplerEnglish
    1·
    24 days ago

    I’ve been exclusively gaming on my Steam Deck since launch and have a slightly different experience. For me, if the game is certified “Playable” or “Verified” on the Steam page, I just download and play it. I have never once tweaked any settings or tried a different version of Proton. I’m sure there are tweaks that can achieve better performance on certain games, but I have never personally felt the need to research that on any game.

    For reference, below are my recently played games. All but Trials worked great for me. Trials is marked “Unplayable” on Steam, though I did get it to work for a few hours before it broke.

  • oaklandnative@lemmy.worldtoPrivacy@lemmy.ml•Official Brave F-Droid repository now available
    41·
    24 days ago

    I have used FF based browsers for a long time and still do. I recently saw this from the GrapheneOS developers, which kinda freaks me out and has me considering switching to a Chromium based browser:

    https://grapheneos.org/usage#web-browsing

    Chromium-based browsers like Vanadium provide the strongest sandbox implementation, leagues ahead of the alternatives. It is much harder to escape from the sandbox and it provides much more than acting as a barrier to compromising the rest of the OS. Site isolation enforces security boundaries around each site using the sandbox by placing each site into an isolated sandbox… Browsers without site isolation are very vulnerable to attacks like Spectre…

    Avoid Gecko-based browsers like Firefox as they’re currently much more vulnerable to exploitation and inherently add a huge amount of attack surface. Gecko doesn’t have a WebView implementation (GeckoView is not a WebView implementation), so it has to be used alongside the Chromium-based WebView rather than instead of Chromium, which means having the remote attack surface of two separate browser engines instead of only one. Firefox / Gecko also bypass or cripple a fair bit of the upstream and GrapheneOS hardening work for apps. Worst of all, Firefox does not have internal sandboxing on Android. This is despite the fact that Chromium semantic sandbox layer on Android is implemented via the OS isolatedProcess feature, which is a very easy to use boolean property for app service processes to provide strong isolation with only the ability to communicate with the app running them via the standard service API. Even in the desktop version, Firefox’s sandbox is still substantially weaker (especially on Linux) and lacks full support for isolating sites from each other rather than only containing content as a whole. The sandbox has been gradually improving on the desktop but it isn’t happening for their Android browser yet.

    EDIT: I really hope Ladybird turns out to be amazing.