Modern & flexible browser fingerprinting library, a successor to the original fingerprintjs
components = {
canvas: function () {
return ...
},
audio: function (audioOptions) {
if (onIos && audioOptions.excludeIos11) {
return ...
} else {
return ...
}
}
}where return ... is the real fingerprinting code, and component functions are only passed their own options (if any), and simply return their value. That simplifies the code base a lot.
For async components we'll have to pass a callback as well (maybe leave async components as-is for now; they're a bit more complicated)
@jonashaag : sorry for my long silence, life got a bit busy.
Current WIP here: SleepProgger/fingerprintjs2@012d255
A bunch of changes in there:
- Added components dict and asyncComponents dict
- Each component now has its own options in options['components'][COMPONENT_NAME]; global options are on the "root" level (like options['preprocessor'] = foo)
- All key/value pairs are now sorted by the key before hashing to keep the hash stable without having to hardcode the order like it was before (also allows easier async handling)
- All keys are now camelCase
- I merged flashFonts and jsFonts keys under the "fonts" component
- Added fp.UNSUPPORTED and fp.EXCLUDED special values which components functions can return to signal that this component should be excluded/is unsupported. Both cases are currently removed in the get function.
There is still a bunch of stuff missing + i am not 100% on some decisions (check for //TODO: comments)
I am off to vacation in 2 days but will react to any critique / suggestions when back
this. attribute accesses as possible since that means readers will easily understand the components are essentially stateless
additionally error callback for async (Later to be changed to promises) and simply raising errors in sync components sounds like the nicest solution to me.
And when I run it locally and run at my site I see one difference that leads to diff fingerprints:
device_memory = 8 local and device_memory = -1 if I run it at my site (or even from local workstation but through local webserver). What is the difference? How does this value calculated?
It's been some time since I last worked on the library, but now I have more time and should spend more on it.
One recent feature that was added is that I removed all old tests that ran in PhantomJS and re-wrote them to use latest Chrome headless.
If you need a better accuracy + more featured product, I suggest you have a loot at a PRO version: https://fingerprintjs.com/pro
It's in a beta testing period currently but you can enroll
Hello dear developers,
When entering for the first time IE 11 loaded the site correctly you can see it in the first picture.
After refreshing the page we see that the page is not being loaded(see the second picture).
If you can help me, I will be grateful.
Thanks.
Images`
You should open up the dev tools and see if there are any errors in console. If there are, ask a question on Stackoverflow about JavaScript/error that you see.
If it's a FPJS specific question, ask it here.
In your case I see that the error has nothing to do with fingerprint.js so it should be asked elsewhere
And take a look the console.
Thanks
http://uniquemachine.org
it can succesfully give me same fingerprint results on same device but on different browsers,
