DeGoogle Yourself

16980 readers

384 users here now

A community for those that would like to get away from Google.

Here you may post anything related to DeGoogling, why we should do it or good software alternatives!

Rules

Be respectful even in disagreement
No advertising unless it is very relevent and justified. Do not do this excessively.
No low value posts / memes. We or you need to learn, or discuss something.

Related communities

!privacyguides@lemmy.one !privacy@lemmy.ml !privatelife@lemmy.ml !linuxphones@lemmy.ml !fossdroid@social.fossware.space !fdroid@lemmy.ml

founded 6 years ago

MODERATORS

CrypticCoffee@lemmy.ml

Byereddithellolemmy@lemmy.world

chevy9294@monero.town

Why Signal Calls Google (media.ccc.de)

submitted 11 hours ago by 45o3b@lemmy.ml to c/degoogle@lemmy.ml

11 comments fedilink hide all child comments

I just started my de-googling journey recently, and so the mechanics of notifications were still unclear to me, and I found this video super helpful.

It explains how most mobile messaging apps (including privacy-focused ones like Signal) rely on Google and Apple's centralized servers to deliver push notifications, which exposes vast amounts of user metadata.

Here's the YT link, for people who prefer it: https://youtu.be/c3ennD3wKn0

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

[–] Aporia@lemmy.ml 1 points 1 hour ago* (last edited 1 hour ago)

From what I recall, Google would be able to see our device received a notification and when but not the actual message nor sender/recipient identity.

I think that's fine for my threat model.

Molly seems like a potential alternative though since its a signal fork and supports UnifiedPush so you can choose a different notification supplier like ntfy or sunup