59
Reducing my browser fingerprint?
(slrpnk.net)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 27 Dec 2024
59 points (95.4% liked)
Privacy
32506 readers
1154 users here now
A place to discuss privacy and freedom in the digital world.
Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.
In this community everyone is welcome to post links and discuss topics related to privacy.
Some Rules
- Posting a link to a website containing tracking isn't great, if contents of the website are behind a paywall maybe copy them into the post
- Don't promote proprietary software
- Try to keep things on topic
- If you have a question, please try searching for previous discussions, maybe it has already been answered
- Reposts are fine, but should have at least a couple of weeks in between so that the post can reach a new audience
- Be nice :)
Related communities
much thanks to @gary_host_laptop for the logo design :)
founded 5 years ago
MODERATORS
So server code is your fingerprint based on what a server is able to see. This would be your fingerprint with JS disabled, essential. Client code is the JS generated fingerprint.
For the emojis I have no idea.
So, if I have the same client code and a different server code, I'm followable only as long as I have JS enabled?
So .... Again, what is the point of this test, lol. What am i looking for? It seems like no one actually knows what the hell this test is showing, lol. Idk why it was posted if no one knows what it's showing? Do you know what I'm supposed to be looking for?
The test is simply showing two fingerprints for your browser. One, the server fingerprint, is one that any tracker can see. The other, the client fingerprint, is what can be used if you have Javascript enabled.
Instead of inundating you with test results, this one is simple - check to see if your fingerprints change between browsing sessions. If they don't change, that means you can be tracked. In which case you can mess with settings and try again.
Mine appears to change each time between browser sessions on a semi-hardened firefox. No clue what the bottom section means though.
The bottom result (the % certain one) is just a fuzzy match of similar fingerprints AFAICT.
So should both the server and client codes change each time you reopen a new browser session? Or just the client?
Both should if your goal is to not have a reusable fingerprint (which for a privacy focus would be). Server should change more frequently since it has access to less information about the browser. Server based fingerprinting is fairly unreliable, client side uses Javascript to generate more bits of unique data.