Bewertet mit 3,9 von 5 Sternen
3,9 von 5 Sternen
- von wolfgang8741, vor 17 TagenBewertet mit 3 von 5 SternenNice effort, but the usability for end users still is quite a burden and lacks a reliable reporting mechanism to inform websites and put social pressure on them.
I'm kind of surprised there isn't an option to track and manually report sites to add social pressure in an aggregate public list of sites who are not meeting freejs practices.
A community generated report card of sites meeting or failing the different standard would provide a path to sites to improve their freejs compliance especially if each criteria matched rules used and options to fix the issues.
- von Firefox-Benutzer 11640498, vor 4 MonatenBewertet mit 3 von 5 SternenThis is perhaps one of the best add-ons out there, deserving thousand of stars. Sadly, I can only give 3 stars because the current GUI makes this add-on unusable.
I perfectly can live with blocked stuff, but I need a handy friendly GUI to unblock stuff. Your current GUI presents an endless list of blocked stuff, and this makes almost impossible the browser experience. If you allow me a suggestion, a kind of uMatrix GUI here will be great. You must present the blocked stuff in a way that the user easily can block or unblock stuff. Perhaps the uMatrix layout wont work... okay, no problem... but please, try something different than the current endless list of blocked stuff.
Also will be nice options to choose categories of blocked JS (not just "accepted" and "blocked").
If you can do that, I'm sure this will become one of most used add-ons.
Thank you in advance!
- von JCOX, vor einem JahrBewertet mit 5 von 5 SternenI give 5 stars because I support the FSF, however this plugin is not reading some licenses present on the current version of WordPress at /wp-includes/js/jquery/jquery.js and wp-includes/js/jquery/jquery-migrate.min.js
- von jawz101, vor 2 JahrenBewertet mit 3 von 5 SternenIt would be nice to know exactly how you know whether a bit of code is free or not. Does the file have to put little licensing blurbs in every file on their site saying that they have to comply with certain terms of service that a group of people say are acceptably free? It's as silly as someone saying "address me as Lord Firefox." It sounds like a silly, toe cheese eating, impractical concept.
- von andreymal, vor 2 JahrenBewertet mit 1 von 5 SternenIt does not block proprietary scripts. It says that a page has no scripts, but a page has lots of proprietary js, and they are working. (I tried to create a bugreport with steps to reproduce on savannah.gnu.org, but the register page does not work lol) Also, librejs is VEEEEEERYYYY SLOOOOOOW, Firefox freezes for 20-30 seconds while librejs is trying to analyze scripts.
- von Firefox-Benutzer 14072894, vor 2 JahrenBewertet mit 5 von 5 SternenMore convenient than the old XUL one, makes me want to use it again. (And I did installed it just now.)
Feature Request: Can you add a button to temporally allow current page's domain?
And it's better to add another button to let us temporally disable it conveniently.
- von Thales Milesius, vor 3 JahrenBewertet mit 5 von 5 SternenIssues reported by users earlier seem to be fixed.
GNU LibreJS is a programme unlike any other and is of great value to any freedom-valuing user.
- von Firefox-Benutzer 12453153, vor 4 JahrenBewertet mit 1 von 5 SternenMoins d'une minute après avoir installé le module, Firefox plante.
J'ai testé en ouvrant différents sites et le plantage se répète. Plus aucun problème après avoir désactivé le module.
Firefox portable v48.0.1
- von Firefox-Benutzer 10880788, vor 4 JahrenBewertet mit 1 von 5 SternenEverything tested with a stable version of Firefox and Dev Edition.
So here is what this add-on did:
1. It crashed (both) Firefox directly after installation.
2. As a web dev I tried to adjust some external JS files using magnet URIs. This resulted in:
2.1. At first one file was recognized as "free", but it was at the same time recognized as "non-free" in the view.
2.2. Later all of my files were recognized as non-free even though all had magnet links marking them as free. There was always a "parsing error" shown in the list.
2.3. The default excluded libraries do not include jQuery 3.1.0 (the latest jQuery version), so I could not use the hard-coded excludes as they were just outdated.
3. The option to show what LibreJS currently analyses slowed down the loading process of the website dramatically and I could not see anything. So I basically could not use this option.
4. LibreJS broke