• deadcadeA
    link
    fedilink
    English
    arrow-up
    8
    ·
    7 months ago

    Most “standard” messaging apps (that includes signal, telegram) use the “OS provided” push service. On Android, they use firebase cloud messaging, a component of google play services.

    Degoogled Android means not having any notifications, unless the app supports UnifiedPush, runs in the background 24/7 (which drains battery), or runs in the background occasionally (which delays notifications).

    If the app runs in the background occasionaly, you can “burden” the people on the other side by being slow to respond.

    • wreckedcarzz@lemmy.world
      link
      fedilink
      English
      arrow-up
      5
      ·
      edit-2
      7 months ago

      Eh, I use a few apps that have true foss forks and thus don’t use gcm but the keep-alive method, and I didn’t notice a difference in battery when I made the switch.

      Also lol #3 isn’t exactly a “burden”, take the hint and go away people. Let me live in blissful solitude.

      • Stantana@lemmy.sambands.net
        link
        fedilink
        English
        arrow-up
        1
        ·
        7 months ago

        Pretty much my experience with pull-based notifications. I’ve even tested the same client on the same setup against both NTFY and client-pull without seeing a noticable difference in battery usage.

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

      Well I’d say those going the degoogle route learn about things like Unified, NLP, etc, along the way. But it is something the end user has to handle themselves, rather than it just being there in the OS.