Maybe, but at least the people who host their own push notification servers can do it entirely on their own accord, without burdening people on the other side of their communications.
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.
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.
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.
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.
Maybe, but at least the people who host their own push notification servers can do it entirely on their own accord, without burdening people on the other side of their communications.
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.
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.
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.
It also means you will be on a very short list of people who use Unified Push.
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.