this post was submitted on 02 Jul 2025
160 points (98.8% liked)
United States | News & Politics
3069 readers
1347 users here now
Welcome to !usa@midwest.social, where you can share and converse about the different things happening all over/about the United States.
If you’re interested in participating, please subscribe.
Rules
Be respectful and civil. No racism/bigotry/hateful speech.
Post anything related to the United States.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I would be curious to learn more about how the OS requires an app to collect data.
Play store requires a home address for app downloads, both for the publisher and any users, so it would allow precise targeting of people if they ask google to disclose the information. No idea why this isn’t published on F-Droid though .
They're iOS devs and probably don't want or know how to do a java project. This can 100% be on fdroid. If anyone knows kotlin or otherwise wants to build the thing please link the github for us.
Their explanation for why it can't be on Android is that the nature of Android push notifications is such that they (the developers) would need to maintain a database of device IDs that could be tied back to physical devices and potentially be used to deanonymize which users received which alerts.
To me, this sounds lazy and like something that could be mitigated with End-To-End encryption.
Yeah they're Apple devs who don't understand Apple was caught in the same push notification scandal. The small technical differences don't matter. Push notifications can have interchangeable providers or none at all now on android.
Someone please help them, I bet their unit tests are nonexistent.
They mean push notifications where you need to store a device identifying URL to push your notifications to.
If traceability is a concern, using the native iOS notifications is not much better, you just move the burden to Apple (which I assume will be more than happy to cooperate, given they're an American corporate), so nothing is really solved.
The only good solution is your own backend which knows nothing and each app installation maintains a permanent WebSocket connection, then you push them to each client.