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.
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.
yes, I opened global and saw warning about DON'T TOUCH THIS! so I didn't
thanks, I asked chatGPT to compare jshelter with NoScript and it said it is good to run them together. I did not notice any slowdowns browsing, and I get a popup when fingerprinting is active or happening. Last time I tried it I doubt I fully understood it (not that I do now -- but hopefully more so)
ChatGPT is pure BS. These extensions have different purposes, but do overlap to some extent. JShelter is primarily for fingerprinting protection. NoScript is for javascript control generally, which can achieve different goals, in total or in part. Using both of these extensions at the same time is going to complicate usage and lead to problems in web surfing.
Have you explored the JShelter GUI?
Instead of disabling the whole extension, you can toggle one of the GUI switches to see which is the offending feature.
Often I find chatGPT helpful -- more so when I also know something about the topic, it did say jshelter was primerly for fingerprinting so you agree on that point.ChatGPT is pure BS. These extensions have different purposes, but do overlap to some extent. JShelter is primarily for fingerprinting protection. NoScript is for javascript control generally, which can achieve different goals, in total or in part. Using both of these extensions at the same time is going to complicate usage and lead to problems in web surfing.
Have you explored the JShelter GUI?
Users need to understand the purpose of an extension and gain familiarity with its GUI and associated features, otherwise they are whistling in the wind and unable to gain relevant experience. This concept also applies to any software, be it browsers or other tools. Users need to understand the purpose of the tool, and be willing to explore, experiment and learn from experience.
I looked over jshelter interface briefly at first, my impression there's a one of two windows, the first is a more general turn 3 main items ON/OFF, then there is much more detailed window with perhaps 20 switches (I did not count them, yet) -- I like the extensions that are more or less set it and forget it, eg, osprey, ublock, as user I rarely have to interact with them. You did disagree with chatGPT conclusion: Using both of these extensions at the same time is going to complicate usage. I just started using NoScript again in the past few weeks, and I see its value, understand it pretty well. So far, the past few days running jshelter too, and surprised how much fingerprinting MT does, which is my understanding so far from jshelter. Other sites where I might expect a lot of fingerprinting are not bothered by jshelter. Learning it as I use...
thanks, I follow what you're saying, and yes, I recall seeing a reference to cloudflare when jshelter was messing with MT... I have made a modfication to jshelter and chatGPT and both seem to be working normally with both jshelter and noscript enabled.
Most users should void using the Global Settings page and use only the first, the drop down flyout, where you can switch on/off three features. After any change, hit "Refresh page" and check for site breakage. Disabling all three is essentially whitelisting that site.
You could disable Javascript Shield and Network Boundary Shield globally, and use only Fingerprint Detector, in which case you'll be notified if fingerprinting is detected. However, doing so then means no fingerprinting protection is enabled. The notifications are just that, and nothing more. Hope that clarifies things for you.
