• @wincing_nucleus073
    7•6 months ago

    I’ve thought about this for a long time. Nice to see it getting attention.

    this is why I don’t really appreciate Graphene’s sandboxed google play services as much as I appreciate MicroG. MicroG allows you to control which GPS-compatible apps get registered to your random ID on google’s servers.

    It’s also worth studying your individual apps and how exactly they handle google push notifications. I know that there are various configurations, some which allow Google to see the content of the notification and some which done. of course, regardless of that, metadata such as who it gets delivered to and when, is still there.

  • @miss_brainfart@lemmy.ml
    6•6 months ago

    What users often do not realize is that almost all such notifications travel over Google and Apple’s servers.

    So on the Android side, is an app safe from this if it doesn’t rely on Firebase Cloud Messaging?

    • @TheAnonymouseJoker@lemmy.mlM
      3•6 months ago

      Yes.

      Consider blocking Firebase domains in HOSTS file, which you can do in NetGuard or Invizible Pro, which you can supply your HOSTS file.

      Not sure if Hagezi or such community made HOSTS rulesets carry Firebase domains in their anti-Google/BigTech part of domains.

      There are no client side tools on Apple to accomplish this, unlike on any Android, no matter $50 or $5000.

        • @TheAnonymouseJoker@lemmy.mlM
          3•6 months ago

          These are in progressing order of complexity.

          • Exodus database shows the “bad” domains an app connects to.
          • Warden on F-Droid does a similar but more comprehensive job for any installed app packages.
          • App Manager shows activities, services, receivers and providers apps utilise or have in a comprehensive manner.
  • edric
    2•6 months ago

    Is it right that Apple is putting the responsibility of preventing it on app developers?