Đánh giá cho NoScript Security Suite
NoScript Security Suite bởi Giorgio Maone
Đánh giá bởi robsku
Xếp hạng 5 trong số 5
bởi robsku, 6 năm trướcI'm sorry I wrote a bad review. It seems to be deleted, although it was not inappropriate - it was mistaken, and PEOPLE NEED TO KNOW ABOUT THIS *FEATURE*; whether intentional or not.
We now have a possibility to use Multi-Container support of Firefox with NoScript; I was very bummed by the missing of ABE from the WebExtension, but this can do some of the same thing; and without understanding the almost esoteric syntax.
See, I though the permissions I had set were disappearing. Turns out the page was in separate container than the last time I had allowed those permissions. The permissions are *CONTAINER SPECIFIC*. I hadn't really properly put Multi-User Container add-on really to good use!
Now I don't lose permissions. I can have certain (all possible to keep things working) Google servers blocked on default - same with any FaceBook servers. In fact, FaceBook servers are only allowed on FaceBook container. And if a site that does not belong to YouTube container, but needs to show video from YouTube, I either temporarily allow the servers, or I move the site into YouTube container; which needs a good good reason if it's not a Google's YouTube services. OR, I'll add another container for pages that don't need all the YouTube and Google servers allowed, but need to have just those allowed that let the videos roll; and move that site there. This is in fact incredibly great way to work, although I still miss the Legacy version - I will soon try changing to a fork that has all the modern support of FF, and support for legacy add-on's. Then I can use the original, and get the massive power of ABE, but will the Legacy code be updated to have same support for multiple containers? That I would love, best of both worlds.
I even have a container for MyWOT.com, which everyone should know already is a scam itself, but the user reviews are real - and great. So that container shouldn't be able to reach any info not loaded while in that very container. And only MyWOT.com ever is.
P.S. I'm 95% certain I wrote a bad review lately - I even deleted the old good one before that, so I didn't just imagine it all, as it's gone. So what happened?
P.P.S. I was really hard thinking of giving you five stars, because it was stated that all the features of legacy version were available here as well. Well, I remember a lot of settings I see nowhere; most notable of them being ABE rulesets. So I almost didn't, just 4; here's your 5 stars anyway ;)
FINALLY: You have to make users so clear about this multi-container feature, that they don't get mistaken like I did. If they use multi-containers, they should easily understand it; if not, what does it matter? ;) But definitely make it clear and clearly shown ;)
We now have a possibility to use Multi-Container support of Firefox with NoScript; I was very bummed by the missing of ABE from the WebExtension, but this can do some of the same thing; and without understanding the almost esoteric syntax.
See, I though the permissions I had set were disappearing. Turns out the page was in separate container than the last time I had allowed those permissions. The permissions are *CONTAINER SPECIFIC*. I hadn't really properly put Multi-User Container add-on really to good use!
Now I don't lose permissions. I can have certain (all possible to keep things working) Google servers blocked on default - same with any FaceBook servers. In fact, FaceBook servers are only allowed on FaceBook container. And if a site that does not belong to YouTube container, but needs to show video from YouTube, I either temporarily allow the servers, or I move the site into YouTube container; which needs a good good reason if it's not a Google's YouTube services. OR, I'll add another container for pages that don't need all the YouTube and Google servers allowed, but need to have just those allowed that let the videos roll; and move that site there. This is in fact incredibly great way to work, although I still miss the Legacy version - I will soon try changing to a fork that has all the modern support of FF, and support for legacy add-on's. Then I can use the original, and get the massive power of ABE, but will the Legacy code be updated to have same support for multiple containers? That I would love, best of both worlds.
I even have a container for MyWOT.com, which everyone should know already is a scam itself, but the user reviews are real - and great. So that container shouldn't be able to reach any info not loaded while in that very container. And only MyWOT.com ever is.
P.S. I'm 95% certain I wrote a bad review lately - I even deleted the old good one before that, so I didn't just imagine it all, as it's gone. So what happened?
P.P.S. I was really hard thinking of giving you five stars, because it was stated that all the features of legacy version were available here as well. Well, I remember a lot of settings I see nowhere; most notable of them being ABE rulesets. So I almost didn't, just 4; here's your 5 stars anyway ;)
FINALLY: You have to make users so clear about this multi-container feature, that they don't get mistaken like I did. If they use multi-containers, they should easily understand it; if not, what does it matter? ;) But definitely make it clear and clearly shown ;)
2.417 đánh giá
- Xếp hạng 5 trong số 5bởi Sunny, 3 giờ trước
- Xếp hạng 5 trong số 5bởi Người dùng Firefox 19664008, 9 ngày trước
- Xếp hạng 5 trong số 5bởi Người dùng Firefox 19487299, 11 ngày trước
- Xếp hạng 5 trong số 5bởi Ryan Steed, 20 ngày trước
- Xếp hạng 5 trong số 5bởi ZeroUnderscoreOu, một tháng trước
- Xếp hạng 5 trong số 5bởi 鼎针皮艺, một tháng trước
- Xếp hạng 5 trong số 5bởi Bob, một tháng trước
- Xếp hạng 1 trong số 5bởi mlatpren, 2 tháng trướcIt does a great job at blocking, but is regularly frustrating with re-enabling things. It's supposed to show you what it's blocking, but that's extremely hit-or-miss. Occasionally, there'd be something blocked where the only solution is to disable the extension. As in, right-click and disable *from Firefox itself.*
- Xếp hạng 3 trong số 5bởi zekromVale, 2 tháng trướcThere needs to be a CPU limit on this extension, using 30% CPU of an intel i7 11th gen laptop CPU on YouTube is ridiculous. Firefox for Ubuntu snap, flatpack, or just .deb are affected. Must disable NoScript to fix it or allow everything fully for all domains on the page. I would like more domains to be added to the global trusted list though (by default) or have a popup at the top when you first visit a page.
- Xếp hạng 5 trong số 5bởi Hopeavirta, 2 tháng trước
- Xếp hạng 5 trong số 5bởi Lazy Cat, 2 tháng trước
- Xếp hạng 5 trong số 5bởi sumobunny, 2 tháng trước
- Xếp hạng 5 trong số 5bởi Zelgadis-San, 2 tháng trước
- Xếp hạng 5 trong số 5bởi Dadou, 2 tháng trước
- Xếp hạng 3 trong số 5bởi aq, 2 tháng trướcUser for at least 15 years, Something is conflicting on Firefox. It is blocking scripts and other add ons such as tampermonkey or violentmonkey with scripts added, but without any listing of what is being blocked. Only option is to shut it off to proceed.
Even blocking games internal scripts without any 'monkey' in use.
Please check and test - Xếp hạng 5 trong số 5bởi Simon Bünemann, 2 tháng trước
- Xếp hạng 5 trong số 5bởi ADKFZ8O, 2 tháng trước
- Xếp hạng 5 trong số 5bởi Marw, 2 tháng trước
- Xếp hạng 2 trong số 5bởi Người dùng Firefox 15990777, 3 tháng trước
- Xếp hạng 5 trong số 5bởi Arman Daneshjoo, 3 tháng trước
- Xếp hạng 5 trong số 5bởi elmika, 4 tháng trước
- Xếp hạng 5 trong số 5bởi Người dùng Firefox 19469020, 4 tháng trước
- Xếp hạng 5 trong số 5bởi Người dùng Firefox 14500718, 4 tháng trước
- Xếp hạng 5 trong số 5bởi Người dùng Firefox 19459487, 4 tháng trướcI'm notified every time WebGL is blocked on each page load. There's no way to disable these notifications and it's very irritating.
Edit: updated to 5 stars as it can be disabled after all but the setting isn't described very clearly.Phản hồi của nhà phát triển
đã đăng 4 tháng trướcYou should not get any notification. Just a little placeholder inside the page, to be able to enable it back. And you can disable it by unchecking "NoScript Options>Appearance>Show synthetic placeholders for invisible capability probes"