At the moment, we use hardware to generate a fingerprint. But given the same hardware (e.g. two iphone users) it's very likely to result in fingerprint collision (need to check this! couple of articles on google about collisions).
Therefore, we need to add more factors into the fingerprint mechanism to discern these users. These factors need to be constant across websites. E.g. browser agent string (though would this change with updates? e.g. v1.2.3 -> v1.2.4 would change the fingerprint?)
The fingerprint needs to remain constant over time and across websites.
there may always be an amount of collisions for the fingerprinting, so may need to just accept an amount of people will get through by duplicate fingerprint, but we need to make sure this is as low as possible
At the moment, we use hardware to generate a fingerprint. But given the same hardware (e.g. two iphone users) it's very likely to result in fingerprint collision (need to check this! couple of articles on google about collisions).
Therefore, we need to add more factors into the fingerprint mechanism to discern these users. These factors need to be constant across websites. E.g. browser agent string (though would this change with updates? e.g. v1.2.3 -> v1.2.4 would change the fingerprint?)
The fingerprint needs to remain constant over time and across websites.