Gregory's Server@mysk Why do apps get such precise values at all instead of simply rounding them to the whole number or oke decimal place?
|
8 comments
@mysk Despite millions of users, tracking would most likely still be possible even with rounded values. Do apps send this data even if app tracking is deactivated via the system prompt? @lukasmueller Yes, it is sent despite opting out. App tracking is also denied. You can see that in the screenshot: "unifiedconfig.pii.advertisingTrackingId":00000000000000000 The value is zeros because I denied the apps access to tracking. @mysk I completely overlooked that. Thank you! @lukasmueller No worries 🙏 @mysk Even as an experienced user, one is unfortunately very limited in options, as there is always a compromise between data protection and usability. Especially on mobile devices and when using apps, the possibilities are limited. In addition, the major players don't need third-party tracking, and built-in tracking can easily be served by the content domains @mysk @lukasmueller this looks like just floating point error. Look at all the 9s in a row; floating point can’t exactly represent 0.35 so you get this close number. Looks like the system already rounding to 1/100 @lukasmueller @mysk Very good question. I wouldn’t be surprised if the backend of the Ad server is truncating them anyway - matching on 5 significant figures would be easier than what you’ve got there. I’m surprised they’re identical actually, unless the OS API isn’t entirely real time. What are the odds of two apps requesting that data one after the other and it actually being the same to that level of precision? |
@lukasmueller Good question, but do you think it will make a difference if the system returns 0.35 instead of 0.3499999940395355?
Other properties combined would still work well at identifying the device.