Modern & flexible browser fingerprinting library, a successor to the original fingerprintjs
Bonus points if you can remove as many
this. attribute accesses as possible since that means readers will easily understand the components are essentially stateless
at some point we could even move the components to separate files for readability
I think the biggest question remaining is how to handle errors.
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.
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.
Got a question. Have the latest version: 1.8.2. I have downloaded and unpacked zip file and run index.html
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?
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?
@/all I've just published a brand-new website for fingerprintjs library. Please check it out https://fingerprintjs.com
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.
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.
@dalakada_gitlab you're not only allowed, but encouraged!
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
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`
@ManukMinasyan usually it's hard to answer someone's questions based purely on screenshot.
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
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
@naydin2_gitlab of course it's being used on production. Thousands of companies are using it.
https://migrolpartnerevent.ch/event2019/ - please take a look to this link, open it with IE 11.
And take a look the console.
Thanks
And take a look the console.
Thanks
hi guys, i've come across this
http://uniquemachine.org
it can succesfully give me same fingerprint results on same device but on different browsers,
http://uniquemachine.org
it can succesfully give me same fingerprint results on same device but on different browsers,
@Valve @jonashaag do you have any plans to implement cross browser features (especially webgl with different setting) ?
I wasn't actually expecting a reply lol
Anyway... I'm trying to implement FPJS2 into a service of mine
But my objective with it is to store each customer object with the generated fingerprint as the "unique key"
For the first few weeks, everything had worked just fine
Altough for the last few days I've been having some issues with the hash repetition ratio
I'm actually getting identical hashes on different scenarios from different users, and this is causing a non-unique flaw into the whole structure
Am I actually using this library in the wrong way? Or is there something I can do to prevent the hash repetition?
thanks in advance :D
Or use human support to decide on a case by case basis