+1, this would be THE feature for me. I'd like to have libreJS enabled all the time, but as it stands, the plugin itself must be disabled each time I need to access a website that depends on non-free javaScript. In practice, I end up having libreJS disabled 90% of the time, because I forget to turn it back on again.
Whitelisting each and every script is tedious and really non-sensical. Exceptions must be made on a per-domain basis. Users can make exceptions for scripts if they read them and conclude they are trivial enough or in general non-malicious. That's good. But when I am forced to access a website with non-free javaScript, I don't want to read their code and confirm it's OK to run for me, I need it to run, no matter what it is. Not because I trust the scripts, but because I need to make an exception for this specific site. So, bottomline, it must be possible to make exceptions on a per-domain basis, not only a per-script basis. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ <[email protected]> schrieb am Donnerstag, 21. Oktober 2021 um 11:34 vorm.: > kirang [email protected] writes: > > > Hi, > > > > I'm emailing about a feature request for LibreJS - it would be useful > > > > to have some kind of functionality to allow selectively disabling > > > > LibreJS on a per-site basis. > > > > In particular, rather than having to whitelist all the external > > > > scripts that a particular site uses, it would be nice to just set an > > > > option to disable LibreJS for a site, and then blanket allow any > > > > external requests for that site. > > This sounds like a good idea. It gives users more control in what to > > whitelist. Also a script could be essential for one website, but not so > > much for another. > > > My motivation is that there are certain non-free JS sites that I am > > > > forced to use for work, but at the same time I don't want to whitelist > > > > the external scripts these scripts use, because I don't want to run > > > > these scripts on other pages. > > > > I wouldn't mind implementing this myself if this is a feature that > > > > would be welcomed to LibreJS, or is there some kind of ideological > > > > reason why this would be bad? > > > > This seemed like the most appropriate place to post this request, > > > > apologies if it was the wrong venue. > > > > Thanks, > > > > Kiran.
