Technology

59421 readers

2822 users here now

This is a most excellent place for technology news and articles.

Our Rules

Follow the lemmy.world rules.
Only tech related content.
Be excellent to each another!
Mod approved content bots can post up to 10 articles per day.
Threads asking for personal tech support may be deleted.
Politics threads may be removed.
No memes allowed as posts, OK to post as comments.
Only approved bots from the list below, to ask if your bot can be added please contact us.
Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 1 year ago

MODERATORS

[email protected]

170

Phone Push Notifications: A Double-Edged Sword for User Privacy and Law Enforcement (www.theregister.com)

submitted 8 months ago by [email protected] to c/[email protected]

18 comments fedilink hide all child comments

Summary:

US courts have received over 130 requests from law enforcement to access push notification data from phones, reported the Washington Post.
This data can reveal a user's location, device details, IP address, and more, even if they use encrypted messaging apps.
This raises concerns about privacy, as prosecutors and foreign governments could potentially access this data for various reasons.
While Apple and Google are promising more transparency regarding data requests, security experts highlight the potential for abuse by governments and marketing organizations.

Key Points:

Push notification metadata includes information like the app receiving the notification, timestamp, and network details.
This data is not encrypted and can be used to track user movements and activity.
Law enforcement can use this data for investigations, but it also raises concerns about potential misuse by other parties.
Experts recommend increased awareness about the information users share through push notifications and the potential privacy risks involved.

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

[–] [email protected] 30 points 8 months ago (3 children)

If every app on your phone was constantly running and asking the server for new messages, it would drain a lot of battery. That's why phones instead use a single app that asks a notification server if any new notifications are there. The way it works is if you e.g. get a WhatsApp message, the WhatsApp server tells the notification server that you have a new message, then when the notification app asks that server for new messages, the server will tell it that there's a new WhatsApp notification. Then the notification app wakes up WhatsApp and tells it there's a new notification, then WhatsApp checks for new messages and shows you the notification.

Most apps use Apple's system (whatever it's called) on iOS or Google's Firebase on Android for that. There are also apps that let you use the open standard UnifiedPush, which let's you use any notification app or server you want.

[–] [email protected] 3 points 8 months ago (1 children)

I don't have Google services and no apps with Google Firebase notifications. I don't see any battery draining issues.

[–] [email protected] 15 points 8 months ago* (last edited 8 months ago) (1 children)

Depends on a lot of factors, maybe you're regaining that battery life elsewhere. But it is fact that several apps all doing their own thing will drain more battery than if they all relied on a single service like Firebase or UnifiedPush to wake them up

[–] [email protected] -3 points 8 months ago

I haven't found a study that gives exact numbers. Maybe the difference in battery consumption will be 0.5%)

[–] [email protected] 3 points 8 months ago (1 children)

How does the notification daemon in Linux work? It's all local and has been around for ages, why can't we do that?

[–] [email protected] 8 points 8 months ago

The applications just run in the background the whole time. KDE was working on implementing UnifiedPush in Plasma but I don't know if it's already implemented or still in the works.