Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

NoScript Not Available for Latest Firefox

noscript.net

Post reply on HN
Print view View original

51–60 of 84 posts

Re: NoScript Not Available for Latest Firefox

#51

Post by ynezz »

amenod wrote: post #34

I upgraded to Firefox 57 only to find all 4 of my extensions missing... I can live without others, but being without NoScript felt like walking on streets naked. So the first thing I did was downgrade to Firefox ESR, then I started looking for alternatives. Turns out that uMatrix fills this role perfectly (for me of course). Not only can I block/allow JS, CSS and similar resources, but I can do it based on domain / 3…

> felt like walking on streets naked

So browsing on the phone is not evoking similar feeling? :-)

Re: NoScript Not Available for Latest Firefox

#52

Post by babuskov »

Endy wrote: post #29
mrich wrote: post #14

The plugin breakage is the only downside of the new Firefox, the rest is just awesome. I'm still looking for a new auto form filler that can have multiple profiles and fills in all fields at once with a hotkey. This is useful for filling in bugzilla bug reports where some fields always get the same data.

"The only downside" Sure. Aside from the number of other extensions that simply won't work in new Firefox. And the lack of any user control to make the browser not work like or look like Chrome.

And the fact that today was the first time I have seen Firefox crash after 3+ years of heavy everyday usage. Luckily I didn't "upgrade" Firefox on my main machine. I'm staying away from 57 until they get it together.

Re: NoScript Not Available for Latest Firefox

#53

Post by babuskov »

majewsky wrote: post #16
akerro wrote: post #11

Brave Browser has "Shield" mechanism where you can block ads/trackers and JS. It's built-in feature, you can set it up to be enabled by default or per-domain.

Switching browsers just because some extension does not work for a few days after an upgrade seems like blowing it waaaay out of proportion.

> does not work for a few days after an upgrade

"A few days" is an understatement. Extension developers have known for months that these changes would break. If they hadn't created compatible versions by now, they certainly won't be able to do some in just a couple of days.

Re: NoScript Not Available for Latest Firefox

#54

Post by mariuolo »

zython wrote: post #7
andrei_says_ wrote: post #2

The title of this post is incorrect. Seems like it is available, just in the old extension format. From the noscript site: > Please be patient: if you feel naked while you're waiting for the "brand new" NoScript, you can still use the "regular" NoScript 5.x (and all the other extensions of yours) on Firefox 52 ESR, which will receive security updates until June 2018. See you soon! Edit: my statement is incorrect, the…

Or you know, "if you feel unsafe" you can always downgrade to 56 or chromium.

Or ESR if you are willing to re-create your profile. It's based on 52.x and is going to be supported until March 2018.

Webextensions should have been sorted out by then. Hopefully.

Re: NoScript Not Available for Latest Firefox

#55

Post by forapurpose »

vesinisa wrote: post #31

uMatrix is a replacement extension from the creator, and compatible with, uBlock. uMatrix migrated to Quantum leveraging the existing Chrome codebase already about a month ago: https://github.com/gorhill/uMatrix Some learning curve is required compared to NoScript since uMatrix allows even finer grained control (not just scripts, but images, cookies, iframes and XHR as well), but I personally migrated about a year ag…

To add some important points:

> uMatrix is a replacement extension from the creator, and compatible with, uBlock.

To avoid any confusion, I think the parent means, 'from the creator of ... uBlock'. uMatrix is not by the creator of NoScript.

Also, blocking just JavaScript is quicker and easier in uMatrix (at least easier than the current NoScript; I don't know about the upcoming version). The UI is far more efficient, and you configure it by origin/remote pairs (e.g., on foo.example.com allow googleapis.com; on other example.com hosts, block it; on example.org allow it everywhere).

But NoScript does far more than block JavaScript; it's a sophisticated firewall, in some ways. Look through the options menus and lookup the features, such as ABE; it's impressive. uMatrix doesn't replace much of that functionality.

Re: NoScript Not Available for Latest Firefox

#56

Post by forapurpose »

ryuuchin wrote: post #20

uBlock Origin and uMatrix can both do the same thing and are compatible. This is just my opinion but both have better and more intuitive interfaces as well.

They do some of the same things, but there's a lot they don't do.

https://news.ycombinator.com/item?id=15730800

Re: NoScript Not Available for Latest Firefox

#57

Post by forapurpose »

K0nserv wrote: post #5

I use UBlock Origin to achieve pretty much the same behaviour as NoScript. Haven't found a reason to use NoScript since I started doing that.

There's a lot of overlap, but uMatrix doesn't replace NoScript.

https://news.ycombinator.com/item?id=15730800

Re: NoScript Not Available for Latest Firefox

#58

Post by forapurpose »

pbhjpbhj wrote: post #9
gdulli wrote: post #3

The utility of the long tail of Firefox plugins was what gave it its value. I've been using a hybrid of Pale Moon and Firefox since the last round of losing plugins and now don't see a reason to keep Firefox at all.

I'd value a resource with a simple explanation of the changes that prevent a compatibility layer from enabling all the old plugins?

AFAIK, the old add-ons could interface with Firefox in any way they wanted; they had carte blanche. You can imagine the dependency hell and security risks; it's not desirable to duplicate that.

Re: NoScript Not Available for Latest Firefox

#59

Post by bitbang »

Karunamon wrote: post #50
jchw wrote: post #40

Earlier quoted context omitted.

Killing the old extension API is a painful, but important, step. From a security standpoint, WebExtensions are a lot better, since they are sandboxed and require explicit permissions to be granted for many things. From a developer standpoint, they are easier to deal with, being JavaScript, and since Chrome and Edge support similar APIs, developers will no longer need multiple codebases to support their extensions on…

From a usability standpoint, WebExtensions have a lot less control of the browser and some use cases are completely closed off. The Webex version of Tree Style Tabs, for instance, requires you to have a redundant tab bar on top because it's not allowed to hide the main one. Pentadactyl can't have it's sub-buffer anymore. Download managers/scrapers like DownThemAll can't even do their main function anymore. On and on…

You can hide the tab bar manually. Supposedly the plug-in should be able to hide it but they claim there is a bug currently in 57 preventing it from working.

Re: NoScript Not Available for Latest Firefox

#60

Post by Asdfbla »

While I can understand that the switch to the new system was necessary, I hope they improve the new extension functionality a bit further.

One negative thing that I noticed that extensions don't seem to be able to interact with the tabs before those have largely (or completely?) loaded - for instance I can't use mouse gestures in a tab that's currently loading or interact with the vimperator replacement (Vim Vixen). Is that inherent to the new system with the extension system having lower priority than the page rendering or is it just those specific extensions I use?

Another thing that would be nice to fix is extensions (at least those that I have tested) seemingly not working in Firefox-internal pages like about:addons.

Post reply on HN