New Update JShelter - JavaScript Restrictor

[simmerskool]

I tried JShelter in firefox on linux and liked its insights, but even after modifying for some websites that loaded funky, it was "problematic" so I disabled it for now. It was unclear to me after I had modified the settings for a specific URL that did not fixed the page loading issues. Will try again on updated versions.

 

[oldschool]

I tried JShelter in firefox on linux and liked its insights, but even after modifying for some websites that loaded funky, it was "problematic" so I disabled it for now. It was unclear to me after I had modified the settings for a specific URL that did not fixed the page loading issues. Will try again on updated versions.

Can you give an example?

 

[simmerskool]

Can you give an example?

I am using chatGPT to help me as I re-familiarize myself with linux. chatGPT would not / could log me in, so I turned off fingerprinting and javascript and page still balked, and this happened more than once. After disabling jshelter completely, chatGPT was ok. I saw something similar on a few other sites that I don't specifically recall.

 

[oldschool]

I turned off fingerprinting and javascript and page still balked, and this happened more than once. After disabling jshelter completely, chatGPT was ok.

Indeed, I've run into this myself on several occasions, at least. This may due to this being the initial MV3 version. I'm considering this to be an experimental extension, so I'm using it mainly for testing purposes, to see how many sites I encounter with the problem you describe. In any case, make sure you leave the global settings at default, or in the alternative, disable the javascript protection globally, and leave the fingerprinting detection feature enabled. This will allow you to see which sites you visit are attempting fingerprinting.

 

[simmerskool]

Indeed, I've run into this myself on several occasions, at least. This may due to this being the initial MV3 version. I'm considering this to be an experimental extension, so I'm using it mainly as testing, to see how many sites I encounter with the problem you describe. In any case, make sure you leave the global settings at default, or in the alternative, disable the javascript protection globally, and leave the fingerprinting detection feature enabled. This will allow you to see which sites you visit are attempting fingerprinting.

yes, I opened global and saw warning about DON'T TOUCH THIS! so I didn't