Privacy

31893 readers

428 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
Discord

much thanks to @gary_host_laptop for the logo design :)

founded 5 years ago

MODERATORS

147

Investigators seek push notification metadata in 130 cases (go.theregister.com)

submitted 8 months ago by baernhelm@feddit.de to c/privacy@lemmy.ml

30 comments fedilink hide all child comments

"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."

you are viewing a single comment's thread
view the rest of the comments

[–] GolfNovemberUniform@lemmy.ml 1 points 8 months ago* (last edited 8 months ago) (1 children)

            
              I'm not a very advanced Android programmer but I know it's possible to make something like universal instructions and dependency lists (if you want unification which I personally don't support). Linux has push notifications for years and on Android they work too if the app is running in the background. In my opinion the app should control the contact with its servers. Just make a daemon or something like that so the whole app doesn't have to stay in memory. Yes it's messy and battery life will be worse but monopolizing is always bad. Federating Firebase is a good idea too but I personally prefer the other method because it gives more flexibility
Video/music progress bar on Firefox for example

[–] Fisch@lemmy.ml 2 points 8 months ago (1 children)

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.

[–] GolfNovemberUniform@lemmy.ml 1 points 8 months ago* (last edited 8 months ago) (1 children)

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

[–] Fisch@lemmy.ml 2 points 8 months ago* (last edited 8 months ago) (1 children)

But that's why UnifiedPush exists, an open standard where you can choose what server to use or selfhost it

[–] GolfNovemberUniform@lemmy.ml 1 points 8 months ago (1 children)

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

[–] Fisch@lemmy.ml 1 points 8 months ago

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.