this post was submitted on 04 Mar 2024
149 points (96.3% liked)
Privacy
31975 readers
239 users here now
A place to discuss privacy and freedom in the digital world.
Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.
In this community everyone is welcome to post links and discuss topics related to privacy.
Some Rules
- Posting a link to a website containing tracking isn't great, if contents of the website are behind a paywall maybe copy them into the post
- Don't promote proprietary software
- Try to keep things on topic
- If you have a question, please try searching for previous discussions, maybe it has already been answered
- Reposts are fine, but should have at least a couple of weeks in between so that the post can reach a new audience
- Be nice :)
Related communities
Chat rooms
-
[Matrix/Element]Dead
much thanks to @gary_host_laptop for the logo design :)
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Tbh I absolutely do not understand why they decided to collect any data for push notifications in the first place. But yea now nobody will fix it. Though I'm wondering if it's only the proprietary part (Firebase or whatever the name is) or the system itself that collects data. I mean if I use a degoogled phone that doesn't even have that proprietary part (means notifications from IMSes don't work either), am I safe from this or not? And does the collected data go to Google or to the app's developers?
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.
BRUH push notifications with Firebase require everything going through a Google server? What in the deleted is that design?
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.
In my opinion there's absolutely no point in sending notifications through Google. It can be done differently and in a much less overengineered way. Unification doesn't make sense here. The additional features don't work in half of the apps now anyways
If you have a better way to do this, I'd really like to hear it. Also, what additional features are you talking about?
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.
Well here it's a matter of personal preference. For me privacy is more important than battery life and I consider Firebase extremely immoral. It can be different for other people. And thank you for telling about Firefox
But that's why UnifiedPush exists, an open standard where you can choose what server to use or selfhost it
As I said earlier, this idea is good too. Open push standards are generally the best for efficiency but they can become proprietary or die (usually after getting bought by a big tech company) and even if a fork emerges it may be difficult to switch to it since it's an important component and 100% compatibility with the previous standard is not always possible. That's the main problem with unification and monopolization. The open standards can run into severe issues and then everything may collapse. When apps control the notifications, such risk is almost completely mitigated. Even though the described scenario is generally unlike to happen, push notifications have always been very "interesting" for big tech which rises the concerns about the stability of open push standards. Fortunately it's possible to make an app that can work in both push and standalone modes (e.g. Telegram) which is good I guess
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.