“App developers can encrypt these messages when they’re stored (in transit they’re protected by TLS) but the associated metadata – the app receiving the notification, the time stamp, and network details – is not encrypted.”
“App developers can encrypt these messages when they’re stored (in transit they’re protected by TLS) but the associated metadata – the app receiving the notification, the time stamp, and network details – is not encrypted.”
I already explained how the whole push notification thing works in this comment. If you’re using a degoogled phone, you’ll be fine. MicroG has the option to use Firebase but you need to be logged in with a Google account, enable device registration and enable cloud messaging for it to use it. Google has the data about when you got a push notification from what app since it goes through their server and the app developer can obviously log the notification data from their app.
deleted by creator
I don’t like Google either but this design makes perfect sense. There’s a reason UnifiedPush works the same way. It sucks that you can’t choose a different server but that’s just how Google does things.
deleted by creator
If you have a better way to do this, I’d really like to hear it. Also, what additional features are you talking about?
deleted by creator
Apps running in the background was how it was done before but it drained a lot of battery, which is why it’s done this way now. Even KDE is implementing UnifiedPush. Things like the Firefox progress bar notification also don’t use this system at all.
deleted by creator
But that’s why UnifiedPush exists, an open standard where you can choose what server to use or selfhost it