Why do you disable it at all?
this post was submitted on 19 Jun 2024
19 points (91.3% liked)
Firefox
18063 readers
59 users here now
A place to discuss the news and latest developments on the open-source browser Firefox
founded 5 years ago
MODERATORS
Well I appreciate the downvote from ya but this is likely an x-y problem.
Was going to suggest an extension to create false fingerprinting since I can't think of any other reason.
Yeah that's the other solution I was thinking of.
Yes, exactly, that's what I use.
Instead of trying to solve the problem of Fingerprinting by completely disabling and then finding ways of enabling/disabling, you can solve the problem by just spoofing the fingerprinting.
Helps to present the problem first, instead of the solution you think is best but can't find an answer for. Usually the reason is that there is a better solution.
Test the implementation here: https://browserleaks.com/
Well asking the right question is also a skill, seems I'm still learning that one! Thank you
Agreed, cheers
WebGL is a strong fingerprinting vector, and as it is not needed for 95% of the webpages I use, I'd rather keep it off. And since the last 5% is a bit annoying at times, I wanted to hear if there are good solutions out there.
Because it's a privacy and security risk? Because it reduces fingerprinting?
But disabling it creates a whole slew of issues, hence the post. Turns out there's much better solutions.
What are the issues? Both my browsers have it disabled.
Oh yeah i forgot your use cases are the same as everyone else's.
OP has the issues. ask them.
OP did not elaborate on their issues. You said it creates a whole slew of issues, I asked what they were.
No need for a strawman here. What are the issues?
I've had exactly two issues that have actually affected me.
1: The screen sharing didn't show up in Zoom, when watching a lecture.
2: When looking for an apartment to rent, the integrated map on the site didn't show. Which was very unpractical as I couldn't see the location of the flat I was looking at.
Haven't had any other problems, so I wouldn't call this a slew of problems either. Both problems were solved by enabling WebGL and refreshing.
NoScript enables you to enable or disable WebGL per site. If you don't want to deal with the hassle of websites being broken, you can set the default to enable JS but disable WebGL then set applications to be trusted with WebGL.
I'll try this, thanks!
On librewolf I get a popup when a site wants to use openGL
What I'm using LibreWolf and I didn't. I probably disabled it at some point then. Oops