> But that could be tackled the same way they've blocked all the other fingerprinting methods (fuzzing, threat of blocking, etc.) The reason browsers implement

> But that could be tackled the same way they've blocked all the other fingerprinting methods (fuzzing, threat of blocking, etc.) The reason browsers implement convoluted AI-based systems for things like rejecting cookies is that browser makers can't risk the regulatory fallout of blocking without a consistently enforced and static business policy. Not implementing a feature at all is a great way to avoid getting in a conflict, such as a lawsuit in some international jurisdiction over whether blocking a particular use of bluetooth is anticompetitive. Thats ignoring that some of the most harmful forms abuse come from those who are willing to register hundreds of throwaway domains to avoid static block lists. Block lists are based on location and not on legal entity.