@JohnnyRuhlen@eric_seufert I think that's what users will come to expect - as they should - but I read "not in scope" as meaning [the enforcement of ATT does not apply in this case] - when the data is collected via another device/outside of iOS.
@JohnnyRuhlen@eric_seufert Actually that link explicitly contradicts you: "Data collected separately, outside of the app and not related to the app is not in scope." - so I was wrong, apple has actually made it clear that this is indeed device specific and does not apply outside of iOS.
@eric_seufert Core of the issue is that ATT is device level but many of these identifiers are user level. Making for a very tough/vague decision for advertisers and practically impossible enforcement.
@eric_seufert What is very unclear is how advertisers should handle multi-device users, and the identifiers (email) that they receive from each device. Say you have an ios app and a web app. End-user ejects ATT, clearly you can't use idfa, but email gathered via web app seems fair game.
@eric_seufert Any of these and other fingerprinting-like solutions can achieve near-deterministic/high probability targeting, that's not a question. But it's all unusable/pointless - explicitly against the app store policy without the use of ATT framework, and unacceptable risk for brands.
@JakeWharton@strangemonad@jessewilson Also in my view part of the context of that library is the assumption that you have a working node setup and don't want to spend a second longer thinking about Java/maven than you have to.
@CodingItWrong that said - we can definitely do better than 61 kB. I think this is the result of too much polyfilling to ensure we "just work" on all browsers.
@CodingItWrong hey Josh! A key goal for us is reducing your site's size by moving integrations server-side (and enable much more than analytics :)). Would love to help figure out why it's 172 kB for you, it's actually 61 kB: curl -sI --compressed https://t.co/Uxb5NzIi5t | grep -i Content-Length
@jfrog@sonatype Thx for checking! Unfortunately still no luck. As an example, com.mparticle:android-core:5.4.3 is in Central but not in jCenter. I have ~30 artifacts in that package, the last version that is mirrored completely was 5.4.0. 5.4.1-2 are partially mirrored, 5.4.3 is missing entirely