3 ms·

not exactly. on ios it's 100% their servers with wide open data. elsewhere if you use firefox their webnotification push servers use a e2ee schema. also on An

not exactly. on ios it's 100% their servers with wide open data. elsewhere if you use firefox their webnotification push servers use a e2ee schema. also on Android apps have the option to not use google's server and pull (e.g. ntfy) ... aren't you glad you bought an iphone thanks to all that "we respect your privacy" marketing? /s

cubefox 3y ago
If you are forced to use a third party for push notifications, there should be end-to-end encryption by default. Really strange they don't do this.
Klonoar 3y ago
It’s “wide open data” if app developers choose to build that way. It’s not rocket science to obscure push notification data. Your beef should be with the app devs who don’t go the extra mile, not Apple.
- withinboredom 3y ago
  If I sent a message to a group of friends, you don't need to know the contents if all you want to know is who my friends are. Just look for groups of people getting notifications at the same time. After a few messages, you'll know exactly who is in that group. I did some anonymization across hundreds of millions of users for some GDPR stuff a few years ago. If I knew when you made a purchase, to within a day, for two separate one-off purchases of our products ... I could deanonymize you. Specifically just you. If you had a subscription payment, and I knew at least one payment you were late on, and the hour you eventually paid it ... I could deanonymize you down to a group of 3-4 people. Correlation and timing are huge for deanonymizing things in otherwise anonymous data. We had to round our dates to the week to keep some of our analytical data anonymous.
  - Klonoar 3y ago
    Yeah, no. You're missing the point of this thread here. > Just look for groups of people getting notifications at the same time. In a sufficiently built system - like what Signal does, and like what most apps should be learning from - all the notification payload is getting is a "check for updates" command. You and literally everyone else are getting that generic notification all the time if you're in more than one chat. Just because Alice sent a message at 12:01PM and Bob received the generic "check me" notification at 12:02PM doesn't mean Bob necessarily received Alice's message specifically, because the notification has absolutely no concept of the messages period. Bob could have gotten that notification due to any of the other chats he's in. At best the argument here is that the government could use the push notification token to link a Signal account to a real username via Apple, but if you're that paranoid you shouldn't use an iOS device anyway. You also likely wouldn't use Signal due to the phone number issue.
    - withinboredom 3y ago
      The birthday paradox won't save you here, there is too much noise.
- ksjskskskkk 3y ago
  oh, right. let me talk to the devs of imessage, which is one of the notifications hinted at the origin of this discussion last week
  - Klonoar 3y ago
    Look, if all you're after here is an "I hate Apple" pity party, you can do better: iMessage is default backed up to iCloud - without encryption - and offers an even easier workaround for the government. I would have to imagine they get more from that than notification payloads. It's pretty simple: don't use iMessage if you value secure communication, since we know Apple gets hamstrung by the government at points. Devs building for the platform should be taken to task here because they need to be aware of and optimize around the data leaking issue, relying on the parent platform to always be a good steward is a recipe for disaster.

cubefox 3y ago

If you are forced to use a third party for push notifications, there should be end-to-end encryption by default. Really strange they don't do this.

Klonoar 3y ago

It’s “wide open data” if app developers choose to build that way. It’s not rocket science to obscure push notification data. Your beef should be with the app devs who don’t go the extra mile, not Apple.

withinboredom 3y ago
If I sent a message to a group of friends, you don't need to know the contents if all you want to know is who my friends are. Just look for groups of people getting notifications at the same time. After a few messages, you'll know exactly who is in that group. I did some anonymization across hundreds of millions of users for some GDPR stuff a few years ago. If I knew when you made a purchase, to within a day, for two separate one-off purchases of our products ... I could deanonymize you. Specifically just you. If you had a subscription payment, and I knew at least one payment you were late on, and the hour you eventually paid it ... I could deanonymize you down to a group of 3-4 people. Correlation and timing are huge for deanonymizing things in otherwise anonymous data. We had to round our dates to the week to keep some of our analytical data anonymous.
- Klonoar 3y ago
  Yeah, no. You're missing the point of this thread here. > Just look for groups of people getting notifications at the same time. In a sufficiently built system - like what Signal does, and like what most apps should be learning from - all the notification payload is getting is a "check for updates" command. You and literally everyone else are getting that generic notification all the time if you're in more than one chat. Just because Alice sent a message at 12:01PM and Bob received the generic "check me" notification at 12:02PM doesn't mean Bob necessarily received Alice's message specifically, because the notification has absolutely no concept of the messages period. Bob could have gotten that notification due to any of the other chats he's in. At best the argument here is that the government could use the push notification token to link a Signal account to a real username via Apple, but if you're that paranoid you shouldn't use an iOS device anyway. You also likely wouldn't use Signal due to the phone number issue.
  - withinboredom 3y ago
    The birthday paradox won't save you here, there is too much noise.
ksjskskskkk 3y ago
oh, right. let me talk to the devs of imessage, which is one of the notifications hinted at the origin of this discussion last week
- Klonoar 3y ago
  Look, if all you're after here is an "I hate Apple" pity party, you can do better: iMessage is default backed up to iCloud - without encryption - and offers an even easier workaround for the government. I would have to imagine they get more from that than notification payloads. It's pretty simple: don't use iMessage if you value secure communication, since we know Apple gets hamstrung by the government at points. Devs building for the platform should be taken to task here because they need to be aware of and optimize around the data leaking issue, relying on the parent platform to always be a good steward is a recipe for disaster.