Are those strings generic enough? I mean, could it become a good fingerprinting point in the future?

Are those strings generic enough? I mean, could it become a good fingerprinting point in the future?

I was curious, so I tried to perform some analysis on vendor/renderer strings seen in the wild. I found this dataset: https://github.com/apify/fingerprint-suite/blob/master/packages/fingerprint-generator/src/data_files/fingerprint-network-definition.zip
I have no idea how reliable or unreliable the dataset is (and I couldn't find any more reliable ones which include vendor/renderer strings), but if we were to draw conclusions from it, it looks like ANGLE (Google, Vulkan 1.3.0 (SwiftShader Device (Subzero) (0x0000C0DE)), SwiftShader driver) (without the -5.0.0) might be more commonly seen in the wild, while not being tied to a specific chip manufacturer (Apple/Intel/AMD). If you think it would be better, I could replace the renderer string with this one.

For reference, here are the results and code I used to analyze this dataset: https://gist.github.com/dumbmoron/bfa33483d9ea1b1c5ac08b5a281af46e

While being less identifiable individually we were likely more identifiable as a group being the only browser that returned a blank string. This would at least help to blend in with legitimate values. It's also a good choice since it's platform-agnostic, that document mentioned windows 10 as an example but there's entries for other platforms such as linux for example.

I don't see any reason we'd want to make them more specific. It's better to keep them generic in order to reduce fingerprintability.

ah oops, looks like I misread your previous comment