Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Advice of data point permanence #132

Open
zkwbbr opened this issue Nov 9, 2021 · 1 comment
Open

Advice of data point permanence #132

zkwbbr opened this issue Nov 9, 2021 · 1 comment

Comments

@zkwbbr
Copy link

zkwbbr commented Nov 9, 2021

I am using the ff. data points to generate a fingerprint:

getBrowser()
getOS()
getOSVersion()
getScreenPrint()
getTimeZone()
getLanguage()
getFonts()
getCanvasPrint()
getEngine()
navigator.hardwareConcurrency
navigator.deviceMemory
navigator.maxTouchPoints

To me this looks "permanent" enough unless there is major change in the user's device. However some users still occasionally experience a different fingerprint. Are there any data points from the above that might change in case a user's browser updates?

@zkwbbr
Copy link
Author

zkwbbr commented Feb 6, 2022

For those who care, I've found out during testing that the JS property screen.availHeight can potentially change during a browsing session by a few pixels even if the user doesn't do anything. I believe this is what's causing the issue in my post above.

This property is used by these clientJs methods: getAvailableResolution() and getScreenPrint().

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant