

I wasn’t suggesting it as “font list and you’re done”. I was using it as an example because it’s one where I’m apparently really unusual.
I would think you’d basically want to spoof all known fingerprinting metrics to be whatever is the most common and doesn’t break compatibility with the actual setup too much. Randomizing them seems way more likely to break a ton of sites, but inconsistently, which seems like a bad solution.
I mean hypothetically you could also set up exceptions for specific sites that need different answers for specific fields, essentially telling the site whatever it wants to hear to work but that’s going to be a lot of ongoing work.
Nu-Cu-Lar Bad? That’s…about as far as they’ll make it. To be fair, that might be as far as they need to. It’s all the oil companies will approve of them learning, at least.
Of course, it sounds like the big problem of how to remove more power from it than you spend keeping it reacting remains an issue, presuming they can continue to extend reaction lifetimes to be functionally unlimited.