ProtonMail / ProtonMail/WebClients
Ditch google notifications
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.6k
- Forks
- 715
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
It seems weird that PM still relies on GCM/FCM for notifications.
Even with PM APK downloaded from the website, and having whitelisted PM in DNSfilter (personalDNSfilter | F-Droid - Free and Open Source Android App Repository 3), I can’t receive PM notifications if I do not open the app, because I blocked GCM/FCM adresses (mtalk.google.com 5, alt1-mtalk.google.com,…) with DNSfilter.
While we trust PM for keeping the minimum metadata, how can we know what Google keeps if PM needs to transmit data to their servers for each notification/message?
Furthermore, curcumventing GCM/FCM has been solved by other android app team, like Tutanota (the blog post also cites Mastodon):
Is there a plan to drop GCM/FCM (which as Tutanota highlights “includes Google’s tracking code for analytics purposes”) for SSE (Server Sent Events API) or another alternative ?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names Android notifications through GCM/FCM and suggests SSE or another alternative, but it identifies no repository files or tests. Start by mapping the existing notification architecture and evaluating the proposed alternatives; done would require an agreed replacement that avoids GCM/FCM while preserving notification delivery.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android
- Domain
- mobile-dev, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100