▲ 755 ▼ Trump Team Has Full Meltdown Over CNN Story on ICE-Tracking App (newrepublic.com) submitted 1 year ago by chobeat@lemmy.ml to c/technology@lemmy.world 106 comments fedilink hide all child comments
[–] ayyy@sh.itjust.works 0 points 1 year ago (4 children) That’s not how push notifications on android work. permalink fedilink source parent hideshow 4 child comments replies: [–] Ghoelian@lemmy.dbzer0.com -1 points 1 year ago (3 children) That doesn't have anything to do with how you install the app. permalink fedilink source parent hideshow 3 child comments replies: [–] ayyy@sh.itjust.works -2 points 1 year ago (2 children) It has to do with receiving notifications from the app in a privacy-preserving way. Unless the app is running with a server connection 24/7 (RIP battery life) you need to rely on the OS to deliver notifications. permalink fedilink source parent hideshow 2 child comments replies: [–] Ghoelian@lemmy.dbzer0.com 4 points 1 year ago (1 child) You don't, there's privacy respecting ways of delivering notifications in android. Also, a 24/7 connection to a server isn't nearly as bad as you might think. The connection isn't active the whole time, it only uses any significant amount of battery if there's actually data being sent or received. You likely already have quite a few of them anyway, how do you think systems normally listen for push notifications? Besides all that, I read in other comments that the privacy issue was the device id firebase needs. Obviously apple also needs some kind of device id, otherwise how do they know where the notifications are going? Did some searching, yup apple also needs a unique identifier: When it’s time to send a notification, you generate a request that contains the notification data and a unique identifier for the user’s device. From https://developer.apple.com/documentation/usernotifications/setting-up-a-remote-notification-server permalink fedilink source parent hideshow 1 child comment replies: [–] SMillerNL@lemmy.world 1 point 1 year ago Apple notification identifiers are unique to an app install and regularly change though, so it’s hardly a device identifier. permalink fedilink source parent
[–] Ghoelian@lemmy.dbzer0.com -1 points 1 year ago (3 children) That doesn't have anything to do with how you install the app. permalink fedilink source parent hideshow 3 child comments replies: [–] ayyy@sh.itjust.works -2 points 1 year ago (2 children) It has to do with receiving notifications from the app in a privacy-preserving way. Unless the app is running with a server connection 24/7 (RIP battery life) you need to rely on the OS to deliver notifications. permalink fedilink source parent hideshow 2 child comments replies: [–] Ghoelian@lemmy.dbzer0.com 4 points 1 year ago (1 child) You don't, there's privacy respecting ways of delivering notifications in android. Also, a 24/7 connection to a server isn't nearly as bad as you might think. The connection isn't active the whole time, it only uses any significant amount of battery if there's actually data being sent or received. You likely already have quite a few of them anyway, how do you think systems normally listen for push notifications? Besides all that, I read in other comments that the privacy issue was the device id firebase needs. Obviously apple also needs some kind of device id, otherwise how do they know where the notifications are going? Did some searching, yup apple also needs a unique identifier: When it’s time to send a notification, you generate a request that contains the notification data and a unique identifier for the user’s device. From https://developer.apple.com/documentation/usernotifications/setting-up-a-remote-notification-server permalink fedilink source parent hideshow 1 child comment replies: [–] SMillerNL@lemmy.world 1 point 1 year ago Apple notification identifiers are unique to an app install and regularly change though, so it’s hardly a device identifier. permalink fedilink source parent
[–] ayyy@sh.itjust.works -2 points 1 year ago (2 children) It has to do with receiving notifications from the app in a privacy-preserving way. Unless the app is running with a server connection 24/7 (RIP battery life) you need to rely on the OS to deliver notifications. permalink fedilink source parent hideshow 2 child comments replies: [–] Ghoelian@lemmy.dbzer0.com 4 points 1 year ago (1 child) You don't, there's privacy respecting ways of delivering notifications in android. Also, a 24/7 connection to a server isn't nearly as bad as you might think. The connection isn't active the whole time, it only uses any significant amount of battery if there's actually data being sent or received. You likely already have quite a few of them anyway, how do you think systems normally listen for push notifications? Besides all that, I read in other comments that the privacy issue was the device id firebase needs. Obviously apple also needs some kind of device id, otherwise how do they know where the notifications are going? Did some searching, yup apple also needs a unique identifier: When it’s time to send a notification, you generate a request that contains the notification data and a unique identifier for the user’s device. From https://developer.apple.com/documentation/usernotifications/setting-up-a-remote-notification-server permalink fedilink source parent hideshow 1 child comment replies: [–] SMillerNL@lemmy.world 1 point 1 year ago Apple notification identifiers are unique to an app install and regularly change though, so it’s hardly a device identifier. permalink fedilink source parent
[–] Ghoelian@lemmy.dbzer0.com 4 points 1 year ago (1 child) You don't, there's privacy respecting ways of delivering notifications in android. Also, a 24/7 connection to a server isn't nearly as bad as you might think. The connection isn't active the whole time, it only uses any significant amount of battery if there's actually data being sent or received. You likely already have quite a few of them anyway, how do you think systems normally listen for push notifications? Besides all that, I read in other comments that the privacy issue was the device id firebase needs. Obviously apple also needs some kind of device id, otherwise how do they know where the notifications are going? Did some searching, yup apple also needs a unique identifier: When it’s time to send a notification, you generate a request that contains the notification data and a unique identifier for the user’s device. From https://developer.apple.com/documentation/usernotifications/setting-up-a-remote-notification-server permalink fedilink source parent hideshow 1 child comment replies: [–] SMillerNL@lemmy.world 1 point 1 year ago Apple notification identifiers are unique to an app install and regularly change though, so it’s hardly a device identifier. permalink fedilink source parent
[–] SMillerNL@lemmy.world 1 point 1 year ago Apple notification identifiers are unique to an app install and regularly change though, so it’s hardly a device identifier. permalink fedilink source parent