• 0 Posts
  • 9 Comments
Joined 2 years ago
cake
Cake day: June 20th, 2023

help-circle



  • The label for the language picker is an issue, but the choices themselves? In the target language. You want French? You pick “Français”. You want Japanese? You pick “日本語”. You want english? You pick “English”.

    Supposedly, if you’d rather have a website in a given language, you must have some level of understanding of that language, and picking its name should not be a challenge in any case. If you somehow change a site/app to a language you don’t know, as long as you can identify the language picker, you’ll be able to change to something you understand.

    It does leave out the case of a user wanting to change to a language they do not understand, but I do not care for those.



  • The same way with iOS. At some point, the third-party service have a way to link a push to a device. It does not mean that you can link an user to a device, or a specific request to a device. You get a unique ID for the notifications, yeah. And someone could tell that the app server have these ID. But that’s not particularly different with iOS. It not being exposed to the app dev directly does not mean that this info does not exist on the third-party server, that can still get asked about it.

    Unless Apple found a way to magically send a message to a specific device, from a specific external server, without anyone, anywhere, having any idea where the notification should go. Which, fair, could be done by sending every messages to everyone after encrypting it for a specific recipient, but that would be a bit inefficient at this scale. The trace for push notifications exists, whether you’re using Apple or Google as the backend.