• pandacoder@lemmy.world
        link
        fedilink
        English
        arrow-up
        15
        ·
        11 months ago

        I mean this only routes a small amount to their servers, the actual data to use a website isn’t sent to 8.8.8.8.

        • Kayn@dormi.zone
          link
          fedilink
          English
          arrow-up
          4
          ·
          11 months ago

          What is Google gonna get from encrypted HTTPS requests that they don’t already get from the associated DNS requests?

          • pandacoder@lemmy.world
            link
            fedilink
            English
            arrow-up
            1
            ·
            11 months ago

            A more granular view of your actual traffic/usage habits.

            Let’s say a page you visit embeds a Tweet, you’ll end up firing off a DNS request for twitter.com, and at least one request to load data from Twitter.

            Now let’s say you actually use Twitter. The DNS request will be the same, and you will have many requests to Twitter to load data.

            In both situations a DNS request is sent off, so the DNS provider knows you probably loaded something but they are going to have a harder time understanding if you are a Twitter user or if you are just frequenting a website with Twitter embeds. However the network provider that can see to what servers the HTTPS request for data are going will see just how often you are actually connecting to Twitter and the size of the transferred data and can build an incomplete but still far more detailed picture of your habits, and they would be able to tell the difference between an only-embed viewer and a regular Twitter user.

            Additional dystopian future possibility:

            Also, for anyone with objectively nefarious future goals, even if the data is encrypted, if one day we are indeed able to break encryption en masse the DNS provider can’t decrypt data they don’t have but the network provider definitely could.

  • Exec@pawb.social
    link
    fedilink
    English
    arrow-up
    77
    ·
    11 months ago

    So third-party VPN apps should be able to provide a connection without a persistent notification now, right?
    Right?

    • ChaoticNeutralCzech@feddit.de
      link
      fedilink
      English
      arrow-up
      11
      arrow-down
      2
      ·
      edit-2
      11 months ago

      If they’re root, they already can. Like Google Play and other root/system apps that can install apps without the pop-up.

      It is an obvious double measure but it’s been around for a long time, and it’s not too insecure or annoying unless manufacturers install malware as system apps and/or disallow locking the boatloader (they do, sadly).

      • lemmyvore@feddit.nl
        link
        fedilink
        English
        arrow-up
        13
        ·
        11 months ago

        If they’re root, they already can. Like Google Play and other root/system apps that can install apps without the pop-up.

        Fun reminder that the Facebook system apps included on many phones can do that too. Look for system apps called “Facebook Bridge”, “Facebook stub”, “Facebook App Installer”, “Facebook App Manager” etc.

        • limerod@reddthat.comM
          link
          fedilink
          English
          arrow-up
          6
          arrow-down
          1
          ·
          11 months ago

          Don’t you mean: Meta app installer, meta app manager, meta services, etc.

      • Exec@pawb.social
        link
        fedilink
        English
        arrow-up
        5
        ·
        11 months ago

        That’s what I meant - if Google’s own stuff is allowed to run in the background then third-party stuff should be allowed too.

        • ChaoticNeutralCzech@feddit.de
          link
          fedilink
          English
          arrow-up
          5
          ·
          11 months ago

          I would not like everything to run as root. But an option to root your phone without too much hassle and make any changes to app permissions would be great.

          • BearOfaTime@lemm.ee
            link
            fedilink
            English
            arrow-up
            0
            arrow-down
            1
            ·
            11 months ago

            Fortunately, Pixel is easy to root these days with Magisk.

            Well, kind of easy. Takes a little technical ability, but the documentation is solid.

  • shiiiiiiiiiiiiiiiiit@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    40
    ·
    11 months ago

    a persistent notification is no longer required. A key icon in the status bar is the only indication you get that the VPN is enabled

    You still get the key icon. Is the fuss that it now takes more screen taps to reach the on/off, rather than just using the persistent notification?

    • limerod@reddthat.comM
      link
      fedilink
      English
      arrow-up
      31
      arrow-down
      5
      ·
      11 months ago

      The fuss is that 3rd party apps need a persistent notification to stay alive. But, because Google owns pixels, it can skip that step and be less intrusive/visible, which others can not.

      • out@lemmynsfw.com
        link
        fedilink
        English
        arrow-up
        17
        ·
        11 months ago

        The WireGuard and tailscale apps work great for me without a persistent notification.

        WireGuard doesn’t support notifications at all. Tailscale does and by default it shows a persistent notification but you can just silence it or turn it off in the apps notification settings.

        Persistent notification thus seems to be unnecessary for VPNs to function, Google/Android dev documentation recommends a persistent notification for the UX but it’s not needed. https://developer.android.com/guide/topics/connectivity/vpn

        In conclusion it appears that third party apps can indeed provide a VPN service without a notification.

        • limerod@reddthat.comM
          link
          fedilink
          English
          arrow-up
          2
          arrow-down
          2
          ·
          11 months ago

          Unfortunately, that will mean your app can be killed on many smartphones from device makers like xiaomi, Oppo, and huawei, which have aggressive battery optimization. I had this issue on a redmi device where background apps would be killed unless a permanent notification was present.

          The WireGuard and tailscale apps work great for me without a persistent notification.

          I haven’t tried wireguard. But, I should give them a try and see how it goes in samsung.

            • limerod@reddthat.comM
              link
              fedilink
              English
              arrow-up
              3
              arrow-down
              1
              ·
              11 months ago

              The ranking may make it sound like samsung is the worst. But that’s not been the case since android 12. I do not have app reload or app killing issues on this one and find it much better than what I used to experience on miui.

              • russjr08@outpost.zeuslink.net
                link
                fedilink
                English
                arrow-up
                5
                ·
                11 months ago

                I published an app on the play store that purely relies on a persistent notification + wakelocks to keep the screen active (since the whole point of the app is to keep the screen awake) - Samsung was definitely the worst when it comes to this for my app, as I would receive endless support emails about people with Samsung devices where it would get killed, even when disabling battery optimization for my app. The other manufacturers listed there came up every now and then, but disabling battery optimization generally did the trick for them.

                With there being nothing that I could do for my app, I tried disabling compatibility in the play store for a ton of Samsung models, but then I got even more emails about people wondering why it wasn’t available anymore so I re-enabled it, but to this day there’s still (AFAIK) zero things I can do to prevent the app from getting killed on those devices.

                • limerod@reddthat.comM
                  link
                  fedilink
                  English
                  arrow-up
                  1
                  ·
                  11 months ago

                  What app is that? I only notice app reload issues when I max my ram usage playing heavy games or running apps which maximum ram.

              • out@lemmynsfw.com
                link
                fedilink
                English
                arrow-up
                4
                ·
                edit-2
                11 months ago

                Clicking on Samsung makes it sound like it’s still a problem on Android 13 at least.

                I’m glad it works for you at least, I have never used a Samsung phone so I might be fixed altogether but idk.

                You could if you want, add an issue or something on their GitHub

                • limerod@reddthat.comM
                  link
                  fedilink
                  English
                  arrow-up
                  1
                  ·
                  11 months ago

                  I do not feel too strongly about it, so I will refrain. But, if I find the time and energy to spend, I may open an issue later.

          • folkrav@lemmy.world
            link
            fedilink
            English
            arrow-up
            2
            ·
            11 months ago

            I was under the impression that the “Disable battery optimisations” feature was to prevent exactly this. Maybe I misunderstood what it does, but a bunch of apps designed to run in the background tell you to disable this functionality for their app for this very reason.

          • ShortFuse@lemmy.world
            link
            fedilink
            English
            arrow-up
            1
            ·
            11 months ago

            That is for applications that need access to a LOCAL_SERVICE while not in foreground. That’s like Geolocation or screen orientation. VPN is not one of those. You can kill the foreground application from the recent apps by sliding up.

            No real VPN app needs to have an application window and a background service (same thread) running to provide a VPN. If it does, it is doing something else not related to VPN.

            If you want to add a pause button, applications can add custom tiles.

      • kadu@lemmy.world
        link
        fedilink
        English
        arrow-up
        8
        arrow-down
        1
        ·
        edit-2
        11 months ago

        Apps that target modern Android APIs do not need a persistent notification.

        Apps that insist on building against Android 5 targets in 2023 do, yes.

        • limerod@reddthat.comM
          link
          fedilink
          English
          arrow-up
          3
          ·
          11 months ago

          Persistent notification was added in response to android 8+ background restrictions. You didn’t need it before.

          Apps that need to be constantly alive do that to avoid being killed by the system on android devices that are not stock or pixel. Apps like tasker, accubattery, Internet speed meter, adguard all target the latest android version 12 or higher.

          We are on android 14. You can not install apps targeting android 5 from the playstore today.

          • kadu@lemmy.world
            link
            fedilink
            English
            arrow-up
            1
            ·
            11 months ago

            If they’re targeting modern Android, they can simply direct the user to the Battery settings panel where one can set the app to run arbitrarily in the background. No notifications are needed.

      • ShortFuse@lemmy.world
        link
        fedilink
        English
        arrow-up
        4
        ·
        edit-2
        11 months ago

        Cite your sources because that’s not how persistent notification works. PIA doesn’t need it. It sounds like a poorly written app.

        Edit: DNS66 as well.

        • limerod@reddthat.comM
          link
          fedilink
          English
          arrow-up
          1
          ·
          11 months ago

          I checked playstore reviews of wireguard, and people are complaining that wireguard stops working after a while. Which makes me think. For wider compatibility and persistent background tasks, you do need one to stay alive.

        • BearOfaTime@lemm.ee
          link
          fedilink
          English
          arrow-up
          1
          ·
          11 months ago

          Because (from what I’ve read) battery optimization may still kill them, depending on the phone.

          • Skull giver@popplesburger.hilciferous.nl
            link
            fedilink
            English
            arrow-up
            1
            ·
            11 months ago

            Perhaps, but this article is specifically about the Pixel which, to my knowledge, doesn’t have a task killer as aggressive as some other vendors have. The closer you come to Google/AOSP Android, the lower the probability that your tasks will get killed at random is my experience.

  • Polyester6435@lemmy.blahaj.zone
    link
    fedilink
    English
    arrow-up
    22
    arrow-down
    1
    ·
    11 months ago

    Persistent notification is one of the best parts about using an always on VPN. You can check the status really quickly

    • Zerfallen@lemmy.world
      link
      fedilink
      English
      arrow-up
      23
      arrow-down
      2
      ·
      11 months ago

      Would be better if it were optional. The little key in the status area is more than enough indication for me. A persistent notification is not a notification, it’s a hack.

      • BearOfaTime@lemm.ee
        link
        fedilink
        English
        arrow-up
        3
        ·
        11 months ago

        The hack is the aggressive battery optimization in some phones that don’t respect the native Android battery optimization settings and still kill apps.

        • Zerfallen@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          11 months ago

          I get it, and i guess the fault is on Google for not providing an alternative for such apps. Still a hack though, because such things don’t belong in the user’s notifications.

      • Fuck spez@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        1
        ·
        11 months ago

        It is optional unless I misunderstood. You can disable the persistent notification by disabling VPN notifications in the Google One app.

  • ShortFuse@lemmy.world
    link
    fedilink
    English
    arrow-up
    14
    ·
    edit-2
    11 months ago

    I don’t understand the article. They either aren’t clearly explaining the issue or just heavily misinformed.

    I have Google One and PIA. Both do the same thing, which is add a key to the top right of the screen. To me, that’s like a persistent notification.

    PIA has never needed to use the actual persistent notification API. There’s no reason to. Persistent notification is for application that don’t want their UI Window to terminate when Android gets memory pressured, or when wanting to use a local service (eg: Location or Orientation) when not the main foreground application. I can kill the PIA Window (swipe up from recent apps) and the VPN is still running.

    If Google One were able to activate VPN without changing my status bar, that’s a different story, and that’s not the case.

    Edit: DNS66 as well

    • anonymous_bot@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      ·
      11 months ago

      From what I understand, Google One had its own persistent notification (left side) when using the VPN as well as the normal key icon (right side). So now it just has the latter.

      • ShortFuse@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        edit-2
        11 months ago

        Nope. I have my Pixel 7 on Android 13 and my Pixel 8 on Android 14.

        The only difference is when you activate on Android 13, you get notification it’s connecting and it’s connected. Neither are permanent, and I can dismiss them.

        Android 14 has no notification and just shows you on the app it’s connected now (different UI).

        It never had a persistent notification, so I’d reason the author was misinformed or misunderstood the change when somebody told them.

  • itsJoelle@lemmy.world
    link
    fedilink
    English
    arrow-up
    10
    ·
    11 months ago

    Weird, my Pixel 6a currently doesn’t have a persistent notification when I use Proton. Is this a GrapheneOS thing? Just curious.

    • FutileRecipe@lemmy.world
      link
      fedilink
      English
      arrow-up
      5
      ·
      11 months ago

      Have you enabled notifications for it? I use Proton with GrapheneOS. I keep the ProtonChannel notifications disabled normally as I don’t need to see it. Enabling it, I see the persistent notification as expected.

  • kvothelu@lemmy.world
    link
    fedilink
    English
    arrow-up
    6
    ·
    11 months ago

    I am on pixel 6a and using third party vpn. there is no persistent notification. only key icon. I don’t see the issue here.