> It provides the required information only when the server requests it In the interest of fingerprinting a server would request this every time. > It provide

> It provides the required information only when the server requests it In the interest of fingerprinting a server would request this every time. > It provides the information in small increments, so servers are only exposed to the information they need and request Then the server would need and request the most comprehensive list possible in order to fingerprint someone with better granularity than a UA string could. I'm not against this as I appreciate the value of this kind on information for the developers. It would be done one way or another. But why is this billed as mainly a privacy move? Nothing suggests it intrinsically offers better privacy when facing a website configured to fingerprint you. It actually looks like it gives even more granular info over which the user has less control than they used to with the UA.