“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.”
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
deleted by creator
The UnifiedPush standard is actually so simple, I don’t think a company could even make that proprietary if they wanted to. You need to keep in mind that it’s not sending the notification contents but just that there is a notification for a specific app.
I definitely agree that it’s best when apps support all methods, so UnifiedPush, running in the background and Firebase (that one just for the Google Play build). That way you can use whatever is best for you.