this post was submitted on 26 Mar 2024
214 points (97.8% liked)

Firefox

17899 readers
48 users here now

A place to discuss the news and latest developments on the open-source browser Firefox

founded 4 years ago
MODERATORS
 

My apologies to the Bugzilla team for wasting their time holding my hand on this one. Would have honestly never noticed the little "HTML5" info icon to the left of the URL bar though without their help.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 46 points 7 months ago (3 children)

Surely this is a user experience that could be improved, no? Awesome feature but confusing solution.

[–] [email protected] 5 points 7 months ago (1 children)

Not really, because doing this will make you more fingerprintable (see my other comment). That's why the default settings are striking a balance between making all users look similar and not breaking too many things (that would cause users to use user-specific overrides that make them more unique), and why resistFingerprinting is in about:config rather than a user-facing setting or enabled by default.

[–] [email protected] 0 points 7 months ago

Or use something like Chameleon and mess with about:config which makes every unique fingerprint, different as your data is scrambled. Firefox still has webRTC leakage, font fingerprinting, audio fingerprinting... That's the reason why people use arkenfox's user.js !

[–] [email protected] 4 points 7 months ago (1 children)

On librewolf I just get a popup asking to allow canvas

[–] [email protected] 4 points 7 months ago (1 children)

A popup sounds like an annoyance you must deal with on every webpage. Not just the ones that use the canvas for useful things

[–] [email protected] 3 points 7 months ago* (last edited 7 months ago)

Canvas is rarely on a web page or at least it rarely affects me

[–] [email protected] 28 points 7 months ago (2 children)

The resist fingerprinting mode scrambles canvas read out to prevent sites from using it to create a fingerprint. Because of that, any site that needs to read the canvas back for legitimate purposes will also receive scrambled data. You get more privacy for the minor inconvenience of having to manually allow canvas usage for the sites that actually need it.

[–] [email protected] 16 points 7 months ago

Yes I’m aware, but the user interface doesn’t make it easy to understand A) why the canvas looks scrambled, and B) how to permit it on a per-site basis.

The technical implementation is fine, it’s just the user workflow that needs fixed.

[–] [email protected] 4 points 7 months ago

And very few sites actually need it.