Chrome wants to get rid of fingerprinting, and has for many years (see the entire Privacy Sandbox effort). But they cannot do it unilaterally, they need to iden

Chrome wants to get rid of fingerprinting, and has for many years (see the entire Privacy Sandbox effort). But they cannot do it unilaterally, they need to identify the legit use cases and design + implement new privacy-preserving technologies to meet those use cases. (Yes, yes, we all know Apple and Firefox have been able to such things unilaterally. But as we've seen by the different reception from Apple having shipped remote integrity attestations in prod for a year to Chrome just proposing it, the rules aren't the same for all browsers.) Fraud prevention/anti-abuse is both an extensive use case for fingerprinting and the most obviously legitimate one. If we demand that browsers close off all the fingerprinting loopholes (it's a great goal!) but don't allow a replacement, the web will be mostly dead as a platform in 10 years. All economic activity will move to native apps on walled garden platforms that are able to provide effective anti-fraud mechanisms.