Take a look, it might be valueable

[Onefivefournine]

Fingerprinting Chrome extensions by accessing resources related to them
https://github.com/z0ccc/extension-fingerprints

Nice fingerprinting collection targeted on gpu and device parameters
https://github.com/Song-Li/cross_browser/tree/master/client/fingerprint

P.S. Maybe start an "awesome fingerprinting" repo?😆

[abrahamjuliot]

Nice. The 2nd is one is amazing. I have the first one on my radar (it's a very nice project).

Maybe start an "awesome fingerprinting" repo

Love this idea!

[Onefivefournine]

I'm pasting it here not to overwhelm you with issues, just FYI
Chrome Devtools detection
https://stackoverflow.com/questions/7798748/find-out-whether-chrome-console-is-open
https://github.com/sindresorhus/devtools-detect

[abrahamjuliot]

That is very interesting. I might create a test page and combine something like this with a handful of event listeners.

[Onefivefournine]

Hey, just FYI - chrome changes list by version - that can be used to determine versions
https://chromestatus.com/roadmap

[abrahamjuliot]

https://chromestatus.com/roadmap

This is a great resource. I've been thinking on a concept here.

I have a different idea I might try at some point. It simplifies this to a hash table using something like.

hash(cssStyleKeys + windowKeys - clientWindowKeys) // specific version or set of versions

I'm currently using a version by version feature detection, but occasionally Opera, Edge, Brave or Chrome on Android will take an unexpected path/timeline on a feature, and it can't be relied on. But, it's good to be mindful of the changes. CSS is nice and stable.