- Rated 2 out of 5by Anonymous, 6 years agoThe new version has to be fixed full stop. The UI did not need to be fixed. And now the app does not remember settings on some sites. I'm thinking about uninstalling this until it is back up to its previous quality.
- Rated 2 out of 5by Firefox user 13556987, 6 years agoJust joined on here to give my view.
I've used NoScript continually since its inception and thinking back there were a few hiccups early days which over time got ironed out, I think it will be the same with this version.
There were lots of folk ranting when it couldn't be used on the new Firefox, some demanding that something be done instantly, which was obviously impossible.
Giorgio obviously got on with this version and possibly rushed both building it and putting it out, these things happen.
However, buggy though it is, it is useable and as with all similar programs when many folk start using them bugs surface, the bugs are a PITA but hopefully, with time, will be resolved.
Lets not forget, that thanks to Giorgio's time and effort over the years, many thousands of surfers, me included, have been protected from who knows what was lurking behind some scripts.
Why not cut him a little slack, even such as the mighty Microsoft, Google, Apple and such others put out buggy stuff and that's with their thousands of programmers and millions of pounds!
So why have I given it two ( for the time being ) stars.
Mainly due to two things.
One, to me very important, there not being available, from the day it came out, any decent instructions in layman's terms, as to how to use it, I'm reasonably computer savvy and can normally get my head around most things, eventually, but this had me going spare, marking sites as trusted then having them revert to untrusted after shutting down and re-starting was a real pain, until I discovered only this morning, whilst reading these revues, that a simple click of the little clock solved this problem, thanks to those who mentioned it.
The second reason was because of the initial buggy nature of the first release.
Will I continue using it, of course.
Why, simply because, even as it is, I can't find another program that is as good as this one and going by past experience it will settle down.
- Rated 2 out of 5by Firefox user 13556524, 6 years agoThere is a problem with the settings. Every time I close Firefox , the settings of what sites are trusted is lost. Every time I start Firefox, I have to configure each page all over again. This is very annoying.
- Rated 2 out of 5by Firefox user 13553842, 6 years agoGeorgio wrote:
> Unfortunately I cannot do the impossible (recreating legacy NoScript on the new, much more limiting WebExtension platform)
> just because "people" ask for the impossible. And I've the duty to provide the best security NoScript
BUT maybe it is not so much about recreating the old thing, than understanding what the problem with the new thing is. First you need to accept that the current approach is simply not intuitive. As a dev (I am one myself, so I had this problem myself) its hard to understand when that happens, because for you its as familiar as a part of your body, but it is obviously a mistery for everbody else.
Also, about your "duty": Its true what you said, but: if many people now dont use NoScript at all, because they do not get it anymore, you decreased web security by a lot.
- Simpler is better. Simpler might be less safer, but if the alternative is not using it at all, it's still better. Way better.
- get rid of the slider. It looks mhm good(?), but its not recognizable as one.
- there is way to much clickable stuff, one does not get what is a button, what a link and whatnot...
- make it simpler: hide everything exept: domain name, status icon and -depending on the status- two buttons for each entry.
- clear design, dont change font size and font color at any time
- No xss-popups. In fact, never, ever use popups.
- a simple list of domains like before, each with a status icon in front of it: your blue "S", for allowed, same with a little clock for temporarily allowd, red crossed "S" for disallowed
- depending on the current status of an entry, two buttons:
- if currently allowed: "disallow" and "temp. disallow"
- if currently disallowed: "allow" and "temp. allow"
- these buttons need to be different than the status icon. I would use red X and green hook/check, each with and without a little clock.
- dont make anything but the buttons clickable! not the text, not the status icon.
You can add a (clearly seperated from the other buttons, clearly different graphic) button behind each list entry to hide all the detailed settings, for the expert. Everybody else gets the simple list.
At the very buttom of the list go -clearly separated - three entries: "temp allow all" and "save permissions for this site" and "deactivate noscript".
No problem to do that in html. And believe me, people will love you again. :)
If you would like me to make a mockup of what Ive just desrcibed, just say so and tell me where to send it.
And btw.: You dont owe us anything. People have no right being rude to you about something you gave us for free. But maybe see their ill-advised passion as a testament to how important NoScript is to us. That is something I think, even if you must hate the internet right now.
I thank you for the old NoScript and that it helped increase my security. But I won't use the current one. So I would thank you again if you make it simple and easy to use again.
- Rated 2 out of 5by Firefox user 13552862, 6 years agoUsed to be good before they recently broke it with confusing and to some extent buggy UI. Tried to wait it out, but it's starting to really get on my nerves so for now I'll disable it and find an alternative. Even had to disable it to write this review, since the alternative seems to be to allow more or less known scripts (permanently?) until I happen to stumble upon the right one.
I really wish they'd just leave NoScript the way it was and make this experimental version a NoScript 2 Alpha/Beta or something like that instead.
- Rated 2 out of 5by Firefox user 13551624, 6 years agoIt is a real pitty that you do not seem to want to listen to the incredible ammount of people who are trying to tell you that you messed this up.
If 90% of the people dont understand the new UI, its not the people, its the UI. For example the list is too large, and without an explaination you cant tell the status of an entry. And if -by accident- you manage to click what was "allow" before you have no idea if its temparily allowed or permanently.
I gave this addon another try today and now I get at least one XSS warning popup every 30 seconds. I mean popups? Really? Reminds me of the old personal firewall days, when you got so much warningsall the time, that after a while you just allwed everything just to be left in peace. Popups are a bad, bad, bad idea.
Please recreate the old look and feel and behaviour!
And I get from your comments that you cant do that exactly, but I dont see a reason why one could not try to recreate that as close as possible. Even if it does not look fancy and colorful like now. Because belive it or not, that is obviously not what people care about."I dont see a reason why one could not try to recreate that as close as possible".
*This* is as close as possible a WebExtension can go, and I've done and I'm doing my best to compensate the unavoidable loss in usability (due to the fact WebExtensions UI are just HTML web pages) with more customizability, and at the same time to provide feature parity security-wise. If people want the old version as it was, with the floating hovering menu and the "Allow / Temporarily allow / Forbid" commands (which, BTW, functionally map one-by-one with the new TRUSTED/UNTRUSTED paradigm), they can use Firefox 52 ESR or the Tor Browser as long as they're supported: on Firefox 57 this stuff is just out of reach for add-ons.
Unfortunately I cannot do the impossible (recreating legacy NoScript on the new, much more limiting WebExtension platform) just because "people" ask for the impossible. And I've the duty to provide the best security NoScript can provide to people which actually rely on it, even for their physical safety (and no, uMatrix / uBlock / ScriptSafe & C. are not up to the task, simply because they've got a completely different scope).
- Rated 2 out of 5by Firefox user 13551289, 6 years agoOk, I just got the update and have to say I really hate the new version and am considering dumping it completely. There are a lot of reasons why.
Under the old version, when you visit a new website, it shows a popup saying that scripts are disabled and giving you a quick option to temporarily or permanently enable scripts for just that website. Under the new version, you don't even know if the scripts are blocked, and if the website is malfunctioning because it needs its scripts, or what.
Also, the new UI really sucks. Everything is all icons now and I don't have a clue what any of them do. Am I allowing scripts or blocking them? Am I permanently allowing them or just temporarily? You could at least give us the option to go back to the classic interface.
I've also noticed that for every single website I go to, I have to tell it not to allow XSS from that website to facebook.com. It's really annoying. There is no option to just say, don't allow XSS from anywhere to facebook.com. Under the old version, it only gave me an XSS warning for a certain few websites which I could then do an unsafe reload. Now it's like there's cross-scripts everywhere.
Ok so maybe a useful feature would be to allow for example facebook.com (seems to be the main offender here) when I'm ON facebook.com, but disable it when any other website tries to cross-script to it.
Anyway to sum it up, the new version nags me incessantly and isn't clear enough about what's going on for me to figure out how to allow the scripts I want and block the ones I don't. Please go back to the old version.1) The UI shows you all the domains that are trying to run active content, just like before, but more compact. You can allow them individually (by assigning the TRUSTED preset), leave them not running (DEFAULT), blacklisting (UNTRUSTED) or even assign CUSTOM permissions. Not just that, but better than before if you can modify each preset on the fly and even see the minimum permissions needed for the site to work (they've got a pink background).
2) To assign the TRUSTED preset temporarily, you just click it once. To make it permanent, you click the clock icon and make it fade away (temporary->permanent).
3) The XSS filter now has a "Always block requests from a.com to b.com" option, that you can use exactly the way you say you want.
- Rated 2 out of 5by Almair, 6 years agoUgly interface. Not usable.
Return old interface, please... :(The UI cannot be the same as before because WebExtensions are limited to a handful of customization entries, all HTML-based. But with some constructive feedback we can make it even better than before (it's already more customizable). Please visit https://noscript.net/forum with your ideas, thanks.
- Rated 2 out of 5by Firefox user 13549703, 6 years agoSo I load a page and the addon button shows a tiny "3", but lists only one domain. I allow all from that domain, reload and the page still doesn't work. How do I see the other 2 domains?!
Then I try the NoScript settings only to find that:
- it by default allows scripts from a bunch of sites that I don't trust,
- there is no way to auto-block all the domains in that list,
- all the old settings are gone .. can't find them anywhere.
Uninstalled.. fortunately, it still works in a slightly older version of FF.
Rating 2 based on the average experience.
- Rated 2 out of 5by Firefox user 13537226, 6 years agoSu Firefox Quantum ha perso molte delle sue caratteristiche e delle possibilità di configurazione. Ora si limita a disattivare gli script con la possibilità di inserire i siti in una white list. Un po quello che faceva l'estensione NOscript.
- Rated 2 out of 5by Firefox user 13548373, 6 years agoThis used to be my go-to script blocker and it was fantastic. With the latest update though to make it work for the new Firefox, everything is upside down and it's more or less unusable in its current state. The addon's menu keeps bugging out and cant decide whether to be a dropdown like before or a standalone window. Furthermore I can no longer easily whitelist entire pages except for temporarily which is rather tedious for sites I visit alot. That it also refuses to save my settings for a specific site (where I have taken the time to click which parts of it I want to trust and which not) just makes the experience more frustrating.
Please return this addon to its former look and functionality, it was much much better.
- Rated 2 out of 5by Firefox user 13547390, 6 years agoUnable to use the newer addon now. Doesn't work now. I'm currently using the 10.1.3 version now but can't get the web browser to work until the addon is disabled again. If the pages are marked to allow access, evetually they get to a state to show allowed but shown in red text. If you toggle not allow allow it doesnt get back to a usable state. I can't even search google now, with page allowed, it doesn't let you select any items returned from a search. Please sort the issue because this is the best software to do the job of blocking items. We appreciate your work, but 2 stars to show it is really busted with the newer firefox version
- Rated 2 out of 5by Firefox user 13547357, 6 years agoWhat a shame! This new UI is horrible.
I can´t get some web-pages to work and looking at the new version, it´s anything but self-explanatory.
Is the protection ON or OFF?!" I don´t know....
Please, update the UI to the older one!
- Rated 2 out of 5by Eelco, 6 years agoI really, really like NoScript. Since the disastrous upgrade of NoScript for FF57 I check upgrades daily. And I guess the author is working on it realy hard, making it work again relatively well on nov 30th. I understand what he wants to doe with the new layout, a table in stead of a list with websites, making it more manageable when pages depend on a lot of domains for their scripts. But the way this is introduced is terrible. I hope for better and stable version management in the future.
- Rated 2 out of 5by Firefox user 13545721, 6 years agoI used to depend on NoScript but now with Firefox 57 the new version is just a disaster. Links don't works and can't figure out why, almost no configuration options. It makes Firefox unusable. Hopefully it will get better over time. I understand it had to be re-written. It's sad but I just can't recommend anymore. Makes me want to go back to FF 56 and the old Noscript.
- Rated 2 out of 5by Firefox user 13541139, 6 years agoWhile being a very satisfied user of NoScript before Firefox 57, using NoScript currently is an absolute horror. Again and again some websites are not working properly. So it has become a daily task for me to check NoScript for updates hoping for the basic functionality to come back soon and for bugs being fixed. I will still give NoScript some more days to get improved. But all in all, it's a quite poor reputation for an addon developer to miss the release of this big Firefox update and leave his addon unusable for so long time.
- Rated 2 out of 5by Firefox user 12959496, 6 years agoAcutally a great plugin which I've used for several years. But the new design is confusing (for example the links are shortened badly, so I see only a really short part of the link) and I have problems with the new version. A lot of pages aren't working anymore, so I had to disable NoScript... I hope the developer is fixing the problems in the near feature, then I will update my rating.
- Rated 2 out of 5by Firefox user 13538324, 6 years agoDon't mean to be too critical, I am hoping that this app will be fixed in time.
But it is basically unusable. It doesn't show all scripts on a page, has some apparently random way of pre-allowing some, the selective temporary command is very confusing, with 6 sub options......
I have gone back to Firefox 52 and the old add-on for the foreseeable.
Hope to be able to upgrade at some point.
I'd second the desire to have the noScript interface be returned to something similar to the last one. It was comprehensible, customizable and flexible.
One of the best extensions ever seems to have taken a very bad turn. Time to correct the course.
- Rated 2 out of 5by Firefox user 12839, 6 years agoEDIT: OK after some time playing around with the settings I understand it much better and the functionality appears to work well. I suggest people experiment with the settings a bit, or check out the noscript forum where there are some explanations of the UI if you find the relevant threads.
In the meantime, I will keep my 2-star rating until a proper help guide to the UI is incorporated into the addon as a link, and an on-boarding process for new installations includes a pop up alerting users to the guide as this is sorely needed, especially for users of the old add-on. This rating reflects my experience as a new user, not my experience now, as this is more relevant to potential new users reading these reviews.
I agree with others that I do not really know how to use this addon any more whereas I had perfect intuition of it pre-57 days. The interface is non-intuitive and is not really explained anywhere. After some time I think I am beginning to understand it but I am still not sure because I cannot reference what I think against official documentation. The latter would help a lot.
I don't blame the addon developer, as he probably had to develop it in his spare time in time for release 57. i acknowledge the effort to upgrade the addon to the new API while many other developers gave up. Thank you, Giorgio for that.
I do blame Mozilla somewhat for switching to a substandard extension API and not having certain vital API features available to developers to test until very late (and some not even yet existing). I realise there were some reasons to make the change, but they should have considered the effect on the existing users and developers and tried to mitigate it somehow.
While I agree that expressing such anger in obscene words is inappropriate, it is appropriate to give an honest review and rating. My rating expresses what I currently think about this addon and is by no means an emotional reaction to change.
I am sure that many improvements will come and user feedback will be acknowledged by the developer. I encourage him to ignore the insults and continue. My review and rating will improve as the addon improves in my estimation.
- Rated 2 out of 5by Firefox user 13209211, 6 years agoThe new version is almost useless. Many sites won't work properly even with all allowed. The NoScript menu seems to only show a few of the scripts the page has so I am unable to allow all needed scripts. Even allow globally doesn't help. Had to disable the app completely. Please make a better version, I like the app and have been using it for years.