silverrump

4 ms·

1. 1.▲
   by silverrump 9mo ago

   Thanks for trying it and calling out problems — it helped us find and fix the bug. The issue has now been resolved and DevicePrint should give much more sensible results going forward.
2. 2.▲
   by silverrump 9mo ago

   Totally hear you — we appreciate the critique. We’ve now fixed a real issue that was skewing results, and the current version relies on deterministic signals rather than anything heuristic or generative.
3. 3.▲
   by silverrump 9mo ago

   Yes — browsers isolate storage between containers, so that behavior is expected. Fingerprints will be consistent within a given profile unless significant attributes change.
4. 4.▲
   by silverrump 9mo ago

   We’ve just deployed a fix to the core matching logic that should significantly improve accuracy and reduce false positives. Feel free to retry at https://deviceprint.io and share your results!
5. 5.▲
   by silverrump 9mo ago

   Thanks for pointing that out — we’ve corrected the display so no other visitors’ IPs or locations are shown. We take privacy seriously and have updated the site to reflect that.
6. 6.▲
   by silverrump 9mo ago

   Good question — we’ve taken that feedback seriously. We’re currently working on making more documentation publicly accessible without a login, so people can evaluate DevicePrint before signing up.
7. 7.▲
   by silverrump 9mo ago

   Thanks everyone for the detailed reports — the strange multiple visits and location jumps were due to a bug in how we combined signals. This has now been resolved, and subsequent fingerprints should be much more accurate across browsers and
8. 8.▲
   by silverrump 9mo ago

   Good catch — that was exactly the symptom of the issue we just resolved. The over-counting was caused by fingerprint collisions in certain edge cases. The fix has been deployed, so it shouldn’t happen on new uses anymore. Thanks for the fee
9. 9.▲
   by silverrump 9mo ago

   Thanks for checking it out! We’ve identified the root cause of the inaccurate visit counts you saw and have now fixed the issue — the accuracy of DevicePrint should be much better now. If you have any remaining odd results, let us know!
10. 10.▲
    by silverrump 9mo ago

    Happy to answer any technical questions or discuss implementation details.
11. 11.▲
    Show HN: DevicePrint – device fingerprinting without cookies

    21 points by silverrump 9mo ago|50 comments