I tried LibreJS 5.4 when it was first released and honestly wasn't impressed.
It's still basically the same, including breaking web pages in ways that are
completely unrelated to Javascript and having a whitelist that only serves to
execute ALL Javascript code used on a whitelisted webpage, regardless of what
script it is or even where it's from.
I still think they should fork NoScript, make it more powerful (so it can
allow and deny individual scripts, rather than having a list of trusted
sources for scripts), and add the LibreJS features.
But that still wouldn't be enough. We need something powerful that combines
the ideas of script blocking (e.g. NoScript) and user scripts (e.g.
Greasemonkey) to allow easy, fine-tuned script execution control. Better and
easier than current user scripts.
I don't get why the FSF seems to approach the problem of proprietary
Javascript so differently than with other proprietary software. LibreJS is
like if, in 1983, RMS had written a shell script that somehow showed
approximately how much proprietary software was on a computer and blocked
that software (plus some collateral damage on free software), then told
people to use the resulting barely-usable or unusable system and complain to
the distributor of the system that the script broke it. If you can see how
absurd that sounds, you can see how absurd I think the idea of LibreJS is.
It's stalling, and the sooner we stop just blocking Javascript and start
actually working to replace the non-free Javascript code (the first step of
which is making running custom Javascript and otherwise controlling
Javascript execution much easier than it is now), the better.
- Re: [Trisquel-users] How to recognize non-free javascrip... onpon4
-