js-shield
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Let's remove WebWorkers in Recommended


From: Libor Polčák
Subject: Re: Let's remove WebWorkers in Recommended
Date: Mon, 16 Oct 2023 14:29:24 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Firefox/91.0 SeaMonkey/2.53.17.1

Libor Polčák napsal(a):
Hello all,

I am looking at the issues raised by users and found 
https://github.com/polcak/jsrestrictor/issues/179 again.

Google maps work correctly when I remove workers. The default level is to make 
them inoperable.

My reasoning was that by removing the Worker API, we make the user more fingerprintable 
and the Recommended profile aims at making users less fingerprintable. 
"Everyone" else has workers on. However, in Chrome, we already remove Battery 
(not sure if they still have the API though) and Network conditions API. So for 
Chrome-based browsers with the Network API, the change is quite small.

We would make Firefox users more visible as we do not remove any other API in 
the Recommended level. Nevertheless, a focused fingerprinter can see some 
artefacts of JShelter behavior anyway (I am not giving hints).

So I say we release 0.16 with the change in both platforms. However, we should 
keep user-defined levels at their preference.


Actually, Google Maps work in Chrome with Recommended just fine.

It seems to me that the issue in Firefox is the same as in 
https://pagure.io/JShelter/webextension/issue/80#comment-852202. Giorgio, any 
estimates on fixing that issue?

Libor

Hello,

a user reported me a bug that now prevents JShelter to load Google spreadsheet 
when WebWorkers are removed. The page works with Strict Worker protection. See 
https://pagure.io/JShelter/webextension/issue/122. Are there any suggestions 
how to approach the issue?

Best wishes

Libor



reply via email to

[Prev in Thread] Current Thread [Next in Thread]