NoScript Security Suite에 대한 리뷰
NoScript Security Suite 제작자: Giorgio Maone
Firefox 사용자 13551289 님의 리뷰
5점 만점에 2점
Firefox 사용자 13551289 님, 8년 전Ok, 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.
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.
개발자 답글
8년 전에 게시됨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.
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.
리뷰 2,373개
- 5점 만점에 5점Firefox 사용자 19072892 님, 하루 전
- 5점 만점에 5점cwqing1973 님, 5일 전
- 5점 만점에 5점Firefox 사용자 14468519 님, 6일 전
- 5점 만점에 5점rabbitshee 님, 8일 전
- 5점 만점에 5점Firefox 사용자 19047433 님, 10일 전
- 5점 만점에 5점A. Bilmanda 님, 13일 전
- 5점 만점에 5점Lazer Bear 님, 13일 전
- 5점 만점에 2점Firefox 사용자 15056996 님, 한 달 전issues with outdoorline.sk ; I have to stop Noscrypt to proceed with Payment gateway GP webpay
- 5점 만점에 4점Firefox 사용자 17847461 님, 한 달 전
- 5점 만점에 5점Firefox 사용자 18989716 님, 한 달 전
- I really wanted to use NoScript. I prefer single-purpose extensions that focus on doing one job well, compared to more multi-purpose extensions like uBlock Origin.
However, I ultimately couldn't stick with it because the user experience did not suit my needs.
E.g. one mobile screen presents around 12 different icons packed into the height of 3 lines of text, leaving a large portion of the screen completely empty below them.
My main frustration is that none of these icons have labels. Expecting users to learn and memorize the meaning of a dozen different unlabeled symbols creates an unnecessary barrier to entry and makes using the extension quickly and efficiently very difficult. It feels counter-intuitive to leave so much screen real estate blank when that space could be used to label each icon and explain its function.
uBlock Origin is easier to use than NoScript. - 5점 만점에 5점LittleFire 님, 한 달 전
- 5점 만점에 4점Firefox 사용자 18920843 님, 2달 전
- 5점 만점에 5점Firefox 사용자 18315395 님, 2달 전
- 5점 만점에 5점Retromania 님, 2달 전