• 1 Post
  • 61 Comments
Joined 3 days ago
cake
Cake day: September 24th, 2025

help-circle




  • ZinQ@lemmy.mlOPtoPrivacy@lemmy.mlMy apps
    link
    fedilink
    arrow-up
    3
    ·
    6 hours ago

    People in the comments already have “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.”


  • ZinQ@lemmy.mlOPtoPrivacy@lemmy.mlMy apps
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    6 hours ago

    I mean Gecko based browsers are actively recommended against on mobile. Chromium based browsers are recommended. Also I use mullvadVPN DNS based ad blocking, and I also have Brave that has built in ad blocking. Do yourself a favor and ditch adblock in favor of Ublock origin







  • ZinQ@lemmy.mlOPtoPrivacy@lemmy.mlMy apps
    link
    fedilink
    arrow-up
    1
    ·
    19 hours ago

    Cromite, but I have switched to brave since, it has better fingerprinting protection, more updates, better security and better sandboxing and isolation. At least that’s what Deepseek R1 with websearch has to say






  • ZinQ@lemmy.mlOPtoPrivacy@lemmy.mlMy apps
    link
    fedilink
    arrow-up
    1
    ·
    19 hours ago

    I think overall I have an edge with Brave, since I use it for NanoGPT webapp which I need to be fast or I’ll kys because it was already slow AF on Vanadium so I assume on FF it will be a lot worse