After a long while, I checked back on the arkenfox.js github page, and they no longer mention two extensions I still use: (1) CanvasBlocker (because if Resist Fingerprinting is enabled in about:config, the per page zoom levels get changed and that drives me crazy), and (2) Smart Referer (because, well, it was recommended). I know that good old UBlock Origin can block javascript, but I’ve been using (3) JavaScript Control because it’s easier to access from the URL bar. So are these three still useful? To answer my own question: I might give RFP another try so I won’t need CanvasBlocker. Since I can achieve what CanvasBlocker and JS Control do with about:config and UBlock tweaks, respectively, I guess I’m mainly interested in what people think about Smart Referer. Also sort of a noodly post.
resist fingerprinting resets zoom levels because its used as a way to fingerprint, sites can get zoom levels and the idea is to blend into the crowd
that said, I share your frustration, I have to disable Resist Fingerprint because of that, the persistent zoom levels are an accessibility requirement for me, no negotiations possible.
Ideally Resist Fingerprinting would allow for more granular options because while I understand the “blending into the crowd” aspect of the option as it is now, it just doesn’t work like this for me and many others with accessibility needs, and that should be addressed
(also replying so I remember to check back for replies, sorry for the ramble, Resist Fingerprinting as it is now annoys me)
As long as sites can get zoom levels, it seems to me like you’ll have to choose one or the other.
Now, if I’m not mistaken, the only way to do that, is via JavaScript, so disabling JS on a site should block that. Alternatively, block or sanitize the JS call used to calculate the canvas vs. window size (maybe via Tampermonkey?). Or just return a window size equal to the canvas size (I’m kind of surprised RFP doesn’t do that).
@Mnglw and @jarfil , do either of you know how to implement the “removeparam” thingamabobber? I’m just about at the limits of what my poor brain can handle here . . . 🤯
Hm, which parameter would you want to get removed?
From what I can see, you can either specify a fixed parameter name, or use a REGEXP… I could help you write an optimized REGEXP if that’s what you need, the example /^utm_/ one seems to target Google’s tracking and be simple enough… but is that what you want to do?
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !technology@beehaw.org
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
resist fingerprinting resets zoom levels because its used as a way to fingerprint, sites can get zoom levels and the idea is to blend into the crowd
that said, I share your frustration, I have to disable Resist Fingerprint because of that, the persistent zoom levels are an accessibility requirement for me, no negotiations possible.
Ideally Resist Fingerprinting would allow for more granular options because while I understand the “blending into the crowd” aspect of the option as it is now, it just doesn’t work like this for me and many others with accessibility needs, and that should be addressed
(also replying so I remember to check back for replies, sorry for the ramble, Resist Fingerprinting as it is now annoys me)
As long as sites can get zoom levels, it seems to me like you’ll have to choose one or the other.
Now, if I’m not mistaken, the only way to do that, is via JavaScript, so disabling JS on a site should block that. Alternatively, block or sanitize the JS call used to calculate the canvas vs. window size (maybe via Tampermonkey?). Or just return a window size equal to the canvas size (I’m kind of surprised RFP doesn’t do that).
which part of “no negotiations possible” do you not get?
I would like a more granular choice, acccessibility is not something I can give up, I don’t care sites can fingerprint me with it
Right, so you basically want the opposite of CanvasBlocker?
@Mnglw and @jarfil , do either of you know how to implement the “removeparam” thingamabobber? I’m just about at the limits of what my poor brain can handle here . . . 🤯
Hm, which parameter would you want to get removed?
From what I can see, you can either specify a fixed parameter name, or use a REGEXP… I could help you write an optimized REGEXP if that’s what you need, the example
/^utm_/one seems to target Google’s tracking and be simple enough… but is that what you want to do?Personally I suggest you straight up install Librewolf instead.
That said, most extensions aside from ublock are pointless these days.