11–20 of 70 posts
Earlier quoted context omitted.
.ai is a ccTLD. Being AI related is not a factor to get one.
But they are considerably more expensive than more common TLDs, so if you’re getting one you presumably want it specifically and understand the association users will make.
Earlier quoted context omitted.
.ai is a ccTLD. Being AI related is not a factor to get one.
But they are considerably more expensive than more common TLDs, so if you’re getting one you presumably want it specifically and understand the association users will make.
Besides, they do sell AI-related services.
Why does this have a domain of .ai, what exactly it is doing AI related?
> This can happen due to several reasons:
> [...] JavaScript Errors: When any of the 24+ fingerprint collection methods throws an error [...]
So when any of the browser APIs it exploits aren't available, it just fails instead of using that as a datapoint in itself. I'm unimpressed.
Is there any library I could use for HW finger printing? I'd like to detect and ban evasions.
Perhaps I'm missing it but does it explain what aspects of your setup contribute the most to your score or suggest remedial actions? I wasn't that surprised to find that my standard setup is highly fingerprintable (for one, I use Firefox which alone is enough to single me out in a crowd) but I also tried using a vanilla Chromium install via a popular commercial VPN and still got a rating of 100%.
https://blog.castle.io/what-browser-fingerprinting-tests-lik...
Still nowhere near as good as creepjs: https://abrahamjuliot.github.io/creepjs/ Doesn't even detect common browser extensions.
Perhaps I'm missing it but does it explain what aspects of your setup contribute the most to your score or suggest remedial actions? I wasn't that surprised to find that my standard setup is highly fingerprintable (for one, I use Firefox which alone is enough to single me out in a crowd) but I also tried using a vanilla Chromium install via a popular commercial VPN and still got a rating of 100%.