-
Notifications
You must be signed in to change notification settings - Fork 201
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Workers testing is easily defeatable. #265
Comments
Nice. I have not tried tampermonkey. Looks cleanly applied. How about here? I created a new label 😅 |
Firefox, right? I wonder if it can be reproduced in Chromium... |
Altering the userprefs in user.js also seems to get the same results, clean incorrect UA. |
Hah :3 I am not trying to save the world from tracking (well, maybe, if I do its a happy accident) But I have been poking at your tools for a while now to find various ways to break it. Like, having navigator be an exit call breaks your site in pretty amazing ways. Your site is also unloadable if the scripts crash (like say too many faults and get shut down by firefox) I learned when function tampering. But this one seemed like something you should be able to detect that something is an outright lie. Oh not sure if I should make a bug report for this one, but TZ is buggy, its easier for me to make it believe a false location than my real one. But I imagine the timezone detection stuff is one of those 'flip of a coin on who its reliable on' more than it being a flip of a coin reliability in itself? I mean its possible my Firefox user profile creation date being older than some of the bug reporters causing some issues with that and and plausibly with the test sometimes coming back with odd data (logs indicate worker crashes) |
You can easily override pretty much all of the worker data with tampermonkey and get no "reds"
Very little of this is not spoofed.
The text was updated successfully, but these errors were encountered: